Fedora 22 was released earlier this week, and if you are running Fedora 21, you will probably want to upgrade to the latest and greatest version of Fedora. Luckily, there is a tool called FedUp that is easiest way to upgrade to Fedora 22.
1. Make sure your current system is up-to-date and backed up
First up, ensure that you have the most up-to-date version of Fedora 21 by updating your system using the Software application, or running the following command in the terminal:
sudo dnf update
2. Install the FedUp tool
Now, open up a Terminal and install FedUp package by using the following command line:
sudo dnf install fedup
3. Start the update with FedUp
Now your system is fully up-to-date, start the upgrade using the following command:
sudo fedup --network 22
This command will tell FedUp to download all the appropriate packages from the Fedora repositories, and prep your system for the upgrade.
4. Reboot, and upgrade
Once the FedUp command from step 3 has completed without errors, reboot your system. In the Fedora Boot Menu (i.e. grub), there will be a menu item “System Upgrade”, select that and press enter.
Boot menu with update option selected
All the appropriate packages and upgrade tasks will now be completed automatically, and when completed you will be able to start using your newly upgraded Fedora system.
Further Information
For more detailed instructions on using FedUp for upgrading (including using a downloaded ISO or another installation source other than the network), check out the FedUp wikipage. This page also has details on issues that you may encounter during an upgrade.
Yu Zhou
Thanks! This is exactly what I am looking for!
dude
Thanks really healpfull!
What about the cleaning up section in the fedup wiki? Should I follow the wiki using dnf instead of yum?
Marco
I was about to ask the same thing!
Óscar Murcia
I’ve been trying to upgrade to Fedora 22 but I’ve had a lot of problems. The last problem was this message: “The volume “filesystem root” has only 0 bytes disk space remaining” Am I doing something wrong? Thanks in advance.
Felipe
I had the same issue too. Can somebody help us? 🙁
Veli-Matti
You should delete files, unused packages, leaves.
Some useful commands, in some cases:
yum-complete-transaction
package-cleanup –dupes
package-cleanup –cleandupes
package-cleanup –orphans
package-cleanup –leaves
package-cleanup –all
package-cleanup –obsoletes
package-cleanup –problems
package-cleanup –leaves | xargs -l1 yum -y remove
You can also delete some operating system, for example I had both gnome and kde and some third.
Moreover I had several language versions of same packages. I deleleted those I didn’t need
PanzerFury
AFAIK, the FedUp will download all the necessary files for the update prior to update. If you only have 200 MB of /boot size, the FedUp will fail (this was my case, since I dual boot to other OSes). I’ve ran gparted and resize/increased /boot to 400 MB, then reran FedUp. It worked this time.
In your case there is probably not enough space on /root to complete the download/upgrade.
Leo
I think it should be “yum” instead of “dnf” in 21.
Leo
jefby
dnf is available in Fedora 21
Andy Green
Very cool… fedup is also working on a headless (no video card) box over serial console if you have that set up already.
Ron Kurtz
After downloading and installing seveal times, still the bootloader will not finish installing and will not save to disk. My old laptop does not have an internal CD drive, I am using an external drive. It will not reboot after shutdown. The rest of 22 seems to have installed okay. The rescue program only asks for a user and password, I have no idea what that is.
Ron
Justin
Hi there, I first started using Fedora 20 about 2 weeks before Fedora 21 was available. I am new to Linux in general, and could not upgrade to Fedora 21, I just couldn’t figure out what I was doing!
Can I use this method to jump from 20 to 22?
Thanks!
Máirín Duffy
If you are too lazy to update the whole system pre-fedup (which you really should do) at least make sure you update systemd, otherwise the upgraded system won’t be able to boot.
acalonius gencatorum
It works perfect, but I recommend 2 tips: deactivate all installed extensions and deactivated automatic login.
To Fedora Project People: In Fedora 22 WS, fonts and graphics of ktorrent and okular don’t work properly (KDE apps). In Fedora 21, worked well.
From a Fedora newbie,
Thanks
MArk
I have many errors with the rpmfusion repos!!!!
Solution = delete all rpmfusion files in /etc/yum.repos.d/
Re-install rpmfusion repos after upgrade to Fedora 22
Thien
It so great 😀
Hakan Duran
Is the fedup option “–product=nonproduct” deprecated? I could not get this to work.
Thanks.
VTor
I will try Fedora 22 on a virtual machine, actually I have Fedora 21 and goes well, in my experience since Fedora 19, at the beginning, the newer version of Fedora is unstable but three months later runs very good.
If you have Fedora 21 updated, you can use dnf in replace of yum, these days I was updating the software with dnf and I have no problems.
Tigger908
Tried this last week and found that many of the repos I use don’t yet have fedora 22 versions. I can’t remember if it was livna or freshrpms which was the issue. There was a suggestion on the forums that these repositories were being moved to a different build system.
Ted Roche
You skipped step zero: make a backup of all the documents you can’t live without, and an image of the machine so you can restore in case of an unsuccessful upgrade. If you do this step, you almost never need them. If you forget this step, you almost always do.
Mitnick
I’m ready with my F22!
Fedup worked perfectly and after of 30 minutes… the computer had the new version 😉
Thanks for your effort!
Tomas
What if I am using KDE spin? Will this overwrite my KDE desktop with GNOME? And if so, how do I upgrade from KDE Fedora 21 to KDE Fedora 22, other than a clean install?
Matthew Miller
Going from the KDE F21 to KDE F22 spins with FedUp should just work — nothing special needed.
Hakan Duran
I have two computers with Fedora 21 KDE spin. The one that was not heavily customized upgraded to Fedora 22 with minimal problems using Fedup. However, Fedup consistently reports that it cannot find the boot images on the mirrors for the other one. I am guessing that this is due to heavy customization that happened over the course of 4 years (from Fedora 17 to 21, always upgraded, no fresh install in between). I would love to be able to upgrade again but since nobody seems to identify the source of this problem, it may be time for a fresh install.
Michael
Not in my case. When I got new F22, KDE stops working at all. After a lot of manipulations I got it worked. BTW any information or howtos I don’t found in Fedora wiki. Shame
dhinds
The Fedora 21 xfce spin 64 bit is installed on a Lenovo thinkPad W520 along with a number of other OS’s. I updated the system and installed fedup and downloaded the net 22 files but on rebooting, the system upgrade is not listed since the last grub installed belongs to another distro and selecting advaned options doesn’t help.
I reinstalled fedora’s grub using yumex but on rebooting again, the grub still wasn’t fedora’s.
Do I need to download the 1726 files again or can I activate the upgrade via the command line?
Thanks in advance for the orientation.
Isaque Galdino
I’ve upgraded using fedup and the whole process was great! I didn’t have to deactivate any of my repos (rpmfusion and adobe) neither my gnome extension (caffeine).
I understand that as standard as your rig is, the less trouble you’ll have.
I also have a few comments about the upgrade process:
1) it would be nice if it have been done using a graphical UI – perhaps you are already working on that; and
2) once the upgrade is performed it would be nice to inform about new software added/available, e.g. I didn’t know Builder was available in this version, I only knew when I read the other article about it.
I’d like to take this opportunity to congrats the whole team for a great work in this release. My box was never this beautiful and if this version can prove to be as trouble free as 21, I’m considering migrating my family computers (non-tech people) to Fedora – today they are running Linux Mint.
Thanks.
Tp
Hi All,
I m running F20 when i run the cmd below;
sudo fedup –network 22 –product=workstation
i get the message below after some time;
Try again later, or specify a repo using –instrepo.
what am i missing out?
Thanks,
TP – South Africa
Josef
When upgrading Fedora 21 to 22 I followed the procedure described above.
Everything went fine but the last step:
After rebooting there was no “System Upgrade (fedup)” option in the boot menu so I was not able to finish the upgrade.
Note: my Fedora is one of three systems on my multiboot desktop.
Any hint how to finish the upgrade? Thanks
Josef
I am sorry that my comment disappeared.
What was wrong with it?
Matthew Miller
Nothing; it just sometimes takes a while to get around to approving comments. There’s a lot of spam, and we also don’t generally approve comments which are entirely negative in nature. But that said, this isn’t generally the best help forum. Try http://ask.fedoraproject.org/ or one of the various other support options.
Josef
Please delete my comments to this post. I followed your advice, entered a question in Ask Fedora and in a few hours got answer with solution. My issue is now SOLVED. Fedora 22 works great.
Thank you.
dhinds
I fixed the grub problem by installing grub customizer and was able to get fedora to take over the grub from there. However, a second problem occurred, when I boot to the System Upgrade (Fedup) line on the Grub. This is what I get:
“[5.813568] dracut-pre-dev [318]rpcbin: Symbol ‘scvauth_none has different size in shared object, consider re-linking [58368171 dracut-pre-undev[318]
rpc.idmapd: Could not find group nobody.”
Then I had to do a hard reboot. The files WERE downloaded to /var/cache/systemupgrade.
I repeated this several times and repeated the process a couple of times also.
The quote given above was hand copied yesterday.
By what means can I correct this? (Meanwhile, Fedora 21 Xfce is up to date and working fine).
Meanwhile, I updated the fedora xfce spin on a desktop from 21 to 22 using fedup w/ no problems. If I get no answers here soon I will probably remove the system upgrade files and do it again.
Matthew
It was advised in previous helpguides that it is recommended to use the form shown below when you have a non-standard or non-Gnome workstation build :-
“su fedup –network 22 –product=nonproduct”
This upgrades what you have already and doesn’t force Gnome components onto the system if you have none already. Is this still true?
Same for non-standard Server builds.
Mogeni Elvis
I’m trying to update my computer with the network. It has done fine with ‘sudo dnf update’. The nightmare is that it is not having all the packages installed even after updating the system then starting the upgrade via network. Will it work fine with the “FAIL” reported packages after the whole download is complete?
Neville A. Cross
The wiki has a section about “cleaning post upgrade”
Most commands are directly related to rpm.
it is distro-sync migrated to dnf?
It is this clean up still a good practice or it fedup has it integrated?
John W
Made mistake of updating my work desktop F21-F22
Feedback: after 4 hours:
BCM5755 interface disappeared from system: (tg3) – cant get back.
3f:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express [14e4:167b] (rev 02)
All sorts of Repo complaints (Adobe, Fusion, XCat). (should remove these?)
NVidia re-work is really unclear – Nouveau, Nvidia-Redhat or NVidia-Nvidia.
Last Fed-ups were pretty clean. Hope to get this back 100% soon.
Hiisi
And the last step should read:
sudo dnf distro-sync
Saiful Bashar
I think i will stay with fedora 21 because installing fedora 22 I faced display problem . Screen all time shaking and all window looked like broken . The problem started after updating the system .I had no idea what happened .
Lawyno
Worked like a charm!
I love how everything looks more polished now!
Thanx! 🙂
Sumosa Jr.
Hi everybody! help me please! the upgrade failed and the terminal show me this message. Thanks
warning: /var/cache/dnf/x86_64/21/google-chrome/packages/google-chrome-stable-43.0.2357.81-1.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
Error: Public key for google-chrome-stable-43.0.2357.81-1.x86_64.rpm is not installed
Alvah
I just updated my laptop to Fedora 22 from Fedora 21. The process worked very nicely with one minor problem. When the laptop boots up, it boots into Gnome, I would prefer to use KDE. In Fedora 21 I could chose which Window manger to use from the login screen. When I go to select KDE from the Fedora 22 loging screen , KDE is not in the list. Is there an easy fix.
Thank you
Tuong
Help me!
Error: Failed to synchronize cache for repo ‘updates’ from ‘https://mirrors.fedoraproject.org/metalink?repo=updates-released-f21&arch=x86_64’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Pulak Arun
i typed in the first commands: sudo dnf update and its nearly 4 hours after which still the terminal shows waiting for process wit pid 11853 to finish. and when i look up the specified pid process in process explorer i see its the dnf process. i am new to fedora 21. please help!
Alessandro Perucchi
By using that procedure, I have one problem… it gives me the following error message:
$ sudo fedup –network 22
Using metadata from Wed Nov 4 17:18:06 2015 (0:17:47 hours old)
Error: cannot install both mozjs17-17.0.0-12.fc22.x86_64 and mozjs17-17.0.0-12.fc21.x86_64
And the only way I could find to solve my issue was before running the “sudo fedup –network 22” to run the following command:
$ sudo rpm –nodeps -e mozjs17-17.0.0-12.fc22.x86_64
and then the fedup command was working… I’m now waiting that the 2.2 GiB of data are downloaded, and I hope the upgrade will go smoothly.
BTW, the fedup told me that he will install the mozjs17 🙂 so it should be good!!
ekimnosneb
As is seen in this Fedora bug (https://bugzilla.redhat.com/show_bug.cgi?id=1284502), just removing mozjs17-17.0.0-12.fc21.i686 with “dnf erase mozjs17-17.0.0-12.fc21.i686” was the solution I used to be able to proceed with the upgrade to Fedora 22.
Alessandro Perucchi
In fact there is an error with this web page… today (04. of November 2015), after running the command “sudo fedup –network 22”, you should run the command “sudo dnf system-upgrade reboot” otherwise it won’t work… and you’ll need to wait at least 5 to 10 minutes, until this crap of systemd gives you back the hand to login and do that command…
So please update this page, because it might have been correct 6 month ago, but today this is not the case anymore.
Cheers,
Alessandro