USB Keyboard not working after Kernel Upgrade [Solved]

[Rochambeau]

Yesterday i upgraded from Kernel 3.7 to 3.8 using the kernel switcher. I followed the wiki and finally rebootet.

My hard disk contains encrypted LVM so during reboot i needed to enter my passphrase, which wasn't possible. Keyboard input just isn't recognized. Even the Num Lock LED can't be switched.

So I reset my PC and bootet Sabayon with Kernel 3.7 and my keyboard worked again.

After that, i switched the repo from weekly to sabayon.orgr to see, if kernel updates are available, which were. I updated in the hope of getting my keyboard problem fixed. But after reboot, the same problem. My keyboard isn't responding with kernel 3.8.

Any suggestions?

[micia]

Hi,
if you used kernel-switcher to upgrade your kernel and you don't use any custom kernel configuration or any particular module to handle that keyboard (which should be the case for a simple USB keyboard), it should just work.
This sounds like a possible bug, could you report it to:
https://bugs.sabayon.org/

Including as much informations as possible?
For example a link to this topic, the procedure you used to upgrade, which packages were pulled by kernel-switcher, keyboard model, lsusb output, the fact you have an encrypted LVM volume and anything you find important, the more the better

[lxnay]

I believe that we're hit by an upstream kernel bug, an updated kernel is coming

[Rochambeau]

Could the fix be in the Linux Sabayon 3.8.3~0 package currently in Limbo or is it some future update?

If yes to the first part, i would volunteer to try and test the update.

[lxnay]

It's in sabayonlinux.org

[Rochambeau]

Ok, i updated the kernel but sadly my problem still exists.

lsusb and keyboard model (last line):

Code: Select all

[email protected] ~ $ lsusb
Bus 003 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 045e:0029 Microsoft Corp. IntelliMouse Optical
Bus 003 Device 004: ID 0bf8:100c Fujitsu Siemens Computers Keyboard FSC KBPC PX

Can I see somehow, which packages were pulled by kernel-switcher?

[lxnay]

Hi,
if you used kernel-switcher to upgrade your kernel and you don't use any custom kernel configuration or any particular module to handle that keyboard (which should be the case for a simple USB keyboard), it should just work.
This sounds like a possible bug, could you report it to:
https://bugs.sabayon.org/

Including as much informations as possible?
For example a link to this topic, the procedure you used to upgrade, which packages were pulled by kernel-switcher, keyboard model, lsusb output, the fact you have an encrypted LVM volume and anything you find important, the more the better

You forgot the most important thing, kernel logs. And if it's a kernel bug, don't waste your time filing a bug against us.

[Rochambeau]

I was looking through /var/log/messages but everytime i booted the 3.8 kernel, no log was written.

The boot process came to where i would type in my encryption password, but since my keyboard wasn't working i had to hard-reset my pc. -> no log.

Or am I looking at the wrong file?

[Matte88]

It's in sabayonlinux.org

Code: Select all

>>  +++ >>>  (4/4) sys-fs/udev-init-scripts-24
>>    ## Scompattamento: sys-fs:udev-init-scripts-24~0.tbz2
>>    ## Installazione pacchetto: sys-fs/udev-init-scripts-24
>>    ## [udev startup scripts for openrc]
>>    ## Aggiornamento database: sys-fs/udev-init-scripts-24
>>    ## Pulizia dei dati dell'applicazione precedente.
>>    ## Package phase: postinstall
 * 
 * You need to add udev-mount to the sysinit runlevel.
 * If you do not do this,
 * your system will not be able to boot!
 * Run this command:
 *      rc-update add udev-mount sysinit
>>    ## Pulizia: sys-fs/udev-init-scripts-24
>>  @@ Installazione completata.
>>  @@ Niente da rimuovere.
>>  @@ Nessun file di configurazione da aggiornare.
sabayon-asusx51l ~ # rc-update add udev-mount sysinit
 * service udev-mount added to runlevel sysinit

As you can see I manually added to the runlevel. What if a user don't read this message (and udev-mount isn't added to sysinit)?

[lxnay]

Try to update the kernel again, there is a new revision for the 3.8.3 kernel now.