Issue with BT: will not enable

Bazzite
1

Hi,

I have been using Bazzite for some tome now, so i don’t know if this issue happened before or not. I am not able to get BT to enable (and I also noticed my wifi controller does not show as well).
I notice this a few days ago when I wanted to try using a controller for a game. Went to System settings and hit the toggle but, BT never enables. I checked that BT was enabled in the Bios, check on Windows and BT worked there and connected a few devices. Came back to bazzite and nada (I am using Secure Boot, if that matters).

I dislike jumping into windows just to play with a controller, but I am new to linux so feel free to communicate to me like I am stupid, I wont take offense if it helps me resolve this issue and if it helps you as well.

sudo dmesg | grep -i bluetooth
[sudo] password for gmngpc: 
[    0.000000] Command line: BOOT_IMAGE=(hd1,gpt2)/ostree/default-f496e7bd941c8b42b7d32ef8e53ee38a860e47f5eeec00b2ccaab2cf7bf5f419/vmlinuz-6.17.7-ba28.fc43.x86_64 rhgb quiet root=UUID=ee4fd530-b30f-43c2-b1b9-011101a27cbe rootflags=subvol=root rw ostree=/ostree/boot.1/default/f496e7bd941c8b42b7d32ef8e53ee38a860e47f5eeec00b2ccaab2cf7bf5f419/0 bluetooth.disable_ertm=1
[    0.044784] Kernel command line: BOOT_IMAGE=(hd1,gpt2)/ostree/default-f496e7bd941c8b42b7d32ef8e53ee38a860e47f5eeec00b2ccaab2cf7bf5f419/vmlinuz-6.17.7-ba28.fc43.x86_64 rhgb quiet root=UUID=ee4fd530-b30f-43c2-b1b9-011101a27cbe rootflags=subvol=root rw ostree=/ostree/boot.1/default/f496e7bd941c8b42b7d32ef8e53ee38a860e47f5eeec00b2ccaab2cf7bf5f419/0 bluetooth.disable_ertm=1
[    0.692775] integrity: Loaded X.509 cert 'Bazzite Bluetooth Signing: 4b21b8017533bb03d9959ba7cf12ea778e441698'
[    7.840465] Bluetooth: Core ver 2.22
[    7.840480] NET: Registered PF_BLUETOOTH protocol family
[    7.840480] Bluetooth: HCI device and connection manager initialized
[    7.840485] Bluetooth: HCI socket layer initialized
[    7.840486] Bluetooth: L2CAP socket layer initialized
[    7.840488] Bluetooth: SCO socket layer initialized
[    8.139381] Bluetooth: hci0: Opcode 0x0c03 failed: -16
[   29.424352] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.424355] Bluetooth: BNEP filters: protocol multicast
[   29.424358] Bluetooth: BNEP socket layer initialized


lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1b1c:0a6b Corsair CORSAIR HS80 RGB Wireless Gaming Receiver
Bus 001 Device 003: ID 1532:0244 Razer USA, Ltd RZ07-0311 Gaming Keypad [Tartarus Pro]
Bus 001 Device 004: ID 0489:e13a Foxconn / Hon Hai Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 003: ID 174c:2174 ASMedia Technology Inc. ASMT2307
Bus 003 Device 004: ID 0b05:1b9b ASUSTek Computer, Inc. USB Audio
Bus 003 Device 005: ID 19f7:001c RODE Microphones RØDE VideoMic GO II
Bus 003 Device 006: ID 0b05:1aa6 ASUSTek Computer, Inc. AURA LED Controller
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 003: ID 0bc2:2320 Seagate RSS LLC USB 3.0 bridge [Portable Expansion Drive]
Bus 004 Device 004: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 005: ID 174c:3174 ASMedia Technology Inc. ASMT2307
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 0b05:1bd7 ASUSTek Computer, Inc. USB2.1 Hub
Bus 009 Device 003: ID 0b05:1bca ASUSTek Computer, Inc. ROG Gaming Display Aura Device
Bus 009 Device 004: ID 0bda:1100 Realtek Semiconductor Corp. HID Device
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 0b05:1bd7 ASUSTek Computer, Inc. USB3.2 Hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub


Operating System: Bazzite 43
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.17.7-ba28.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 9950X3D 16-Core Processor
Memory: 64 GiB of RAM (60.5 GiB usable)
Graphics Processor 1: AMD Radeon RX 9070 XT
Graphics Processor 2: AMD Ryzen 9 9950X3D 16-Core Processor
Manufacturer: ASUS
Model: ROG STRIX X870E-E GAMING WIFI
2

I have the same problem posted here

Try this command

sudo rmmod btusb
sudo modprobe btusb

It should help.

Other then that i recommend rebasing back to 43.20260217 if you don’t want to do it each reboot.

3

Thank you. I tried them but I am still having the issue. It just doesn’t enable at all. Weird.

4

try workaround here: No bluetooth after update · Issue #3112 · ublue-os/bazzite · GitHub

….the workaround is so-called cold reset, shutting off and removing power cable for 30 seconds….

funny but it works

5

I have this same issue. Sometimes after booting up my PC, bluetooth simply wont appear on taskbar and checking from settings to enable it, it wont turn on. Restarting my PC after this occurs most of the time fixes it, it’s like roulette.

6

@Tgen_Matt @Alt thanks for the suggestions. I will try that and see.

Thanks for taking your time to reply. I am open to trying anything.

7

Hi everyone.

I have tried your suggestions but it still does not enable. For what I understand, my BT device does not initiate. It is there and it can be seen but it does not initiate in Bazzite.

Mar 23 20:29:17 bazzite kernel: Bluetooth: hci0: Opcode 0x0c03 failed: -16

I tried:

sudo rmmod btusb
sudo modprobe btusb

I also tried a cold rest.

And I made sure the devices are enabled, not in auto like in some asrocks mobos. Mine is an ASUS and the devices can only be enabled or disabled. And they are enabled and working on Windows.

I guess I am stuck for now with Windows since I got me some Crimson Desert and I play other games that are “better” with a controller. If anyone needs me to find some other logs or send me some info, I am open to helping out!

Thanks everyone for the suggestion, I appreciate your time.

8

I see someone already gave you a similar answer, but I’ll write what I do and what can be done.

Completely disconnect the power from the outlet or switch the power switch to OFF. Hold the start button for a few seconds and then try to turn the device on. If it still doesn’t appear, check whether the Bluetooth/Wi‑Fi switch is enabled in the system. For me, from time to time, especially after updates, Bluetooth disappears and I have to do something like this so everything shows up again — after later restarts or shutdowns I don’t have any problems.

the software developers for the Wi‑Fi/Bluetooth card need to fix this, but I doubt they feel like doing it.