Red Hat Bugzilla – Bug 117507
After making a custom kernel usb keyboard and mouse fail
Last modified: 2007-11-30 17:07:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922
Description of problem:
After installing RedHat Enterprise Linux Version 3 Workstation with
kernel build extensions, use the manual's custom kernel build
procedure. After booting the custom kernel, both the USB keyboard and
USB mouse fail to function.
Version-Release number of selected component (if applicable):
kernel-2.4.21-9.0.1.EL and kernel-2.4.21-9.1.EL
Steps to Reproduce:
1.Install RedHat Enterprise WS Version 3 with kernel source
2.in root, cd /usr/src/linux-2.4
4.cp configs/kernel-2.4.21-i686.config .config
13.boot new kernel
Actual Results: USB keyboard and USB mouse stop working.
Expected Results: USB keyboard and USB mouse continue to function
The appropiate portion of the lsmod output is as follows:
keybdev 2976 0 (unused)
mousedev 5524 0 (unused)
input 5920 0 [keybdev mousedev]
hid 11864 0 (unused)
ehci-hcd 27880 0 (unused)
usb-uhci 26412 0 (unused)
usbcore 86336 1 [hid ehci-hcd usb-uhci]
An alternate procedure circumvents problem:
1.su to root and cd /usr/src/linux-2.4
3.cp /boot/config-2.4.21-9.0.1.EL .config
11.boot new kernel
This is not an alternative procedure, it's the main procedure.
"make oldconfig" is the only thing which works. You do not need
to run it twice.
If you really need menuconfig, do it, but then run oldconfig
to clean up the pieces scattered by menuconfig. Ditto xconfig.
Oh wait, I remember now.
There is actually a page a www.redhat.com, which used to recommend
"make xconfig", which, of course, inundated me with bugs...
I complained to Tammy, and she was all ready to throw that
garbage out, when a well meaning support person claimed that
"make oldconfig" was too unfriendly, blah blah. In the end,
a "compromise" was reached, where the page was changed to
recommend menuconfig. It is a little less broken, so actually
this is the first bug about this since then.
So, I guess, officially, menuconfig is the primary procedure,
at least according to the website.
Here's the page:
Dunno what to do about it. To fix the menuconfig is beyond human
capabilities. To fix the manual is to admit defeat :-)
I think I'll re-close with WONTFIX rather than NOTABUG,
it's more honest that way.