You are not logged in.
Pages: 1
So, in terms of related troubleshooting, I have tried leaving it for 6 hours, nothing changes. I have also tried the "power off, unplug, hold power button" to get rid of static. That didn't help either. The only things I have access to are the tty and Arch iso usb.
I have a pretty new AMD Ryzen CPU, so it's probably Zen5. I have tried to downgrade the kernel from linux6.17.8 to 17.7, but that didn't help.
Is there a way to get around the issue, for instance, keep the cpio running even if it isn't truly random? The seemingly obvious answer of starting the KDA Plasma desktop from tty doesn't work because
the Qt platform plugin "xcb" could not be loaded even though it was found
Any help would be appreciated.
Last edited by konokaiden (2025-11-24 06:08:57)
Offline
https://bbs.archlinux.org/viewtopic.php … 9#p2274119
seemingly obvious answer of starting the KDA Plasma desktop from tty doesn't work because
Offline
"clearcpuid=rdseed"
Is already present on the linux line of Grub, and the error still shows (plus doesn't boot into plasma automatically).
I was able to start plasma with the code from the wiki. The code I had tried came from the top answer on this r/archlinux post:
https://www.reddit.com/r/archlinux/comm … madesktop/
Which needless to say was not sufficient.
Last edited by konokaiden (2025-11-24 09:46:43)
Offline
I was able to start plasma with the code from the wiki. The code I had tried came from the top answer on this r/archlinux post:
https://www.reddit.com/r/archlinux/comm … madesktop/Which needless to say was not sufficient.
that post is 11yrs old
startx /usr/bin/startplasma-x11 # ??
startplasma-waylandOffline
Because of your other thread, is the RDSEED32 error now gone?
What's the output of
lscpuOffline
konokaiden wrote:I was able to start plasma with the code from the wiki. The code I had tried came from the top answer on this r/archlinux post:
https://www.reddit.com/r/archlinux/comm … madesktop/Which needless to say was not sufficient.
that post is 11yrs old
startx /usr/bin/startplasma-x11 # ?? startplasma-wayland
Maybe those will work, I'll have to try it sometime. X11 has scaling issues, so I don't want to boot into it. My monitor setup requires some of the features introduced after X11, so wayland is the way to go.
On the age note, I wasn't aware that "run desktop environment" had changed. Seems like a command you'd want to change as little as possible over time. But mostly, I wasn't looking at the dates, as it was one of the first things to pop up
on a google search, and it was the easiest to understand.
/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland is what worked for me.
Last edited by konokaiden (2025-11-24 12:31:50)
Offline
Because of your other thread, is the RDSEED32 error now gone?
What's the output oflscpu
No, the error message persists, but I'm able to use my computer and everything is as it was. So I can wait for Linux 6.18 to come out and resolve the issue (plus whenever the BIOS updates happen).
I don't usually turn it off, but rebooting is standard when changing certain things up, so with all the MATLAB troubleshooting we were doing on another thread, I rebooted and just now am seeing the error,
while others saw it a week or two ago.
Offline
So I can wait for Linux 6.18 to come out and resolve the issue
Ie you think you're running into https://www.phoronix.com/news/AMD-Zen-5-RDSEED-CachyOS
Are you running CachyOS?
Offline
No, I'm running vanilla Arch. I think I'm running into
https://www.amd.com/en/resources/produc … -7055.html
Last edited by konokaiden (2025-11-24 20:11:52)
Offline
You can pre-test https://pkgbuild.com//~gromit/linux-bis … kg.tar.zst
Offline
Pages: 1