Fedora 10 (x86_64) eth1: no link during initialisation

[neutrix]

Hi all,

I've been running Fedora 10 for the last 2 days, and after a while yesteday I got the following strange message when booting up the machine:

eth1: no link during initialisation
ADDRCONF(NETDEV_UP): eth1: link is not ready

Unfortunately this just appears in the console after plymouth finishes it's loading procedure and I'm stuck, unable to get into the operating system.

I then reinstalled the operating system incase anything had got corrupted and everything was back to normal. I just booted it up now and it has returned again, so I'm not sure what to do. Does anyone have any ideas how to fix this?

Thanks.

[mvpittman]

I got the same thing. I have to network interfaces on my board, so I get two messages.

My understanding is that it has something to do with udev not assgning network interfaces the same way each time it boots, but that's based on a old post in some debian list, and they solved it by hard-coding the interfaces.

http://lists.debian.org/debian-user/.../msg00075.html

The problem you and I have seems to be that it is keeping us from booting. I muttered something about "Fedora Sucks" and then went and booted Windows... I thought about switching distros over it, but I couldn't bring myself to do it.

I decided to give it another try, so here I am, answering your post, but without any real answers. Hopefully this brings some attention to it, or at least gives me a place to come back to if I ever solve the problem.

[mvpittman]

A little more searching got me here:

http://www.linuxhomenetworking.com/f...ad.php?t=18055

which is starting to make me thing it's a DHCP/IPv6 issue. I'm probably going to try re-installing and seeing if I can turn off IPv6 and just use IPv4.

[mvpittman]

Grr... I'm installing from a LiveUSB key. No option to select IPv4 vs. IPv6 in that install... However, a little more google-fu applied got me these two links:

https://fedorahosted.org/install-guide/ticket/26
http://www.g-loaded.eu/2008/05/12/ho...ra-and-centos/

I guess integration of NetworkManager in Fedora 10 is the source of our woes, but I could be off. My issues don't show up until I apply updates. Probably a kernel updated that does it, since my install works fine, but when I add repos, and do the kmod-nvidia dance and reboot, I get the error.

I'm not feeling like downloading and burning a DVD, and I don't really know a good way of disabling IPv6. However, I'm wondering if this is a good reason to get a different (better?) router. I've been thinking about going back to using ClarkConnect. Guess I could build a box and find out, huh?

[m-momr]

I have the same problem, does anyone have a solution yet?

[mvpittman]

No solution for me. I did get 32-bit Fedora 10 installed from a flash drive, and moved on. Since then, I killed the partition, and reinstalled on a second 32-bit computer as well.

I might give a 64-bit DVD install another try soon.

[m-momr]

my problem started when i installed the kmod-nvidia, all i want is the graphic driver not an ethernet driver, can i bypass the error by disabling boot dhclient?

[mvpittman]

My problem happened after kmod-nvidia too. Turning off the Ethernet controllers kind of fixed it, but then I didn't have any Internet. I'm thinking maybe there was an update in the kernel or the nvidia driver that made it work. Not necessarily my switch to 32-bit.

[valleyrat818]

I had the same issue. I installed F10, and I kept getting the "eth0: no link during initialization
ADDRCONF(NETDEV_UP): eth0: link is not ready" message 3-4 reboots after the initial install. The OS would not load, grrrrrrrrrrrrrrr.

I would re-install the OS, it was good for about 3-4 reboots, then it would hang again with the above mentioned error.

After trying to configure different networking settings from run levels 1 and 3 and making sure IPv6 was off, I finally just re-installed F10 again. This time before I did any 'yum update' command or mess with any network settings, I ran 'sudo yum install NetworkManager'

That did the trick, I didnt have to mess with any other settings! I've been using my latest F10 install for a week now and I have not gotten that dreaded ADDRCONF error again! woohoo!

[mvpittman]

I'm pretty sure my issue was with the nvidia driver and having two cards in SLI. I just didn't see the same problem when I got to Fedora 10, I guess.

I had to put a BusID line the "Device" section of my xorg.conf file, as detailed in this thread:

http://www.fedoraforum.org/forum/sho...d.php?t=190393

[m-momr]

yes i have 2x8800gtx in sli

[ygmarchi]

I have the same identical problem.

I started facing it after I did an 'apt-get upgrade' of my Debian Lenny installation (currently the testing distribution) few days ago.

So, either it's a bug related to the new software I installed, or it's due to the interaction of the new software with my 'old' configuration files. This latter situation has already happened to me (udev at some point broke compatibility with older rules).

Carlo.