#Bluetooth Refuses to Work (Details Below)

52 messages · Page 1 of 1 (latest)

olive grove
#

HW/SW info: https://termbin.com/d4qz

I've been having progressively worse bluetooth info over the past week. Today the default manager for Mint started crashing with an error message about it failing to launch something (I didn't think to write it down, since I thought it would be a repeatable error). Afterwards, I did some research and ran dmesg | egrep -i 'blue|firm|btusb'; lsmod | grep bluetooth; hciconfig -a to get info, which currently reads:

[    0.462254] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.486315] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
[    5.732201] iwlwifi 0000:04:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm
[  497.909586] Bluetooth: Core ver 2.22
[  497.909608] NET: Registered PF_BLUETOOTH protocol family
[  497.909609] Bluetooth: HCI device and connection manager initialized
[  497.909613] Bluetooth: HCI socket layer initialized
[  497.909615] Bluetooth: L2CAP socket layer initialized
[  497.909619] Bluetooth: SCO socket layer initialized
[  506.395079] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  506.395083] Bluetooth: BNEP filters: protocol multicast
[  506.395087] Bluetooth: BNEP socket layer initialized
bluetooth            1073152  9 bnep
ecdh_generic           16384  1 bluetooth```

Running `blueman-manger` in terminal yields:
```blueman-manager 20.32.13 ERROR    Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 20.32.13 ERROR    Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting```

I'll be available to run any new commands. I've no clue what's wrong.
olive grove
#

@signal fossil hey, are you able to help me out with this? my bluetooth is thoroughly jacked up lol

olive grove
# signal fossil What results for `lsusb`
Bus 005 Device 003: ID 046d:c547 Logitech, Inc. USB Receiver
Bus 005 Device 002: ID 04d9:0356 Holtek Semiconductor, Inc. Ducky Keyboard
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0b05:1939 ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub```
olive grove
#

same as in the termbin above

#

i should note that i had tried to revert my kernel before (for semi-related reasons), but it didn't work so I timeshifted back to before i changed it

signal fossil
#

Might have to remove and reinstall the wifi card. might be a bad connection to motherboard

olive grove
#

Will do, give me 5

olive grove
signal fossil
#

Is this dual boot with Windows?

olive grove
#

Nope

signal fossil
#

Any different if you power off and then boot compared to a reboot?

olive grove
#

Just checked, same error

signal fossil
#

This could be a hardware issue since it has been getting worse, the newest upstream kernel has the same code as 6.5 for that bluetooth and the dmesg shows nothing about loading the intel bluetooth firmware

olive grove
#

I tried doing some timeshift and grub shenanigans to test whether it was my driver/kernel for that one game, and now it's just flat broken

signal fossil
#

One thing to try> sudo modprobe -r btusb && sleep 5 && sudo modprobe btusb

olive grove
signal fossil
#

Might also want to check BIOS settings for any bluetooth settings

olive grove
#

I just ran sudo /etc/init.d/bluetooth start, and now the manager opens. I got a socket connection error when trying to connect my controller. Removed the controller from devices and re-added it. It connects, now, but none of my games are receiving any input.

Using bluez-tools, running bt-device -l with just the controller conencted gives

GuliKit Controller XW (98:B6:EA:80:A2:C5)```

Additionally, I can connect my bluetooth earbuds perfectly fine. Audio works well.
#

Rebooting reverts all of the above changes.

olive grove
signal fossil
#

There has to be something going on that I am not seeing. Intel Bluetooth usually works well

olive grove
signal fossil
#

You would have had to blacklist btusb and btintel or something more

olive grove
#

Okay, ran an update. sudo /etc/init.d/bluetooth start no longer works. I have no clue what the fuck is wrong anymore.

New sys info: https://termbin.com/fbgy
I also have a list of my packages if needed.

#

Alright, I'm just gonna go through every single thing that I did before this became an issue so that everything is clear.

Everything was fine a couple weeks ago. I was on kernel 6.5.0-17. I needed a vm to run some software, so I enable virtualization and then created a windows 10 vm through virtualbox. I then ran a system update which updated my kernel to 6.5.0-21. After this, for some reason, my controller randomly stopped being detected SM64-coop-dx (an online game through wine, don't even need proton for it). I tried fiddling with it and made a ticket about it. Someone suggested that it could be some weird package issue, so I timeshifted back to about two weeks prior (about a month ago, from today). this fixed the issue, but i no longer had virtual box. i tried running the update again without updating the kernel, and it still caused problems for that one game. I was confused at this point, because none of the other packages were related to bluetooth or wine. for some reason, in my infinitely idiotic wisdom, i decided to try downgrading my kernel. I think this may have been the point where my blueooth broke.

signal fossil
#

Open 2 terminal windows, in one run dmesg -w and in the second one sudo modprobe -v btusb and see if any errors are shown

olive grove
# signal fossil Open 2 terminal windows, in one run `dmesg -w` and in the second one `sudo modpr...

The second command ran normally

insmod /lib/modules/6.5.0-25-generic/kernel/crypto/ecdh_generic.ko 
insmod /lib/modules/6.5.0-25-generic/kernel/net/bluetooth/bluetooth.ko 
insmod /lib/modules/6.5.0-25-generic/kernel/drivers/bluetooth/btmtk.ko 
insmod /lib/modules/6.5.0-25-generic/kernel/drivers/bluetooth/btintel.ko 
insmod /lib/modules/6.5.0-25-generic/kernel/drivers/bluetooth/btbcm.ko 
insmod /lib/modules/6.5.0-25-generic/kernel/drivers/bluetooth/btrtl.ko 
insmod /lib/modules/6.5.0-25-generic/kernel/drivers/bluetooth/btusb.ko```

Interestingly, I did get some wifi/bluetooth errors that could be relevant from the first command (along with an nvidia error that I'll include just in case):
```...
[    5.750821] iwlwifi 0000:04:00.0: WRT: Invalid buffer destination
...
[    9.535778] iwlwifi 0000:04:00.0: WRT: Invalid buffer destination
...
[   23.098439] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000900] Failed to grab modeset ownership
...
[  124.079387] Bluetooth: hci0: Malformed MSFT vendor event: 0x02```

It also seemingly stopped after displaying something labeled [UFW BLOCK], although I don't know if that's normal. I can snag everything currently being displayed if you need it
signal fossil
#

Can you disable UFW and see if things work then?

olive grove
# signal fossil Can you disable UFW and see if things work then?

Okay, that fixed part of the problem. The error "br-connection-create-socket" when initially connecting the controller no longer appears. However, the controller still doesn't work.

If already previously paired and trusted, it will connect and immediately disconnect. If re-paired, it will remain connected, but not work on any games.

#

Okay, so, even though that error is sorted, the bluez manager still crashes after a reboot.

#

It feels like there's like three or four different problems happening at the same time...

signal fossil
#

Try opening through terminal with blueman-manager and see if some other info is revealed

olive grove
signal fossil
#

It may be worth trying in terminal sudo rm -r /var/lib/bluetooth/*

#

Then reboot

olive grove
signal fossil
#

Might be time for a USB dongle for Bluetooth, like the Edimax bt8500

olive grove
#

Frick. This is a really weird way for my widi/bt card to shit iself lol

#

it's been maybe a year since i got it, but it was cheap, so

signal fossil
#

Intel is normally solid in wifi/bt cards

olive grove
#

yea, idk. maybe some other part of the card failed

#

it was probably like 40 bucks

#

why tne heck did timeshift change anything, though...

#

i might try a fresh install on a different hard drive, just to be sure

signal fossil
#

Only reason timeshift could have helped is if some config or driver was messed up