I just tried a 2nd upgrade F8-> rawhide.
On reboot, it hung a long time on bringing up eth0, and failed. This never had a problem on F8.
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
When it went to start X, all I got was an 'X'. And an apparantly dead machine.
I rebooted into mode 3. Ran top. Nothing showed a significant load average. Quit top. Now, no response from keyboard.
Rebooted into mode 1. Looked at /var/log/messages. Millions(?) of lines from named. chkconfig named off. Rebooted again. Now, running OK, but still no eth0.
No wired shown in NM. Don't know why.
Neal Becker wrote:
I just tried a 2nd upgrade F8-> rawhide.
On reboot, it hung a long time on bringing up eth0, and failed. This never had a problem on F8.
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
When it went to start X, all I got was an 'X'. And an apparantly dead machine.
I rebooted into mode 3. Ran top. Nothing showed a significant load average. Quit top. Now, no response from keyboard.
Rebooted into mode 1. Looked at /var/log/messages. Millions(?) of lines from named. chkconfig named off. Rebooted again. Now, running OK, but still no eth0.
No wired shown in NM. Don't know why.
I am not certain but from memory I believe NM does not work with static ip addresses. If you have set up the ip manually at install this may be the problem. I would disable NM if this is the case. I had similar problems but once NM was disabled and i had configured eth0 manually everything went fine. Might be worth a try.
On Sat, May 3, 2008 at 2:58 AM, Neal Becker ndbecker2@gmail.com wrote:
No wired shown in NM. Don't know why.
check your ifcfg-eth0 file and see if NM_CONTROLLED=no or =yes or go through the properties dialog/tab in s-c-network for the eth0 device and make sure the checkbox for NM control is checked.
NM has grown some ability to parse the ifcfg files for devices. And s-c-network has grown some hooks to 'hide' devices from NM by setting a variable in the ifcfg file for each device. Make sure you aren't running to this. -jef
Neal Becker wrote:
On reboot, it hung a long time on bringing up eth0, and failed. This never had a problem on F8.
...
No wired shown in NM. Don't know why.
I tried upgrading to rawhide on Saturday (May 10).
My machine had a static IP, and as a result the networking was completely botched. Mercifully it was a local machine, not a remote one.
I had to disable NetworkManager, delete all ".bak" interfaces in system-config-network, and re-configure eth0.
This will be a killer bug for anyone doing remote upgrades...
- Mike
On Mon, May 12, 2008 at 6:52 AM, Dr. Michael J. Chudobiak mjc@avtechpulse.com wrote:
Neal Becker wrote:
On reboot, it hung a long time on bringing up eth0, and failed. This
never
had a problem on F8.
...
No wired shown in NM. Don't know why.
I tried upgrading to rawhide on Saturday (May 10).
My machine had a static IP, and as a result the networking was completely botched. Mercifully it was a local machine, not a remote one.
I had to disable NetworkManager, delete all ".bak" interfaces in system-config-network, and re-configure eth0.
This will be a killer bug for anyone doing remote upgrades...
- Mike
I have a static IP. In s-c-n, am I supposed to say NM controlled=yes or NM controlled=no?
NM controlled =yes in one sense might mean "Can NM turn this on for you given the static IP address and DNS setting"?
Saying NM Controlled = NO may mean "can we turn on eth0 for you, ignoring NM?"
Or NM controlled = yes might mean "Should NM try to run DHCP for you and destroy your IP settings and erase the DNS?"
See what I mean? It is unclear what the option means.
PJ