Bootloop in Grub menu, if "Restart" option is used

Logs: https://clbin.com/UkyYI

Issue: If I select Restart option then the system cannot boot past grub menu. It will restart again and will loop till grub. If i power down and start, then system boots fine.

Bought this laptop yesterday, and installed EndeavourOS today. Except Bluetooth(seems driver issue from what i can gather from internet), all looks ok.
Any help is appreciated.

For the Bluetooth, see if the following could help:

1 Like

Thanks for the reply mate.
That’s the first thing I did. Then, I started hunting for solution on google and " Mediatek Corp. Device 7961" chip has issues with bluetooth on linux. Sadly can’t find a solution.
Running this OS on old laptop and all is perfect.

1 Like

Are you dual booting Windows and EndeavourOS? Make sure that the fast start up feature in Windows is disabled & secure boot is disabled in Bios.

After use bluetoothctl to try to get the bluetooth working if everything is installed and enabled for it.

1 Like

Thanks for the reply.

Are you dual booting Windows and EndeavourOS? Make sure that the fast start up feature in Windows is disabled & secure boot is disabled in Bios.

Negative on Dual boot. Before install EOS, I had disabled fast start up & secure boot from Bios.

After use bluetoothctl to try to get the bluetooth working if everything is installed and enabled for it.

I tried following things:-

  1. While using bluetoothctl, i got “No default controller available”.

  2. Next I tried rfkill list all,

0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
  1. “systemctl status bluetooth” got me this:
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Sat 2021-09-18 21:49:55 IST; 25min ago
       Docs: man:bluetoothd(8)
   Main PID: 829 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18463)
     Memory: 2.1M
        CPU: 15ms
     CGroup: /system.slice/bluetooth.service
             └─829 /usr/lib/bluetooth/bluetoothd

  1. “systemctl list-unit-files | grep blue”
bluetooth-mesh.service                                                    disabled        disabled
bluetooth.service                                                         enabled         disabled
dbus-org.bluez.service                                                    alias           -
bluetooth.target                                                          static          -

  1. " lspci" output:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166a
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166b
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166c
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166d
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166e
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166f
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1670
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1671
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c3)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] (rev c3)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
05:00.0 Network controller: MEDIATEK Corp. Device 7961
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c4)
07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
07:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
07:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
07:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller

  1. “sudo dmesg | grep -i bluetooth”
[    2.804975] Bluetooth: Core ver 2.22
[    2.805002] NET: Registered PF_BLUETOOTH protocol family
[    2.805003] Bluetooth: HCI device and connection manager initialized
[    2.805007] Bluetooth: HCI socket layer initialized
[    2.805008] Bluetooth: L2CAP socket layer initialized
[    2.805010] Bluetooth: SCO socket layer initialized
[    2.829273] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.829277] Bluetooth: BNEP filters: protocol multicast
[    2.829282] Bluetooth: BNEP socket layer initialized

Any ideas.

PS: Purple theme looks really awesome on this site.

You have to use bluetoothctl to get it to connect. Its a whole process using bluetoothctl commands to start scan, pair, connect, etc etc.

Edit: Sometimes it just takes going through the process and remove it and set it up to work.

1 Like

Thanks for further reply.

You have to use bluetoothctl to get it to connect. Its a whole process using bluetoothctl commands to start scan, pair, connect, etc etc.

I have tried all the commands, but it still returns as below:

$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]# list
[bluetooth]# power off
No default controller available
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 wlan      phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked
inxi -nz
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8169 
  IF: enp4s0 state: down mac: <filter> 
  Device-2: MEDIATEK driver: mt7921e 
  IF: wlan0 state: up mac: <filter> 
$ sudo dmesg | grep -i blue

[    2.481360] Bluetooth: Core ver 2.22
[    2.481384] NET: Registered PF_BLUETOOTH protocol family
[    2.481385] Bluetooth: HCI device and connection manager initialized
[    2.481393] Bluetooth: HCI socket layer initialized
[    2.481395] Bluetooth: L2CAP socket layer initialized
[    2.481399] Bluetooth: SCO socket layer initialized
[    2.550849] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.550852] Bluetooth: BNEP filters: protocol multicast
[    2.550855] Bluetooth: BNEP socket layer initialized

$ /sbin/lspci -nnk | grep -iA3 net
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
	Subsystem: ASUSTeK Computer Inc. Device [1043:208f]
	Kernel driver in use: r8169
	Kernel modules: r8169, r8168
05:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7961]
	Subsystem: AzureWave Device [1a3b:4680]
	Kernel driver in use: mt7921e
	Kernel modules: mt7921e

lsusb -v | grep Bluetooth
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
      bFunctionProtocol       1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing

I tried a whole lot of basic troubleshooting for getting Bluetooth up and running from what i can find on google but nothing for it.

Any idea about bootlooping in grub menu if i just reboot machine. Not a deal-breaker as just power off and start, but to know a solution will be nice.

And again thanks for taking out time to help me out.

Did you check that bluetooth is turned on on this laptop?

1 Like

Also have you tried installing gnome-bluetooth and see if that works.

1 Like

Did you check that bluetooth is turned on on this laptop?

It worked on windows, but cannot make it work on linux.

Also have you tried installing gnome-bluetooth and see if that works.

Yes, It’s installed.


As you can see, this is what is in gnome settings.

So I just want to ask because your Topic Title Is a little off to me and your explanation. Is your problem with WiFi not working because this is your WiFi.

Network: Device-2: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: f000 
           bus-ID: 05:00.0 chip-ID: 14c3:7961 

Your bluetooth is

Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-4:2 
           chip-ID: 13d3:3563 
           Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: 
           hardware: no software: yes address: see --recommends 

Your title is about the Grub menu in a bootloop if you restart! So does your WiFi work? But Bluetooth doesn’t? And is the bootloop still happening?

I found this regarding the MediaTek mt7921e chip.

https://bbs.archlinux.org/viewtopic.php?id=267837

https://bugs.archlinux.org/task/72138?project=1&order=dateopened&sort=desc

Your WiFi is MediaTEK and I’m not sure if the bluetooth chip co-exists also on the same? Or is a separate chip

Anyway I just wanted to confirm if your WiFi is working and if it is only BlueTooth that isn’t working.

Edit: It seems that the device id’s are the problem in all that i read here.

1 Like

If you booted windows it may have claimed the BT adapter which happened to me when i needed to use my windows USB for a firmware update. It locked me outta the wifi/BT for a month or so (maybe a couple idr) till i decided to see if it worked in windows then it released it when i shut down instead of rebooting.

as for BT not showing in the gnome settings make sure

bluez-tools
bluez
bluez-libs
bluez-utils

are all installed and just reinstall them for good measure because it wont hurt anything to try it.

Im assuming youve tried

sudo systemctl disable bluetooth
sudo systemctl enable bluetooth
1 Like

@n1729m you may also need to get the latest linux-firmware git package for that as Michael at phoronix needed to on the ASUS ROG Strix G15 but it will likely be unreliable for the moment as its still seeing active work.

EDIT: Looking at your PCIe IDs Im betting you have the G15 advantage dont you?

This article may help you somewhat
https://www.phoronix.com/scan.php?page=article&item=ryzen9-5900hx-linux&num=2

2 Likes

This chip also has open issues related to disappearing or just not working

EDIT: Looks like some fixes coming in 5.15, If you trust me I could try building a kernel patched for you with a potential fix or if you have some sort of network connection and want to you could build it yourself.

This is the needed patch for it coming in 5.15

--- a/drivers/bluetooth/btusb.c	2021-08-14 00:37:46.712280128 +0300
+++ b/drivers/bluetooth/btusb.c	2021-08-14 00:41:57.333028926 +0300
@@ -410,6 +410,22 @@
 	/* Additional MediaTek MT7615E Bluetooth devices */
 	{ USB_DEVICE(0x13d3, 0x3560), .driver_info = BTUSB_MEDIATEK},
 
+	/* Additional MediaTek MT7668 Bluetooth devices */
+	{ USB_DEVICE(0x043e, 0x3109), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH |
+						     BTUSB_VALID_LE_STATES },
+
+	/* Additional MediaTek MT7921 Bluetooth devices */
+	{ USB_DEVICE(0x04ca, 0x3802), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH |
+						     BTUSB_VALID_LE_STATES },
+	{ USB_DEVICE(0x13d3, 0x3563), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH |
+						     BTUSB_VALID_LE_STATES },
+	{ USB_DEVICE(0x0489, 0xe0cd), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH |
+						     BTUSB_VALID_LE_STATES },
+
 	/* Additional Realtek 8723AE Bluetooth devices */
 	{ USB_DEVICE(0x0930, 0x021d), .driver_info = BTUSB_REALTEK },
 	{ USB_DEVICE(0x13d3, 0x3394), .driver_info = BTUSB_REALTEK },

You can easily apply it and build a kernel using TK-Glitches pkgbuilds

This i believe is related to your Mediatek chip preventing boot actually, the bluetooth and boot issues i think are related as it has been reported the mediatek chip will prevent you booting at times.

1 Like

Thanks for the reply mate.

Your title is about the Grub menu in a bootloop if you restart! So does your WiFi work? But Bluetooth doesn’t? And is the bootloop still happening?

Sorry, for not being clear.
Wifi works, but bluetooth doesn’t. Both are on integrated chipset.
If I restart, then the grub is displayed > timer times out > manufacturers logo and grub again. Keeps repeating until I manually power down and start again.

No issues, if i power down and start.
Hope this clarifies my issues.

As @Echoa pointed out fix is coming for it in kernel v5.15 and both of you provided what may be a potential fix for me.

I am going to manually compile it with patch included and see if it works.

Really appreciate you and @ricklinux for taking out time to help me mate.

This is the needed patch for it coming in 5.15

Thanks for pointing me in right direction. Will complie the kernel with the fix.

Understood.

Yeah man, I found it in stock so I went ahead. Beast machine with gorgeous EndeavourOS is perfect for me.

And again really appreciate you guys helping. It means a lot.

Yes i pointed that information out also in my post if you click on the links above. I just wanted to make sure i understood that it’s just the Bluetooth not working. Sometimes it hard to tell from the log if it’s on the same chip or not but i assumed it was. The 5.15 kernel will be around Halloween when it’s released so sometime after that it will make it’s way here.

1 Like

Yes, you did and I really appreciate you for taking time and helping me to hunt down solutions.

That’s on me for not being clear. I just suck at explaining things. But now i know, so if next time I need help I will try to explain to more concisely.

Happy to know. I jumped ship’s from windows 2 months back and I’m really grateful to myself that I choose EndeavourOS. Any issues i had, i solved them with your’s and Arch wiki.

Also shoutout to your “Welcome” app.

1 Like

I really hope that the mediatek chip will work down the road with newer kernel.

2 Likes

It seems like its getting a decent amount of use in newer laptops so i imagine it will. Just a matter of time.

1 Like