i installed fedora core 2 test 2 today and i am having the same problem i had with core 1...eth0 fails to initialize. the error is "tulip device eth0 does not seem to be present, delaying initialization".

i've checked lsmod, and the tulip module is active. tried to remove and insmod, but says it's busy. nic is aliased in /etc/modprobe.conf, and shows up in lspci.

ifup gives same error. any ideas on correcting this problem, i'm ready to switch distros?

pete

Remember you it's a TEST distro so , can have some bugs :/

Maybe try stopping networking before unloading tulip driver?

What does ifconfig show?

it's show your network config and infos ....

I know what ifconfig does...I meant what is the output when he runs ifconfig

ifconfig shows loopback only. stopped the network, removed the tulip module, reinserted. (got that QM_MODULES error, but read that that is normal....verified it was inserted w/lsmod).

still, i get "eth0 does not seem to be present, delaying initialization".

oops, forgot to mention that ifconfig DID did show sit0, but i disabled ipv6 in order to isolate the problem.

What worked for me,

I have a 21041 that Mandrake 9.1 drove fine with the tulip module. After upgrading (?!) to Fedora Core 2 test 2, I had to change to the DE4x5 module using Network Configuration, and my eth0 started working. It seems to die after a while, though. Maybe when/if the module auto unloads, then the kernel tries to reload the wrong (tulip) module? Just guessing.

Anyhow, Network Configuration is your friend, although you'll get tired of seeing him after a while. I'm trying to find how to keep the DE4x5 module around after a reboot. I'm afraid I'm gonna have to go to Network Configuration every new boot. (Which shouldn't happen very often, dammit.)

Fedora Core 2 test 2
kernel ver: 2.6.3-2.1.253.2.1

hooya27

After much googling and recompiling, I (a relatively newbie to Linux) found a solution that fixed the problem on my machine (Fedora 1.92 test 3). My symptoms were identical to those mentioned previously, but nothing on the internet solved my problem--so I resorted to the "It is already broken, so why not mess with it and break it more mode." The problem was quickly solved.

Course of action:
Read man modprobe to get a little insight into what was going on.
Ran modprobe de2104x...OK.
Ran modprobe tulip and received "FATAL: Error inserting tulip (/lib/modules/2.6.5.../.../tulip.ko): Unknown symbol in module, or unknown parameter (see dmesg)." This peaked my interest...why can't it load tulip.ko?
Ran dmesg...many "tulip: Unkown parameter 'mem'"
Edited /etc/modprobe.conf and removed everything after options tulip. I probably only needed to remove the mem parameter, but for good measure I removed it all.
Ran modprobe tulip...OK!
Tried to activate eth0 again...it worked!!!

I hope this helps someone else figure out their problem.

Press on.

Well, after finding the previous post, I have fixed this in my FC2 installation. So this problem is still there with the initial release of FC2.