Bluetooth connexion

[Member rmarion37]

Hello,

I have an old machine (emachines em350) with a WIFI/BT card (atheros AR9485, it’s not the original hardware for this computer).
My problem is I’m not able to to use bluetoothctl.

I used rfkill unblock bluetooth to unblock my hardware/software.
With hciconfig hci0 up, I put UP the hardware (I check with hciconfig inq and after the command, my card is UP).
when I use hcitool dev, I have a device hci0 with a MAC address. So OK.
But when I use the command bluetoothctl, no possible to connect to the daemon. I have a message “Waiting to connect to bluetoothd …” without success.

Do you have a idea to connect the bluetooth and use bluetoothctl ?

Thanks by advance.

Rémy

[Member madibi]

Helpful

Up

0

::

Hi,
I’m not a big expert, so I try to spent my 2 cents 🙂

1st question: have you verified the status of your bluetooth with connman UI setup? This is the main tool for wirelss connections in antiX
2nd question: have you tried to use the native antiX program: menu -> applicazioni -> preferenze – gestore bluetooth – (those are the Italian names, I guess that in En they may be: menu – programs – preferences – bluetooth)
3rd question: which hw do you want to connect? sometimes you should write a connection key that depends on the hw you want to connect

m

[Member rmarion37]

Helpful

Up

0

::

Hello,

Thanks for your reply.
In connman UI, I have a green status. But when I enter hciconfig -a in a terminal, my device is DOWN.

hci0: Type: Primary Bus: USB
BD Address: 54:27:1E:AB:61:44 ACL MTU: 1022:8 SCO MTU: 183:5
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT

After entering hciconfig hc0 up, my device is well UP :

hci0: Type: Primary Bus: USB
BD Address: 54:27:1E:AB:61:44 ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING
RX bytes:1685 acl:0 sco:0 events:67 errors:0
TX bytes:757 acl:0 sco:0 commands:62 errors:0

and with rfkill list bluetooth I can verify that my soft and hard are well OK. So, no problem :

2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

But bluetoothctl is still not working. I have the message “Waiting to connect to bluetoothd…”.

May be, it’s a problem with the bluetoothd dameon because when I try to start it in a terminal, I have the message :

“D-Bus setup failed: Connection “:1.11” is not allowed to own the service “org.bluez” due to security policies in the configuration file”

Have you an idea to treat the problem ? My principal aim is to have a blueetooth connection available directly at the boot in a CLI.

Regards.

Rémy

[Member crackulator]

Helpful

Up

0

::

I had the same problem with D-Bus permissions. Comparing to a different, working distro, I discovered that the working one had this file:
/etc/dbus-1/system.d/bluetooth.conf
…which the antiX did not have. So I copied that file over to the non-working system and it seems to have fixed the problem.

• This reply was modified 10 months ago by crackulator.

[Member crackulator]

Helpful

Up

0

::

For some reason, I am unable to either attach the file or post the content of the file.

[Member crackulator]

Helpful

Up

0

::

Here it is.

Attachments:

1. bluetooth.conf_.txt

[Author]

Posts