On 24/07/06 13:19, Filippo Giunchedi wrote: > Could you try with newest bluez-utils package? (3.1-2, but 3.1-3 is imminent) > If it still doesn't work we should talk to upstream and try to figure this > out.
with 3.1-2: # hid2hci --tohci Switching device 046d:c704 to HCI mode was successful # hid2hci --tohid No devices in HID mode found (by the way, I think this error message is wrong - I'm trying to switch _to_ HID mode, so it should say "No devices in HCI mode found" - unless I'm misinterpreting it, I should check with upstream if that's intentional) On 28/11/05 19:28, Marcel Holtmann mentioned something relevant on the bluez-users mailinglist, see: http://sourceforge.net/mailarchive/message.php?msg_id=18102606 >> There are two problems I wanted to ask about: >> 1. The dongle doesnt reset to HID mode when system is shut off ... so I have >> no ability to use the keyboard in grub! I need to write a script to reset it >> to hid mode when the system is shut off. How can i do this? The hid2hci >> program supposedly provides an option to switch back to hid mode ... but it >> doesn't work. I get the error "No devices in hid mode found" (obviously!). > > we don't know the magic sequence to switch it back into HID mode. I'm assuming the situation hasn't changed in the mean time. Looking at the device_list in hid2hci.c we can see that only the non-logitech dongles mentioned there can be switched back to hid mode. Rock = not switching to hci on boot means no bluetooth functionality, and people who installed the bluetooth packages probably expect to be able to use it. Hard place = switching to hci means that logitech users won't be able to use their keyboard during boot-up (BIOS and GRUB). -- Mourad -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
