Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #72427 > unrolled thread

Bug#961401: Sequence of module loading is relevant

Started byMarkus Hiereth <translation@hiereth.de>
First post2021-07-22 19:10 +0200
Last post2021-07-22 19:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#961401: Sequence of module loading is relevant Markus Hiereth <translation@hiereth.de> - 2021-07-22 19:10 +0200

#72427 — Bug#961401: Sequence of module loading is relevant

FromMarkus Hiereth <translation@hiereth.de>
Date2021-07-22 19:10 +0200
SubjectBug#961401: Sequence of module loading is relevant
Message-ID<CDKmR-55K-1@gated-at.bofh.it>
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

[toc] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web