Dear Maintainers, recently I found out that scanner communication is dependent on the sequence of loading of the two kernel modules ehci-hcd and uhci-hcd.
This sequence may, in normal day-by-day boot procedures, differ. Thus, the scanner communication fails sometimes; Or, to tell the truth, it fails more often than it works. As I managed to make the scanner work by unloading all kernel modules (rmmod) and afterward loading (modprobe) them manually, I made variations of the loading sequence. Meanwhile I found out, that the most simple way to establish communication with the scanner on the USB bus is to unload only ehce-hcd and uhci-hcd followed by loading first ehci-hcd and then uhci-hcd. Probably this helps you to analyse the problem and serves others who have similar problems with USB devices as a workaround. Best regards Markus Hiereth
