Arch Linux

depletedKnowledge

Member

Registered: 2021-11-21

Posts: 1

bluetooth issue (change systemd boot order?)

Hello, I am having difficulties configuring bluetooth in my fresh installation, looking around to fix the issue I got across this page on archWiki, it says "Some Bluetooth cards (e.g. Broadcom) conflict with the network adapter. Thus, you need to make sure that your Bluetooth device gets connected before the network service boot.". I think I messed up the boot order in systemd not knowingly and set my network manager to boot first than my bluetooth service. Searched for a fix in how to change the systemd boot order, but found nothing actually connected to my problem, this is the closest I got but still. https://wiki.archlinux.org/title/system … ot_manager.
In the beginning I thought maybe linux-firmware just does not support my bluetooth device anymore, tried this

sudo dmesg | grep -i bluetooth

and got this output:

[    2.546076] Bluetooth: Core ver 2.22
[    2.546139] NET: Registered PF_BLUETOOTH protocol family
[    2.546141] Bluetooth: HCI device and connection manager initialized
[    2.546145] Bluetooth: HCI socket layer initialized
[    2.546147] Bluetooth: L2CAP socket layer initialized
[    2.546153] Bluetooth: SCO socket layer initialized
[    3.687912] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.687915] Bluetooth: BNEP filters: protocol multicast
[    3.687919] Bluetooth: BNEP socket layer initialized
[    3.688289] random: bluetoothd: uninitialized urandom read (4 bytes read)
[    4.829605] Bluetooth: hci0: Reading Intel version command failed (-110)
[    4.832890] Bluetooth: hci0: command tx timeout

It doesn't even recognize my bluetooth card (for some context, I have an acer helios 300)

Already installed:

 linux-firmware bluez bluez-utils pulseaudio pulseaudio-bluetooth

Any help you could give would be greatly appreciated!

burafino

Member

From: London

Registered: 2009-12-07

Posts: 19

Website

Re: bluetooth issue (change systemd boot order?)

Check this thread. It's a kernel bug. Waiting for a fix. For now, putting the computer to sleep and waking it up again makes BT work for me.