Wheezy: Problem with Bluetooth


24 posts
by Himbeere » Mon Jul 16, 2012 6:10 am
Hello,

unfortunately I have some problems with "Bluetooth". I request periodically (every 10min) a solar inverter in order to retrieve the data. But quite often the program stuck with: "bluetooth time out"

If this happens, the whole bluetooth does not work any more until restart of the "bluetoothd" daemon. E.g. even other bluetooth programs don't work any more:

Code: Select all
root@raspberrypi:~# hcitool scan
Scanning ...
Inquiry failed: Connection timed out


I'm using (hopefully) the newest "firmware" (rpi_update) and "packages" (apt-get update/upgrade).

I start then the bluetoothd manually with the "debug" option - see results below (the problem starts @18:40):
Code: Select all
Jul 15 18:30:01 raspberrypi /USR/SBIN/CRON[3684]: (root) CMD (/opt/sma/sma-request.sh)
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: plugins/hciops.c:conn_complete() status 0x00
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: src/adapter.c:adapter_get_device() 00:80:25:XX:XX:XX
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: src/adapter.c:adapter_create_device() 00:80:25:22:07:E1
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: src/device.c:device_create() Creating device /org/bluez/3398/hci0/dev_00_80_25_XX_XX_XX
Jul 15 18:30:24 raspberrypi kernel: [ 3146.244559] ------------[ cut here ]------------
Jul 15 18:30:24 raspberrypi kernel: [ 3146.244641] WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0xa0/0xc8()
Jul 15 18:30:24 raspberrypi kernel: [ 3146.244698] sysfs: cannot create duplicate filename '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:42'
Jul 15 18:30:24 raspberrypi kernel: [ 3146.244747] Modules linked in: bnep rfcomm ipv6 snd_bcm2835 snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd aes_generic ecb btusb bluetooth spi_bcm2708 i2c_bcm2708
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245244] [<c00153d4>] (unwind_backtrace+0x0/0xfc) from [<c03f95a0>] (dump_stack+0x20/0x24)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245349] [<c03f95a0>] (dump_stack+0x20/0x24) from [<c002d830>] (warn_slowpath_common+0x5c/0x74)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245443] [<c002d830>] (warn_slowpath_common+0x5c/0x74) from [<c002d904>] (warn_slowpath_fmt+0x40/0x48)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245537] [<c002d904>] (warn_slowpath_fmt+0x40/0x48) from [<c015d92c>] (sysfs_add_one+0xa0/0xc8)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245628] [<c015d92c>] (sysfs_add_one+0xa0/0xc8) from [<c015d9c8>] (create_dir+0x74/0xcc)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245695] [<c015d9c8>] (create_dir+0x74/0xcc) from [<c015daf0>] (sysfs_create_dir+0x94/0x10c)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245773] [<c015daf0>] (sysfs_create_dir+0x94/0x10c) from [<c02503e4>] (kobject_add_internal+0xb4/0x1d8)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245870] [<c02503e4>] (kobject_add_internal+0xb4/0x1d8) from [<c02507fc>] (kobject_add+0x58/0x98)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.245956] [<c02507fc>] (kobject_add+0x58/0x98) from [<c029b29c>] (device_add+0xdc/0x5a4)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.246223] [<c029b29c>] (device_add+0xdc/0x5a4) from [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth])
Jul 15 18:30:24 raspberrypi kernel: [ 3146.246473] [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth]) from [<c0049210>] (process_one_work+0x154/0x480)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.246579] [<c0049210>] (process_one_work+0x154/0x480) from [<c004bf48>] (worker_thread+0x168/0x3ac)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.246682] [<c004bf48>] (worker_thread+0x168/0x3ac) from [<c0050b5c>] (kthread+0x98/0xa0)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.246793] [<c0050b5c>] (kthread+0x98/0xa0) from [<c000f1dc>] (kernel_thread_exit+0x0/0x8)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.246871] ---[ end trace f53f973d33019315 ]---
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247002] kobject_add_internal failed for hci0:42 with -EEXIST, don't try to register things with the same name in the same directory.
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247085] [<c00153d4>] (unwind_backtrace+0x0/0xfc) from [<c03f95a0>] (dump_stack+0x20/0x24)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247164] [<c03f95a0>] (dump_stack+0x20/0x24) from [<c02504f0>] (kobject_add_internal+0x1c0/0x1d8)
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: src/device.c:btd_device_ref() 0x40a34e00: ref=1
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: src/device.c:device_set_temporary() temporary 1
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247259] [<c02504f0>] (kobject_add_internal+0x1c0/0x1d8) from [<c02507fc>] (kobject_add+0x58/0x98)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247337] [<c02507fc>] (kobject_add+0x58/0x98) from [<c029b29c>] (device_add+0xdc/0x5a4)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247514] [<c029b29c>] (device_add+0xdc/0x5a4) from [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth])
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247712] [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth]) from [<c0049210>] (process_one_work+0x154/0x480)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247822] [<c0049210>] (process_one_work+0x154/0x480) from [<c004bf48>] (worker_thread+0x168/0x3ac)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.247919] [<c004bf48>] (worker_thread+0x168/0x3ac) from [<c0050b5c>] (kthread+0x98/0xa0)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.248025] [<c0050b5c>] (kthread+0x98/0xa0) from [<c000f1dc>] (kernel_thread_exit+0x0/0x8)
Jul 15 18:30:24 raspberrypi kernel: [ 3146.248152] Bluetooth: Failed to register connection device
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: plugins/hciops.c:remote_features_information() hci0 status 0
Jul 15 18:30:24 raspberrypi bluetoothd[3398]: plugins/hciops.c:remote_name_information() hci0 status 0
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: plugins/hciops.c:disconn_complete() handle 42 status 0x00
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: src/event.c:btd_event_disconn_complete()
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: src/adapter.c:adapter_remove_connection()
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: src/adapter.c:adapter_remove_connection() Removing temporary device /org/bluez/3398/hci0/dev_00_80_25_22_07_E1
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: src/device.c:device_remove() Removing device /org/bluez/3398/hci0/dev_00_80_25_22_07_E1
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: src/device.c:btd_device_unref() 0x40a34e00: ref=0
Jul 15 18:30:33 raspberrypi bluetoothd[3398]: src/device.c:device_free() 0x40a34e00
Jul 15 18:40:01 raspberrypi /USR/SBIN/CRON[3689]: (root) CMD (/opt/sma/sma-request.sh)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.943307] ------------[ cut here ]------------
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: plugins/hciops.c:conn_complete() status 0x00
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: src/adapter.c:adapter_get_device() 00:80:25:22:07:E1
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: src/adapter.c:adapter_create_device() 00:80:25:XX:XX:XX
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: src/device.c:device_create() Creating device /org/bluez/3398/hci0/dev_00_80_25_XX_XX_XX
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: src/device.c:btd_device_ref() 0x40a34e00: ref=1
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: src/device.c:device_set_temporary() temporary 1
Jul 15 18:40:22 raspberrypi kernel: [ 3743.943409] WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0xa0/0xc8()
Jul 15 18:40:22 raspberrypi kernel: [ 3743.943457] sysfs: cannot create duplicate filename '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:42'
Jul 15 18:40:22 raspberrypi kernel: [ 3743.943512] Modules linked in: bnep rfcomm ipv6 snd_bcm2835 snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd aes_generic ecb btusb bluetooth spi_bcm2708 i2c_bcm2708
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944035] [<c00153d4>] (unwind_backtrace+0x0/0xfc) from [<c03f95a0>] (dump_stack+0x20/0x24)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944138] [<c03f95a0>] (dump_stack+0x20/0x24) from [<c002d830>] (warn_slowpath_common+0x5c/0x74)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944241] [<c002d830>] (warn_slowpath_common+0x5c/0x74) from [<c002d904>] (warn_slowpath_fmt+0x40/0x48)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944334] [<c002d904>] (warn_slowpath_fmt+0x40/0x48) from [<c015d92c>] (sysfs_add_one+0xa0/0xc8)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944425] [<c015d92c>] (sysfs_add_one+0xa0/0xc8) from [<c015d9c8>] (create_dir+0x74/0xcc)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944533] [<c015d9c8>] (create_dir+0x74/0xcc) from [<c015daf0>] (sysfs_create_dir+0x94/0x10c)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.944615] [<c015daf0>] (sysfs_create_dir+0x94/0x10c) from [<c02503e4>] (kobject_add_internal+0xb4/0x1d8)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.951095] [<c02503e4>] (kobject_add_internal+0xb4/0x1d8) from [<c02507fc>] (kobject_add+0x58/0x98)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.951208] [<c02507fc>] (kobject_add+0x58/0x98) from [<c029b29c>] (device_add+0xdc/0x5a4)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.951483] [<c029b29c>] (device_add+0xdc/0x5a4) from [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth])
Jul 15 18:40:22 raspberrypi kernel: [ 3743.951709] [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth]) from [<c0049210>] (process_one_work+0x154/0x480)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.951816] [<c0049210>] (process_one_work+0x154/0x480) from [<c004bf48>] (worker_thread+0x168/0x3ac)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.951917] [<c004bf48>] (worker_thread+0x168/0x3ac) from [<c0050b5c>] (kthread+0x98/0xa0)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952027] [<c0050b5c>] (kthread+0x98/0xa0) from [<c000f1dc>] (kernel_thread_exit+0x0/0x8)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952082] ---[ end trace f53f973d33019316 ]---
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952187] kobject_add_internal failed for hci0:42 with -EEXIST, don't try to register things with the same name in the same directory.
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952305] [<c00153d4>] (unwind_backtrace+0x0/0xfc) from [<c03f95a0>] (dump_stack+0x20/0x24)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952406] [<c03f95a0>] (dump_stack+0x20/0x24) from [<c02504f0>] (kobject_add_internal+0x1c0/0x1d8)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952510] [<c02504f0>] (kobject_add_internal+0x1c0/0x1d8) from [<c02507fc>] (kobject_add+0x58/0x98)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952614] [<c02507fc>] (kobject_add+0x58/0x98) from [<c029b29c>] (device_add+0xdc/0x5a4)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.952813] [<c029b29c>] (device_add+0xdc/0x5a4) from [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth])
Jul 15 18:40:22 raspberrypi kernel: [ 3743.953057] [<bf0499f0>] (add_conn+0x48/0x188 [bluetooth]) from [<c0049210>] (process_one_work+0x154/0x480)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.953157] [<c0049210>] (process_one_work+0x154/0x480) from [<c004bf48>] (worker_thread+0x168/0x3ac)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.953260] [<c004bf48>] (worker_thread+0x168/0x3ac) from [<c0050b5c>] (kthread+0x98/0xa0)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.953362] [<c0050b5c>] (kthread+0x98/0xa0) from [<c000f1dc>] (kernel_thread_exit+0x0/0x8)
Jul 15 18:40:22 raspberrypi kernel: [ 3743.953457] Bluetooth: Failed to register connection device
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: plugins/hciops.c:remote_features_information() hci0 status 0
Jul 15 18:40:22 raspberrypi bluetoothd[3398]: plugins/hciops.c:remote_name_information() hci0 status 0
Jul 15 18:42:04 raspberrypi bluetoothd[3398]: plugins/hciops.c:set_state() hci0: new state 3
Jul 15 18:42:04 raspberrypi kernel: [ 3846.228427] Bluetooth: hci0 link tx timeout
Jul 15 18:42:04 raspberrypi kernel: [ 3846.228519] Bluetooth: hci0 killing stalled connection 00:80:25:22:07:E1
Jul 15 18:42:04 raspberrypi kernel: [ 3846.228883] Bluetooth: hci0 link tx timeout
Jul 15 18:42:04 raspberrypi kernel: [ 3846.228964] Bluetooth: hci0 killing stalled connection 00:80:25:22:07:E1
Jul 15 18:42:04 raspberrypi bluetoothd[3398]: plugins/hciops.c:resolve_names() found_dev 0 need_name 0
Jul 15 18:42:04 raspberrypi bluetoothd[3398]: plugins/hciops.c:set_state() hci0: new state 0
Jul 15 18:42:04 raspberrypi bluetoothd[3398]: plugins/hciops.c:auth_complete() hci0 status 5
Jul 15 18:42:05 raspberrypi kernel: [ 3847.228279] Bluetooth: hci0 command tx timeout
Jul 15 18:42:06 raspberrypi kernel: [ 3848.228305] Bluetooth: hci0 command tx timeout
Jul 15 18:50:01 raspberrypi /USR/SBIN/CRON[3694]: (root) CMD (/opt/sma/sma-request.sh)


Any ideas?
Posts: 14
Joined: Wed Jun 20, 2012 8:56 am
by Fanjita » Mon Jul 16, 2012 1:07 pm
Sadly I've seen similar results with cheap bluetooth dongles for a long time when running on Debian-based Linuxes.

Occasionally my hardware freezes up hard enough that the dongle needs to be unplugged before the bluetooth stack recovers - I even went to far as to create a custom USB cable that disconnects power for a few seconds once every few hours, so that my PV inverter monitoring is more-or-less uninterrupted.

You might want to check that you're supplying sufficient power to your bluetooth dongle - mine has been a lot less reliable since I stuck it on the end of a fairly long extension cable, to site it closer to the inverter, and I expect that's causing issues with undervolting the dongle.
Posts: 17
Joined: Thu Jun 07, 2012 9:31 am
Location: Edinburgh, UK
by recantha » Mon Jul 16, 2012 1:48 pm
Try the Debian Squeeze v6 image that's recommended on the Download page.
I had trouble with both Wheezy AND Arch. I'm going to post my experience up on the Net later which deals with getting WiFi and BT working automatically on the Pi with Deb Squeeze.
My Raspberry Pi blog with all my latest projects and links to articles
http://raspberrypipod.blogspot.com. +++ Current project: PiPodTricorder - lots of sensors, lots of mini-displays, breadboarding, bit of programming.
Posts: 209
Joined: Mon Jun 25, 2012 10:41 am
by Himbeere » Mon Jul 16, 2012 3:46 pm
Sadly I've seen similar results with cheap bluetooth dongles for a long time when running on Debian-based Linuxes.
Occasionally my hardware freezes up hard enough that the dongle needs to be unplugged before the bluetooth stack recovers - I even went to far as to create a custom USB cable that disconnects power for a few seconds once every few hours, so that my PV inverter monitoring is more-or-less uninterrupted.
You might want to check that you're supplying sufficient power to your bluetooth dongle - mine has been a lot less reliable since I stuck it on the end of a fairly long extension cable, to site it closer to the inverter, and I expect that's causing issues with undervolting the dongle.


I tried 2 different BT-Sticks. One of them was working for about half a year at a NSLU2 without a problem doing the same thing with my PV-Inverter.

The BT Stick is directly connected to the RaPi and I'm using an 1.5A power supply. As it starts over again after I restart the BT daemon I "believe" in a SW bug.

Try the Debian Squeeze v6 image that's recommended on the Download page.


Yes I will try to revert to the "old" Squeeze ...
Posts: 14
Joined: Wed Jun 20, 2012 8:56 am
by mickster04 » Thu Aug 02, 2012 10:37 am
Any updates on Wheezy?
I want it because I couldn't get sound working in Squeeze...
Alls i wan the pi to do is play music when my phone is within range :S
so it just needs the bluetooth and the audio out working :p
Posts: 1
Joined: Thu Aug 02, 2012 10:35 am
by honda4life » Fri Aug 17, 2012 11:32 am
same problems here guys, very difficult to solve :?
Posts: 70
Joined: Thu Mar 15, 2012 7:27 pm
by Himbeere » Sat Aug 18, 2012 6:03 pm
.. the same problem with "squezze" :cry:
Posts: 14
Joined: Wed Jun 20, 2012 8:56 am
by thefullmooner » Wed Aug 22, 2012 12:43 pm
Same problem over here...

created duplicated topic since i haden't found this one
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=14005&p=153704
Posts: 6
Joined: Wed Aug 08, 2012 8:43 pm
by honda4life » Thu Aug 23, 2012 5:15 pm
I'm going to test the rfcomm socket now.
Hope I have positive feedback within a few hours.
For who want to help: http://people.csail.mit.edu/albert/blue ... /x502.html
Posts: 70
Joined: Thu Mar 15, 2012 7:27 pm
by Chris-Mouse » Thu Aug 23, 2012 5:40 pm
I just downloaded the latest version of wheezy, and got nowhere with Bluetooth.

Fresh install of 2012-08-16-wheezy-raspbian
sudo apt-get update and sudo apt-get upgrade to get the latest packages.
apt-get install bluetooth bluez-utils blueman to install bluetooth software
hcitool scan finds my bluetooth device
bluetooth-agent 1234 & to set a pairing number

An attempt to connect to the device with rfcomm gets a connection refused error.
about two seconds later the whole system crashes with a kernel null pointer dereference error.

this is not new with this version of Raspian, it happened with the previous version as well.
Posts: 3
Joined: Mon Jan 23, 2012 8:12 pm
by gregd72002 » Sat Aug 25, 2012 5:07 pm
The root cause is in regression bug in 3.1.x and 3.2.x kernels..
Kernel 3.3 is known to resolve the issue.

https://github.com/raspberrypi/linux/issues/66

Anyone tried kernel 3.3?
Posts: 31
Joined: Tue May 08, 2012 9:17 pm
by honda4life » Sun Aug 26, 2012 11:00 am
Compiling kernel with patches on the rpi.
Keep you informed guys ;)
Posts: 70
Joined: Thu Mar 15, 2012 7:27 pm
by benburch » Sun Aug 26, 2012 6:20 pm
Thank you!

I've been tearing out my remaining hair last couple days. I'll wait until the new kernel.
Posts: 6
Joined: Sun Aug 26, 2012 6:15 pm
by honda4life » Mon Aug 27, 2012 4:49 pm
Made a mistake when doing the diff manual, so compilation failed.
too busy atm to retry this evening :cry:
Posts: 70
Joined: Thu Mar 15, 2012 7:27 pm
by benburch » Mon Aug 27, 2012 5:15 pm
Software takes time to bake. Never a problem! :)
Posts: 6
Joined: Sun Aug 26, 2012 6:15 pm
by honda4life » Mon Aug 27, 2012 6:24 pm
Here we go again until tomorrow :mrgreen:
Posts: 70
Joined: Thu Mar 15, 2012 7:27 pm
by Sander » Tue Sep 04, 2012 11:23 am
honda4life wrote:Here we go again until tomorrow :mrgreen:


Any news?

You were trying to compile kernel 3.3, right? Did you succeed? And: does it solve the Bluetooth problem?

FYI: I have the same problems. Restarting bluetoothd does not make hcitool work again. Only rebooting works.

Code: Select all
pi@raspbian-frank-armhf ~ $ sudo service bluetooth restart
[ ok ] Stopping bluetooth: /usr/sbin/bluetoothd.
[ ok ] Starting bluetooth: bluetoothd.

pi@raspbian-frank-armhf ~ $ hcitool scan
Scanning ...
Inquiry failed: Connection timed out
pi@raspbian-frank-armhf ~ $

pi@raspbian-frank-armhf ~ $ dmesg | grep -i hci0
[14241.552429] Bluetooth: hci0 command tx timeout
pi@raspbian-frank-armhf ~ $
User avatar
Posts: 174
Joined: Wed Aug 31, 2011 1:01 pm
by honda4life » Wed Sep 05, 2012 4:56 pm
No not compining 3.3, integrating patches in current kernel but failed because I'm a noob :mrgreen:
Posts: 70
Joined: Thu Mar 15, 2012 7:27 pm
by benburch » Thu Sep 06, 2012 5:13 pm
I got better results when I added "dwc_otg.fiq_fix_enable=1" to the /boot/cmdline.txt.

At least it does not freeze as often.

Still cannot get a PAN session set up for networking over bluetooth, though.
Posts: 6
Joined: Sun Aug 26, 2012 6:15 pm
by collywobbles » Fri Sep 07, 2012 12:26 pm
I'm doing the same thing, running smatool to get solar readouts. I was using a bluetooth dongle and a wifi dongle. I tried a powered hub (recommended on the wiki) and that didn't work, I just bought a ethernet over power plug and took the wife dongle out, still no joy.

Looking for a solution!
Posts: 9
Joined: Mon Mar 19, 2012 12:06 pm
by lmirel » Mon Nov 05, 2012 9:45 am
Any luck with this one?
I have a similar issue with 3.2.27+ and two different BT dongles.
Posts: 1
Joined: Mon Nov 05, 2012 9:44 am
by thefullmooner » Mon Nov 05, 2012 1:31 pm
since the last update of raspberian i never encounter this issue anymore.
Posts: 6
Joined: Wed Aug 08, 2012 8:43 pm
by optimus » Sun Dec 30, 2012 5:21 am
I'm running the latest versions / updates but still have this issue.

I am up to my 3rd bluetooth device now. The USB BT adapter is the only thing plugged in to the Pi apart from the power cable!
Posts: 14
Joined: Fri Nov 25, 2011 1:54 pm
by castalla » Mon Jan 21, 2013 11:08 am
I've no idea how my bt issue relates to this thread - but in the bluetooth quest, it's a case of any port in a storm.

I can get bt working - pairing & playing audio.

BUT if I switch the device off then the whole ethernet network connection goes down, and requires a cold boot.

If I use wifi then I can switch the device off, then the network persists UNTIL I switch the device on again ... and bam! it's gone again.

Same happens with 2 different bt devices.

Just my 2 cents worth into the gruel of bluetooth.
Posts: 465
Joined: Thu Jul 19, 2012 3:46 pm