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.
Created attachment 46591 [details, diff] bluetooth-init.patch Make hid2hci first in start() function and add an one second delay
added to 2.16's init script.
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.
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.
