gnac wrote:For some reason my wireless logitech headset causes X to crash. I removed the usb dongle and I was able to restart X. Insterting the dongle caused an immediate crash.
Apparently X thinks its an input device, which maybe it is since it has controls, but either way X no longer likes it.
Perhaps you have a similar device that is causing a crash?
- Code: Select all
[ 2650.464] (II) XINPUT: Adding extended input device "Logitech Logitech Wireless Headset" (type: KEYBOARD, id 11)
[ 2650.464] (**) Option "xkb_rules" "evdev"
[ 2650.464] (**) Option "xkb_model" "evdev"
[ 2650.464] (**) Option "xkb_layout" "us"
[ 2650.464] (II) evdev: Logitech Logitech Wireless Headset: initialized for absolute axes.
[ 2650.465]
***crash***
I had what appears to be a similar situation a few years ago. In my case I was trying to get a DVB-T USB stick (Afa Technologies Inc. AF9035A USB Device) working. Notice in the output from dmesg posted below that the usbhid driver incorrectly thought that my DVB-T stick was a KEYBOARD (just like in your case):
- Code: Select all
[ 824.549123] generic-usb 0003:15A4:1001.0001: input,hidraw0: USB HID v1.01 Keyboard [Afa Technologies Inc. AF9035A USB Device] on usb-0000:00:1d.7-4/input1
It was necessary to stop the usbhid driver from doing this, because the DVB-T stick certainly isn't a keyboard.
Now, if the usbhid driver is a kernel module (CONFIG_USB_HID=m in the kernel config) then the way to tell the usbhid driver to ignore this specific device, as it has its own driver, would be to pass an option to the usbhid driver by putting the following line in the file /etc/modprobe.d/usbhid.conf
- Code: Select all
options usbhid quirks=0x15a4:0x1001:0x0004
where 0x15a4 is the Vendor ID and 0x1001 is the Product ID, both obtained by looking at the output of either the dmesg or lsusb commands, and the 0x0004 flag is HID_QUIRK_IGNORE, which tells the usbhid driver to ignore the device.
However, in the case of my kernel the usbhid driver was not a module, it was built into the kernel (CONFIG_USB_HID=y in the kernel config), so the way to tell the usbhid driver to ignore this specific device, as it has its own driver, would be to pass the option to the usbhid as a boot parameter, by editing /boot/grub/grub.cfg and adding the following boot parameter to the end of the kernel boot line:
- Code: Select all
usbhid.quirks=0x15a4:0x1001:0x0004
Then when I rebooted I saw the following for the DVB-T stick in the dmesg output:
- Code: Select all
[ 196.322403] usb 1-1.4: new high speed USB device using ehci_hcd and address 13
[ 196.414896] usb 1-1.4: New USB device found, idVendor=15a4, idProduct=1001
[ 196.414903] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 196.414909] usb 1-1.4: Product: AF9035A USB Device
[ 196.414913] usb 1-1.4: Manufacturer: Afa Technologies Inc.
[ 196.414917] usb 1-1.4: SerialNumber: AF0102020700001
[ 196.415183] usb 1-1.4: configuration #1 chosen from 1 choice
Compare the new dmesg output above with the old dmesg output at the top of this post. You can see that the usbhid driver now ignores the DVB-T stick and it is no longer listed as a keyboard.
So it could be that you need to do something along similar lines, obviously changing the 0x15a4:0x1001 to the appropriate vendor ID and product ID for your USB dongle.
