I've been following the UX31 and Bluetooth wiki pages and I'm trying to pair my earpiece/headset (a crappy one no doubt, but it pairs perfectly with my android phone and with my Playstation 3). I've tried discovering my phone as well, but nothing. The phone scan isn't able to see the laptop either, and I've enabled discovery in the GNOME bluetooth config.
I've installed dbus, and my rc.conf lists "dbus bluetooth" in that order inside the DAEMONS line. This is the output of hciconfig:
hci0: Type: BR/EDR Bus: USB BD Address: 74:2F:68:CE:81:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:1351 acl:0 sco:0 events:58 errors:0 TX bytes:985 acl:0 sco:0 commands:58 errors:0
Here's the output of rfkill list:
0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 2: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no
The above struck me as a bit odd... Why is it listing two separate bluetooth interfaces? I even tried running bluetoothd -nd and looked for anything curious in the output while I was running hcitool scan but nothing jumped out at me.
Help! If more information is required please let me know and I'll get it.
Last edited by regulatethis (2012-02-17 05:49:11)
Have you figured out what is wrong?
I am having the same problem. Everything seems to load correctly, but no devices are detected.
/var/log/messages.log file shows the following on startup:
eb 23 10:43:30 localhost blueman-mechanism: Starting blueman-mechanism Feb 23 10:43:30 localhost dbus: [system] Successfully activated service 'org.blueman.Mech anism' Feb 23 10:43:30 localhost blueman-mechanism: loading Network Feb 23 10:43:30 localhost blueman-mechanism: loading Ppp Feb 23 10:43:30 localhost blueman-mechanism: loading RfKill Feb 23 10:43:30 localhost blueman-mechanism: loading Config Feb 23 10:44:00 localhost blueman-mechanism: Exiting
hci0: Type: BR/EDR Bus: USB BD Address: E0:B9:A5:D2:9C:B1 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:844 acl:0 sco:0 events:35 errors:0 TX bytes:646 acl:0 sco:0 commands:35 errors:0
RfKill shows everything on; it also shows two bluetooth devices for some reason.
rfkill list 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 2: asus-wlan: Wireless LAN Soft blocked: yes Hard blocked: no 3: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 5: hci0: Bluetooth Soft blocked: no Hard blocked: no
Is hci0 the wrong device to use? Should the asus-bluetooth device be used instead? How do you switch to it if that's the case?
There was a lot of talk about having to modify the kernel on the ubuntu last fall, https://help.ubuntu.com/community/AsusZenbook, so I have tried the latest kernel, 3.2.7-1-ARCH, available as test under archlinux, but no change or improvement.
So I checked the latest kernel and found out that the patch suggested on this page (look for Fryie)
had not made it into the test kernel 3.2.7-1-ARCH I had installed - well bluetooth scanned but did not work...
So I got the latest kernel source using abs and ABSROOT=. abs core/linux
This apparently got me 3.2.6-2 instead of the recently released 3.2.7-1-ARCH which kind of surprised me.
Anyways, following the archlinux wiki and the changes suggested at the post listed earlier, I was able to rebuild the kernel and now bluetooth works for my mouse and apparently for my phone (though I am having trouble transfering a file - probably user error :-)
Hopefully, the patch will make it into the next kernel release. From this post, it should http://thread.gmane.org/gmane.linux.bluez.kernel/18801
Just want to mention that I had the same issue on the UX31, and that random.bit's solution solved it for me as well (3.2.8 kernel).
EDIT: I've just discovered that there is a custom kernel in the AUR that incorporates this patch along with a few others for Zenbook compatibility:
Last edited by lichengeese (2012-03-02 13:28:03)
I had the same issue for several month.
my device: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Today I wanted to use the bluetooth so I did a Bluez git bisect and found that the offending commit is 5b1a2a39dc7710f5a58e4f676389fea06764800b
Fix event mask setting for 1.1 controllers Controllers based on the core spec 1.1 support the event mask HCI command but need a very stripped down default value for the mask. This patch makes sure the command gets issued for 1.1 controllers with the appropriate value.
Can you try the last version that works for me?
Γίνε ρεαλιστής, μείνε ονειροπόλος ...