FC% Kernel Update Lost eth0

Fedora Core 5 just had a kernel update to 2. 6. 18-1. 2200. fc5. Following the update, I rebooted the system and get an eth0 error. During the boot, the system faults at determining IP information for eth0.

Everything Linux 1798 This topic was started by zenarcher, 2006-10-17 19:41

Discussion 2

zenarcher

237 Posts
Location -
Joined 2004-10-14

#157907

2006-10-17 21:41

Fedora Core 5 just had a kernel update to 2.6.18-1.2200.fc5. Following the update, I rebooted the system and get an eth0 error. During the boot, the system faults at "determining IP information for eth0." Following a long delay and pinging, it displays 100% packet loss...then continues through the boot process. I have no eth0 connection. When I reboot, back to the previous kernel, all works fine. I'm using an the ethernet port on my MSI K8T Neo-V motherboard running to my Linksys router. I've never experienced this kind of issue with other kernel updates on FC5. Anyone else having problems or an idea how to resolve it?

Cheers,
zenarcher

RED ALERT 2 PROBL;EM

Dual boot Ubuntu/Xp Pro problem

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.

Create a new user account. Registration is free and takes only a few seconds.

This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic

danleff

2895 Posts
Location -
Joined 2002-08-30

#157908

2006-10-18 20:47

When you boot the new kernel, did you look at the Network Configuration and see what it says about the interface? Does it list it as inactive? Also look and see if it looks like it is configured for the correct eth0 connection for the hardware. I believe this is a realtek lan interface?

zenarcher

237 Posts
Location -
Joined 2004-10-14

#157909

2006-12-17 11:53

I found the problem, danleff. Oddly, the ethernet port on the motherboard died....somehow, just when I rebooted the system. Anyway, the motherboard was under warranty....sent it back to MSI and they replaced it. Problem resolved.

Cheers,
zenarcher