The Bluetooth icon at the top of the panel is no longer showing, why might it not show and how do I get it back?
#Where did Bluetooth go?
pastel token
lofty basalt
The Bluetooth icon at the top of the panel is no longer showing, why might it no...
usually means bt is disabled or not available. run the Bluetooth app from your start menu
pastel token
I cannot find the Bluetooth app in the start menu. What specifically is it called?
lofty basalt
I cannot find the Bluetooth app in the start menu. What specifically is it call...
search for blueman
pastel token
/usr/share/blueman
rustic oxide
and read the network section
pastel token
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-9:4
chip-ID: 8087:0029 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: no
address: <filter>
pastel token
It's like it is disabled or something "state: down"?
rustic oxide
down but idk how
lofty basalt
nothing shows, search comes up completely empty
what happens when you press "adapters" button?
pastel token
Adapters button?
pastel token
I don't know -- There is no Blueman app, program, icon, or anything I am aware of, available to press on
lofty basalt
I don't know -- There is no Blueman app, program, icon, or anything I am aware o...
any chance you removed it?
and any chance you dualboot?
pastel token
I'm 110% sure I did not remove it : )
But if it was removed, it would have been by something in the system, not me, and I don't know what would have done that
Dual boot: I set up another drive with LMDE 6 on it too, and tried to get it to boot and get grub to see it, but it won't boot that drive and I have not yet learned how to make grub see that other drive. So for now, I'm on this first drive only, mostly happily running LMDE 6 on this one
lofty basalt
bluetoothctl devices
pastel token
$ bluetoothctl devices
No default controller available
lofty basalt
yeah that seems to be an issue
lofty basalt
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-...
but according to this, it works fine?
I suggest you to double check if fast boot in BIOS is disabled (it must be) and see if it works in a live boot.
pastel token
I personally think it is a bug in the kernel, or somewhere in Mint, but I don't know for sure.
The Wi-Fi works fine, and usually Bluetooth does too.
Except Bluetooth is not working today, same system, same hardware
Bluetooth works with a Live USB every time
I've had this happen twice or 3 or 5 times before, and have "solved" it by reinstalling LMDE. It works for days to months and then one day it just stops working, and I don't know why.
I know when it stops working as soon as I see that the Bluetooth icon no longer shows in the panel.
The closest hint I can think of: I unplugged my computer yesterday and left it that way until this morning. I plugged it in again and started it up as normal.
Usually I don't unplug it, but I do tell it to shut down. There's still power available to the power supply unless I unplug it.
Could a total loss of power affect anything with that WiFi/Bluetooth module?
pastel token
Is there a way to force a restart of the blueman-applet?
bold agate
Is there a way to force a restart of the `blueman-applet`?
If Fast Boot is enabled in BIOS, that is likely the problem
pastel token
Checked: Fast Boot is Disabled in BIOS
bold agate
in terminal sudo hciconfig hci0 up
pastel token
$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
$ sudo hciconfig hci0 up
$
I tried it twice ^
bold agate
Ok, then do bluetoothctl power on then bluetoothctl scan on
pastel token
$ bluetoothctl power on
No default controller available
$ bluetoothctl power on
No default controller available
$ bluetoothctl scan on
No default controller available
bold agate
What results for dmesg | egrep -i 'blue|firm'
pastel token
[ 9.413547] Bluetooth: Core ver 2.22 [ 9.413583] NET: Registered PF_BLUETOOTH protocol family [ 9.413585] Bluetooth: HCI device and connection manager initialized [ 9.413591] Bluetooth: HCI socket layer initialized [ 9.413595] Bluetooth: L2CAP socket layer initialized [ 9.413602] Bluetooth: SCO socket layer initialized [ 10.369955] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.369958] Bluetooth: BNEP filters: protocol multicast [ 10.369962] Bluetooth: BNEP socket layer initialized [ 10.665586] r8169 0000:05:00.0: firmware: direct-loading firmware rtl_nic/rtl8125b-2.fw [ 11.507119] Bluetooth: hci0: command 0xfc05 tx timeout [ 11.507119] Bluetooth: hci0: Reading Intel version command failed (-110) [ 1427.935551] Bluetooth: hci0: Reading Intel version command failed (-110) [ 1431.330962] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 [ 1431.335999] Bluetooth: hci0: Device revision is 1 [ 1431.336007] Bluetooth: hci0: Secure boot is enabled
[ 1431.336010] Bluetooth: hci0: OTP lock is enabled
[ 1431.336011] Bluetooth: hci0: API lock is enabled
[ 1431.336013] Bluetooth: hci0: Debug lock is disabled [ 1431.336015] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 1431.337225] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi [ 1431.337232] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [ 1431.337260] Bluetooth: hci0: Boot Address: 0x24800 [ 1431.337263] Bluetooth: hci0: Firmware Version: 15-45.22 [ 1434.740200] Bluetooth: hci0: Waiting for firmware download to complete [ 1434.740584] Bluetooth: hci0: Firmware loaded in 3323639 usecs [ 1434.740641] Bluetooth: hci0: Waiting for device to boot [ 1434.758415] Bluetooth: hci0: Device booted in 17370 usecs [ 1434.766924] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.ddc [ 1434.766935] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc [ 1434.775710] Bluetooth: hci0: Applying Intel DDC parameters completed [ 1434.780969] Bluetooth: hci0: Firmware revision 0.3 build 15 week 45 2022
I need to paste long output in a better way without uploading to a 3rd party something : )
bold agate
Lets try something echo "blacklist btusb"|sudo tee /etc/modprobe.d/bluetooth.conf Reboot and then do sudo modprobe btusb
bold agate
Result different now for bluetoothctl power on
pastel token
Shall I run bluetoothctl power on now or do I need to un-blacklist it first and reboot?
Hey, after blacklisting it and rebooting, and my previous reply, I see (just noticed) the Bluetooth icon in the panel again... cool! But how did it return, how can I make it return, how may I make it stay?
pastel token
( I ask cause with much gratitude to all who helped in this thread, I am not yet sure which step got that Bluetooth working again, and when it breaks again, if it does, I have not yet learned which steps will repair it to good working order once more)
bold agate
( I ask cause with much gratitude to all who helped in this thread, I am not yet...
I think there is a timing issue with your computer that doesn't allow the bluetooth chip to initialize before the driver does its probe and firmware upload
pastel token
Does blacklisting it provide that opportunity for the chip to initialize before the driver load?
...and would I need to just leave it as-is or does it require an additional step to probe and firmware upload?
I guess worded differently,
To fix Bluetooth when it doesn't work, which of the steps above and in what order are most likely to get it up and running again? -- quick start guide for the newbie : )
bold agate
You could try removing the blacklist file and reboot sudo rm /etc/modprobe.d/bluetooth.conf and see if it works. Something else that could help is to change the UEFI boot order and put PXE network boot above ubuntu and that may provide enough delay