On Sun, 2008-11-16 at 13:40 +0000, Martin G Miller wrote: > Chow Loong Jin wrote: > "1. Set HID2HCI_ENABLED=0 in /etc/default/bluetooth, and then manually > run > PM_FUNCTIONS=/usr/lib/pm-utils/pm-functions > /usr/lib/pm-utils/sleep.d/48hid2hci > > This results in no error message." > > This would not give an error message as it has just switched the device > from HID to HCI mode. > It would for me because I don't have any bluetooth devices. > Then, if you do: > "2. Set HID2HCI_ENABLED=1 in /etc/default/bluetooth, and the manually run > PM_FUNCTIONS=/usr/lib/pm-utils/pm-functions > /usr/lib/pm-utils/sleep.d/48hid2hci > > This results in the error message "No devices in HID mode found"." > > This confirms that the HCI mode is still enabled from the previous > command, which should not be the case. Basically running the command complains because I do not have any bluetooth devices. Well I do, but it's not enabled, and doesn't show up in lsusb. If it complains (on my system), that means the command is run. If it doesn't, it isn't run. Simple as that. > > Is there any way to determine the status of the device before and after > issuing the commands? That way you could boot with HID2HCI_ENABLED=0 set and > test to see that it is in fact in HID mode. Then run the command: > "PM_FUNCTIONS=/usr/lib/pm-utils/pm-functions > /usr/lib/pm-utils/sleep.d/48hid2hci" > and again test to see what mode the device is in. I believe it is changing > to HCI even though it shouldn't be. > You could test the hook by modifying the /usr/sbin/hid2hci --tohci to have an echo in front. Then see if it's printed when you run the PM_FUNCTIONS... command. I highly doubt it's the hook that's causing the problem.
-- Chow Loong Jin -- bluetooth service does not restart after a suspend to ram https://bugs.launchpad.net/bugs/268877 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs