[RESOLVED] bluetooth not working properly
txirrindulari
Status: New User - Welcome
Joined: 17 Feb 2022
Posts: 4
Reply Quote
I have recently changed the generic kernel from ubuntu 21.10 to liquorix 5.16-8ubuntu1~impish, but the bluetooth works very badly and I don't know what I should look for to make it work the same as the generic version.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4075
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Start with showing: inxi -bExz

that will show your bluetooth and basic system info.

If for some reason inxi -bExz doesn't work, try: -bxz but that means your system is probably too old anyway to run liquorix.
Back to top
txirrindulari
Status: New User - Welcome
Joined: 17 Feb 2022
Posts: 4
Reply Quote
I think this is the relevant info from inxi

:: Code ::

System:
  Kernel: 5.16.0-9.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 11.2.0
  Desktop: GNOME 40.5 Distro: Ubuntu 21.10 (Impish Indri)
Network:
  Device-1: Intel Ethernet I218-V vendor: Micro-Star MSI driver: e1000e
  v: kernel port: f080 bus-ID: 00:19.0
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: b000
  bus-ID: 09:00.0
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
  v: 0.8 bus-ID: 3-8:7
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1
  lmp-v: 4.0

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 982
Reply Quote
Hmm, that sounds like you might have an imbalance between the newer kernel and older firmware.

What's the output of sudo journalctl -k | grep -i firmware?

Also separately, the output of sudo journalctl -k | grep -i bluetooth.
Back to top
txirrindulari
Status: New User - Welcome
Joined: 17 Feb 2022
Posts: 4
Reply Quote
This is what I got;

sudo journalctl -k | grep -i bluetooth
systemd-sysv-generator[379]: Native unit for bluetooth.service already exists, skipping.
systemd-sysv-generator[379]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
systemd-sysv-generator[379]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
systemd-sysv-generator[379]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
systemd-sysv-generator[379]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.
systemd[1]: unit_file_build_name_map: alias: /etc/systemd/system/dbus-org.bluez.service → bluetooth.service
kernel: Bluetooth: Core ver 2.22
kernel: NET: Registered PF_BLUETOOTH protocol family
kernel: Bluetooth: HCI device and connection manager initialized
kernel: Bluetooth: HCI socket layer initialized
kernel: Bluetooth: L2CAP socket layer initialized
kernel: Bluetooth: SCO socket layer initialized
kernel: Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 2 week 3 2013
kernel: Bluetooth: hci0: Intel device is already patched. patch num: 57
kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
kernel: Bluetooth: BNEP filters: protocol multicast
kernel: Bluetooth: BNEP socket layer initialized
kernel: Bluetooth: RFCOMM TTY layer initialized
kernel: Bluetooth: RFCOMM socket layer initialized
kernel: Bluetooth: RFCOMM ver 1.11
systemd-sysv-generator[7296]: Native unit for bluetooth.service already exists, skipping.
systemd-sysv-generator[7296]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
systemd-sysv-generator[7296]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
systemd-sysv-generator[7296]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
systemd-sysv-generator[7296]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.
systemd-sysv-generator[7321]: Native unit for bluetooth.service already exists, skipping.
systemd-sysv-generator[7321]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
systemd-sysv-generator[7321]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
systemd-sysv-generator[7321]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
systemd-sysv-generator[7321]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.
systemd-sysv-generator[7381]: Native unit for bluetooth.service already exists, skipping.
systemd-sysv-generator[7381]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
systemd-sysv-generator[7381]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
systemd-sysv-generator[7381]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
systemd-sysv-generator[7381]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.
systemd-sysv-generator[7414]: Native unit for bluetooth.service already exists, skipping.
systemd-sysv-generator[7414]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
systemd-sysv-generator[7414]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
systemd-sysv-generator[7414]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
systemd-sysv-generator[7414]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.

sudo journalctl -k | grep -i firmware

kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
kernel: iwlwifi 0000:09:00.0: loaded firmware version 17.3216344376.0 7260-17.ucode op_mode iwlmvm

thank you for your help
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 982
Reply Quote
Your system seems to be fine and you have the latest firmware, so most likely you're experiencing a kernel regression. Searching bugzilla lead me to this open issue: bugzilla.kernel.org/show_bug.cgi?id=203535. They recommend disabling btusb's autosuspend with:

:: Code ::
echo 'options btusb enable_autosuspend=0' | sudo tee /etc/modprobe.d/bluetooth.conf


Then reboot.

Also, did you get the output from those two commands after you had experienced problems with bluetooth? Typically you'll see a lot of log entries when something's going wrong, but if you pulled those logs right after booting then everything will look hunky dorey.

One last thing, can you provide the output of sudo journalctl -u bluetooth -b0 after using whichever bluetooth device that's problematic?
Back to top
txirrindulari
Status: New User - Welcome
Joined: 17 Feb 2022
Posts: 4
Reply Quote
My problem is solved. Thank you very much for your unparalleled help.

I already have the btusb enable_autosuspend=0 option built in.
I don't know exactly how it was fixed. But in sudo upgrade a security update appeared. I also installed some bluetooth utilities through synaptic related to bluetooth in case some library could correct the problem. And I also changed the antennas that the wifi/bluetooth uses.
Now bluetooth has a powerful clean connection.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours