Quantcast
Channel: openSUSE Forums
Viewing all articles
Browse latest Browse all 40713

No wireless keyboard during boot, after update to kernel 3.11

$
0
0
I updated to kernel-default-3.11 today. After the update, I am unable to use my Logitech wireless keyboard, but only when prompted for my pass-code to unlock my encrypted system volume.

The keyboard works during POST, and works at the grub menu (I use legacy grub if it makes a difference). When prompted for my crypt-setup pass-code, the wireless keyboard does not work and I am forced to plug in an old PS2 keyboard, just for the pass-code. Once the drive is unlocked, the keyboard remains dead until later in the boot process. When KDM starts, the keyboard works as it should.

I am not sure if this is a problem with the new kernel, a problem with mkinitrd, or maybe a problem with cryptsetup-mkinitrd.

I'll post the outputs of the commands I have run so far:
Code:

  ronnie@Opto:~> lsusb
 Bus 001 Device 003: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port Hub
 Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 004: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port Hub
 Bus 001 Device 005: ID 06a3:0460 Saitek PLC ST290 Pro Flight Stick
 Bus 001 Device 006: ID 054c:002c Sony Corp. USB Floppy Disk Drive
 Bus 001 Device 007: ID 046d:c242 Logitech, Inc. 
 

 ronnie@Opto:~> lsmod | grep usb
 usb_storage            62063  0 
 usbhid                    53007  0 
 usbcore                241252  7 xpad,usb_storage,ohci_pci,ohci_hcd,ehci_pci,ehci_hcd,usbhid
 usb_common          13057  1 usbcore
 

 

 ronnie@Opto:~> lsmod | grep logitech
 hid_logitech_dj        18604  0

In the output of lsmod, it apperas that usbhid and hid_logitech_dj are loaded, but not being used, even though the wireless keyboard works correctly.
I use an older motherboard that is not USB 3 capable. It has worked perfectly until the kernel upgrade today, along with re-installing the ATI proprietary driver after the kernel upgrade.

Since I am still able to get into my system, I'll keep this kernel rather than downgrading. If anyone has any troubleshooting suggestions, I'll be able to comply.

Viewing all articles
Browse latest Browse all 40713

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>