© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I've tried 3.12-rc2, as far as I can tell just opening and closing the rfcomm in BT seems to no longer crash the box - however, some characteristics changed and NetworkManager no longer accepts /dev/rfcomm* as a valid communications device as before, so I can't fully test it.
A bit tricky - using the same userland,
Linux-3.5.7-gentoo - works flawlessly
Linux-3.8.13-gentoo - crashes when BT rfcomm is closed
Linux-3.12-rc2 (raw from kernel.org) - blueman able to set up rfcomm but networkmanager does not notice that rfcomm was setup. Supposedly NM should notify blueman via dbus that it acknowledges the device, but blueman times out waiting and NM does not recognize the device. In trying to diagnose the problem I tried using busybox microcom on /dev/rfcomm0 directly. I was able to send my modem AT commands like on previous kernels, indicating the bluetooth link indeed works. I was able to shutdown the rfcomm link on blueman as well after sending those bytes through. No crash - a positive sign... but it may depend on the number of bytes sent.
I'll need to see why NM does not like the rfcomm device now, but I am no NM or dbus expert...