Yum upgrade from FC5 to FC6

From MyWiki

Jump to: navigation, search

Contents

Prerequisites

  • Make sure your running a kernel >= 2.6.17 Otherwise, you'll get this during the yum upgrade:
    Error: Package hal conflicts with kernel < 2.6.17
    • Edit /etc/grub.conf to check/set default
    • Reboot into desired kernel
    • rpm -e old kernels
    • Check/verify that /etc/grub.conf is ok

Procedure

  • Run the following command first to ensure that you dont run into any residual dependency issues: 
 $ yum clean all
  • Update the package deciding which yum repositories to use: 
 $ rpm -Uhv ftp://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/Fedora/RPMS/fedora-release-\*.noarch.rpm
  • Do the upgrade: 
 $ yum upgrade
  • Again, check /etc/grub.conf to make sure the system will reboot to the new FC6 kernel. The first kernel listed is the kernel to be booted, if default is set to 0. The default setting is an index for the entry to boot (starting at 0). 
title Fedora Core (2.6.22.5-49.fc6)
        root (hd0,0)
        kernel /vmlinuz-2.6.22.5-49.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.22.5-49.fc6.img
  • Then restart the system: 
 $ reboot
  • After the reboot, remove the fc5 kernel 
rpm -e `rpm -qa|grep kernel|grep fc5`
  • And clean up the yum cache 
 $ yum clean all
  • Reinstall the Tivoli client, if it was necessary to remove it earlier in the upgrade (see below for details)
  • Run vmware-config-tools.pl (see below for details)
  • Then restart the system once more to ensure all startup scripts are set correctly: 
 $ reboot

Troubleshooting

Missing Dependency for Tivoli Client

  • During yum upgrade, if you receive a missing dependency (compat-libstc++...) for the Tivoli software, you may want to uninstall the Tivoli packages until after the upgrade to FC6 (there may be better/easier way, but this is what I did). 
rpm -e TIVsm-API 
rpm -e TIVsm-BA
  • After the upgrade is successful, reinstall the Tivoli software 
cd /tmp

ftp backup.ncsa.uiuc.edu (anonymous)
cd nonafs (on ftp server)
ascii
get tiv_install.sh
bin 
get linux86.tar
quit (ftp)

chmod +x tiv_install.sh
./tiv_install

vmware-config-tools.pl

  • If you receive the following during vmware-config-tools.pl: 
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] 
  
The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match
your running kernel (version 2.6.22.4-45.fc6).  Even if the module were to 
compile successfully, it would not load into the running kernel.
  • This is caused by running an older version of the vmware-config-tools.pl script. The 1.0.3 version seems to run fine on FC6, so
    • Uninstall vmware tools
    • Install version 1.0.3 (or higher) of vmware tools (root@swiki:~/vmware/VMwareTools-1.0.3-44356.i386.rpm)
    • Rerun vmware-config-tools.pl

Problems with VMware and FC 6 X-Windows

  • In some cases there have been problems starting X-Windows when running FC6 on VMware. If you see the following error message, you have a problem: 
 $ startx
 
 X Window System Version 7.1.1
 Release Date: 12 May 2006
 X Protocol Version 11, Revision 0, Release 7.1.1
 Build Operating System: Linux 2.6.9-42.0.8.ELsmp i686 Red Hat, Inc.
 Current Operating System: Linux gridshib-ca 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686
 Build Date: 26 February 2007
 Build ID: xorg-x11-server 1.1.1-47.6.fc6
       Before reporting problems, check http://wiki.x.org
       to make sure that you have the latest version.
 Module Loader present
 Markers: (--) probed, (**) from config file, (==) default setting,
       (++) from command line, (!!) notice, (II) informational,
       (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar  2 04:42:49 2007
 (==) Using config file: "/etc/X11/xorg.conf"
 Data incomplete in file /etc/X11/xorg.conf
       Undefined Monitor "vmware" referenced by Screen "Screen0".
 (EE) Problem parsing the config file
 (EE) Error parsing the config file
 
 Fatal server error:
 no screens found
 (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
 (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
  • Replacing the current xorg.conf with this xorg.conf file seems to work. Remember to save a copy of your current xorg.conf just to be safe.

Other Resources

Retrieved from "http://mywiki.ncsa.uiuc.edu/wiki/Yum_upgrade_from_FC5_to_FC6"
Personal tools