That can be fixed if done properly.
Yep, I remember reading those threads at the time.
And I just remembered why I decided to try all this from fresh builds. I though it might help you guys nail down any problems. And then I got lost in the mess in my own head lol.
The problem is the migration to xlibre. It ends the GUI session, and if you are dsync’ing in the GUI it will abort the update midway. Which will either break sddm, systemd, or both.
OK, I can confirm 4271 works properly.
Does this mean xLibre might be behind these behaviours on the fresh installs?
I think that would explain why the wayland versions are fine yes?
It could just be bad images. That happens from time to time. I’m working another issue then I will download a recent ROME slim and check it.
NP. and no pressure either, take your time (-:
I can reproduce. Something with the ROME images is currently broken.
Here is likely what you are going to have to do.
- Pick the arch you want, because they are probably both broken.
znver1is probably fine. - Install as you normally would.
- Reboot after install, switch to a VT, log in on the TUI login prompt and do the following command to keep it from restarting:
sudo systemctl stop sddm - Continue to (attempt to) fix, by doing the following with the arch you chose:
sudo dnf in x11-driver-video-amdgpu -–enable-repo=cooker-znver1 - Reboot
- Login and test
I just tested on 4316 and got the same results also.
So far, all the latest ROME Plasma (slim and normal) builds that I have tried have been the same.
I will gladly do this now.
Before I do, I was going to offer (anyone there) for you to remotely access my machine if it’s possible, and if you wanted, to use my machine to do further testing.
I could do reinstalls here and then let you back in again if its needed/wanted.
Just thought I might be able to help in some way if its wanted/useful.
That’s not necessary, but the offer was very kind.
NP, glad to help in any way I can
Following those instructions now then (-:
I just dd’d build 4316 but the usb wasn’t recognised under the UEFI boot menu. I am redoing it now.
I just want to check, when dding, once the terminal prompt returns it means the dd process is finished and the USB can be removed yes?
This command is probably more helpful:
ok, so the conv=”fsync” will make sure it completes before reporting.
Why do the options in that have the “double quotes” around them where the one shown in here don’t?
I used dd without the quotes earlier and it worked.
I am a little confused?
Only necessary if there are spaces. As a normal practice, there shouldn’t be. I would just omit them.
np
OK, installed; logged in from tty2 (instead of splash gui)
Did those
rebooted from TUI
Same behaviour with the tty1 blinky )-:
Any errors installing x11-driver-video-amdgpu?
not that I noticed.
But I didn’t think to actively check for them :embarrassed:
Should I try that again from the install and actually check this time?
It would be obvious if there were.