You are not logged in.
Hi!
As the title says, when booting I get stuck on load/save random seed for minutes until it boots. My second problem which may or may not be related is that when I run "shutdown" it seems to do most of what it is required but the computer never shuts down. This is from a fresh install.
To deal with the first problem I have tried three different kernels, tried updating mesa/amdgpu (since I suspect the graphics drivers).
journalctl -b for boot
https://pastebin.com/fcCzQ8bN
journalctl -b -1 -r for shutdown
https://pastebin.com/NkTk62Lm
I hope those two logs are what is relevant. Let me know if there is something more I need to provide.
Last edited by discocutie (2021-08-30 20:36:58)
Offline
For issue 1 see here
https://wiki.archlinux.org/title/Haveged
Offline
Thank you for the reply!
Doesn't it look like from the log that the random seed finishes loading after ~1s but I still don't get to a login screen until a few minutes later? Sorry, I'm not trying to be rude and I will give Haveged a shot if you think that's what is wrong.
Not too good at randomness and encryption but according to my understanding there shouldn't be any security issues related with getting it, right?
Offline
The part below can be seen closely before I get to the login screen (taken from the boot log). It looks to me (newbie) like after whatever got killed on that thread blocked from SDDM starting. Is it related to amdgpu?
Aug 18 21:42:27 archcutie kernel: amdgpu:
failed to send message 260 ret is 0
Aug 18 21:42:35 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:42:39 archcutie kernel: amdgpu:
failed to send message 260 ret is 0
Aug 18 21:42:47 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:42:51 archcutie kernel: amdgpu:
failed to send message 260 ret is 0
Aug 18 21:42:57 archcutie systemd-udevd[333]: 0000:06:00.0: Worker [365] processing SEQNUM=3155 killed
Aug 18 21:42:59 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:43:03 archcutie systemd-udevd[333]: Worker [365] terminated by signal 9 (KILL)
Aug 18 21:43:03 archcutie systemd-udevd[333]: 0000:06:00.0: Worker [365] failed
Aug 18 21:43:03 archcutie kernel: amdgpu:
failed to send message 260 ret is 0
Aug 18 21:43:03 archcutie kernel: amdgpu 0000:06:00.0: amdgpu: Using BACO for runtime pm
Aug 18 21:43:03 archcutie kernel: [drm] Initialized amdgpu 3.41.0 20150101 for 0000:06:00.0 on minor 0
Aug 18 21:43:03 archcutie sddm[487]: Adding new display on vt 1 ...
Aug 18 21:43:03 archcutie sddm[487]: Loading theme configuration from ""
Aug 18 21:43:03 archcutie sddm[487]: Display server starting...
Aug 18 21:43:03 archcutie sddm[487]: Adding cookie to "/var/run/sddm/{0e45e8b3-78a3-432c-ae58-5b85186af447}"
Aug 18 21:43:03 archcutie sddm[487]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{0e45e8b3-78a3-432c-ae58-5b85186af447} -noreset -displayfd 17
Aug 18 21:43:06 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:43:10 archcutie kernel: amdgpu:
failed to send message 154 ret is 0
Aug 18 21:43:11 archcutie kernel: amdgpu 0000:06:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on uvd (-110).
Aug 18 21:43:15 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:43:19 archcutie kernel: amdgpu:
failed to send message 15a ret is 0
Aug 18 21:43:19 archcutie kernel: [drm:process_one_work] *ERROR* ib ring test failed (-110).
Aug 18 21:43:23 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:43:27 archcutie kernel: amdgpu:
failed to send message 155 ret is 0
Aug 18 21:43:31 archcutie kernel: amdgpu:
last message was failed ret is 0
Aug 18 21:43:35 archcutie kernel: amdgpu:
failed to send message 15b ret is 0
Aug 18 21:43:35 archcutie sddm[487]: Setting default cursor
Aug 18 21:43:35 archcutie sddm[487]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Aug 18 21:43:35 archcutie sddm[487]: Display server started.
Aug 18 21:43:35 archcutie sddm[487]: Socket server starting...
Aug 18 21:43:35 archcutie sddm[487]: Socket server started.Offline
I forgot to update this earlier but the solution to both issues was updating my B450 AORUS ELITE (rev. 1.x) motherboard's firmware to the latest version. Hope it is of help to someone else out there with the same issue.
Offline