Description of problem: When I boot Fedora 12 Beta, at the login screen the keyboard and mouse don't work. If I pull out the dongle and re-insert it they work. + Keyboard and Mouse work fine for previous Fedora releases. + Also doesn't work at RunLevel 3, console. Version-Release number of selected component (if applicable): How reproducible: Every Time Steps to Reproduce: 1. Boot Fedora 12 Beta. 2. 3. Actual results: Expected results: Additional info: Keyboard and mouse are Logitech diNova. Bluetooth Keyboard and Mouse. However I'm not sure they are really working in Bluetooth "mode" just as standard USB devices - the dongle does not allow me to connect to other Bluetooth devices, and neither keyboard or mouse show up in Bluetooth configuration tool. When I re-plug in the USB dongle I get the following the messages file ... ov 2 17:06:12 trantor kernel: usb 2-2.1.2: new full speed USB device using ehci_hcd and address 15 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2: New USB device found, idVendor=046d, idProduct=0b02 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2: Product: Logitech BT Mini-Receiver Nov 2 17:06:12 trantor kernel: usb 2-2.1.2: Manufacturer: Logitech Nov 2 17:06:12 trantor kernel: usb 2-2.1.2: configuration #1 chosen from 1 choice Nov 2 17:06:12 trantor kernel: hub 2-2.1.2:1.0: USB hub found Nov 2 17:06:12 trantor kernel: hub 2-2.1.2:1.0: 3 ports detected Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: new full speed USB device using ehci_hcd and address 16 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: New USB device found, idVendor=046d, idProduct=c70b Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: Product: Logitech BT Mini-Receiver Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: Manufacturer: Logitech Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: SerialNumber: 000761446B1F Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.2: configuration #1 chosen from 1 choice Nov 2 17:06:12 trantor kernel: input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.2/2-2.1.2.2/2-2.1.2.2:1.0/input/input9 Nov 2 17:06:12 trantor kernel: generic-usb 0003:046D:C70B.0007: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.2.2/input0 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: new full speed USB device using ehci_hcd and address 17 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: New USB device found, idVendor=046d, idProduct=c70c Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: Product: Logitech BT Mini-Receiver Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: Manufacturer: Logitech Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: SerialNumber: 000761446B1F Nov 2 17:06:12 trantor kernel: usb 2-2.1.2.3: configuration #1 chosen from 1 choice Nov 2 17:06:12 trantor kernel: input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.2/2-2.1.2.3/2-2.1.2.3:1.0/input/input10 Nov 2 17:06:12 trantor kernel: generic-usb 0003:046D:C70C.0008: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.2.3/input0 -- I guess this could be connected with the delayed bluetooth startup ? -- Worked ok through installation.
(In reply to comment #1) > I'm not sure they are really working in Bluetooth "mode" just as standard USB > devices - the dongle does not allow me to connect to other Bluetooth devices, > and neither keyboard or mouse show up in Bluetooth configuration tool. > You mean even after unplugging and replugging they don't show up as bluetooth devices?
Correct - if I select Bluetooth preferences the mouse and keyboard do not appear as a bluetooth device. The dongle doesn't even get detected as a bluetooth receiver as far as I know. I think this changed sometime around F8, in F8 I had use hciattch(?) to connet the devices. Since then they have just worked although I couldn't use the dongle to connect other bluetooth devices. As I understand it the logitech bluetooth dongle can "emulate" a normal USB keyboard/mouse, so it works to access the BIOS, boot loader etc. I assume that is what it doing.
Some more data points. + The dongle is not recognised as a bluetooth device hcitool dev - doesn't show it or the bluetooth options off the menu. + I can use the keyboard in grub. + I can't use the keyboard at run level 3, without reinserting the dongle. I've gone through the output of dmesg and pulled out the relevant stuff ( I think ). Looks like some errors about resetting the device. usb 2-2.1.3: New USB device found, idVendor=046d, idProduct=0b02 usb 2-2.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2.1.3: Product: Logitech BT Mini-Receiver usb 2-2.1.3: Manufacturer: Logitech usb 2-2.1.3: configuration #1 chosen from 1 choice hub 2-2.1.3:1.0: USB hub found hub 2-2.1.3:1.0: 3 ports detected usb 2-2.1.3.2: new full speed USB device using ehci_hcd and address 6 usb 2-2.1.3.2: New USB device found, idVendor=046d, idProduct=c70b usb 2-2.1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-2.1.3.2: Product: Logitech BT Mini-Receiver usb 2-2.1.3.2: Manufacturer: Logitech usb 2-2.1.3.2: SerialNumber: 000761446B1F usb 2-2.1.3.2: configuration #1 chosen from 1 choice input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.3/2-2.1.3.2/2-2.1.3.2:1.0/input/input3 generic-usb 0003:046D:C70B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.3.2/input0 usb 2-2.1.3.3: new full speed USB device using ehci_hcd and address 7 usb 2-2.1.3.3: New USB device found, idVendor=046d, idProduct=c70c usb 2-2.1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-2.1.3.3: Product: Logitech BT Mini-Receiver usb 2-2.1.3.3: Manufacturer: Logitech usb 2-2.1.3.3: SerialNumber: 000761446B1F usb 2-2.1.3.3: configuration #1 chosen from 1 choice input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.3/2-2.1.3.3/2-2.1.3.3:1.0/input/input4 generic-usb 0003:046D:C70C.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.3.3/input0 <snip> usb 2-2.1.3.1: New USB device found, idVendor=046d, idProduct=c709 usb 2-2.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-2.1.3.1: Product: Logitech BT Mini-Receiver usb 2-2.1.3.1: Manufacturer: Logitech usb 2-2.1.3.1: SerialNumber: 000761446B1F usb 2-2.1.3.1: configuration #1 chosen from 1 choice <snip> drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 usb 2-2.1: clear tt 3 (9082) error -71 drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.2/input0, status -32 usb 2-2.1.3: USB disconnect, address 5 usb 2-2.1.3.1: USB disconnect, address 8 btusb_intr_complete: hci0 urb ffff880218d93a80 failed to resubmit (19) btusb_bulk_complete: hci0 urb ffff880218d93900 failed to resubmit (19) btusb_bulk_complete: hci0 urb ffff880218d93480 failed to resubmit (19) btusb_send_frame: hci0 urb ffff88021b931600 submission failed ----> I think this where I pull out and re-insert the dongle. usb 2-2.1.3.2: USB disconnect, address 6 usb 2-2.1.3.3: USB disconnect, address 7 usb 2-2.1.3: new full speed USB device using ehci_hcd and address 9 usb 2-2.1.3: New USB device found, idVendor=046d, idProduct=0b02 usb 2-2.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2.1.3: Product: Logitech BT Mini-Receiver usb 2-2.1.3: Manufacturer: Logitech usb 2-2.1.3: configuration #1 chosen from 1 choice hub 2-2.1.3:1.0: USB hub found hub 2-2.1.3:1.0: 3 ports detected usb 2-2.1.3.2: new full speed USB device using ehci_hcd and address 10 usb 2-2.1.3.2: New USB device found, idVendor=046d, idProduct=c70b usb 2-2.1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-2.1.3.2: Product: Logitech BT Mini-Receiver usb 2-2.1.3.2: Manufacturer: Logitech usb 2-2.1.3.2: SerialNumber: 000761446B1F usb 2-2.1.3.2: configuration #1 chosen from 1 choice input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.3/2-2.1.3.2/2-2.1.3.2:1.0/input/input5 generic-usb 0003:046D:C70B.0003: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.3.2/input0 usb 2-2.1.3.3: new full speed USB device using ehci_hcd and address 11 usb 2-2.1.3.3: New USB device found, idVendor=046d, idProduct=c70c usb 2-2.1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-2.1.3.3: Product: Logitech BT Mini-Receiver usb 2-2.1.3.3: Manufacturer: Logitech usb 2-2.1.3.3: SerialNumber: 000761446B1F usb 2-2.1.3.3: configuration #1 chosen from 1 choice input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.3/2-2.1.3.3/2-2.1.3.3:1.0/input/input6 generic-usb 0003:046D:C70C.0004: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.3.3/input0
drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1d.7-2.1.3.3/input0, status -32 From Documentation/usb/error-codes.txt: -EPIPE Specified endpoint is stalled. For non-control endpoints, reset this status with usb_clear_halt().
FOR REFERENCE, FEDORA 11 no such errors .... +[trantor] ~ $dmesg | egrep -i "hid|logitech" usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver usb 2-2.1.3: Product: Logitech BT Mini-Receiver usb 2-2.1.3: Manufacturer: Logitech usb 2-2.1.3.2: Product: Logitech BT Mini-Receiver usb 2-2.1.3.2: Manufacturer: Logitech input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.3/2-2.1.3.2/2-2.1.3.2:1.0/input/input3 generic-usb 0003:046D:C70B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.3.2/input0 usb 2-2.1.3.3: Product: Logitech BT Mini-Receiver usb 2-2.1.3.3: Manufacturer: Logitech input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2.1/2-2.1.3/2-2.1.3.3/2-2.1.3.3:1.0/input/input4 generic-usb 0003:046D:C70C.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-2.1.3.3/input0
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The problem seem to have gone in F12 Final - so closing.