Bluetooth - no default controller

Hi all. trying to use some bluetooth headphones and struggling to connect them.
Bluetooth works fine on Windows and, as far as I can tell, should be working with linux…
Any ideas for next steps? I’m relatively new to linux… I’ve reached the limit of my google/chatGPT finds.

Any help appreciated!!!

specs:
ASRock X670e pro RS
4.18.0-477.15.1.el8_8.x86_64

$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
$ rfkill list all
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor p>
   Active: active (running) since Tue 2023-08-08 12:40:21 EDT; 30min ago
     Docs: man:bluetoothd(8)
 Main PID: 1469 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 815528)
   Memory: 2.5M
   CGroup: /system.slice/bluetooth.service
           └─1469 /usr/libexec/bluetooth/bluetoothd

Aug 08 12:40:21 * systemd[1]: Starting Bluetooth service...
Aug 08 12:40:21 * bluetoothd[1469]: Bluetooth daemon 5.63
Aug 08 12:40:21 * bluetoothd[1469]: Starting SDP server
Aug 08 12:40:21 * systemd[1]: Started Bluetooth service.
Aug 08 12:40:21 * bluetoothd[1469]: Bluetooth management interface 1.21 i>
$ dmesg | grep Bluetooth
[   13.131698] Bluetooth: Core ver 2.22
[   13.131707] Bluetooth: HCI device and connection manager initialized
[   13.131708] Bluetooth: HCI socket layer initialized
[   13.131710] Bluetooth: L2CAP socket layer initialized
[   13.131712] Bluetooth: SCO socket layer initialized
[   13.536239] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.536241] Bluetooth: BNEP filters: protocol multicast
[   13.536244] Bluetooth: BNEP socket layer initialized
$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

most bluetooth controllers are USB, run the command lsusb -v and look for a USB controller.
On my desktop computer I have a USB bluetooth controller in a SDcard reader 3.5 inch floppy disk driver format insert in the computers case, and it gives me the following (only top few lines shown as its quite long)
Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a12 Cambridge Silicon Radio, Ltd
idProduct 0x0001 Bluetooth Dongle (HCI mode)
bcdDevice 31.64
and the systemctl status is as follows.

systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Wed 2023-08-09 10:14:56 BST; 29min ago
Docs: man:bluetoothd(8)
Main PID: 1310 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 38233)
Memory: 2.4M
CPU: 54ms
CGroup: /system.slice/bluetooth.service
└─1310 /usr/libexec/bluetooth/bluetoothd

Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/sbc_xq
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc_xq
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/faststream
Aug 09 10:15:37host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/faststream_duplex
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/opus_05
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/opus_05
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Aug 09 10:15:37 host bluetoothd[1310]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Aug 09 10:15:38 host bluetoothd[1310]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down

bluetoothctl
Agent registered
[bluetooth]# show
Controller 00:15:83:3D:0A:57 (public)
Name: host
Alias: host
Class: 0x006c0104 (7078148)
Powered: yes
PowerState: on
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0544
Discovering: no

rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

and mine is working fine, via KDE’s bluetooth panel.

update quick look on your board and I believe the wifi module is an The Intel AX210 chipset.
if thats correct its not supported until kernel 5.10 so an upgrade to rocky 9 may be the simplest solution.

and that will be the reason its not working.

regards peter

Sorry I missed this, I appreciate the reply. it’s actually mediatek, not Intel. I am considering switching to 9. thanks for the input. One distint difference between our output above is when you run ‘show’ for bluetoothctl, you get a controller. mind can’t fine the controller. I’m assuming that’s the root of it.

same problem then as the intel i mentioned
needs kernel 5.17 as detailed in this link

as that will be the MT7922A22M acording to searches i have found.

then i searched to check if you can install 5.17 on rocky 8 (well i searched on rhel8/centos 8, but you get the jist.
and i found this.

so rather than do all that work to see if it fixes your problem why not try an upgraded kernel first and see if that fixes the problem, then you can consider EL9 upgrade, but hold off a few people have been having issues with 9.2, so may be worth seeing if that problem resolves itself and just get the kernel for now.
regards peter

Really appreciate all the input!