Screen freezing on systemd-boot but boot finishes

General system Kernel, boot, graphics & hardware
1

I’ve had this issue a few times when i was first installing endeavourOS, but i was running it for two-three months with no issue until it happened again. My system boots through grub, and into systemd-boot, but right after either [OK] Started rule-based handler for files and events or [OK] Started rf killswitch (i dont remember what their names were exactly) it freezes. I’m able to use a live media drive to see logs and it seems to have finished the booting process behind the frozen screen, despite no response from the system once it does.

I can’t figure out how to post logs, but i do have them ready and i’ll try to post them in the comments if i can figure out how

2
3

Wait, i think i was confused. My install uses grub and boots into the init system systemd, not the boot-loader systemd-boot. Sorry for the confusion

4

That makes more sense. Would you be able to post some logs from the welcome app. Or you can do it manually.

Hardware info and boot log maybe?

5

boot-log: http://0x0.st/oaxK.txt
hardware-info: http://0x0.st/oxVV.txt

6

First thing i would recommend is updating the bios. There are like 16 newer versions so you should update to the latest version 3805. I also see your cpu is running pretty hot.

System Temperatures: cpu: 96.0

Edit: You may want to look at your current thermal solution and upgrade that.

Edi2: The boot log shows no entries. Post the link

journalctl -b -0 | eos-sendlog
7

The boot-log i sent you is the same one it sent with that command.
Just incase something got messed up, here it is again, this one is from re-running that command:
https://0x0.st/oaxK.txt

8

Did you originally run it from the welcome app? Because it’s not showing anything.

Edit: Could be a mirror issue depending on your location or something else.

9

I originally ran it by copy-pasting (not with ctrlc+v, that doesnt copy correctly for w/e reason) the command i found in the welcome app’s link on how to share log files into the terminal. (i did it from a chroot into the OS that is having the issues)

10

You could try updating the eos-mirrors on the Welcome app and see. I may be off track but not sure why it’s not working. Works here but i know some people have this issue but I don’t know why.

11

Can you also post

inxi -Ga
12

I ran it with eos-sendlog so i didn’t have to paste a whole wall of text into the forums and clog it up
https://0x0.st/oxVw.bin
i can paste the normal, non-eos-sendlog result if you need it

13

Yes that would be better.

14 
  12Device-1 Intel HD Graphics 530 12vendor ASUSTeK 12driver i915 12v kernel 12arch Gen-9 12process Intel 14n
    12built 2015-16 12ports 12active none 12empty DP-1,HDMI-A-1,HDMI-A-2 12bus-ID 00:02.0 12chip-ID 8086:1912
    12class-ID 0380
  12Device-2 NVIDIA GM206 [GeForce GTX 960] 12vendor Gigabyte 12driver nouveau 12v kernel
    12non-free 515.xx+ 12status current (as of 2022-10) 12arch Maxwell 12code GMxxx 12process TSMC 28nm
    12built 2014-19 12pcie 12gen 1 12speed 2.5 GT/s 12lanes 16 12link-max 12gen 3 12speed 8 GT/s 12ports
    12active DVI-D-1,HDMI-A-3 12empty DP-2,DVI-I-1 12bus-ID 01:00.0 12chip-ID 10de:1401 12class-ID 0300
    12temp 34.0 C
  12Display 12server X.org 12v 1.21.1.4 12with Xwayland 12v 22.1.4 12compositor xfwm 12driver 12X
    12loaded intel,nvidia 12unloaded modesetting 12alternate fbdev,nouveau,nv,vesa 12dri i965 12gpu nouveau
    12display-ID :0.0
  12Monitor-1 DVI-D-1 12model Asus VP228 12serial <filter> 12built 2017 12res 1920x1080 12dpi 102 12gamma 1.2
    12size 476x268mm (18.74x10.55") 12diag 546mm (21.5") 12ratio 16:9 12modes 12max 1920x1080 12min 720x400
  12Monitor-2 HDMI-A-3 12model Acer QG241Y 12serial <filter> 12built 2021 12res 1920x1080 12dpi 93 12gamma 1.2
    12size 526x296mm (20.71x11.65") 12diag 604mm (23.8") 12ratio 16:9 12modes 12max 1920x1080 12min 720x400
  12Message GL data unavailable for root.```
15

Can you put code tags around what you post?

Edit: You need to add 3 ``` before and after or 3 ~~~ or use the pre-formatted text button when you post it.

16

I see you are using nouveau open source driver. Any reason for not using the nvidia driver? I also see you have two monitors?

Edit: Your card is supported with the latest drivers.

17

I used noveau because i read somewhere (dont remember where) that the normal drivers caused this for some people, and i was ruling them out as an issue.

18

I don’t think i would agree with that with the hardware you have. I think as i posted earlier i would first update the UEFI Bios. Then you could try from there but i think it’s running way too hot. I know that’s not what you want to hear but that’s what i think.

I would look at the noctua cpu air coolers.

Edit: Something like this would be good but you need to look up what fits your processor, motherboard and case. This is just an example.

nh_d12l_1

I would also try it with the current nvidia drivers.

19

Could you please edit the title of the thread and change systemd-boot to something more appropriate to reflect the actual issue which has nothing to do with systemd-boot per se ?