This is a guide to upgrading from one version of Fedora to the next (24->25, 25->26, 26->27, etc)
Take note, that I have had every upgrade, issues with NVIDIA. I did get a functional mesa Wayland session or Xorg session, but a fix was needed
INSTALL UPGRADE SUPPORT FOR DNF
sudo dnf -y install dnf-plugin-system-upgrade --best
sudo dnf upgrade --refresh sudo systemctl reboot
sudo dnf system-upgrade download --releasever=27
If you run into issues you may need to use:
sudo dnf system-upgrade download --releasever=27 --best --allowerasing
If you are having issues upgrading and have third-party repositories installed on your system, you may need to disable these repositories while you are upgrading. For support with repositories not provided by Fedora, please contact the providers of the repositories.
REBOOT INTO UPGRADE TOOL
sudo dnf system-upgrade reboot
BOOT & UPGRADE
- Boot into the newest/latest kernel. This should be top of the list in GRUB2
- Allow the upgrade tool to do its magic.
- When complete reboot, to be certain everything went well.
UPDATE NEW SYSTEM INSTALL
sudo dnf -y update
If you are using Negativo's repo for NVIDIA drivers, and have any issues with the kernel module not working correctly, here is the fix:
sudo dnf -y reinstall nvidia-driver kernel-devel akmod-nvidia nvidia-driver-libs nvidia-driver-libs.i686
sudo dnf -y reinstall nvidia-driver kernel-devel dkms-nvidia nvidia-driver-libs nvidia-driver-libs.i686
I don't have a system to test out the rpmfusion NVIDIA drivers on for an upgrade. If anyone has any tips, I am all ears. Email me the procedure. I would presume it is similar:
dnf reinstall xorg-x11-drv-nvidia-libs xorg-x11-drv-nvidia-libs.i686 xorg-x11-drv-nvidia akmod-nvidia "kernel-devel-uname-r == $(uname -r)" dnf update -y
- For Lutris, add the repo for the version you are upgrading to to make the upgrade tool able to just migrate to that new version.
- Rather than allow for packages to be auto-removed, I prefer to manually do it, keep track of them, and decide after the new version is installed, if I want to keep using that program or not, and find a way to make it happen if I do. Sofar, since this has been a feature, I have been able to just install it normally once the system has booted up after upgrade. Its been exclusively oddball (read BADLY MADE PACKAGES) rpms that are not fixed this way.
- Do keep in mind you may run into a broken system after upgrade -- backup anything that you cannot lose (ssl keys, etc).