You are not logged in.
Looks like yours: https://bbs.archlinux.org/viewtopic.php?id=289227
Offline
Looks like yours: https://bbs.archlinux.org/viewtopic.php?id=289227
Damn, it really does. I guess it's waiting until it's fixed then?
I got rid of "quiet" and added debug, earlyprintk=efi,keep, log_buf_len=16M but these messages go by so fast I can't really read it. Made a video of it and tried to slow playback down on youtube but quality isn't the best: https://youtu.be/1dhZM3RdzyI
Offline
Ah, the panel turns off (looks like it ends w/ unmounting the filesystems) - I had hoped the system would just stall there and show you the tail of the log.
amdgpu.runpm=0 amdgpu.bapm=0 amdgpu.aspm=0 amdgpu.audio=0 amdgpu.msi=0 pcie_aspm=off
Ideally, "amdgpu.dpm=0" but most likely the system will just not usably boot w/ that at all.
This is just graping for straws, btw. the "aspm" parameters should be inert anyway.
Offline
BTW is it any different with the LTS kernel?
Offline
https://bbs.archlinux.org/viewtopic.php … 8#p2123728
Edit: tl;dr it "works" b/c the amdgpu module crashes…
Last edited by seth (2023-10-02 18:40:12)
Offline
https://bbs.archlinux.org/viewtopic.php … 8#p2123728
Edit: tl;dr it "works" b/c the amdgpu module crashes…
Ah I see thanks! Also, I didn't realise this GPU is so new.
Last edited by topcat01 (2023-10-02 18:45:57)
Offline
seth do you think it is worth trying 6.6-rc4 or amd-drm-next?
Offline
You're asking because you're gonna have to build that, right?
It certainly looks like support-in-progress (from complete failure in the LTS to only some shutdown issues now)
Otoh is the ubuntu/mint situation where things work despite (or maybe b/c) the system basically crashing out of the session. And the systemd relation…
Mint might simply resort to a forced shutdown if the init process doesn't respond :\
6.6 is still a month out, so depends on how curious the OP (or the users in the other thread) is - I don't think we'll get why it failed, but ideally it's just fixed w/ the update.
*shrug*
Offline
seth do you think it is worth trying 6.6-rc4 or amd-drm-next?
Is there a manual on the wiki on how to get these running and what the best place is to find these? I found some stuff on AUR (linux-mainline, then linux-amd-drm-next and also linux-amd-staging-drm-next-git) but I'm not sure if those are the ones and if I can just build them using yay for example.
Offline
You can just build/install https://aur.archlinux.org/packages/linux-amd-drm-next and you can use yay for that, too. Yes.
Offline
yay: yes, it's probably the most simple way. _somebody_ will spawn telling you not to use it, though.
https://wiki.archlinux.org/title/Arch_U … g_packages
https://wiki.archlinux.org/title/Kernel … e_PKGBUILD => especially disabling the docs(chapter 2.1) and add the line "make localmodconfig" under prepare (chapter 2.2)
Edit: too slow
Last edited by jl2 (2023-10-02 19:56:24)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
Tried 6.6-rc4 and amd-drm-next but still the same issue. Also tried linux-firmware-git as it was suggested in a similar issue on the endeavour forum here and try to look for sp5100_tco or other stuff related to the watchdog but couldn't find any.
Otoh is the ubuntu/mint situation where things work despite (or maybe b/c) the system basically crashing out of the session. And the systemd relation…
Mint might simply resort to a forced shutdown if the init process doesn't respond :\
If on mint the system is basically crashing out of the session is it even safe for my hardware to use that? I would use that then for a while until the issue may be resolved in future. Don't have another GPU that I can use as I sold my 2080 when I got the AMD one "working" on Mint
Offline
I don't think that a bunch of crashing userspace processes is gonna harm your HW, notably
Oct 01 15:38:47 stoepsel-pc systemd[1]: Unmounted /run/user/1000/gvfs.
Oct 01 15:38:47 stoepsel-pc systemd[1]: Unmounted /run/user/1000/doc.
Oct 01 15:38:47 stoepsel-pc systemd[1]: Unmounted /run/user/1000.
Oct 01 15:38:48 stoepsel-pc systemd[1]: Unmounting /boot/efi...
Oct 01 15:38:48 stoepsel-pc systemd[1]: Unmounting /run/credentials/systemd-sysusers.service...
Oct 01 15:38:48 stoepsel-pc systemd[1]: Unmounted /boot/efi.
Oct 01 15:38:48 stoepsel-pc systemd[1]: Unmounted /run/credentials/systemd-sysusers.service.
Oct 01 15:38:48 stoepsel-pc systemd[1]: Reached target Unmount All Filesystems.
Oct 01 15:38:49 stoepsel-pc systemd-shutdown[1]: Syncing filesystems and block devices.
Also Mint resorting to a forced shutdown is nothing but a wild theory to make any sense out of the data at hand.
Your watchdog module was iTCO_wdt, there's no indication for sp5100_tco being present.
Did you ever try to reboot from the rescue.target?
Offline
Yeah, I still have iTCO_wdt on my blacklist. Reboot from rescue.target also doesn't work.
Offline