Every time I install Solus, I need to use the older 4.2 ISO and eopkg upgrade to 4.3 after installation. This is because after installing via the 4.3 ISO, the boot process takes at least 10 times longer and flashes a white line that grows and shrinks in resolution several times. It successfully boots the OS after like a full minute, but it loses that instantaneous effect that I get with a 4.2 install, where it was like 15 seconds max and seemed seamless.
Using the exact same methods (all defaults, single drive, clean wipe, sole OS), I have experienced this behavior on two other PCs (installing Solus for a friend and a brother) as well as several times on my own home PC. I'm very glad I had the 4.2 ISO laying around. But as time goes on, and the ISOs get further from eachother, I'm beginning to worry that this workaround won't prevail.
What can I do to prevent this from happening in the future? I use all the default settings and partition schemes from the installer between two versions, so I'm not sure what's causing the issue.
All this said however, it's baffling how brainless the upgrade process is between the versions, even if it's a rolling system, it's impressively handled and eopkg is very reliable. The scripts for auto-managing dependencies / cleanly applying upgrades etc are the only things in the Linux world to rival the usability of AUR with pacman/yay in my opinion.
(Side note, the time between 4.2 and 4.3 also happens to be when the kernel stopped supporting my dynamic mic input which has been plug-and-play since forever. I am able to fix this on Arch with by using pipewire instead, but I look forward to the day we can enjoy it here. And Wayland of course, on GNOME 41 the 144hz frame consistency for Ryzen cards is a game changer for Linux desktop, apps moves with such fluidity I haven't seen on xorg!)
