On 07/08/2009 03:39 PM, Peter J. Stieber wrote:
In the hopes of helping someone else out with similar problems... This machine was configured with static a IP address. A while ago the NetworkManager had problems with a static IP configuration so I switched the machine to the old network service. The static IP address problem has been fixed in the NetworkManager, so I enabled the NetworkManager in F10. After manually adding the proper lines to /etc/sysconfig/network-scripts/ifcfg-* to get DNS working, the NetworkManager worked under F10. When performing an upgrade reboot, the NetworkManager still had problems. It turns out this was anaconda's fault. It setup the system to use a Kickstart file that didn't have a static IP configuration line. When this is the case, anaconda defaults to using DHCP. This broke the install. I added the proper "network" line to /boot/upgrade/ks.cfg and the install is now working. Here is a bugzilla reference that will explain this better... https://bugzilla.redhat.com/show_bug.cgi?id=475027 I have upgraded this system several times. I must have loaded a pre F8 version because my boot partition was only 100 MB. This made it impossible to download the install image (111 MB) from mirrors during the preupgrade process. This made network access absolutely essential for the upgrade reboot to work. I really hope this helps someone else out, Pete
I had a similar problem. If using preupgrade, when it gets to the point where it displays a "reboot" button, edit /boot/upgrade/ks.cfg and add:
network --bootproto=static --ip=192.168.1.2 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=4.2.2.1 --device=eth0
Make sure it's all on one line. And, of course, substitute your own IP addresses. Save the file and click "reboot" and it should work.
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
