Bug 120832 - Keyboard unusable without CONFIG_USB_UHCI_HCD=y
Summary: Keyboard unusable without CONFIG_USB_UHCI_HCD=y
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 2
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact:
URL: http://www.muru.com/linux/amd64/
: 120833 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-04-14 11:48 UTC by Chris Kloiber
Modified: 2015-01-04 22:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-16 05:04:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Chris Kloiber 2004-04-14 11:48:04 UTC
Description of problem:

My laptop (eMachines M6807) is buggy in many ways, but it seems the
showstopper currently is that I am unable to use the keyboard until
usb-uhci is loaded. I have built a custom kernel using the suggestions
found at http://www.muru.com/linux/amd64/ including patches for acpi
and apic to make other things like pcmcia and ip-apic work right, as
well as changing the configuration option:


which will allow my keyboard to be used. I was thinking that since we
have given up on trying to fit on a boot floppy that there would be
less resistance to building the kernel with low-level usb drivers
included so that things like keyboards and mice work as they should
even in runlevel 1, or emergency mode.

As far as the patches go, they apply cleanly to kernel-2.6.5 from
kernel.org and may not be acceptable as written, but I hope you can
make a patch for our trees that can fix the same problems these do for
me. Thanks.

Comment 1 Arjan van de Ven 2004-04-14 11:53:22 UTC
*** Bug 120833 has been marked as a duplicate of this bug. ***

Comment 2 Pete Zaitcev 2004-04-20 21:45:08 UTC
This was mentioned on the internal kernel list and I suggested
putting modules into initrd. But this may be too hard for FC2.
Arjan/DaveJ have to bunch together and decide what to do.

Comment 3 Pete Zaitcev 2004-04-21 01:07:54 UTC
Don't forget about systems with OHCI. If UHCI goes in, so should OHCI.
EHCI always has OHCI compatibility mode, so perhaps it can be left out.

Comment 4 Chris Kloiber 2004-04-21 21:04:04 UTC
Um, This machine is an x86_64, not a Mac (ppc). 

Do the Mac's also need this compiled in, or did we get the wrong
blocker bug number?

Comment 5 Alan Cox 2004-05-02 23:32:00 UTC
Given how few modern machines lack OHCI/UHCI maybe it should be
compiled in on all of them ?

Comment 6 Marty Shannon 2004-05-22 19:50:02 UTC
Yes, the blocker bug number is wrong.  This is an x86_64 machine.

Comment 7 Chris Kloiber 2004-05-23 00:27:40 UTC
I tried putting these modules into the initrd manually, the kernel
still complains very loudly before the initrd is loaded, but it does
eventually work. It's much neater logging wise to have them already
compiled in however.

Comment 8 Bastien Nocera 2004-06-10 09:47:19 UTC
The blocker bug is wrong, Macs use OHCI USB controllers.

Comment 9 Marty Shannon 2004-08-19 16:07:19 UTC
http://www.rmecc.com/~v2/em/ is a wonderful resource -- it solves this
problem nicely.  The bottom line is that the BIOS is quite borked as
shipped by eMachines.  Updating the BIOS permits FC3T1 (current as I
write this) to install on the eMachines M6805 without any kernel
command line options.  The install is in progress as I type, so I'll
update this with any other info once it's done & I get a chance to see
what hath been wrought.

Comment 10 Chris Kloiber 2004-08-19 16:43:08 UTC
I know about that site, see mine (which points to that one):

Comment 11 Chris Kloiber 2004-08-19 16:45:05 UTC
I should add that the bios upgrade from that page is UNOFFICIAL, and
not supported by eMachines. If you choose to do that upgrade you are
almost certainly voiding any warranties you may otherwise have
recourse under.

Comment 12 Dave Jones 2004-12-08 06:04:10 UTC
any better with teh current updates ?

Comment 13 Dave Jones 2005-04-16 05:04:12 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.

Note You need to log in before you can comment on or make changes to this bug.