Arch Linux

Vins

Member

From: Italy

Registered: 2005-12-14

Posts: 67

Bluetooth - PC not discoverable. SOLVED! READ THIS!

Hi all,

bluetooth is really driving me crazy. My PC was not discoverable anymore, even if I had "iscan enable; pscan enable" in my hcid.conf.

To solve this issue I added the following line in the hcid.conf (device section):

discovto 0;

Now the PC is discoverable again. Hope it helps!

V.

nicholai

Member

Registered: 2005-04-26

Posts: 51

Re: Bluetooth - PC not discoverable. SOLVED! READ THIS!

Had the same problem. My solution was to specify the class with hciconfig

#hciconfig hci0 class 0x3e0100

Even though it's included in the hcid.conf I still have to set it once in a while.

Might help some one else too.

/Nic

---

Desktop :Athlon64       2.2 GHz
Laptop   :Toshiba R100    1GHz

nicholai

Member

Registered: 2005-04-26

Posts: 51

Re: Bluetooth - PC not discoverable. SOLVED! READ THIS!

Actually, I think I discovered the Mother of all Bluetooth problems (at least in my case). The hcid daemon, which is initiated with the /etc/rc.d/bluetooth script, depends on dbus! Problem is it does not give any error if dbus isn't running. The result is that most of the settings from /etc/bluetooth/hcid.conf is not read.

Would it be a solution to add dbus as an depency in the bluetooth script and where would be the proper place to propose that?

Regards,

Nicholai

---

Desktop :Athlon64       2.2 GHz
Laptop   :Toshiba R100    1GHz

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: Bluetooth - PC not discoverable. SOLVED! READ THIS!

It would not be a dependency, but the script should check whether dbus is running.

As this script is AL-specific, it's an AL problem.

File a bugreport in flyspray : http://bugs.archlinux.org/

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)