Header Shadow Image

Red Hat Linux Fedora: Fedora 10 to Fedora 11 upgrade.

Well, Fedora 11 has been out for some time now.  And though I've been coping with the new KDE 4.0 deployment, my general experience has left me somewhat unsatisfied, though sure enough, there are good points about it.  Somehow I don't feel alone but can't help stick with it.  After all, KDE 4.0 is a COMPLETE rewrite of KDE in Qt4 and this sort of stuff is to be expected. 

With new things comes new apps like KDE 4.3 which I've been itching to get my hands on.  So with time permitting, I can get to do some updates in hope of getting lot's of the old functionality back in KDE or simply adapting to my new environment. 

Without further delay it's time to do some updates:

Before upgrading to Fedora 11, you may want to read about running into possible ATI issues in F11 and future support of certain graphics cards:

  1. nice -n 19 yum update (If you get No Packages marked for Update you are good.)
  2. cd /some/dir
  3. mkdir ./F10toF11
  4. cd ./F10toF11
  5. Ensure you have debuglevel=10 and errorlevel=10 enabled in /etc/yum.conf in case we need more debugging information.
  6. nice -n 19 yum -y upgrade (should be the same as step 1 above)
  7. nice -n 19 yum clean all
  8. nice -n 19 yum clean all (Just to make sure everything looks clean)
  9. wget http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/i386/os/Packages/fedora-release-11-1.noarch.rpm
  10. wget http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/i386/os/Packages/fedora-release-notes-11.0.0-2.fc11.noarch.rpm
  11. rpm -Uvh fedora-release*.rpm
  12. cat /etc/fedora-release  (Make sure ‘Fedora release 11 (Leonidas)‘ appears )
  13. nice -n 19 yum -y upgrade 2>&1|tee -a ./F10-to-F11-upgrade.Jul.11.2009.08.09.PM.txt
  14. Refer below for any issues and repeat from step 12) as necessary.


One of the easiest things to do is to run into problems.  If you ever do, try to a search this blog for some solutions I've encountered.  For some notable ones that popped up, see the section below.

Aside from the above, this upgrade was no exception to repo errors.  Just a note in case you are new here: CAUTION: Some steps during such upgrades require removal of certain RPM's.  If it happens that you end up rebooting after deleting an RPM before you fully upgrade, you may end up running into other issues.  You have been warned:

Error Downloading Packages:
  grubby-6.0.87-1.fc11.i586: failure: grubby-6.0.87-1.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  12:dhcp-devel-4.1.0-22.fc11.i586: failure: dhcp-devel-4.1.0-22.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  12:dhcp-4.1.0-22.fc11.i586: failure: dhcp-4.1.0-22.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  blender-2.49a-1.fc11.i586: failure: blender-2.49a-1.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  12:dhclient-4.1.0-22.fc11.i586: failure: dhclient-4.1.0-22.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  espeak-1.40.02-2.fc11.i586: failure: espeak-1.40.02-2.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  gstreamer-plugins-good-0.10.15-3.fc11.i586: failure: gstreamer-plugins-good-0.10.15-3.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  1:dovecot-1.2.0-1.fc11.i586: failure: dovecot-1.2.0-1.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  gdb- failure: gdb- from updates: [Errno 256] No more mirrors to try.

So I find by doing some digging ($ locate yum|grep cache) out that it's storing the updates in /var/cache/yum/updates/packages and go to that folder:

cd /var/cache/yum/updates/packages

Then locate the repos I need off the web.  Unfortunately they're off the testing repos so if you're reading this, you should weight the risks using these repos, if it's right for you before going forward.  I'm running Fedora, bleeding edge stuff, so these are fine for me.  I'll upgrade later when new updates become available (NOTE: I'm in folder /var/cache/yum/updates/packages when I run below commands effectively saving to this folder:

wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/grubby-6.0.87-1.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/dhcp-devel-4.1.0-22.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/dhcp-4.1.0-22.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/blender-2.49a-1.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/dhclient-4.1.0-22.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/espeak-1.40.02-2.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/gstreamer-plugins-good-0.10.15-3.fc11.i586
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/dovecot-1.2.0-1.fc11.i586*
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/dovecot-1.2.0-1.fc11.i586
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/gstreamer-plugins-good-0.10.15-3.fc11.i586.rpm
wget http://mirror.anl.gov/pub/fedora/linux/updates/testing/11/i386/dovecot-1.2.0-1.fc11.i586.rpm

Running the update again, it then resulted in:

Error Downloading Packages:
  1:dovecot-1.2.0-1.fc11.i586: failure: dovecot-1.2.0-1.fc11.i586.rpm from updates: [Errno 256] No more mirrors to try.
  gdb- failure: gdb- from updates: [Errno 256] No more mirrors to try.

I couldn't find anything for dovecot and gdb matching the above at the moment, leaving me with only the last sensible thing I could do:

$ rpm -aq|grep dovecot
$ rpm -e dovecot-1.1.16-1.fc10.i386
$ rpm -e gdb-6.8-32.fc10.i386
error: Failed dependencies:
        gdb is needed by (installed) kdbg-1:2.1.0-3.fc10.i386
        gdb is needed by (installed) bug-buddy-1:2.24.2-1.fc10.i386
        gdb is needed by (installed) ddd-3.3.11-19.fc10.i386
$ rpm -e kdbg-2.1.0-3.fc10.i38
$ rpm -e bug-buddy-2.24.2-1.fc10.i386
Could not parse file '/usr/share/applications/switchdesk.desktop': Key file contains line '????????? ?????????????' which is not a key-value pair, group, or comment
$ rpm -e gdb-6.8-32.fc10.i386

And that moved the upgrade forward.  Moving right along to rerunning step 13 above, we get this:

Transaction Check Error:
  file /usr/bin/keytab-lilo from install of syslinux-3.75-1.fc11.i586 conflicts with file from package lilo-21.4.4-26.i386
  file /etc/rc.d/init.d/iscsi from install of iscsi-initiator-utils- conflicts with file from package iscsi-
  file /sbin/iscsi-iname from install of iscsi-initiator-utils- conflicts with file from package iscsi-
  file /sbin/iscsid from install of iscsi-initiator-utils- conflicts with file from package iscsi-
  file /usr/share/man/man8/iscsid.8.gz from install of iscsi-initiator-utils- conflicts with file from package iscsi-

If you look closely, there are really two issues here which can be solved in this manner (By deleting the RPM's to the right of the error above):

$ rpm -e lilo-21.4.4-26.i386
$ rpm -e iscsi-

 Rerunning the upgrade, finally gave me after a few hours:

  xorg-x11-drv-spaceorb.i386 0:1.1.0-6.fc9
  xorg-x11-drv-summa.i386 0:1.2.0-2.fc10
  xorg-x11-drv-tek4957.i386 0:1.2.0-1.fc9
  xorg-x11-drv-ur98.i386 0:1.1.0-5.fc9
  xorg-x11-drv-wiimote.i386 0:0.0.1-1.fc9

You have new mail in /var/spool/mail/root

Sure enough the system booted fine but an old bug (unable to authenticate user) came up that was solved for Fedora 10 earlier.  This time it required another step.  Please see Fedora 10: unable to authenticate user and reenabling the root login access.


If you have not already done this, you may wish to visit the previous Fedora 10 upgrade post for both latest bugs and other issues encountered and remedied after the upgrade.  There is lot's new in Fedora 8 and above, with Fedora 11 not being an exception to that rule, so this upgrade may not be for all if you plan on using KDE.  KDE 3.X is worlds different then the newly shipped KDE 4.X.  Just a word of caution in case you are fully entrentched in the old KDE 3 functionality.  :)


Granted we all should be using a non root account.  Eventually, I would like to transition to one.  I can also understand how the open source community would like to keep their reputation of Linux being a safer operating system then windows.  All good things.

In respect of above, I've gone quite some time using the root account form above all else, resolving system errors I've had.  Thinking back I've saved countless of hours not using a plain user account and relying on su or falling into other restrictions thereby resolving issues that much more difficult.  I also do plenty of software configuration and administration which has a rather heavy relieance on previlidged accounts.  So for me, root is essential until I find time to transition my stuff over. 

Tom K.

Leave a Reply


  Copyright © 2003 - 2013 Tom Kacperski (microdevsys.com). All rights reserved.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License