something change in the bluetooth service? I can't seem to enable it today

T

termdiscOP•1/17/24, 6:34 PM

:testing branch

T

termdiscOP•1/17/24, 6:34 PM

(~) >>> rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

(~) >>> rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

(~) >>> rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

(~) >>> rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Ttermdisc something change in the bluetooth service? I can't seem to enable it today

K

Kyle Gospo•1/17/24, 6:35 PM

nada

K

Kyle Gospo•1/17/24, 6:35 PM

let me double check on deck

T

termdiscOP•1/17/24, 6:37 PM

this is on my desktop

T

termdiscOP•1/17/24, 6:37 PM

the Deck is still working as I paired a controller this morning

B

BrenIngham•1/17/24, 6:37 PM

can you do anything with bluetoothctl ?

K

Kyle Gospo•1/17/24, 6:37 PM

yeah working fine here

BBrenIngham can you do anything with bluetoothctl ?

T

termdiscOP•1/17/24, 6:38 PM

what can I do from here?

Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]#

Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]#

KKyle Gospo yeah working fine here

T

termdiscOP•1/17/24, 6:38 PM

I was able to connect a controller as recently as 1.12 How to safely downgrade bluez?

B

BrenIngham•1/17/24, 6:38 PM

if you type list , you will see your controllers

T

termdiscOP•1/17/24, 6:38 PM

[bluetooth]# list
[bluetooth]#

[bluetooth]# list
[bluetooth]#

B

BrenIngham•1/17/24, 6:39 PM

looks like the driver failed to load, is there anything in dmesg?

T

termdiscOP•1/17/24, 6:40 PM

(~) >>> dmesg | grep -i blue
[    6.657480] Bluetooth: Core ver 2.22
[    6.659002] NET: Registered PF_BLUETOOTH protocol family
[    6.659005] Bluetooth: HCI device and connection manager initialized
[    6.659009] Bluetooth: HCI socket layer initialized
[    6.659012] Bluetooth: L2CAP socket layer initialized
[    6.659020] Bluetooth: SCO socket layer initialized
[    8.744256] Bluetooth: hci0: Reading Intel version command failed (-110)
[    9.335652] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.335656] Bluetooth: BNEP filters: protocol multicast
[    9.335660] Bluetooth: BNEP socket layer initialized

(~) >>> dmesg | grep -i blue
[    6.657480] Bluetooth: Core ver 2.22
[    6.659002] NET: Registered PF_BLUETOOTH protocol family
[    6.659005] Bluetooth: HCI device and connection manager initialized
[    6.659009] Bluetooth: HCI socket layer initialized
[    6.659012] Bluetooth: L2CAP socket layer initialized
[    6.659020] Bluetooth: SCO socket layer initialized
[    8.744256] Bluetooth: hci0: Reading Intel version command failed (-110)
[    9.335652] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.335656] Bluetooth: BNEP filters: protocol multicast
[    9.335660] Bluetooth: BNEP socket layer initialized

(~) >>> dmesg | grep -i blue
[    6.657480] Bluetooth: Core ver 2.22
[    6.659002] NET: Registered PF_BLUETOOTH protocol family
[    6.659005] Bluetooth: HCI device and connection manager initialized
[    6.659009] Bluetooth: HCI socket layer initialized
[    6.659012] Bluetooth: L2CAP socket layer initialized
[    6.659020] Bluetooth: SCO socket layer initialized
[    8.744256] Bluetooth: hci0: Reading Intel version command failed (-110)
[    9.335652] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.335656] Bluetooth: BNEP filters: protocol multicast
[    9.335660] Bluetooth: BNEP socket layer initialized

(~) >>> dmesg | grep -i blue
[    6.657480] Bluetooth: Core ver 2.22
[    6.659002] NET: Registered PF_BLUETOOTH protocol family
[    6.659005] Bluetooth: HCI device and connection manager initialized
[    6.659009] Bluetooth: HCI socket layer initialized
[    6.659012] Bluetooth: L2CAP socket layer initialized
[    6.659020] Bluetooth: SCO socket layer initialized
[    8.744256] Bluetooth: hci0: Reading Intel version command failed (-110)
[    9.335652] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.335656] Bluetooth: BNEP filters: protocol multicast
[    9.335660] Bluetooth: BNEP socket layer initialized

T

termdiscOP•1/17/24, 6:40 PM

(~) >>> dmesg | grep -i ax200
[    7.018469] iwlwifi 0000:28:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340

(~) >>> dmesg | grep -i ax200
[    7.018469] iwlwifi 0000:28:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340

B

BrenIngham•1/17/24, 6:42 PM

do you have the bluetooth module loaded? you can see with

lsmod

lsmod

T

termdiscOP•1/17/24, 6:44 PM

looks like it

(~) >>> lsmod | grep blue
bluetooth            1060864  17 btrtl,btmtk,btintel,btbcm,bnep,btusb
rfkill                 40960  13 iwlmvm,bluetooth,cfg80211

(~) >>> lsmod | grep blue
bluetooth            1060864  17 btrtl,btmtk,btintel,btbcm,bnep,btusb
rfkill                 40960  13 iwlmvm,bluetooth,cfg80211

(~) >>> lsmod | grep blue
bluetooth            1060864  17 btrtl,btmtk,btintel,btbcm,bnep,btusb
rfkill                 40960  13 iwlmvm,bluetooth,cfg80211

(~) >>> lsmod | grep blue
bluetooth            1060864  17 btrtl,btmtk,btintel,btbcm,bnep,btusb
rfkill                 40960  13 iwlmvm,bluetooth,cfg80211

B

BrenIngham•1/17/24, 6:44 PM

hmm, so that's an affirmative

T

termdiscOP•1/17/24, 6:45 PM

that's what's confusing me. everything points to it being available except for actually being able to using it

B

BrenIngham•1/17/24, 6:46 PM

have you tried turning it off and on again? kek

(no but seriously i'vepreviously had countless issues with the ax200 wifi card, do a hard reboot, shutdown, pull cord/turn off at switch wait ~15secs and then try again)

T

termdiscOP•1/17/24, 6:46 PM

I have rebooted, but I have not shut down to a cold state yet

KKyle Gospo fixed friday

L

linux_doggo•1/17/24, 6:47 PM

gaming

B

BrenIngham•1/17/24, 6:47 PM

i think the ax200 has an issue where it wont be detected if fastboot is enabled on windows before you reboot into linux (thats the issue i had anyway) no idea if that translates over to bluetooth

T

termdiscOP•1/17/24, 6:48 PM

I haven't booted into Windows in a while, and I haven't messed with the BIOS either

T

termdiscOP•1/17/24, 6:49 PM

I'm connected to a wifi network right now as well

B

BrenIngham•1/17/24, 6:49 PM

is secureboot enabled, and have you enrolled the ublue key?

T

termdiscOP•1/17/24, 6:49 PM

I don't know to both

T

termdiscOP•1/17/24, 6:49 PM

I did see that on the changelog, so I should probably get on that

B

BrenIngham•1/17/24, 6:50 PM

you can see if secure boot is enabled by doing

mokutil --sb-state

mokutil --sb-state

T

termdiscOP•1/17/24, 6:50 PM

disabled

B

BrenIngham•1/17/24, 6:50 PM

okidoke...last thing i can think of, is the bluetooth systemd service working?

T

termdiscOP•1/17/24, 6:51 PM

(~) >>> 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 2024-01-17 12:27:06 CST; 23min ago
       Docs: man:bluetoothd(8)
   Main PID: 1243 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38303)
     Memory: 2.1M
        CPU: 52ms
     CGroup: /system.slice/bluetooth.service
             └─1243 /usr/libexec/bluetooth/bluetoothd

Jan 17 12:27:06 hearteater bluetoothd[1243]: Starting SDP server
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: Bluetooth management interface 1.22 initialized
Jan 17 12:27:06 hearteater systemd[1]: Started bluetooth.service - Bluetooth service.

(~) >>> 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 2024-01-17 12:27:06 CST; 23min ago
       Docs: man:bluetoothd(8)
   Main PID: 1243 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38303)
     Memory: 2.1M
        CPU: 52ms
     CGroup: /system.slice/bluetooth.service
             └─1243 /usr/libexec/bluetooth/bluetoothd

Jan 17 12:27:06 hearteater bluetoothd[1243]: Starting SDP server
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: Bluetooth management interface 1.22 initialized
Jan 17 12:27:06 hearteater systemd[1]: Started bluetooth.service - Bluetooth service.

(~) >>> 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 2024-01-17 12:27:06 CST; 23min ago
       Docs: man:bluetoothd(8)
   Main PID: 1243 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38303)
     Memory: 2.1M
        CPU: 52ms
     CGroup: /system.slice/bluetooth.service
             └─1243 /usr/libexec/bluetooth/bluetoothd

Jan 17 12:27:06 hearteater bluetoothd[1243]: Starting SDP server
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: Bluetooth management interface 1.22 initialized
Jan 17 12:27:06 hearteater systemd[1]: Started bluetooth.service - Bluetooth service.

(~) >>> 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 2024-01-17 12:27:06 CST; 23min ago
       Docs: man:bluetoothd(8)
   Main PID: 1243 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38303)
     Memory: 2.1M
        CPU: 52ms
     CGroup: /system.slice/bluetooth.service
             └─1243 /usr/libexec/bluetooth/bluetoothd

Jan 17 12:27:06 hearteater bluetoothd[1243]: Starting SDP server
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 17 12:27:06 hearteater bluetoothd[1243]: Bluetooth management interface 1.22 initialized
Jan 17 12:27:06 hearteater systemd[1]: Started bluetooth.service - Bluetooth service.

T

termdiscOP•1/17/24, 6:51 PM

even after restarting the service

T

termdiscOP•1/17/24, 6:51 PM

weird...

T

termdiscOP•1/17/24, 6:53 PM

gonna go into bios and disable/enable it to see if that does anything

B

BrenIngham•1/17/24, 6:54 PM

i found this https://unix.stackexchange.com/questions/562602/bluetooth-wont-work-hci0-reading-intel-version-information-failed

Unix & Linux Stack Exchange

Bluetooth won't work: "hci0 Reading Intel version information failed"

I had bluetooth working fine till today when I needed to add a USB storage device. The usb device didn't work, the system couldn't see it (lsblk didn't show anything). So tried rebooting the system.

B

BrenIngham•1/17/24, 6:54 PM

based of something i saw in your dmesg

Ttermdisc gonna go into bios and disable/enable it to see if that does anything

T

termdiscOP•1/17/24, 7:03 PM

this did it (based on https://superuser.com/a/1451102)

BBrenIngham i found this https://unix.stackexchange.com/questions/562602/bluetooth-wont-work...

T

termdiscOP•1/17/24, 7:03 PM

this was still being reported when I had disabled the wifi/bt controller

T

termdiscOP•1/17/24, 7:04 PM

back to life now

message.txt1.96KB

T

termdiscOP•1/17/24, 7:04 PM

it's a modification of the turn it off and on solution again hahah

T

termdiscOP•1/17/24, 7:04 PM

thanks for working it through with me

Ttermdisc this did it (based on https://superuser.com/a/1451102)

K

Kyle Gospo•1/17/24, 7:05 PM

I love computers

B

BrenIngham•1/17/24, 7:09 PM

still think cutting power for 15secs would have solved

glad you got it sorted

BBrenIngham still think cutting power for 15secs would have solved 😆 glad you got it sorte...

T

termdiscOP•1/17/24, 7:10 PM

you see that would've involved bending over under the desk

B

BrenIngham•1/17/24, 7:10 PM

fair

T

termdiscOP•1/17/24, 7:11 PM

TIL DualSense features work via Bluetooth now

B

BrenIngham•1/17/24, 7:12 PM

if anyone cares, stadia controllers work pretty well, if you have one gathering dust - even vibrating works

KKyle Gospo I love computers

C

CharlieBros•1/17/24, 7:31 PM

When I had a 2014 Macbook Pro, I installed windows for some stuff, but after the first boot, if for whatever reason, you let the computer go to sleep, it will slow down really fast, like, you log in, and in 5 seconds everything crawls done to the point that you think is frozen. Doesn't matter how many times you reboot, it will just simply stop moving. The issue? The driver of the wifi chipset. When the PC goes to sleep, Windows applies the low power profile, problem is, the driver doesn't know to handle that, neither does the WiFi card, at least in windows, so when you go back from sleep, the driver will reset infinitely to the point that will use the entire CPU and everything else, as the driver never goes back from sleep, Windows can never go back to performance mode

C

CharlieBros•1/17/24, 7:32 PM

The solution was to, at the first boot, IMMEDIATELY apply a permanent high performance mode

something change in the bluetooth service? I can't seem to enable it today

Similar Threads

Similar Threads

Similar Threads