[Bug 296567] [NEW] dinovo dongle isn't reset to HID mode on restart/shut down

[Matt Hanyok]

Public bug reported:

Hello,

This may be somewhat related to Bug #123920.

I have the DiNovo Media Desktop Laser (keyboard, media pad and MX1000
mouse) and I'm using the included BT adapter on Ubuntu 8.10 32-bit.

I had to log in using a USB mouse and keyboard. I was then able to get
the devices added via the "setup new device" option of the Bluetooth
preferences.

After a reboot I don't have keyboard functionality in the BIOS or GRUB.
If I shut down the system and disconnect/reconnect the dongle I can get
it to work in the BIOS but it still won't respond in GRUB.

My guess is that the HID2HCI_UNDO setting in /etc/default/bluetooth
isn't switching the dongle back to HID mode (for my set at least)...
though I'm honestly not sure why I can get it to work in the BIOS but
not GRUB.

I checked the link in the below file text (the debian bug link) but I
see that it goes back more than two years, though interestingly the
original report is also for a DiNovo setup. Also, using their software
in Windows the dongle is set to HCI mode (I have used the dongle with
other devices) and on reboot from there BIOS/GRUB functionality is fine.

Maybe Logitech has a funny way of switching their BT dongles back to HID
mode? What information could I provide to help troubleshoot?

My /etc/default/bluetooth:

# Defaults for bluez

# start bluetooth on boot?
# compatibility note: If this variable is not found bluetooth will
# start
BLUETOOTH_ENABLED=1

# This setting will switch HID devices (e.g mouse/keyboad) to HCI mode, that is
# you will have bluetooth functionality from your dongle instead of only HID.
# Note that not every bluetooth dongle is capable of switching back to HID
# mode, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497
HID2HCI_ENABLED=1
HID2HCI_UNDO=1

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New

-- 
dinovo dongle isn't reset to HID mode on restart/shut down
https://bugs.launchpad.net/bugs/296567
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.