Description of problem: Hello, IMHO, the following question worths a FAQ or an explicit paragraph in RedHat's Install Guide: Please consider an x86_64 machine (hardware) with a fresh install of Fedora on it - the i386 version of Fedora. Is it technically possible to obtain a fully functional x86_64 installation of Fedora by *upgrading* the software, using the x86_64 installation CDs or DVD (i.e. without completely wipping and reinstalling the OS) ? Is such an upgraded installation reliable and clean (i.e., if possible, is this procedure discouraged) ? More of it: if possible in the first place, could such an upgrade be performed by yum also (i.e. starting from a fresh install of i386 to upgrade online to a x86_64 version, just by changing the appropriate repositories in yum's configuration)? Regards, Razvan Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I don't have an x86_64 machine to try this on. Could you please perform the experiment and document your results for me? I could then add this material to the IG.
Hello, Here is the experiment: I just performed a full, clean install of Fedora Core 6, i386 version, on a 64-bit architecture (PC - Asus P5LD2 SE motherboard, 1 GB RAM, 80 GB HDD). Installation went with no problem. For full documenting, here is the first part of the experiment: attached are the installation logs of the i386 full install. I tried to be as precise as possible: - I installed all packages in the distro (put all marks when selecting packages), in order to see if some package generates errors. - I did no online updates after installation, to compare logs easily after i386 installation and after x86_64 upgrade. I will come back with the second part: the x86_64 upgrade. Regards, Razvan
Created attachment 145439 [details] anaconda-ks.cfg after i386 installation
Created attachment 145440 [details] install.log after i386 installation
Created attachment 145441 [details] install.log.syslog after i386 installation
Created attachment 145442 [details] /var/log/anaconda.log after i386 installation
Created attachment 145443 [details] /var/log/anaconda.syslog after i386 installation
Created attachment 145444 [details] /var/log/anaconda.xlog after i386 installation
Created attachment 145445 [details] /var/log/boot.log after i386 installation
Created attachment 145446 [details] /var/log/dmesg after i386 installation
Created attachment 145447 [details] /var/log/messages after i386 installation
Created attachment 145448 [details] /var/log/rpmpkgs after i386 installation
Hello, Here is the second part of the experiment: the upgrade from i386 software to x86_64. It DOESN'T work ! The upgrade took very little time. Apparently, only x86_64 packages were "upgraded" / installed. After reboot: 1. on tke "normal" kernel I got a kernel panic. It says: Red Hat nash version 5.1.19 starting insmod: can't read '/lib/uhci-hcd.ko': No such file or directory and the same for ohci-hcd.ko, ehci-hcd.ko, jbd.ko, ext3.ko, scsi_mod.ko, sd_mod.ko, libata.ko, ata_piix.ko Obviously, I get a kernel panic (my S-ATA HDD can't be seen). 2. on the kernel-xen I got a few messages of: Red Hat nash version 5.1.19 starting request_module:runaway loop modprobe binfmt_464c and then the machine became unresponsive. So I used the CD, went into rescue mode and copied the same logs on a floppy. For documenting, here they are, *after* the upgrade. I hope they are interesting for a more knowledgeable user. ;-) Regards, Razvan
Created attachment 145781 [details] /root/install.log after unsuccesful upgrade
Created attachment 145782 [details] /root/upgrade.log after unsuccesful upgrade
Created attachment 145783 [details] /var/log/anaconda.log after unsuccesful upgrade
Created attachment 145784 [details] /var/log/anaconda.syslog ater unsuccesful upgrade
Created attachment 145785 [details] /var/log/anaconda.xlog after unsucessful upgrade
Created attachment 145786 [details] /var/log/boot.log after unsuccesful upgrade
Created attachment 145787 [details] /var/log/dmesg after unsuccesful upgrade
Created attachment 145788 [details] /var/log/messages after unsuccesful upgrade