You are not logged in.
I have installed arch on a friend's pc. and after an update KDE would no longer launch. Running startplama-wayland gave me a could not determine $DISPLAY error. Similarity glx info gave me a unable to open display error. However the gpu showed up just fine in lspci. Based on this I assume it is something with the drivers, unless the hardware was physically damaged exactly when I updated.
Could someone walk me through troubleshooting this, or send me a guide? I can't seem to find a cohesive guide for this, more so a random assortment of issues and their fixes, with not much way to tell the exact issue.
Here is the output of journalctl, grepped for amdgpu: https://drive.google.com/file/d/1zxEBj1 … sp=sharing
Offline
Mar 30 12:41:00 JoeysPC kernel: amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.0.1 test failed (-110)
Please post full journal (as root) and the part of /var/log/pacman.log relevant to the update .
EDIT:
see https://wiki.archlinux.org/title/List_o … n_services for methods to upload logs/journals to a public hosting site.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The log file was a massive 777MB, because of it I didn't upload the full thing, but maybe that was a clue of something very wrong, should have thought about that. It also compressed extremely well. Said journalctl log.
I messed with pacman a bunch, so I'm not exactly sure what update it was, but there are probably dates on the files I could use to search for what one I thought it was, I'll try to complete that some time tonight.
Offline
It now occurs to me I was messing with the cachyos repos, I though I was using them before, but I think they were messed up. Would it be helpful to try removing them, doing a pacman -Syu, and see if anything changes, or is that unnecessary? I also hadn't explicitly update that computer in quite a while. I believe the date where I updated and broke stuff was 2025-05-16.
Offline
sudo journalctl -b | wc -l # if that number isn't 10.000+ lines
sudo journalctl -b | curl -F 'file=@-' 0x0.st
https://wiki.archlinux.org/title/System … ing_output
You might also want to look at https://wiki.archlinux.org/title/System … size_limit
If you remove the cachyos repo
1. you've so far not been using archlinux but cachyos
2.
pacman -Syuu # allows "downgrades"
There's https://bbs.archlinux.org/viewtopic.php?id=305727 (seems to only affect nouveau + vmware, though) and in doubt try the LTS kernel
Offline
Sorry for taking so long to reply, got distracted with other things, I removed the cachyos repo, here is the journalctl from only the last boot: https://0x0.st/8Y6N.log
Offline
Jun 03 17:37:40 JoeysPC kwin_wayland_wrapper[741]: MESA-LOADER: failed to open dri: libxml2.so.2: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
Jun 03 17:37:40 JoeysPC kwin_wayland[741]: kwin_core: Failed to create gbm device for "/dev/dri/card1"
Jun 03 17:37:40 JoeysPC kwin_wayland[741]: kwin_wayland_drm: No suitable DRM devices have been found
https://archlinux.org/packages/extra/x8 … l2-legacy/ - but this means you've some non-repo binaries, specifically surrounding mesa and kwin
pacman -Qm
pacman -Qikk mesa libxml
Offline
I ran those commands, and a few others I don't remember, maybe they did something to help, or maybe they didn't, but it didn't work after running them.
It worked after running reinstalling everything via pacman -Qqn | pacman -S -
Offline
Those will only print information about non-repo packages and the integrity of mesa and libxml, they will not fix anything for sure.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline