For karmic this is a new bug actually. It was fixed differently for hardy and intrepid. Karmic introduced a different hid2hci and killswitch interface.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kai Jauch Sent: Thursday, June 11, 2009 5:57 AM To: [email protected] Subject: [Bug 330934] Re: Dell bluetooth adapters don't return to HCI modeafter suspend 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 -- Dell bluetooth adapters don't return to HCI mode after suspend https://bugs.launchpad.net/bugs/330934 You received this bug notification because you are a member of The Dell Team, which is subscribed to Dell Ubuntu Project. -- Dell bluetooth adapters don't return to HCI mode after suspend https://bugs.launchpad.net/bugs/330934 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
