The upgrade to the 4.18 kernel requires different amdgpu command line settings for my ancient AMD “Sea Islands” GPU. I can test that by letting it boot up with “radeon”.
Some vital package was removed - an awful lot of packages that look important got taken away, as you can see from the gist.
I couldn’t get a console to look at messages - once it prints out that it has started gdm the keyboard no longer accepts keystrokes
Update: the 4.18 kernel / AMD Sea Islands issue is at least part of the problem. I can get a console with carefully minimized “kargs” settings. But still no GNOME Display Manager login prompt.
The amdgpu driver is in rapid flux these days to cope with numerous new cards and it’s not at all surprising that a five-year-old card isn’t getting treated fairly. I can at least troubleshoot gdm now.
cannot update repo 'rpmfusion-free-updates': Cannot prepare internal mirrorlist: file "repomd.xml" was not found in metalink
How can I solve this? And the error appeared not before downloading the whole image – can’t this be checked in advance? Quite some checks just are done afterwards, this wastes a lot of time…
// At installing the RPM Fusion 29/branched RPMs on F28SB via sudo rpm-ostree install <RPMs>), I get these error messages:
0. nothing provides system-release(29) needed by rpmfusion-free-release-29-0.5.noarch
1. nothing provides system-release(29) needed by rpmfusion-nonfree-release-29-0.5.noarch
//// After uninstalling all layered RPMs, removing local RPM-Fusion packages and COPR files of /etc/yum.repos.d/, I was able to rebase. Sadly, F29SB turns out to be extreeeemly slow and lauchnching some programs (for example gnome-terminal) caused the whole system to freeze (all extensions disabled). Should I report this anywhere, or is this normal for the current beta phase?
Update: An rpm-ostree rebase from Atomic Host 28 to Silverblue 29 was successful in a Virtual Machine Manager virtual machine with 2 GB of RAM and 1 core. There are some anomalies with the desktop - I can log in normally (default Wayland) but if I try to log in with GNOME on Xorg it sits there for about a minute and drops me back to a GDM login. The display seems painfully slow - I’m going to push the RAM up to 4 GB and add a processor before I do any more testing on it.
The slowness might be due to an sepolicy issue that has just been fixed. Until a new image is available, you can try editing /etc/selinux/config and changing SELINUX to permissive instead of enforcing.
By the way, as we speak of SE-Linux: I get one or two geoclue warnings almost every time I log in, and sometimes I even get immediately thrown out of the shell again, when I log in.
And is it ok to layer atomic and use it still, or may this cause issues? It’s nice that I don’t have to type in my password with atomic.