I wanted to share this with other people since I always have to remember. I learned about this when I upgraded Fedora 35 to Fedora 36 and figured there was a better way than nuke’n’booting my desktop every 6 months.
If you attempt to install the latest version of Fedora via GNOME Software, in this case Fedora 37, you’ll most likely encounter an error if you have RPMFusion enabled for Nvidia drivers. One way to get around this is to follow the directions in the documentation, but add a few more flags to your command.
Thanks for the tip! I usually nuke and pave, but for the first time in forever I got an error when trying to do so. The error says the installation is missing a boot parameter, but when I press ‘e’ at GRUB to go to the kernel command line I see an inst.stage2 variable pointing to my drive and Fedora Silverblue 37.
I tried adding a simple inst.repo=hd but no luck. I did the sha256sum on the ISO before I wrote it to the USB and it matched, also used the recently updated Fedora Media Writer (Fedora Flatpak) to write the file to the drive. I’ll try rebasing and hopefully report back success! Thanks again for the command.
Hey so there is an important new part of RPM Fusion this time, the mesa-va-drivers-freeworld package which re-enables video acceleration for h264. I can’t get this to install, it keeps giving me this error. Any thoughts?
error: Checkout mesa-va-drivers-freeworld-22.2.3-1.fc37.x86_64: Hardlinking 89/c6114b411440ce804773e11b7218ee7a0a9c9b5749220a66009e62454f4fa7.file to nouveau_drv_video.so: File exists