Usb keyboard dies when gdm starts

[Martin Kristensen]

When I boot Ubuntu Dapper Drake Flight 4 the keyboard dies. From the time the drivers are loaded during boot, until I enter gdm the keyboard works and I am able to swith Num Lock and Caps Lock on and off, when gem starts I can no longer do this, and if num lock is on is switched off. I am able to log in by unplugging the keyboard and plugging it back in. When I then log in I am, however, unable to switch between keyboard layouts. (GB and DK).

I have looked in messages, Xorg.0.log and every other file in /var/log without finding anything that resembles a relevant error message.

My machine is an AMD 3500+ running the AMD64 version of flight 4. The keyboard is a logitech cordless.

[Sebastien Bacher (seb128)]

Is that an USB keyboard? Does syslog or messages or dmesg have anything about that? Does that happen if you try an another login manager than gdm or use startx?

[Martin Kristensen (martin-miknet)]

It is a USB keyboard. Syslog, messages, syslog and dmesg report nothing out of the ordinary. However when I disconnect and reconnect, dmesg only reports the reconnection. The problem is also consistant, on both an upgraded flight 3 and flight 4.

[Daniel Holbach (dholbach)]

This might be related to https://bugs.freedesktop.org/show_bug.cgi?id=3451 - maybe you could try to boot in recovery mode and use the settings mentioned in the bug?

[Martin Kristensen (martin-miknet)]

I have had to reinstall 5.10 since unplugging the keyboard at every boot, was getting on my nerves. However the problem persists when using the Dapper Flight 5 live cd. I have also discovered that the problem is not gdm specifik, but consistent across xorg.

Daniel: I have not been able to test your suggestion, however I am not convinced the two issues are related. My problem is not that certain key don't work. It is that not input is registered, it seems as if starting X somehow terminates my keyboard driver, which is then reloaded when I unplug and plug in the keyboard. If you can come up with any test I can carry out using the live CD, please let me know.

[Martin Kristensen (martin-miknet)]

Same problem in KUbuntu 6.04 flight 5. Also dmesg message related to usb from boot of Ubuntu 6.04 flight 5 is inserted below.

ubuntu@ubuntu:~$ dmesg |grep -i usb
[ 34.243333] PCI0 UAR2 UAR1 AC97 USB1 USB2 USB3 USB4 EHCI PWRB SLPB
[ 39.242558] usbcore: registered new driver usbfs
[ 39.243132] usbcore: registered new driver hub
[ 39.245164] USB Universal Host Controller Interface driver v2.3
[ 39.246565] uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
[ 39.247862] hub 1-0:1.0: USB hub found
[ 39.348003] uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
[ 39.348081] hub 2-0:1.0: USB hub found
[ 39.449668] uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
[ 39.449889] hub 3-0:1.0: USB hub found
[ 39.551435] uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
[ 39.551643] hub 4-0:1.0: USB hub found
[ 39.655990] ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
[ 39.656005] ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 39.656086] hub 5-0:1.0: USB hub found
[ 40.694100] usb 4-1: new full speed USB device using uhci_hcd and address 2
[ 40.822920] hub 4-1:1.0: USB hub found
[ 41.137278] usb 4-2: new low speed USB device using uhci_hcd and address 3
[ 41.478576] usb 4-1.1: new low speed USB device using uhci_hcd and address 4
[ 41.616580] usbcore: registered new driver hiddev
[ 41.648357] input: Logitech USB Receiver as /class/input/input0
[ 41.648436] input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:10.3-2
[ 41.675277] input: Logitech USB Receiver as /class/input/input1
[ 41.675287] input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:10.3-1.1
[ 41.736164] input: Logitech USB Receiver as /class/input/input2
[ 41.736320] input,hiddev96: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:10.3-1.1
[ 41.736329] usbcore: registered new driver usbhid
[ 41.736331] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[ 145.098113] usb 4-1.2: new full speed USB device using uhci_hcd and address 5[ 146.426965] Bluetooth: HCI USB driver ver 2.9
[ 146.462265] usbcore: registered new driver hci_usb
[ 186.338676] usb 4-1: USB disconnect, address 2
[ 186.338679] usb 4-1.1: USB disconnect, address 4
[ 186.338981] usb 4-1.2: USB disconnect, address 5
[ 187.339537] usb 4-1: new full speed USB device using uhci_hcd and address 6
[ 187.399315] hub 4-1:1.0: USB hub found
[ 187.528578] usb 4-1.1: new low speed USB device using uhci_hcd and address 7
[ 187.602554] input: Logitech USB Receiver as /class/input/input3
[ 187.602571] input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:10.3-1.1
[ 187.630698] input: Logitech USB Receiver as /class/input/input4
[ 187.630742] input,hiddev96: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:10.3-1.1

[TrinitronX (trinitronx-comcast)]

I have had the same problem with my keyboard, however it is not a USB keyboard. Mine is a standard 104 key generic Dell brand keyboard, plugged in to the PS/2 port on my desktop PC.
I've noticed this problem in gdm, kdm, and even in the recovery terminal... the only link I managed to find between the behavior was that I've only noticed it happening in kernel 2.6.15-19. I'm using the i686 version, installed from Flight 6 with recent updates. The problem only started after the update to the kernel image.

I can confirm the num lock behaviour, it acts as an indicator of sorts to whether or not my keyboard will be locked up or not. If num lock is on when gdm/kdm/recovery console starts... then the keyboard doesn't work, if the num lock light is off... then it is responsive.
Being a PS/2 keyboard, sadly I am not able to simply fix the problem by unplugging/replugging it in. The problem seems random, and usually a reboot (or two,three... etc..) will eventually ge the keyboard to work again (at least until the next reboot... sometimes).

So far, I havent' had this problem with kernel image 2.6.15-18-i686/i386, only with the -19 versions.

[TrinitronX (trinitronx-comcast)]

I just did another fresh install from the Flight 6 install disc, and this problem still ocurrs.

It seems it is only in the 2.6.15-19-686 kernel and restricted modules.

[Martin Kristensen (martin-miknet)]

I solved my problem. At least half of it. It seems the reason my keyboard dies is because the bluetooth subsystem takes over control of the reciever, which handles the mouse and keyboard. However the keyboard does not communicate using bluetooth. I disabled bluetooth and I can now use my keyboard, I will try to see if I can configure it as a bluetooth keyboard and write my solution here, if possible.

Thanks for all the help.

[TrinitronX (trinitronx-comcast)]

This problem is still happening in the new kernel update 2.6.15-20-686, although it doesn't seem to be happening as much. I've noticed that the moment the num lock light turns off (if the keyboard is not going to lock up), is during the usplash sequence, when it is loading the kernel modules.

I'm not sure if the lockup occurs then, it just appears that it's recognizing the keyboard at that point.

[Robin Haswell (rob-digital-crocus)]

I can confirm this problem is still exhbiting with "Linux serpentine 2.6.15-23-k7 #1 SMP PREEMPT Tue May 23 14:20:54 UTC 2006 i686 GNU/Linux". I have a Logitech Bluetooth Desktop pack, so my keyboard and mouse (MX900) both run off bluetooth.

Some new information: The problem affects the bluetooth mouse as well. Also the mouse will move for a very short time after gdm/X is loaded. This problem could be related to the bluetooth subsystem, however I wasn't aware that Linux was loading the bluetooth subsystem. Even with bluez installed Linux can't recognise the receiver, which does work as a dongle in Windows. The mouse and keyboard run fine without bluetooth support in the OS, as exhibited by keyboard support in the BIOS.

I am using a constantly updated Dapper Flight 6.

[James Cuzella (trinitronx)]

I have just managed to get my PS/2 keyboard working by unplugging it and plugging it into my PC's other PS/2 port (labelled for use with a mouse)

Please see bug #48877 for my full post, PC specs (if needed), and current xorg.conf file.
Here: https://launchpad.net/distros/ubuntu/+bug/48877

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[JamesRichardson (james-time4tea)]

linux-2.6.27

Still present for me..... open two years... :-(

[ 5.201983] ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 5.204378] ata3.00: configured for UDMA/133
[ 5.314569] usb 6-1.3: configuration #1 chosen from 1 choice
[ 5.321525] usbcore: registered new interface driver hiddev
[ 5.326565] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1.2/6-1.2:1.0/input/input1
[ 5.332547] input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.1-1.2
[ 5.341617] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1.3/6-1.3:1.0/input/input2
[ 5.341844] input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.1-1.3
[ 5.341856] usbcore: registered new interface driver usbhid
[ 5.341858] usbhid: v2.6:USB HID core driver
[ 6.108014] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 6.110502] ata4.00: ATAPI: SONY DVD RW DRU-190S, 1.63, max UDMA/100
[ 6.113509] ata4.00: configured for UDMA/100
[ 6.448013] ata5: SATA link down (SStatus 0 SControl 300)
[ 6.784012] ata6: SATA link down (SStatus 0 SControl 300)

(x boots)

[ 26.948364] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 27.033894] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[ 27.033898] apm: disabled - APM is not SMP safe.
[ 27.168357] ppdev: user-space parallel port driver
[ 29.728361] Bluetooth: Core ver 2.13
[ 29.729245] NET: Registered protocol family 31
[ 29.729248] Bluetooth: HCI device and connection manager initialized
[ 29.729252] Bluetooth: HCI socket layer initialized
[ 29.743991] Bluetooth: L2CAP ver 2.11
[ 29.743996] Bluetooth: L2CAP socket layer initialized
[ 29.750741] Bluetooth: SCO (Voice Link) ver 0.6
[ 29.750746] Bluetooth: SCO socket layer initialized
[ 29.795495] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 29.795499] Bluetooth: BNEP filters: protocol multicast
[ 29.815289] Bridge firewalling registered
[ 29.815498] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 30.049356] Bluetooth: RFCOMM socket layer initialized
[ 30.050033] Bluetooth: RFCOMM TTY layer initialized
[ 30.050037] Bluetooth: RFCOMM ver 1.10
[ 30.361432] usb 6-1.1: new full speed USB device using uhci_hcd and address 5
[ 30.495518] usb 6-1.1: configuration #1 chosen from 1 choice
[ 30.592202] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 30.592803] usbcore: registered new interface driver btusb
[ 35.956008] eth0: no IPv6 routers present

(unplugged)

[ 182.680040] usb 6-1: USB disconnect, address 2
[ 182.680045] usb 6-1.1: USB disconnect, address 5
[ 182.681015] btusb_intr_complete: hci0 urb f5db4380 failed to resubmit (19)
[ 182.681262] btusb_send_frame: hci0 urb f5530780 submission failed
[ 182.933138] usb 6-1.2: USB disconnect, address 3
[ 182.948915] usb 6-1.3: USB disconnect, address 4
[ 186.136013] usb 6-1: new full speed USB device using uhci_hcd and address 6
[ 186.373117] usb 6-1: configuration #1 chosen from 1 choice
[ 186.376072] hub 6-1:1.0: USB hub found
[ 1...

[penalvch (penalvch)]

Martin Kristensen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]