Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #72427
| From | Markus Hiereth <translation@hiereth.de> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#961401: Sequence of module loading is relevant |
| Date | 2021-07-22 19:10 +0200 |
| Message-ID | <CDKmR-55K-1@gated-at.bofh.it> (permalink) |
| References | <A9TI6-65H-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
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
Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread
Bug#961401: Sequence of module loading is relevant Markus Hiereth <translation@hiereth.de> - 2021-07-22 19:10 +0200
csiph-web