After uprading from kernel 2.6.11-gentoo-r11 to 2.6.12-gentoo-r6, my keyboard
does not work anymore during boot (after grub). Similar problems were reported
in the forums (http://forums.gentoo.org/viewtopic-t-367828.html). The solution
proposed there (setting "Legacy USB" to 'off' in bios) does not work for me.
Steps to Reproduce:
1. emerge gentoo-sources
2. copy .config from previous kernel
3. make && make modules_install; install new kernel in /boot; modify grub.conf
4. reboot with new kernel
keyboards does not work (also no SHIFT-PGUP during boot)
> 2. copy .config from previous kernel
> 3. make && make modules_install; install new kernel in /boot; modify grub.conf
Did you do make oldconfig?
It sounds like you're using a USB keyboard?
*Attach* your kernel .config, also you need to run 'make .oldconfig' (which is
not really that much recommended anyway between different kernel versions).
Created attachment 65590 [details]
.config file used for compilation of 2.6.12-gentoo-r6 kernel
A PS/2 keyboard, no USB keyboard.
Usually module 'atkb' is coldplugged; explicitly autoloading it did not help.
Was not aware of "make oldconfig", will try and report back.
Created attachment 65597 [details]
.config used for 2.6.12-gentoo-r6 kernel compilation after "make oldconfig"
This .config file was created by running "make oldconfig" on the .config file
for the 2.6.11-gentoo-r11 kernel. The previous one was a version modified with
The result is still the same: my PS/2 keyboard does not work after grub.
Requested info given, reopening bug (please tell me if this is not for me to judge).
Hmm, don't know what's wrong here. Compiling keyboard support as a module seems
like a bad idea to me in any case.
Yes, please compile keyboard support as built-in. See if that helps.
Do you have any USB keyboards which you could try? Do you have other machines on
your network that could SSH into your dead-keyboard-PC and obtain some logs?
When you say 'keyboard does not work', I assume you mean you can't type
anything. Do the caps lock / num lock lights operate as normal? Are any of them
on by default?
Compiling atkbd in the kernel and not as a module seems to resolve the problem.
What's the use of modules, if... this is probably a bug for the people at
No other keyboard/computer available to do other tests.
*LOCK keys don't work, leds keep status specified in bios.
Although building something as core as the keyboard driver as a module doesn't
make any sense, this does look like a minor bug.
Please see if you can reproduce it with vanilla-sources-2.6.13_rc6 (atkbd built
as a module, automatically loaded on bootup). If so, we can take the appropriate
steps towards getting it reported upstream.
I tried vanilla-sources-2.6.13_rc6: (make oldconfig, all defaults)
* built-in: keyboard works (expected);
* module, coldboot: keyboard does not work (atkbd loaded?);
* module, autoload: keyboard does not work (atkbd loaded according to bootup
When I talk about "keyboard does not work", everything is as described by my
Please advise on further action on my part if necessary.
If you remove the .config file, and then run "make menuconfig", are you able to
select atkbd as a module? I have tried to do this and it will not let me. I
think this is because atkbd is always on for PC-machines.
Yes, I can select atkbd as a module or compiled-in starting with a clean "make
menuconfig" (default is compiled-in).
Ah, thats an AMD64-ism. I got another AMD64 person to test this and it worked
fine as a module.
We now need to compare dmesg logs from the built-in and the modular kernel.
Please build atkbd into the kernel, boot 2.6.13-rc6, and save your dmesg, i.e.:
# dmesg > dmesg-atkbd-built-in.txt
Attach this file to this bug.
Then, compile atkbd as a module, add it to /etc/modules.autoload.d/kernel-2.6,
copy over the updated bzImage. You now need to reboot into the broken kernel and
run the same command without being able to type! If you are able to SSH in from
a networked machine and save the dmesg to a file in a similar manner as above,
then thats easiest. If not, you can set it to be automatically saved at boot as
Edit /etc/conf.d/local.start and add the following line at the end of the file:
dmesg > /tmp/dmesg-$(date +%s).txt
Now you can reboot into the broken 2.6.13-rc6 kernel. As soon as you see the
login prompt, reboot into a known working file, and remove that line from
You'll now have two files in /tmp with name dmesg-XXXX.txt (where XXXX is a big
number). Take the _first_ one and attach it here.
(In reply to comment #15)
> Ah, thats an AMD64-ism.
I wouldn't be so certain of that...
I have a Compaq DL 380 server which is running great:
Linux filestore 2.6.12-gentoo-r4 #1 SMP Wed Jul 27 18:32:55 PDT 2005 i686
Intel(R) Xeon(TM) CPU 3.20GHz GenuineIntel GNU/Linux
...except for the fact that the PS/2 keyboard does not do anything once grub
hands over control. I plugged in a USB keyboard into this machine and that
works fine (damn inconvenient). I figured it was an issue of exotic hardware.
But it happened again. I use a USB keyboard but I keep a PS2 (normal) keyboard
around for guests. I went to use that on a Dell Dimension and I realized that
the PS2 keyboard was dead there too:
Linux mindnoise 18.104.22.168 #2 SMP Sat Aug 20 11:21:01 PDT 2005 i686 Intel(R)
Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
This machine was recently changed to the 2005.1 profile.
So that's 2 non AMD64 machines that have this exact problem. I've tried
compiling all the keyboard things (that I could find) directly into the
kernel. Any help would be appreciated. If you would like more information from
me, let me know specifically what you're looking for.
Thanks and good luck with this one.
Chris: No, thats a different problem.
Erik's keyboard works when he compiles keyboard support into his kernel, but
does not work when it is an autoloaded module. Erik is on AMD64.
On x86 you simply cannot compile atkbd as a module. Thats what I meant by "its
an AMD64ism" - the fact that you can even try modular keyboard support... (I was
trying to reproduce the bug on my x86 system, but was unable to do this for this
Feel free to open a new bug for your problem.
Created attachment 66680 [details]
dmesg when booting with atkbd built in
Created attachment 66681 [details]
dmesg when booting with atkbd as module
Created attachment 66682 [details]
diff dmesg-atkbd-built-in.txt dmesg-atkbd-as-module
Ok, please file this bug against 2.6.13-rc6 at http://bugzilla.kernel.org and
post the new bug URL here.
Submitted bug at kernel.org: <http://bugzilla.kernel.org/show_bug.cgi?id=5158>.
I don't think that the following config is allowed:
# Hardware I/O ports
Did you edit your .config by hand?
Will track upstream bug, thanks Dmitry