Bug 75255 - net-wireless/bluez-utils : hid2hci needs to be run first with a delay
Bug#: 75255 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: All Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: mobile@gentoo.org Reported By: swanson@ukfsn.org
Component: Applications
URL: 
Summary: net-wireless/bluez-utils : hid2hci needs to be run first with a delay
Keywords:  
Status Whiteboard: 
Opened: 2004-12-21 16:15 0000
Description:   Opened: 2004-12-21 16:15 0000 
In the bluetooth initscript hid2hci needs to be run first, followed by a short
delay before running the chosen bluetooth daemons.

It needs to be run first otherwise there will be no bluetooth device/drivers
for daemons as the device would currently be a HID device only.

There also needs to be a short delay to allow hotplugging time to detect the
"new" HCI device and load the bluetooth modules. Otherwise there will still be
no device/drivers for the daemons that are run immediately after hid2hci. A one
second delay is sufficient.

Although sleeps are not nice in initscripts, this only affects people using
hid2hci. For example, my Logitech receiver that came with my MX900 mouse.

------- Comment #1 From Alan Swanson 2004-12-21 16:17:29 0000 ------- 
Created an attachment (id=46591) [details]
bluetooth-init.patch

Make hid2hci first in start() function and add an one second delay

------- Comment #2 From Alastair Tse (RETIRED) 2005-04-26 06:13:52 0000 ------- 
added to 2.16's init script.

------- Comment #3 From Alan Swanson 2005-04-26 16:15:46 0000 ------- 
Patch not applied correctly, the only change made was to add the sleep.

It is perhaps not clear if only reading the patch and not actually applying, but the bug was that the HID2HCI_ENABLE section needs to the be the first to be run in the start() function.

------- Comment #4 From Alastair Tse (RETIRED) 2005-04-27 05:36:26 0000 ------- 
yes, you're correct. i overlooked the fact that you shifted the block to before
the hcid. the problem is i don't have any bluetooth hid equipment, so i can't
test this out for sure.

anyway, i've fixed the init script and bumped the version. hopefully this will
work better for you now.