[SOLVED] Linux Mint 20.2 not showing any bluetooth devices on Asus Zephyrus M16

[KenoKokoro]

Hello everyone,

After fresh install in dual boot with Windows 10 (comes pre-installed with the laptop), and Linux Mint 20, and long fight to find the right kernel that works with the machine properly (GPU, fn commands, wifi..), I got to the issue that I can't fix with the bluetooth that just shows `Searching for devices...` and nothing else. I can toggle power on and off on the bluetooth, but no devices are shown.
I disabled fast boot and hibernation on Windows, and also executed `powercfg /h off` (even though not sure what this command actually does, I am desperate at this point)

I am using the `5.13.13` Kernel, and this is the only issue that I can't go through. I saw similar issues on similar network adapters from Asus G14/15, that are resolved with upgrade to 5.14+ Kernel and Ubuntu 21.04, but since I am using mint, can't really work with this.

On top of that, I tried to recompile the `btusb.ko` kernel bluetooth driver (from 5.14.2), since it had some new changes for the mt7921, but it is still the same.
When I try `bluetoothctl` and type `show` it just says "No default controller available".

Any suggestions?

Code: Select all

inxi -Fx              
          
System:    Host: kenshin Kernel: 5.13.13-051313-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.5 
           Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: ASUSTeK product: ROG Zephyrus M16 GU603HR_GU603HR v: 1.0 serial: M7NRKD009930304 
           Mobo: ASUSTeK model: GU603HR v: 1.0 serial: 7D17MC0035 UEFI: American Megatrends LLC. v: GU603HR.309 
           date: 06/24/2021 
Battery:   ID-1: BAT0 charge: 27.7 Wh condition: 90.8/90.0 Wh (101%) model: ASUSTeK ASUS Battery status: Discharging 
CPU:       Topology: 8-Core model: 11th Gen Intel Core i7-11800H bits: 64 type: MT MCP arch: N/A L2 cache: 24.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 73728 
           Speed: 1159 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 1018 2: 803 3: 1035 4: 995 5: 1016 6: 789 7: 849 
           8: 1098 9: 797 10: 908 11: 1040 12: 803 13: 976 14: 815 15: 834 16: 951 
Graphics:  Device-1: Intel vendor: ASUSTeK driver: i915 v: kernel bus ID: 0000:00:02.0 
           Device-2: NVIDIA vendor: ASUSTeK driver: nvidia v: 470.63.01 bus ID: 0000:01:00.0 
           Display: server: X.Org 1.20.11 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1680x1050~85Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT1) v: 4.6 Mesa 21.0.3 direct render: Yes 
Audio:     Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0000:00:1f.3 
           Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0000:01:00.1 
           Sound Server: ALSA v: k5.13.13-051313-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: 3000 
           bus ID: 0000:2d:00.0 
           IF: eno2 state: down mac: 04:42:1a:85:d7:b2 
           Device-2: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: 3000 bus ID: 0000:2f:00.0 
           IF: wlo1 state: up mac: 48:e7:da:56:2d:f5 
           IF-ID-1: br-37a1948a6a57 state: down mac: 02:42:6c:ff:82:05 
           IF-ID-2: docker0 state: down mac: 02:42:d0:7e:e7:de 
Drives:    Local Storage: total: 953.87 GiB used: 54.11 GiB (5.7%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00B00 size: 953.87 GiB 
RAID:      Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 bus ID: 0000:00:0e.0 
Partition: ID-1: / size: 143.18 GiB used: 19.04 GiB (13.3%) fs: ext4 dev: /dev/nvme0n1p8 
           ID-2: /boot size: 1.80 GiB used: 434.8 MiB (23.6%) fs: ext4 dev: /dev/nvme0n1p10 
           ID-3: /home size: 288.38 GiB used: 17.32 GiB (6.0%) fs: ext4 dev: /dev/nvme0n1p9 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 2100 
Info:      Processes: 379 Uptime: 17m Memory: 15.31 GiB used: 2.53 GiB (16.5%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
           Shell: zsh v: 5.8 inxi: 3.0.38 

[SMG]

since it had some new changes for the mt7921, but it is still the same.

Welcome to the forum, KenoKokoro.

'mt7921' rang a bell for me as I recalled doing research on it. I did in this thread Problem after suspend laptop [SOLVED]. I wanted to pass along that thread as it mentions some of the kernels and things that person tried as well as bug reports, etc. The person did mention bluetooth was not working, but since the main issue of the thread was not bluetooth, I do not know if he found success with bluetooth.

I do not know the current progress of the 5.13-oem kernel (which is an Ubuntu kernel), but maybe advances with it, oem-firmware, or some of the bug reports might give you some leads on a resolution to this issue.

Have you checked dmesg yet for lines related to the bluetooth device?

[KenoKokoro]

Thanks for the quick response.

I am not sure if this is helpful.. but this is what I remember checking in the dmesg, but in all honesty I don't know if this is good or bad..

Code: Select all

sudo dmesg | grep -i 'blue'                                                                                                         

[    4.465840] Bluetooth: Core ver 2.22
[    4.465868] Bluetooth: HCI device and connection manager initialized
[    4.465874] Bluetooth: HCI socket layer initialized
[    4.465876] Bluetooth: L2CAP socket layer initialized
[    4.465878] Bluetooth: SCO socket layer initialized
[    4.717337] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.717341] Bluetooth: BNEP filters: protocol multicast
[    4.717345] Bluetooth: BNEP socket layer initialized

I will double check it also now to upgrade to kernel 5.13.16 (I can see that is the latest stable for 5.13), maybe that will help something. I will post an uupdate.

[SMG]

I am using the `5.13.13` Kernel, and this is the only issue that I can't go through. I saw similar issues on similar network adapters from Asus G14/15, that are resolved with upgrade to 5.14+ Kernel and Ubuntu 21.04, but since I am using mint, can't really work with this.

I did not quite understand this statement.

The kernels you are discussing are mainline kernels which Ubuntu/Mint do not use. I understand some people do need to use mainline kernels when their hardware is very new in order to get drivers.

Yet, you mention something was resolved in Ubuntu 21.04? It's my understanding you should be able to use in Mint whatever is used in Ubuntu 21.04.

I am not sure if this is helpful.. but this is what I remember checking in the dmesg, but in all honesty I don't know if this is good or bad..

I'm not sure. It was not what I was expecting, but newer hardware does often have newer functionality so it may be what is expected for this device.

[KenoKokoro]

Thanks again for your response!

Before I answer, I used the `5.13.0-1012-oem` kernel, but still nothing. Bluetooth behavior is the same. This is what I get from the journal -b if is from any help.

Code: Select all

journalctl -b | egrep -i 'blue|mt7921'                        
Sep 13 23:12:35 kenshin kernel: Bluetooth: Core ver 2.22
Sep 13 23:12:35 kenshin kernel: Bluetooth: HCI device and connection manager initialized
Sep 13 23:12:35 kenshin kernel: Bluetooth: HCI socket layer initialized
Sep 13 23:12:35 kenshin kernel: Bluetooth: L2CAP socket layer initialized
Sep 13 23:12:35 kenshin kernel: Bluetooth: SCO socket layer initialized
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0: enabling device (0000 -> 0002)
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0: disabling ASPM L0s L1
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0: ASIC revision: 79610010
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0: HW/SW Version: 0x8a108a10, Build Time: 20210612122717a
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0: WM Firmware Version: ____010000, Build Time: 20210612122753
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0: Firmware init done
Sep 13 23:12:35 kenshin systemd[1]: Starting Bluetooth service...
Sep 13 23:12:35 kenshin bluetoothd[825]: Bluetooth daemon 5.53
Sep 13 23:12:35 kenshin systemd[1]: Started Bluetooth service.
Sep 13 23:12:35 kenshin systemd[1]: Reached target Bluetooth.
Sep 13 23:12:35 kenshin bluetoothd[825]: Starting SDP server
Sep 13 23:12:35 kenshin bluetoothd[825]: Bluetooth management interface 1.20 initialized
Sep 13 23:12:35 kenshin kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 13 23:12:35 kenshin kernel: Bluetooth: BNEP filters: protocol multicast
Sep 13 23:12:35 kenshin kernel: Bluetooth: BNEP socket layer initialized
Sep 13 23:12:35 kenshin NetworkManager[830]: <info>  [1631563955.3311] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so)
Sep 13 23:12:35 kenshin NetworkManager[830]: <info>  [1631563955.9599] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.7/0000:2f:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)
Sep 13 23:12:35 kenshin kernel: mt7921e 0000:2f:00.0 wlo1: renamed from wlan0
Sep 13 23:12:44 kenshin dbus-daemon[1570]: [session uid=1000 pid=1570] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.60' (uid=1000 pid=1872 comm="blueberry-obex-agent                              ")
Sep 13 23:12:44 kenshin systemd[1542]: Starting Bluetooth OBEX service...
Sep 13 23:12:44 kenshin dbus-daemon[1570]: [session uid=1000 pid=1570] Successfully activated service 'org.bluez.obex'
Sep 13 23:12:44 kenshin systemd[1542]: Started Bluetooth OBEX service.

The kernels you are discussing are mainline kernels which Ubuntu/Mint do not use. I understand some people do need to use mainline kernels when their hardware is very new in order to get drivers.

To be honest I wasn't really sure how to fix the drivers issue, since initially almost nothing was working on the laptop with the initial 5.4 kernel. So I just used https://launchpad.net/~tuxinvader/+arch ... s-mainline to install 5.13.13

On 5.12 the wifi doesn't work at all. So this is my best working kernel so far. I just need to find a way how to fix the bluetooth somehow, but I am out of ideas/options.

Yet, you mention something was resolved in Ubuntu 21.04? It's my understanding you should be able to use in Mint whatever is used in Ubuntu 21.04.

But as I know Linux Mint 20.2 is based on Ubuntu 20.04 (focal fossa), so I am not sure if I should upgrade following upgrade guide for Ubuntu 21.04. Basically how I understood there is that, upgrading to Ubuntu 21.04, will give the option to upgrade the kernel to 5.14+ (the libc6 library should be >=2.33, and this is done on Ubuntu 21.04 but not on Mint 20.2 or Ubuntu 20.04), and basically the Ubuntu 21.04 + 5.14 kernel fixes the bluetooth issue.

But I also recompiled the `btusb.c` from the `5.14.3` kernel, and that still didn't fix the issue. Not sure how these things work, maybe I am missing some firmware... I do not have the knowledge to proceed from here to be honest. Usually all my fixes for not recognized hardware were just bump kernel version..

[SMG]

Before I answer, I used the `5.13.0-1012-oem` kernel, but still nothing. Bluetooth behavior is the same. This is what I get from the journal -b if is from any help.

That is more along the lines of what I would expect to see. The driver is listed as well as lines about bluetooth services started (as noted by the operating system). I do not see any error messages, however I do see one "interesting" line.

Code: Select all

Sep 13 23:12:35 kenshin NetworkManager[830]: <info>  [1631563955.9599] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.7/0000:2f:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)

Running rfkill list in a terminal will indicate whether or not bluetooth is blocked, but you would have to switch back to the 5.13-oem kernel to run it.

To be honest I wasn't really sure how to fix the drivers issue, since initially almost nothing was working on the laptop with the initial 5.4 kernel.

With hardware as new as yours, we recommend using the Linux Mint 20.2 "Uma" - Cinnamon (Edge, 64-bit) ISO with the 5.11 kernel as a starting point. When that does not have the drivers then the 5.13-oem is the next one to try. Then after that would be the mainline kernels.

Mainline kernels and Ubuntu kernels are different "branches" in the kernel "tree" which is why they are not necessarily interchangeable (which is why there is risk in doing so).

But as I know Linux Mint 20.2 is based on Ubuntu 20.04 (focal fossa), so I am not sure if I should upgrade following upgrade guide for Ubuntu 21.04. Basically how I understood there is that, upgrading to Ubuntu 21.04, will give the option to upgrade the kernel to 5.14+ (the libc6 library should be >=2.33, and this is done on Ubuntu 21.04 but not on Mint 20.2 or Ubuntu 20.04), and basically the Ubuntu 21.04 + 5.14 kernel fixes the bluetooth issue.

I am not aware of there being official means of upgrading to kernel 5.14+ in the notes for upgrading to Ubuntu 21.04? It's my understanding that Ubuntu 21.10 might be coming out with 5.14, but that would be an Ubuntu 5.14 kernel and it would also become available for other Ubuntu-based products to try/use after that release comes out.

[KenoKokoro]

Thanks again for the response, much appreciated.

Okay so, I booted on `5.13.0-1012-oem` and checked the `rfkill`, but I guess things are normal there.

Code: Select all

rfkill list
                                                                                                                      
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

I wasn't aware of the Edge releases, I will try it from bootable USB, or lnstall it as 3rd OS (since I need my current mint for work, the bluetooth is not big blocker, it just sucks to not be able to connect my headphones).
I will post back once I try this option.

Thanks again!

[SMG]

Okay so, I booted on `5.13.0-1012-oem` and checked the `rfkill`, but I guess things are normal there.

That looks good.

If you attempt to put your headphones in range of where the bluetooth should pick up, are there any messages in dmesg which might relate to the headphones? I do not know if this might be a range/distance issue, the signal is just not being recognized for some reason, or the issue is somehow OS related.

Sometimes the bluetooth/wireless cards are the same card and interference can happen, but I do not know if that might apply in this case.

I wasn't aware of the Edge releases, I will try it from bootable USB, or lnstall it as 3rd OS (since I need my current mint for work, the bluetooth is not big blocker, it just sucks to not be able to connect my headphones).

The difference between the Edge ISO and the "regular" ISO is the kernel (plus some kernel header files, I believe). Everything else is the same.

[KenoKokoro]

Okay so.. the Edge didn't solve the issue. Everything is the same. I upgraded to 5.13-oem kernel, but I still have the same issue.

If you attempt to put your headphones in range of where the bluetooth should pick up, are there any messages in dmesg which might relate to the headphones? I do not know if this might be a range/distance issue, the signal is just not being recognized for some reason, or the issue is somehow OS related.

It works perfectly fine on the Windows 10, I have 2 headphones, 1 speaker, even my phone, they are all recognized on the Windows 10. But I just get the `Searching for devices...` on the linux mint.

I am back to the original Linux Mint installation with the `5.13.0-1012-oem` Kernel. I tried having some devices with bluetooth on, but nothing appears on the `dmesg` or the journal. The only thing that I see in the journal is when I turn it off and on again the Bluetooth:

Code: Select all

Sep 15 18:18:43 kenshin rfkill[5624]: block set for type bluetooth
Sep 15 18:18:44 kenshin rfkill[5628]: unblock set for type bluetooth

I still have the "No default controller available" on bluetoothctl:

Code: Select all

bluetoothctl                                                                                                                         

Agent registered
[bluetooth]# show
No default controller available
[bluetooth]# 

And also something else that I notice is the name of the device (I attached screenshot). It says: "Enable Bluetooth to edit".. so that is confusing as well for me, since as you can see the bluetooth is enabled.

[KenoKokoro]

Another update. I used the kernel 5.14.3 (since I can see changes for the mt7921 driver https://git.kernel.org/pub/scm/linux/ke ... 2=v5.13.13, and I had to disable the nvidia driver in order to boot, but at least I managed to boot it to check the bluetooth), but the issue still persists.

This is the journal log:

Code: Select all

journalctl -b --boot=-1 | egrep -i 'blue|mt7921'

Sep 15 22:06:21 kenshin kernel: mt7921e 0000:2f:00.0: enabling device (0000 -> 0002)
Sep 15 22:06:21 kenshin kernel: mt7921e 0000:2f:00.0: disabling ASPM L0s L1
Sep 15 22:06:21 kenshin kernel: mt7921e 0000:2f:00.0: ASIC revision: 79610010
Sep 15 22:06:21 kenshin kernel: Bluetooth: Core ver 2.22
Sep 15 22:06:21 kenshin kernel: NET: Registered PF_BLUETOOTH protocol family
Sep 15 22:06:21 kenshin kernel: Bluetooth: HCI device and connection manager initialized
Sep 15 22:06:21 kenshin kernel: Bluetooth: HCI socket layer initialized
Sep 15 22:06:21 kenshin kernel: Bluetooth: L2CAP socket layer initialized
Sep 15 22:06:21 kenshin kernel: Bluetooth: SCO socket layer initialized
Sep 15 22:06:21 kenshin kernel: mt7921e 0000:2f:00.0: HW/SW Version: 0x8a108a10, Build Time: 20210612122717a
Sep 15 22:06:21 kenshin systemd[1]: Starting Bluetooth service...
Sep 15 22:06:21 kenshin bluetoothd[829]: Bluetooth daemon 5.53
Sep 15 22:06:21 kenshin systemd[1]: Started Bluetooth service.
Sep 15 22:06:21 kenshin systemd[1]: Reached target Bluetooth.
Sep 15 22:06:21 kenshin bluetoothd[829]: Starting SDP server
Sep 15 22:06:21 kenshin kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 15 22:06:21 kenshin kernel: Bluetooth: BNEP filters: protocol multicast
Sep 15 22:06:21 kenshin kernel: Bluetooth: BNEP socket layer initialized
Sep 15 22:06:21 kenshin dbus-daemon[834]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=829 comm="/usr/lib/bluetooth/bluetoothd ")
Sep 15 22:06:21 kenshin bluetoothd[829]: Bluetooth management interface 1.21 initialized
Sep 15 22:06:21 kenshin kernel: mt7921e 0000:2f:00.0: WM Firmware Version: ____010000, Build Time: 20210612122753
Sep 15 22:06:21 kenshin kernel: mt7921e 0000:2f:00.0: Firmware init done
Sep 15 22:06:21 kenshin NetworkManager[835]: <info>  [1631732781.7508] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so)
Sep 15 22:06:22 kenshin NetworkManager[835]: <info>  [1631732782.3569] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.7/0000:2f:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)
Sep 15 22:06:22 kenshin kernel: mt7921e 0000:2f:00.0 wlo1: renamed from wlan0
Sep 15 22:06:22 kenshin kernel: Modules linked in: nvidia_drm(POE+) nvidia_modeset(POE) nvidia(POE) snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus ledtrig_audio snd_soc_core snd_compress ac97_bus overlay snd_pcm_dmaengine bnep snd_hda_codec_hdmi intel_tcc_cooling snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep btusb snd_pcm btrtl btbcm btintel mei_hdcp snd_seq_midi intel_rapl_msr snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp bluetooth mt7921e snd_rawmidi uvcvideo mt76_connac_lib videobuf2_vmalloc nls_iso8859_1 mt76 videobuf2_memops videobuf2_v4l2 ecdh_generic videobuf2_common ecc joydev coretemp mac80211 snd_seq kvm_intel cfg80211 snd_seq_device kvm snd_timer intel_cstate processor_thermal_device_pci_legacy processor_thermal_device input_leds
Sep 15 22:06:42 kenshin dbus-daemon[1768]: [session uid=1000 pid=1768] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.58' (uid=1000 pid=2100 comm="blueberry-obex-agent                              ")
Sep 15 22:06:42 kenshin systemd[1737]: Starting Bluetooth OBEX service...
Sep 15 22:06:42 kenshin dbus-daemon[1768]: [session uid=1000 pid=1768] Successfully activated service 'org.bluez.obex'
Sep 15 22:06:42 kenshin systemd[1737]: Started Bluetooth OBEX service.
Sep 15 22:08:25 kenshin rfkill[3875]: block set for type bluetooth
Sep 15 22:08:27 kenshin rfkill[3878]: unblock set for type bluetooth (I turned it off and on again here)

Still same response from the `bluetoothctl` command as well. I am really starting to think that it might be something that the windows is doing to the bluetooth, so it is not enabled properly or something. I have no clue what to do from here.

[SMG]

If you attempt to put your headphones in range of where the bluetooth should pick up, are there any messages in dmesg which might relate to the headphones? I do not know if this might be a range/distance issue, the signal is just not being recognized for some reason, or the issue is somehow OS related.

It works perfectly fine on the Windows 10, I have 2 headphones, 1 speaker, even my phone, they are all recognized on the Windows 10. But I just get the `Searching for devices...` on the linux mint.

Where I was heading with that comment is perhaps Mint, for some reason, is not powering that device the same way it is powered in Windows so the radio signal does not extend as far a desired. I've been trying to find more specific info about that card. It seems to be a wireless-bluetooth combo card. On some combo cards, there can be interference of one signal with the other. Should really be different frequencies between the two, but I'm running low on ideas.

All the dmesg lines seem to indicate things are working. There are even lines indicating powersave mode is not activated which means there should be a steady signal. (However, that line may only be an issue with the wireless aspect of the card.)

I did find this thread Garunda Linux: Bluetooth is not being enabled which has several interesting ideas. One was related to a BIOS/UEFI setting. Another indicates when Windows pairs the device that it locks out other operating systems from pairing devices. Once a device is auto-connected in Windows then it can not be auto-connected with other sources? I do not have a way of testing that to know if it is true.

And then at the end it mentions a patch that that is available and probably will be coming out with kernel 5.15. The patch mentions
/* Additional MediaTek MT7921 Bluetooth devices */, but I do not know if your MT7921e is part of the same category. Or if that is related to the patch you mentioned in your original post.

(since I can see changes for the mt7921 driver https://git.kernel.org/pub/scm/linux/ke ... 2=v5.13.13,

That looks slightly different than the one attached to the Garunda Linux thread.

(Still same response from the `bluetoothctl` command as well. I am really starting to think that it might be something that the windows is doing to the bluetooth, so it is not enabled properly or something. I have no clue what to do from here.

See if something in the pairing of devices discussion might give you some ideas.

[KenoKokoro]

Just an update.

I had a time today to quickly go through the BIOS/UEFI settings, and I couldn't find anything related to this. The only thing that I found out was the Secure Boot which is disabled. I also remember disabling this, when I had to install the nvidia drivers at the first place.
I couldn't find anything related to the hardware scanning settings there.

Also, Fast boot is disabled (I learned this lesson on my previous machine).

Regarding the devices, I will double check and confirm that just to be sure, but I haven't paired anything to the bluetooth on the windows. Also, I see random devices nearby from my neighbors on my phone's bluetooth, but nothing shows up on my laptop.

Also regarding the Garunda Linux issue, I can see that in his response from `inxi -Fza`, there is actual `Bluetooth...` device, where in my case, I can't see that. Also, the driver in use for the bluetooth is actually `btusb`. And I am almost sure that the 2021 Asus ROG laptops have the same bluetooth/wifi chip (since the network wifi on his output is also `mt7921e`, just like mine.
His output:

Code: Select all

Network:   Device-1: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: 4000 bus-ID: 03:00.0 
chip-ID: 14c3:7961 class-ID: 0280 
IF: wlp3s0 state: up mac: <filter> 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 
v: kernel port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
IF: enp4s0 state: down mac: <filter> 
Device-3: Lite-On Dell Wireless Mouse WM118 type: USB driver: hid-generic,usbhid bus-ID: 1-3:2 
chip-ID: 04ca:00a8 class-ID: 0301 
Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-14:4
chip-ID: 13d3:3563 class-ID: e001 serial: <filter>

And then my output:

Code: Select all

sudo inxi -Fza                                                
          
System:
  Kernel: 5.13.0-1012-oem x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/vmlinuz-5.13.0-1012-oem 
  root=UUID=0c0b2e07-6d35-47e6-9179-71ee188a9a76 ro quiet splash 
  Desktop: Cinnamon 5.0.5 wm: muffin 5.0.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: ASUSTeK product: ROG Zephyrus M16 GU603HR_GU603HR 
  v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: GU603HR v: 1.0 serial: <filter> 
  UEFI: American Megatrends LLC. v: GU603HR.309 date: 06/24/2021 
Battery:
  ID-1: BAT0 charge: 60.4 Wh condition: 91.1/90.0 Wh (101%) volts: 15.9/15.9 
  model: ASUSTeK ASUS Battery type: Li-ion serial: <filter> 
  status: Discharging cycles: 9 
CPU:
  Topology: 8-Core model: 11th Gen Intel Core i7-11800H bits: 64 
  type: MT MCP arch: N/A family: 6 model-id: 8D (141) stepping: 1 
  microcode: 2C L1 cache: 640 KiB L2 cache: 24.0 MiB L3 cache: 24.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 73728 
  Speed: 1559 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 1716 2: 1674 
  3: 2285 4: 1657 5: 1806 6: 4028 7: 3671 8: 1761 9: 801 10: 3551 11: 1724 
  12: 3613 13: 1073 14: 1378 15: 1766 16: 2629 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 0000:00:02.0 chip ID: 8086:9a60 
  Device-2: NVIDIA vendor: ASUSTeK driver: nvidia v: 470.63.01 
  bus ID: 0000:01:00.0 chip ID: 10de:249d 
  Display: server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1680x1050~85Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT1) v: 4.6 Mesa 21.0.3 
  direct render: Yes 
Audio:
  Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus ID: 0000:00:1f.3 chip ID: 8086:43c8 
  Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus ID: 0000:01:00.1 chip ID: 10de:228b 
  Sound Server: ALSA v: k5.13.0-1012-oem 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus ID: 0000:2d:00.0 
  chip ID: 10ec:8168 
  IF: eno2 state: down mac: <filter> 
  Device-2: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: 3000 
  bus ID: 0000:2f:00.0 chip ID: 14c3:7961 
  IF: wlo1 state: up mac: <filter> 
  IF-ID-1: br-37a1948a6a57 state: up speed: 10000 Mbps duplex: unknown 
  mac: <filter> 
  IF-ID-2: docker0 state: down mac: <filter> 
  IF-ID-3: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
  IF-ID-4: veth199912d state: up speed: 10000 Mbps duplex: full 
  mac: <filter> 
  IF-ID-5: veth6802120 state: up speed: 10000 Mbps duplex: full 
  mac: <filter> 
  IF-ID-6: veth78f4c6a state: up speed: 10000 Mbps duplex: full 
  mac: <filter> 
  IF-ID-7: vethc4f40f5 state: up speed: 10000 Mbps duplex: full 
  mac: <filter> 
  IF-ID-8: vethc7f1ef9 state: up speed: 10000 Mbps duplex: full 
  mac: <filter> 
Drives:
  Local Storage: total: 953.87 GiB used: 56.24 GiB (5.9%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00B00 
  size: 953.87 GiB block size: physical: 512 B logical: 512 B 
  speed: 63.2 Gb/s lanes: 4 serial: <filter> rev: GXA7301Q scheme: GPT 
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller 
  driver: vmd v: 0.6 port: 5000 bus ID: 0000:00:0e.0 chip ID: 8086.9a0b 
  rev: N/A 
Partition:
  ID-1: / raw size: 146.48 GiB size: 143.18 GiB (97.75%) 
  used: 19.28 GiB (13.5%) fs: ext4 block size: 4096 B dev: /dev/nvme0n1p8 
  ID-2: /boot raw size: 1.86 GiB size: 1.80 GiB (96.75%) 
  used: 431.3 MiB (23.4%) fs: ext4 block size: 4096 B dev: /dev/nvme0n1p10 
  ID-3: /home raw size: 293.99 GiB size: 288.38 GiB (98.09%) 
  used: 18.27 GiB (6.3%) fs: ext4 block size: 4096 B dev: /dev/nvme0n1p9 
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 469 Uptime: 1h 04m Memory: 15.32 GiB used: 7.77 GiB (50.7%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 
  Shell: zsh (sudo) v: 5.8 running in: terminator inxi: 3.0.38 

Anything useful from this?

[SMG]

Also regarding the Garunda Linux issue, I can see that in his response from `inxi -Fza`, there is actual `Bluetooth...` device, where in my case, I can't see that.

You mean the USB device? I believe usb devices usually use the btusb driver.

Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-14:4
chip-ID: 13d3:3563 class-ID: e001 serial: <filter>

Maybe the person is using that external usb bluetooth until getting the internal one working? I did not think of that earlier, but that is an option if you have a spare usb port for one. I would just caution to check reviews on anything you are considering buying to see if it works with Linux-based distros.

And I am almost sure that the 2021 Asus ROG laptops have the same bluetooth/wifi chip (since the network wifi on his output is also `mt7921e`, just like mine.

Chip ID is exactly the same, so I would presume they are the same.

Garunda Linux output:

Code: Select all

 Device-1: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: 4000 bus-ID: 03:00.0 
chip-ID: 14c3:7961 class-ID: 0280 

Your output:

Code: Select all

  Device-2: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: 3000 bus ID: 0000:2f:00.0 
chip ID: 14c3:7961 

That person is using a newer version of inxi, but I would expect the chip info is the same on both versions. If you want the newer inxi version, here is how to install the latest 3.3.06 inxi on Mint. I do not know that it would make a difference for troubleshooting the issue you posted, but for comparison's purpose you might want the same version.

[KenoKokoro]

Thanks again for your response. I appreciate it!!

I updated the `inxi` version just for comparison, but you are right, my bluetooth is also with the `btusb` driver, and same chip so they are same devices.

Code: Select all

Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-14:5 chip-ID: 13d3:3563 
           class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: no 
           address: <filter> 
           Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: slave accept 
           Device-2: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8 bus-ID: 3-4:10 
           chip-ID: 0a12:0001 class-ID: e001 
           Report: ID: hci1 rfk-id: 5 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 sub-v: 22bb hci-v: 4.0 rev: 22bb 
           Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park link-mode: slave accept 
           service-classes: rendering, capturing, object transfer

Anything useful to be found here? The `Device-2` is the USB dongle that works just fine.
of c
I removed the USB dongle, and tried to bring it up:

Code: Select all

 sudo  hciconfig                                                                                                                     
hci0:	Type: Primary  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:3 acl:0 sco:0 commands:1 errors:0

Code: Select all

sudo hciconfig hci0 up                                                                                                              
Can't init device hci0: Connection timed out (110)

I also want to try if I can patch my `btusb.c` with the latest 5.15-rc1 `btusb.c` file (if possible). I can see a lot of changes there related to this driver. https://git.kernel.org/pub/scm/linux/ke ... &id2=v5.13 Maybe this is my solution, or I just have to wait a bit...
I am guessing if I download the source files for the kernel, and replace the `btusb.c` content from v5.15-rc1, would I be able to just compile the kernel and then install it with dpkg? I do not understand how things go with the patches to be honest

[SMG]

Anything useful to be found here? The `Device-2` is the USB dongle that works just fine.

Was the bluetooth dongle the device generating that output in dmesg earlier in the thread (that seemed to indicate bluetooth was working)?

The inxi developer did indicate the newer version had more info and I see it really helps for this type of issue. Look at all that bluetooth info.

I also want to try if I can patch my `btusb.c` with the latest 5.15-rc1 `btusb.c` file (if possible). I can see a lot of changes there related to this driver. https://git.kernel.org/pub/scm/linux/ke ... &id2=v5.13 Maybe this is my solution, or I just have to wait a bit...
I am guessing if I download the source files for the kernel, and replace the `btusb.c` content from v5.15-rc1, would I be able to just compile the kernel and then install it with dpkg? I do not understand how things go with the patches to be honest

I do not know all the dependencies with regards to bluetooth and I would suspect the patch may not be backward compatible (to prior kernel versions) without doing additional work.

As far as using the newer kernel with any patch you might do, you might run into issues with the Nvidia driver. Nvidia is doing better with regards to making sure drivers work with newer kernels, but I have not yet heard how well they work with the 5.15 kernel candidates. And I do not know if Mint might have any issues with it (probably not, but I do not know).

[KenoKokoro]

Thanks again for the response!

Was the bluetooth dongle the device generating that output in dmesg earlier in the thread (that seemed to indicate bluetooth was working)?

I only put the dongle for the first time when I updated the `inxi`. So everything before my last thread about the bluetooth, it was only from the laptop's bluetooth device.

And true for the newer kernels and nvidia. Even 5.14 kernels do not work with nvidia. But for me, I would try to put any other kernel, and then just boot with software rendering mode, just to verify that the bluetooth needs newer kernel/driver, and it is not something that is being stuck from the windows or something like that.
When I tried the 5.14.3 kernel, it was working even worse than the 5.13 that I am currently running in terms of support for the keyboard..etc.., but I am only curious about the bluetooth at this point. I don't think I will stick to those until they are well supported.

Weekend is coming, so I will have plenty of time to play around with this. I just wanna see the bluetooth working so I can diagnose the issue.

[SMG]

I only put the dongle for the first time when I updated the `inxi`. So everything before my last thread about the bluetooth, it was only from the laptop's bluetooth device.

So it seems like this is strictly related to the hardware. Just wanted to make sure I had been interpreting the prior data correctly.

And true for the newer kernels and nvidia. Even 5.14 kernels do not work with nvidia. But for me, I would try to put any other kernel, and then just boot with software rendering mode,

Actually, I would think you should be able to use the Intel driver which does have hardware rendering. Software rendering is when neither the Intel nor the Nvidia drivers load and you see llvmpipe as the renderer. Notice in the first inxi output of the thread that Intel was doing hardware rendering.

just to verify that the bluetooth needs newer kernel/driver, and it is not something that is being stuck from the windows or something like that.

My general approach is if there are issues listed on the Arch-based forums about the hardware (since they usually use the leading edge kernels and drivers), then it is likely just too new of hardware and not a Windows-related phenomena. That's not to say my approach is correct, but that's my approach.

[KenoKokoro]

Thanks again!

Actually, I would think you should be able to use the Intel driver which does have hardware rendering. Software rendering is when neither the Intel nor the Nvidia drivers load and you see llvmpipe as the renderer. Notice in the first inxi output of the thread that Intel was doing hardware rendering.

I see, I will double check this!

My general approach is if there are issues listed on the Arch-based forums about the hardware (since they usually use the leading edge kernels and drivers), then it is likely just too new of hardware and not a Windows-related phenomena. That's not to say my approach is correct, but that's my approach.

In all honesty, I think the issue is because it is too new of hardware. Just googling things like: `asus g14 bluetooth linux`, `asus mt7921 bluetooth` (there are for issues on arch/fedora/ubuntu) or anything related to the 2020?/2021 asus ROG/TUF laptop series, will lead to the same issues, since they replaced the intel wireless card with the mediatek.
I found some places where on the G14 2-3 people fixed it just by using Ubuntu 21.04 with the latest 5.14 kernel, but I can't find them for reference now for some reason, I found one of the post, but it is 404 on stackoverflow

I will play around over the weekend. I am finally home, with good internet, so it will be a lot of trial/error to see how to fix the bluetooth.

[SMG]

In all honesty, I think the issue is because it is too new of hardware. Just googling things like: `asus g14 bluetooth linux`, `asus mt7921 bluetooth`

I happened to notice in the latest linux-firmware update there is reference to firmware which might relate to your bluetooth device. Here is the changelog.

linux-firmware (1.187.20) focal; urgency=medium

* amdgpu: Add initial firmware for Beige Goby (LP: #1946304)
* Update firmware for MT7921 WiFi/Bluetooth (LP: #1947829)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
- linux-firmware: update firmware for MT7921 WiFi device

Here is the #1947829 bug report Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS . Not sure if it will help you, but it looks like progress is being made.

[KenoKokoro]

Not sure if it will help you, but it looks like progress is being made.

Yes yes! I am actually just waiting for the updates to be rolled out, so I can try them out to post back that hopefully things are fixed. In the meantime I just use a dongle for it, but I am hoping to get the updates soon.

Thanks for still keeping an eye on it!