Opensuse 12.1 No bluetooth on Asus G53jw laptop

Hi All,

Since I moved to 12.1 (64bit) I’m having problems with bluetooth in Opensuse. I did a clean install and before I was using Opensuse 11.4. The thing is that the meny shows the bluetooth icon at the bar but it is turned off and I can’t turn it on no matter what. Moreover, if I restart the laptot, then no bluetooth is shown whatsoever. I have a double partition with Win7 and if I go from suse to win7 restarting without shutting down, bluetooth doesn’t appear under windows neither, I need to turn off the machine and then go to windows from Grub if I want a session with bluetooth (!?). It seems that when suse starts it turns definitely OFF the bluetooth some how. I’ve been trying to read var/log/messages and certainly I found strange things related to bluetooth… but I can’t figure out what could be wrong, that’s why I asking you guys for help.

under “messages” I have the following lines:

Jan 21 18:20:48 Bourne kernel:    10.711410] Bluetooth: Core ver 2.16
Jan 21 18:20:48 Bourne kernel:    10.711429] NET: Registered protocol family 31
Jan 21 18:20:48 Bourne kernel:    10.711432] Bluetooth: HCI device and connection manager initialized
Jan 21 18:20:48 Bourne kernel:    10.711435] Bluetooth: HCI socket layer initialized
Jan 21 18:20:48 Bourne kernel:    10.711437] Bluetooth: L2CAP socket layer initialized
Jan 21 18:20:48 Bourne kernel:    10.711449] Bluetooth: SCO socket layer initialized
Jan 21 18:20:48 Bourne kernel:    10.711790] Bluetooth: Generic Bluetooth USB driver ver 0.6

Up to here, all fine, but a bit later I found this:

Jan 21 18:20:48 Bourne bluez-coldplug[1288]: ..done
Jan 21 18:20:48 Bourne bluetoothd[1315]: Bluetooth daemon 4.96
Jan 21 18:20:48 Bourne bluetoothd[1317]: Starting SDP server
Jan 21 18:20:48 Bourne mcelog[1264]: Starting mcelog... ..done
Jan 21 18:20:48 Bourne bluetoothd[1317]: D-Bus failed to register org.bluez.Proximity interface
Jan 21 18:20:48 Bourne bluetoothd[1317]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Jan 21 18:20:48 Bourne bluetoothd[1317]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Jan 21 18:20:48 Bourne kernel:    15.933545] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 21 18:20:48 Bourne kernel:    15.933549] Bluetooth: BNEP filters: protocol multicast
Jan 21 18:20:48 Bourne bluetoothd[1317]: Listening for HCI events on hci0
Jan 21 18:20:48 Bourne /usr/sbin/cron[1303]: (CRON) INFO (running with inotify support)
Jan 21 18:20:48 Bourne bluetoothd[1317]: HCI dev 0 up
Jan 21 18:20:48 Bourne bluetoothd[1317]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Jan 21 18:20:48 Bourne kernel:    15.979077] Bluetooth: RFCOMM TTY layer initialized
Jan 21 18:20:48 Bourne kernel:    15.979084] Bluetooth: RFCOMM socket layer initialized
Jan 21 18:20:48 Bourne kernel:    15.979086] Bluetooth: RFCOMM ver 1.11
Jan 21 18:20:48 Bourne kernel:    15.979482] r8169 0000:06:00.0: eth0: link down
Jan 21 18:20:48 Bourne kernel:    15.980265] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 21 18:20:48 Bourne kernel:    15.982337] NET: Registered protocol family 17
Jan 21 18:20:48 Bourne nmb[1326]: Starting Samba NMB daemon ..done
Jan 21 18:20:48 Bourne smb[1409]: Starting Samba SMB daemon ..done
Jan 21 18:20:48 Bourne SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jan 21 18:20:48 Bourne bluetoothd[1317]: HCI dev 0 down
Jan 21 18:20:48 Bourne bluetoothd[1317]: Adapter /org/bluez/1315/hci0 has been disabled

and finally:

Jan 21 18:21:30 Bourne pulseaudio[2255]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Jan 21 18:21:30 Bourne pulseaudio[2255]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Jan 21 18:21:30 Bourne pulseaudio[2255]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod

from here I don’t know if I’m missing some configuration files, some packages… or what! Does anybody had this kind of trouble before?

Also, I get nothing from:

hcitool scan
Device is not available: No such device

Thanks a lot for your help!

Hi,

I’m also experiencing trouble with Bluetooth currently, but it does not look similar to what you have.
Just wanted to mention that you’re probably using ‘hcitool’ in the wrong way.
You should use ‘hcitool dev’ to list your bluetooth adapters.
‘hcitool scan’ will look for devices that can be connected to your bluetooth adapter.

You should also post the output from ‘hciconfig’ and if it lists a bluetooth adapater marked DOWN try ‘hciconfig hci0 up’

Good luck.
Pieter

Hi Pieter,

thanks for the tip… yup still quite noob in many aspects here.

the output from hcitool dev is blank:

hcitool dev
Devices:

hciconfig lists something:

hciconfig
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 74:F0:6D:BC:47:25  ACL MTU: 1021:8  SCO MTU: 64:1
        DOWN 
        RX bytes:956 acl:0 sco:0 events:39 errors:0
        TX bytes:175 acl:0 sco:0 commands:41 errors:1

But when trying hciconfig hci0 up, I have a connection time out

hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Thanks for the help! I hope this could complement the previous info!

Hi,

What does ‘rfkill’ tell?
That will show you if you have any hardware buttons/switches that turn off your bluetooth adapter.

Kind regards,
Pieter

This is what I get:

rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

fkill event
1327380525.775245: idx 0 type 1 op 0 soft 0 hard 0
1327380525.775298: idx 1 type 2 op 0 soft 0 hard 0

…nothing strange I guess

Hello.
I also have difficulties with bluetooth.
In OpenSuse 12.1 KDE

hcitool dev
Devices:
hci0 00:1B:DC:03:66:56

hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:DC:03:66:56 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1575 acl:0 sco:0 events:60 errors:0
TX bytes:991 acl:0 sco:0 commands:56 errors:0

hcitool scan
Scanning …

No results.
And other bluetooth devices cannot find this one.
I am also having dual-boot and in Win7x64 all works fine :frowning:
Anybody knows what the problem?
Thanks A Lot.

is bluedevil installed in your package ??

Hi Soni,

Thanks for stopping by! Yes it is installed. Nevetheless, I have news, weird news.

All of the sudden, as any other day, I tried to enable bluetooth from my toolbar yesterday and… WORKED! (?!) very very strange. I didn’t update ANYTHING, just worked with exactly the same configuration and things I had before so I started doing some tests.

  1. I was wondering if it could be a firmware problem as I also read in other forums so went to Windows, turned it ON-OFF-ON again, restarted with the bluetooth OFF into Suse again and seemed to keep working.

After this, I re-took an old problem I’m having with USB3 in my computer, I have an old thread here. (I know I’m mixing things… but just wait a second) I tried to enable/disable the xhci-hcd module under /etc/sysconfig/kernel, also playing with an extra kernel parameter “pci=nomsi” to see if I could get it to work, and after a reboot, I lost bluetooth again! All back to zero, no output from hcitool dev, and time out messages for hciconfig hci0 up; hciconfig hci0 reset. tried 1) again… and NOTHING, all dead when was back to Suse.

Under \var\log\messages I keep having the same as what I posted on #1](http://forums.opensuse.org/english/get-technical-help-here/laptop/471496-opensuse-12-1-no-bluetooth-asus-g53jw-laptop.html#post2432860).

Another interesting thing is:

When I have no bluetooth and I go for hibernation, after resuming from hibernation I have NO CONNECTIVITY AT ALL on ANY USB. (strange). When I got bluetooth working for a bit of time, everything seemed fine after hibernation. (?!) Now I start to believe that my bluetooth problem could be a consequence of another problem… and that’s why I referred my post on USB3 problems… (I don’t know if it is exactly that but I’m making connections in my newbee linux brain side)

Ok, second thing I tried Kernel-default. …nothing, exactly the same, so I went back to kernel-desktop. When I came back to kernel-desktop I tried again to enable bluetooth and… WHAT?! It’s working again??? …so the first thing I did was to check again the /var/log/messages and this is what I got:

an 28 15:25:39 Bourne bluez-coldplug[1350]: ..done
Jan 28 15:25:39 Bourne bluetoothd[1367]: Bluetooth daemon 4.96
Jan 28 15:25:39 Bourne bluetoothd[1369]: Starting SDP server
Jan 28 15:25:39 Bourne bluetoothd[1369]: D-Bus failed to register org.bluez.Proximity interface
Jan 28 15:25:39 Bourne bluetoothd[1369]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Jan 28 15:25:39 Bourne bluetoothd[1369]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Jan 28 15:25:39 Bourne kernel:    17.094896] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 28 15:25:39 Bourne kernel:    17.094899] Bluetooth: BNEP filters: protocol multicast
Jan 28 15:25:39 Bourne bluetoothd[1369]: Listening for HCI events on hci0
Jan 28 15:25:39 Bourne bluetoothd[1369]: HCI dev 0 up
Jan 28 15:25:39 Bourne bluetoothd[1369]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Jan 28 15:25:39 Bourne dbus-daemon[1150]: /etc/NetworkManager/dispatcher.d/netcontrol_services: line 37: scripts/ifhostname-services: No such file or directory
Jan 28 15:25:39 Bourne kernel:    17.288470] Bluetooth: RFCOMM TTY layer initialized
Jan 28 15:25:39 Bourne kernel:    17.288474] Bluetooth: RFCOMM socket layer initialized
Jan 28 15:25:39 Bourne kernel:    17.288476] Bluetooth: RFCOMM ver 1.11
Jan 28 15:25:39 Bourne SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jan 28 15:25:40 Bourne /usr/sbin/cron[1360]: (CRON) INFO (running with inotify support)
Jan 28 15:25:40 Bourne mcelog[1330]: Starting mcelog... ..done
Jan 28 15:25:40 Bourne mcelog: mcelog read: No such device
Jan 28 15:25:40 Bourne bluetoothd[1369]: HCI dev 0 down
Jan 28 15:25:40 Bourne bluetoothd[1369]: Adapter /org/bluez/1367/hci0 has been disabled

so again, when the system booted, the bluetooth couldn’t be activated. Now, when I activated manually, I can see in the log:

Jan 28 15:26:17 Bourne pulseaudio[2332]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Jan 28 15:26:17 Bourne pulseaudio[2332]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Jan 28 15:26:17 Bourne pulseaudio[2332]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Jan 28 15:26:17 Bourne pulseaudio[2354]: [pulseaudio] pid.c: Daemon already running.
Jan 28 15:26:17 Bourne pulseaudio[2356]: [pulseaudio] pid.c: Daemon already running.
Jan 28 15:26:18 Bourne polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.53 [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 28 15:26:22 Bourne bluetoothd[1369]: HCI dev 0 up
Jan 28 15:26:22 Bourne bluetoothd[1369]: Adapter /org/bluez/1367/hci0 has been enabled

Look that I activated it in the event at (Jan 28 15:26:22), nevertheless at (Jan 28 15:26:17) there were still being error logs, in this case from pulseaudio.

When I run now hcitool dev, I get:

hcitool dev
Devices:
        hci0    74:F0:6D:BC:47:25

Also, hciconfig hci0, gives no errors:

hciconfig hci0
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 74:F0:6D:BC:47:25  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING PSCAN 
        RX bytes:1781 acl:0 sco:0 events:74 errors:0
        TX bytes:1062 acl:0 sco:0 commands:74 errors:0

I will restart my computer now and will post in some minutes the updated log from /var/log/messages to see if, after restarting or turning off the computer with bluetooth WORKING, it keeps working later.

From all my tests I also have results for the USB3 problem. For that, I will update my previous post to see if somebody can shed some light.

Thanks a lot again for stopping by and for the help!

Turned the computer off, then back on again into Suse and Bluetooth seems activated now during boot.

Jan 28 16:09:34 Bourne bluetoothd[1309]: Bluetooth daemon 4.96
Jan 28 16:09:34 Bourne bluetoothd[1318]: Starting SDP server
Jan 28 16:09:34 Bourne bluetoothd[1318]: D-Bus failed to register org.bluez.Proximity interface
Jan 28 16:09:34 Bourne bluetoothd[1318]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Jan 28 16:09:34 Bourne bluetoothd[1318]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Jan 28 16:09:34 Bourne kernel:    15.408328] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 28 16:09:34 Bourne kernel:    15.408331] Bluetooth: BNEP filters: protocol multicast
Jan 28 16:09:34 Bourne bluetoothd[1318]: Listening for HCI events on hci0
Jan 28 16:09:34 Bourne mcelog[1234]: Starting mcelog... ..done
Jan 28 16:09:34 Bourne bluetoothd[1318]: HCI dev 0 up
Jan 28 16:09:34 Bourne bluetoothd[1318]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Jan 28 16:09:34 Bourne kernel:    15.454084] Bluetooth: RFCOMM TTY layer initialized
Jan 28 16:09:34 Bourne kernel:    15.454090] Bluetooth: RFCOMM socket layer initialized
Jan 28 16:09:34 Bourne kernel:    15.454093] Bluetooth: RFCOMM ver 1.11
Jan 28 16:09:34 Bourne nmb[1312]: Starting Samba NMB daemon ..done
Jan 28 16:09:34 Bourne bluetoothd[1318]: Adapter /org/bluez/1309/hci0 has been enabled

I really don’t know for how long this is going to last… I would like to figure out where the problem could be coming from…

Thanks all!