© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I can confirm the problem. I also have a Logitech MX 5000.
I think the problem is a duplicate of https:/
There are two possible situations:
1. Your mouse&keyboard work.
This means they are in legacy HID mode. That means Linux thinks they are plain old USB devices, not bluetooth.
If you have a mobile phone and let it scan, it won't find your bluetooth dongle.
2. Your mouse&keyboard don't work.
This means you are now in HCI mode, which means bluetooth works.
Your mobile phone will be able to find your bluetooth dongle, but you won't be able to enter the passcode because keyboard&mouse don't work.
You can go from HID to HCI by typing the following command:
hid2hci
(quite unexpected!)
You can go from HCI to HID by unplugging your bluetooth dongle for a second. Or by typing hid2hci --hid, if you had a working keyboard.
When you boot, you start in HID mode. BIOS doesn't know about Bluetooth. That is why you can use the keyboard in Grub.
When your gdm or kdm or xdm comes up, you have a few seconds when the keyboard still works. This is just enough for me to type my username, if I'm fast enough.
After a few seconds, "something in the background" (I don't know what) switches your bluetooth from HID to HCI, and the keyboard stops working.
To get it working again, unplug the dongle (you are now back in HID mode).
This showstopper is almost a year old now, and still unconfirmed. Someone in one of the duplicate bug reports suggested sponsoring one of the bluetooth devs: donate money via paypal so they can buy a bluetooth rig and fix this bug.
The problem could be related to the Broadcomm chipset in the Bluetooth dongle.