Occasional Shutdown Freezes

General system Kernel, boot, graphics & hardware
1

Hello!
I’ve been dual-booting EOS with windows 10 for a few weeks now. About 50% of the time, my system freezes like this (sorry for the horrible quality had to take it with my phone):

IMG_20240928_161123 Cropped
IMG_20240928_161123 Cropped1920×451 107 KB

The mouse and keyboard are disconnected and the system is completely unresponsive. All I can do at this point is force my PC to turn off by holding the power button. I tried setting acpi_osi to windows since apparently it could help and I’ve never had such problems in windows:

GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi='Windows 2020' nowatchdog nvme_load=YES resume=UUID=a34263f1-b86b-416e-9c9a-3baababb3064 loglevel=3 nvidia-drm.modeset=1"

Of course it didn’t help lol

Here’s my system info:

System:
  Kernel: 6.10.10-arch1-1 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.1.5 Distro: EndeavourOS
Machine:
  Type: Desktop Mobo: ASUSTeK model: H110M-R v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 3401
    date: 03/20/2017
CPU:
  Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 560.35.03
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    gpu: nvidia resolution: 1600x900
  API: EGL v: 1.5 drivers: nvidia,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03
    renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
  API: Vulkan v: 1.3.295 drivers: nvidia surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel
  Device-3: Focusrite-Novation Focusrite Scarlett 2i2 2nd Gen
    driver: snd-usb-audio type: USB
  API: ALSA v: k6.10.10-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.2.5 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 10:7b:44:4f:de:ef
Drives:
  Local Storage: total: 1.02 TiB used: 404.31 GiB (38.8%)
  ID-1: /dev/sda vendor: Seagate model: ST1000VM002-1SD102 size: 931.51 GiB
  ID-2: /dev/sdb vendor: Kingston model: SA400S37120G size: 111.79 GiB
Partition:
  ID-1: / size: 57.18 GiB used: 24.6 GiB (43.0%) fs: ext4 dev: /dev/sda6
  ID-2: /boot/efi size: 196.9 MiB used: 283 KiB (0.1%) fs: vfat
    dev: /dev/sda4
Swap:
  ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%)
    dev: /dev/sda5
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB available: 31.29 GiB used: 3.03 GiB (9.7%)
  Processes: 209 Uptime: 22m Shell: Zsh inxi: 3.3.36

And here’s the journal log for the last boot which got stuck: https://0x0.st/XgNe.txt

Any help would be appreciated!

2

Welcome @CheeseMeat! :wave: :sunglasses: :enos_flag:

Your motherboard UEFI/BIOS is about 9 versions behind. You’d need only update to the latest version if you choose to do that, but the notes suggest improvements to performance, stability and compatibility. It may not fix this issue, but it’s worth ruling out (and gaining the benefits of the update).

The other things you might check in your UEFI/BIOS (and re-check after a BIOS update):

  • Ensure Fastboot is disabled.
  • Ensure Secureboot is disabled.
  • Ensure legacy boot / CSM is disabled.
2 Likes
3

This is an excellent variable that needs to be ruled out.
If 10 versions behind, I’ll bet this is an uncomplicated bios with a lot of settings that have not been tried…
That’s another very real variable as well. OP has a new install, 10 weeks in, 50% hell.
Dear OP: eliminate variables.

[after what I learned last night I will shout it across the mountaintops for a long time. came into a free old laptop. nuked windows, made it GPT. would not install sh*t. what it would install would never boot. made master BIOS master passwords. This opened up new settings options that finally solved the problem].

1 Like
4

Thank you both!

I admittedly knew about the bios update but was kinda scared to do it :joy:

A few questions though. Do I have to update the bios through my windows install? I don’t think I could do it with Linux?
And more importantly, will it mess with grub or anything else?

5

Nevermind it was just a single file I had to copy over to my flash drive.

I updated the bios, disbaled fastboot, secureboot, and csm. will let you know if that did anything.

2 Likes
6

Being an Asus board, it’s likely you’ll be able to update it from within your UEFI/BIOS. This would be the safest way to update.

Here’s a guide on how to use the BIOS EZ Flash utility.
https://www.asus.com/support/faq/1012815/

As for whether it will impact Grub… well I have an Asus board (ROG Crosshair VII Hero), and I use Grub. I’ve not encountered Grub issues post BIOS update.

That said, I’ve seen others have issues, so I wouldn’t rule out the possibility. It may reset your BIOS settings, which could cause issues. As mentioned above, after an update you’ll need to:

  • Ensure Fastboot is disabled.
  • Ensure Secureboot is disabled.
  • Ensure legacy boot / CSM is disabled.

Not doing that will likely result in boot issues.

If you do encounter issues, have the Endeavour OS bootable ISO standing by on a USB drive (prepare this first if you have only one system). This article links to arch-chroot instructions, and explains how to “Repair GRUB on EFI/UEFI systems”.

https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/

1 Like
7

Haven’t encountered any more shutdown problems since. Thank you!

1 Like
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.