Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.hardware > #3610
| From | Theo <theom+news@chiark.greenend.org.uk> |
|---|---|
| Newsgroups | comp.os.linux.hardware |
| Subject | Re: Intriguing issue |
| Date | 2023-01-13 12:51 +0000 |
| Organization | University of Cambridge, England |
| Message-ID | <SXl*4tf8y@news.chiark.greenend.org.uk> (permalink) |
| References | <tphso5$8cv$1@gioia.aioe.org> <Qgq*2287y@news.chiark.greenend.org.uk> <op.1ymrmmlca3w0dxdave@hodgins.homeip.net> |
David W. Hodgins <dwhodgins@nomail.afraid.org> wrote: > From > https://access.redhat.com/solutions/194273 > "This error indicates that USB 2.0 may not function on your system, or may function only at USB 1.1 speeds." Good to see Redhat are following Microsoft in non-answer answers. EHCI is the USB 2 host controller standard, so it's a problem with USB 2. But it doesn't say *why* it's a problem with USB2. All the message tells us is the USB stack got to a point where it got nothing sensible out of the device and was forced to reset it. It doesn't know why it got like that. Typically that means either a cabling problem or a device-side problem (much more likely than a 'replace the motherboard'). > See https://bbs.archlinux.org/viewtopic.php?id=89688 for disabling ehci-pci. Disabling EHCI will force USB 1.1 speeds (12Mbps), but for most devices that makes them useless. It is likely to be a hardware side issue, so things like: * Changing the cabling * Remove or change any hubs * Checking hub power supplies * Check device firmware is up to date would be worth trying. One other thing is to try a USB 3.0 hub, assuming the port supports that. That (should) change the offboard communication to use USB 3 signalling (and the XHCI host controller standard), which might not suffer an issue related to something USB 2 specific. If it doesn't work, at least it'll illuminate the problem. Theo
Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar
Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-09 20:17 +0000
Re: Intriguing issue Marco Moock <mo01@posteo.de> - 2023-01-09 21:36 +0100
Re: Intriguing issue mjb@signal11.invalid (Mike) - 2023-01-10 20:57 +0000
Re: Intriguing issue Theo <theom+news@chiark.greenend.org.uk> - 2023-01-11 22:23 +0000
Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-11 18:31 -0500
Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-12 19:21 +0000
Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-12 18:32 -0500
Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-13 15:03 +0000
Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-13 16:23 -0500
Re: Intriguing issue Theo <theom+news@chiark.greenend.org.uk> - 2023-01-13 12:51 +0000
Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-14 20:04 +0000
Re: Intriguing issue Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-01-15 09:17 +0000
Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-15 13:36 +0000
Re: Intriguing issue Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-01-16 07:14 +0000
Re: Intriguing issue Andrew <Doug@hyperspace.vogon.gov> - 2023-01-16 10:06 +0100
Re: Intriguing issue Eric Pozharski <whynot@pozharski.name> - 2023-01-16 15:00 +0000
Re: Intriguing issue John-Paul Stewart <jpstewart@personalprojects.net> - 2023-01-16 15:28 -0500
Re: Intriguing issue "Carlos E.R." <robin_listas@es.invalid> - 2023-01-16 20:47 +0100
Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-16 17:08 -0500
Re: Intriguing issue "Carlos E. R." <robin_listas@es.invalid> - 2024-11-08 13:57 +0100
csiph-web