Bluetooth is not AutoEnabled

eephyne · 12 July 2023 15:01

Hello everyone.

I have a fresh gnome manjaro installed but I face a issue with bluetooth.
Its not auto enabled on startup, After searching I set AutoEnable on /etc/bluetooth/main.cfg but It have no effect.

I can simply enable it and it work but since I have bt mouse, its kind of annoying.
its not deactivated after suspend
bluetooth service is enabled.

here my inxi for the bluetooth

Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1.1:3
    chip-ID: 0489:e0d8 class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends

jal · 12 July 2023 15:02

$ sudo systemctl enable bluetooth

eephyne · 12 July 2023 15:05

bluetooth service is already enabled.

jal · 13 July 2023 13:22

Ah right.

After a reboot, what does

$ sudo systemctl status bluetooth

tell you?

eephyne · 13 July 2023 17:54

juste rebooted.

 bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Thu 2023-07-13 19:51:04 CEST; 33s ago
       Docs: man:bluetoothd(8)
   Main PID: 632 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37497)
     Memory: 2.3M
        CPU: 17ms
     CGroup: /system.slice/bluetooth.service
             └─632 /usr/lib/bluetooth/bluetoothd

juil. 13 19:51:19 asgard bluetoothd[632]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq_453
juil. 13 19:51:19 asgard bluetoothd[632]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq_453
juil. 13 19:51:19 asgard bluetoothd[632]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq_512
juil. 13 19:51:19 asgard bluetoothd[632]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq_512
juil. 13 19:51:19 asgard bluetoothd[632]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq_552
juil. 13 19:51:19 asgard bluetoothd[632]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq_552
juil. 13 19:51:19 asgard bluetoothd[632]: Failed to add UUID: Failed (0x03)
juil. 13 19:51:19 asgard bluetoothd[632]: Failed to add UUID: Failed (0x03)
juil. 13 19:51:19 asgard bluetoothd[632]: Failed to add UUID: Failed (0x03)
juil. 13 19:51:19 asgard bluetoothd[632]: Failed to add UUID: Failed (0x03)

could that be the culprit here ?
After enabling it using gnome, the systemctl status don’t show anything new.

eephyne · 17 July 2023 14:24

So after some reboots, I detected something strange:

The wifi is not detected at startup (the bluetooth is not enabled).
As soon as I start the browser (I suspect any app using network connection to do the same), the wifi start.

If I start the bluetooth manually , it don’t seem to enable the wifi.

I talk about both because its on the same card like almost every laptop.

Here a journal of what happened between session start and wifi/bt enabled

juil. 17 16:02:48 asgard bluetoothd[618]: Failed to add UUID: Failed (0x03)
juil. 17 16:02:48 asgard gnome-shell[1719]: Failed to create color profile from colord profile: Erreur lors de l’ouverture du fichier /var/lib/gdm/.local/share/icc/edid-3df377a1277bb0722fcc33fc120c255d.icc : Permission non accordée
juil. 17 16:02:48 asgard gsd-media-keys[1998]: Failed to grab accelerator for keybinding settings:playback-repeat
juil. 17 16:02:48 asgard gsd-media-keys[1998]: Failed to grab accelerator for keybinding settings:magnifier-zoom-out
juil. 17 16:02:48 asgard gsd-media-keys[1998]: Failed to grab accelerator for keybinding settings:hibernate
juil. 17 16:02:48 asgard gnome-shell[749]: Connection to xwayland lost
juil. 17 16:02:48 asgard pulseaudio[1033]: X11 I/O error handler called
juil. 17 16:02:48 asgard pulseaudio[1033]: X11 I/O error exit handler called, preparing to tear down X11 modules
juil. 17 16:02:48 asgard gnome-shell[749]: Xwayland terminated, exiting since it was mandatory
juil. 17 16:02:48 asgard gnome-shell[749]: (../mutter/src/core/meta-context.c:501):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop))
juil. 17 16:03:11 asgard gnome-keyring-daemon[1639]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
juil. 17 16:03:11 asgard gnome-keyring-d[1639]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
juil. 17 16:03:12 asgard kernel: mt7921e 0000:04:00.0: not ready 65535ms after FLR; giving up
juil. 17 16:03:17 asgard wpa_supplicant[1138]: bgscan simple: Failed to enable signal strength monitoring
juil. 17 16:03:17 asgard kernel: warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
juil. 17 16:03:24 asgard wpa_supplicant[1138]: bgscan simple: Failed to enable signal strength monitoring
juil. 17 16:03:29 asgard kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
juil. 17 16:04:39 asgard gnome-shell[1719]: Could not open device /dev/input/event17: GDBus.Error:System.Error.ENODEV: No such device
juil. 17 16:13:10 asgard gnome-shell[1719]: JS ERROR: Extension x11gestures@joseexposito.github.io: TypeError: obj._toucheggTracker is undefined
                                            unhook@/usr/share/gnome-shell/extensions/x11gestures@joseexposito.github.io/src/v40/EntryPoint40.js:171:5
                                            stop@/usr/share/gnome-shell/extensions/x11gestures@joseexposito.github.io/src/v40/EntryPoint40.js:160:23
                                            disable@/usr/share/gnome-shell/extensions/x11gestures@joseexposito.github.io/extension.js:63:18
                                            _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:132:32
                                            _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:565:24
                                            _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:717:20
                                            ExtensionManager/<@resource:///org/gnome/shell/ui/extensionSystem.js:36:18
                                            _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42
                                            _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10
                                            _sync@resource:///org/gnome/shell/ui/sessionMode.js:208:14
                                            pushMode@resource:///org/gnome/shell/ui/sessionMode.js:167:14
                                            activate@resource:///org/gnome/shell/ui/screenShield.js:617:34
                                            _onLongLightbox@resource:///org/gnome/shell/ui/screenShield.js:336:18
                                            onComplete@resource:///org/gnome/shell/ui/lightbox.js:198:18
                                            _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:153:13
                                            _easeActor/<@resource:///org/gnome/shell/ui/environment.js:240:64
juil. 17 16:13:11 asgard kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3

koshikas · 18 July 2023 03:44

post output of this;

$ rfkill list

please

eephyne · 18 July 2023 14:13

okay, i don’t get what is happening here.

Now when I reboot, the wifi is on (everytime I tested) and I can’t enable bluetooth anymore.

rfkill list                                                                                                                                                                                                                                      ✔ 
0: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no

when I click on the bt button on gnome I got this in journal log:

juil. 18 16:13:28 asgard gsd-rfkill[2023]: GTask cc_rfkill_glib_send_change_all_event (source object: 0x560e6fae6ed0, source tag: 0x560e6ef27ec0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.

eephyne · 18 July 2023 14:22

okay, I succeded rebooted with no wireless, seem a bit random.

Here the rfkill list at stark (bt off /no wireless existing)

rfkill list                                                      ✔ 
0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
1: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no

Here what happen when I enable bt (with gnome button, and its working):

rfkill list                                                      ✔ 
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no

and here what it show when I start chrome and after some times the wireless is detected and online.

rfkill list                                                  INT ✘ 
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

As you can see, the phy0 does not appear at boottime.

I watched dmesg and i got several :

[    5.323714] mt7921e 0000:04:00.0: not ready 2047ms after FLR; waiting
[    7.590665] mt7921e 0000:04:00.0: not ready 4095ms after FLR; waiting
[   11.858354] mt7921e 0000:04:00.0: not ready 8191ms after FLR; waiting
[   20.180369] mt7921e 0000:04:00.0: not ready 16383ms after FLR; waiting
[   37.244086] mt7921e 0000:04:00.0: not ready 32767ms after FLR; waiting
[   71.377334] mt7921e 0000:04:00.0: not ready 65535ms after FLR; giving up
[   71.604962] mt7921e 0000:04:00.0: ASIC revision: 79220010
[   71.684259] mt7921e 0000:04:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230530123154a
[   72.050762] mt7921e 0000:04:00.0: WM Firmware Version: ____000000, Build Time: 20230530123236
[   73.155640] mt7921e 0000:04:00.0 wlp4s0: renamed from wlan0

mt7921 is the model of my card. I look like its not succed to load it multiple times

koshikas · 19 July 2023 10:06

firstly mediatek is one of those vendors having odd hardware support on linux over the years, but its getting better since recently.

support for mediatek wireless cards were supposedly finalized in kernel 5.18. make sure you are atleast running kernel 5.18 or later best is to run the latest LTS; 6.1
if BT is listed as soft-blocked under rfkill then you should be able to enable it with;

$ sudo rfkill unblock bluetooth

wanting wireless devices enabled (not enabled by default), can be done by explicitly setting TLP settings in /etc/tlp.conf. locate

#DEVICES_TO_ENABLE_ON_STARTUP="wifi"

and change it to

DEVICES_TO_ENABLE_ON_STARTUP="wifi bluetooth"

Restart TLP and the bluetooth service.

what you didnt mention was that this is possibly a laptop having internal wireless card and you are having issues with a USB wireless card. in such cases detection, device firmware might need additional time to wake and standby for connections. cant you connect to the inbuilt bluetooth, seems to be readily available

eephyne · 19 July 2023 10:12

Yep , I tested on lts 6.1, also 6.4 and even 6.5
Sometimes its blocked but thats not what it really blocking, as you can see in my previous post, just clicking on bt button on gnome interface unblock the device.
, I don’t have tlp.conf file in /etc . is it normal ? (i see a tlp package, should I install it ?)
its not a usb wireless card, (at least I don’t think so , and lsusb don’t show it).

thanks for your time and patience with me