The Dell BT 370 still doesn't work after resume from suspend on karmic: $ hcitool scan Device is not available: No such device
/lib/udev/rules.d/62-bluez.rules contains: ACTION=="add", ENV{ID_VENDOR}=="413c", ENV{ID_CLASS}=="mouse", ATTRS{bmAttributes}=="e0", KERNEL=="mouse*", RUN+="/usr/sbin/hid2hci --method dell -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hci"
Doing it manually works: $ sudo hid2hci --method dell -v 413c -p 8158 --mode hci Attempting to switch device 413c:8158 to HCI mode was successful
Enabling and disabling the killswitch after resuming from suspend also sets the bluetooth module to the right mode.
bluez 4.40-0ubuntu1 udev 142-2
The Dell BT 370 still doesn't work after resume from suspend on karmic:
$ hcitool scan
Device is not available: No such device
/lib/udev/ rules.d/ 62-bluez. rules contains: VENDOR} =="413c" , ENV{ID_ CLASS}= ="mouse" , ATTRS{bmAttribu tes}==" e0", KERNEL=="mouse*", RUN+="/ usr/sbin/ hid2hci --method dell -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hci"
ACTION=="add", ENV{ID_
Doing it manually works:
$ sudo hid2hci --method dell -v 413c -p 8158 --mode hci
Attempting to switch device 413c:8158 to HCI mode was successful
Enabling and disabling the killswitch after resuming from suspend also sets the bluetooth module to the right mode.
bluez 4.40-0ubuntu1
udev 142-2