From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network failed and weird error message
Date: Sat, 05 Oct 2013 11:04:44 +0200 [thread overview]
Message-ID: <524FD62C.80208@gmail.com> (raw)
In-Reply-To: <20131004215231.GA7163@waltdnes.org>
On 04/10/2013 23:52, Walter Dnes wrote:
> On Fri, Oct 04, 2013 at 09:35:33PM +0200, Alan McKinnon wrote
>
>> OHCI is a USB 1.1 implementation, I can't imagine why you have it
>> loaded. Surely you do not have USB 1 only hardware? USB2 deals with that
>> nicely. It is possible that you have a shit storm of USB weirdness going
>> on and this in locking up the desktop. Try disabling USB stuff you don't
>> need and see what gives.
>
> Do *NOT* remove lowspeed USB driver... unless you have a rescue USB
> stick boot handy. I tried that a few years ago and found that my USB
> keyboard and mouse stopped working. UHCI is used by Intel and VIA cpus,
> according to the help in "make menuconfig". AMD may be OHCI, I don't
> know.
>
It depends on the hardware on the motherboard, not on the CPU. Different
cpus for the most part have matching chipsets and the USB implementation
is in the chipset. USB1 had two implementations - uhci and ohci.
If you have hardware that is usb1 only, then you need those drivers.
These days, that is rare. These days, most motherboards have lots of
usb2 ports and when you plug in a keyboard, they run in usb1 mode but
still use the ehci driver to do it. I have a usb1 keyboard and mouse
plugged into this laptop right now:
$ lsmod | grep -i \[uo\]hci
firewire_ohci 31868 0
firewire_core 50381 1 firewire_ohci
$ lsmod | grep -i ehci_hcd
ehci_hcd 38782 1 ehci_pci
usbcore 152800 7
btusb,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid,xhci_hcd
No [uo]hci. And the only machine I have left with usb1-only hardware
dates from 2004, everything else uses only ehci and the lowspeed drivers
are not even built.
Dale changed his motherboard recently, presumably he knows what his
chipset offers
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2013-10-05 9:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 16:09 [gentoo-user] Network failed and weird error message Dale
2013-10-04 19:35 ` Alan McKinnon
2013-10-04 20:19 ` Dale
2013-10-05 8:54 ` Alan McKinnon
2013-10-05 10:06 ` Dale
2013-10-05 13:41 ` Bruce Hill
2013-10-06 18:36 ` Dale
2013-10-06 18:55 ` Alan McKinnon
2013-10-06 19:24 ` Dale
2013-10-06 19:52 ` Dale
2013-10-06 19:59 ` Neil Bothwick
2013-10-06 20:31 ` Dale
2013-10-06 20:55 ` Frank Steinmetzger
2013-10-07 0:11 ` Dale
2013-10-07 8:08 ` Neil Bothwick
2013-10-06 21:07 ` Alan McKinnon
2013-10-06 22:39 ` Neil Bothwick
2013-10-07 0:36 ` Dale
2013-10-06 21:42 ` Bruce Hill
2013-10-07 0:28 ` Dale
2013-10-07 8:06 ` Neil Bothwick
2013-10-07 14:17 ` Dale
2013-10-04 21:52 ` Walter Dnes
2013-10-05 9:04 ` Alan McKinnon [this message]
2013-10-05 10:13 ` Dale
2013-10-05 13:37 ` Alan McKinnon
2013-10-06 18:38 ` Dale
2013-10-13 12:26 ` Dale
2013-10-13 17:31 ` Mick
2013-10-13 21:49 ` Dale
2013-10-14 7:23 ` Mick
2013-10-14 15:18 ` Dale
2013-10-14 11:03 ` OT - RAM disks - WAS " Tanstaafl
2013-10-14 12:08 ` Dale
2013-10-15 5:53 ` Pandu Poluan
2013-10-07 2:29 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524FD62C.80208@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox