Bluetooth Not Recognized on ArchLinuxARM Install (RPi4)

[gtrmstr53]

Hi there,

I've tried posting this problem on the ArchLinuxARM forum and a couple subreddits a week or two ago, but haven't heard anything back. So please come to my rescue!

Anyways, the problem I'm running into is that ArchLinuxARM doesn't seem to be recognizing my bluetooth device (and maybe not my wifi either; see below).

Some background about my setup: I have a Raspberry Pi 4 and I installed the the RPi4 ArchLinuxARM image (see https://archlinuxarm.org/platforms/armv ... berry-pi-4). I've added a few RPi- and bluetooth-specific packages (firmware-raspberrypi, linux-raspberrypi4, raspberrypi-bootloader, raspberrypi-bootloader-x, raspberrypi-firmware, bluez, bluez-hid2hci, bluez-utils-compat, pi-bluetooth). Let me know if there's other info about my install that might be helpful.

Some specifics about the behaviour I first noticed is when I use bluetoothctl and its list, agent on, and power on commands I get the following output:

Code: Select all

    [thomas@alarmpi ~]$ bluetoothctl
    Agent registered
    [bluetooth]# list
    [bluetooth]# agent on
    Agent is already registered
    [bluetooth]# power on
    No default controller available

This is the main sort of behaviour that made me think that the bluetooth module isn't being recognized, but I've tried a few other bluetoothctl commands that also respond with No default controller available (or similar). Let me know if there's more info at this stage you could use, either from bluetoothctl or from other commands.

I've poked around a little deeper, and the stuff I've turned up seems to reinforce my suspicion that ArchLinuxARM isn't recognizing the bluetooth. I booted the RPi using an SD card with LibreElec installed and was able to discover my cell phone through bluetooth, so that should mean the issue is with my ArchARM install and not with the RasPi hardware.

I've also booted into ArchARM and tried using hcitool, which gave me the following result:

Code: Select all

    hcitool dev
    Devices:

That seems to backup my suspicion that the bluetooth device isn't being recognized in the first place, because otherwise there would be something listed under 'Devices:' (right?).

Finally, I've been using an ethernet connection so far but recently noticed that the wifi card might not be getting recognized also, but I'm not sure about this. When I use lspci, I don't see the wifi card listed:

Code: Select all

[thomas@alarmpi ~]$ lspci -k
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
        Kernel driver in use: pcieport
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)
        Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller
        Kernel driver in use: xhci_hcd

That's what's making me suspect the wifi card isn't being properly recognized. However, when I use ip commands I get information about wlan0. For example:

Code: Select all

[thomas@alarmpi ~]$ ip link show dev wlan0
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

This makes me less certain about the wifi card not being recognized. I haven't dug much deeper than this into the wifi, so let me know if you could use more info or if you think it's a dead end.

Anyways, that's where I'm at at this point. Any pointers you could share would be a huge help. I'm getting antsy to have my USB mouse and speaker connected, as they're about the last essentials I need before I can use the RPi as my pseudo-desktop.

Thanks!

[fruitoftheloom]

Hi there,

I've tried posting this problem on the ArchLinuxARM forum and a couple subreddits a week or two ago, but haven't heard anything back. So please come to my rescue!

Anyways, the problem I'm running into is that ArchLinuxARM doesn't seem to be recognizing my bluetooth device (and maybe not my wifi either; see below).

Some background about my setup: I have a Raspberry Pi 4 and I installed the the RPi4 ArchLinuxARM image (see https://archlinuxarm.org/platforms/armv ... berry-pi-4). I've added a few RPi- and bluetooth-specific packages (firmware-raspberrypi, linux-raspberrypi4, raspberrypi-bootloader, raspberrypi-bootloader-x, raspberrypi-firmware, bluez, bluez-hid2hci, bluez-utils-compat, pi-bluetooth). Let me know if there's other info about my install that might be helpful.

Some specifics about the behaviour I first noticed is when I use bluetoothctl and its list, agent on, and power on commands I get the following output:

Code: Select all

    [thomas@alarmpi ~]$ bluetoothctl
    Agent registered
    [bluetooth]# list
    [bluetooth]# agent on
    Agent is already registered
    [bluetooth]# power on
    No default controller available

This is the main sort of behaviour that made me think that the bluetooth module isn't being recognized, but I've tried a few other bluetoothctl commands that also respond with No default controller available (or similar). Let me know if there's more info at this stage you could use, either from bluetoothctl or from other commands.

I've poked around a little deeper, and the stuff I've turned up seems to reinforce my suspicion that ArchLinuxARM isn't recognizing the bluetooth. I booted the RPi using an SD card with LibreElec installed and was able to discover my cell phone through bluetooth, so that should mean the issue is with my ArchARM install and not with the RasPi hardware.

I've also booted into ArchARM and tried using hcitool, which gave me the following result:

Code: Select all

    hcitool dev
    Devices:

That seems to backup my suspicion that the bluetooth device isn't being recognized in the first place, because otherwise there would be something listed under 'Devices:' (right?).

Finally, I've been using an ethernet connection so far but recently noticed that the wifi card might not be getting recognized also, but I'm not sure about this. When I use lspci, I don't see the wifi card listed:

Code: Select all

[thomas@alarmpi ~]$ lspci -k
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
        Kernel driver in use: pcieport
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)
        Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller
        Kernel driver in use: xhci_hcd

That's what's making me suspect the wifi card isn't being properly recognized. However, when I use ip commands I get information about wlan0. For example:

Code: Select all

[thomas@alarmpi ~]$ ip link show dev wlan0
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

This makes me less certain about the wifi card not being recognized. I haven't dug much deeper than this into the wifi, so let me know if you could use more info or if you think it's a dead end.

Anyways, that's where I'm at at this point. Any pointers you could share would be a huge help. I'm getting antsy to have my USB mouse and speaker connected, as they're about the last essentials I need before I can use the RPi as my pseudo-desktop.

Thanks!

Personally would advise to use Manjaro which uses ArchLinuxArm as it's base:

https://osdn.net/projects/manjaro-arm/storage/rpi4/

[gtrmstr53]

Personally would advise to use Manjaro which uses ArchLinuxArm as it's base:

https://osdn.net/projects/manjaro-arm/storage/rpi4/

Thanks for the pointer. I'm planning to stick with Arch for the time being, because it forces me to dig into things and learn them (and the RPi isn't my main machine so I don't mind the down time).

[gtrmstr53]

Someone got back to me at the ArchARM forum (https://archlinuxarm.org/forum/viewtopi ... 084#p63084), and they've fixed the issue for themselves. I'm still trying to get it to work on my machine, so if anyone wants to look there and see if they have any feedback for me, that'd be amazing. However, I figured the cross post would be useful for anyone who comes across this post with the same issue.

[gtrmstr53]

Quick update. Someone got back to me on reddit (https://www.reddit.com/r/archlinuxarm/c ... erry_pi_4/) and their solution worked for me. I followed the steps here (https://gist.github.com/shenghaoyang/92 ... 3e640663c2) and everything looks to be working great now.