BUMP... No responses......? Let me rephrase my question. Standard issue Supermicro server with dual 10/100 network ports built in. RH9 and Fedora Core 1 see both network interfaces on cold-boot and everything works great. If I do a soft reboot (without physically powering the server down for a few seconds), the network cards are not seen as active and kudzu complains about removed hardware. RH 7.3 used to work just fine for a year on this machine. I've tried reloading both RH9 and Fedora thinking I missed something along the way - no change. Reinstalling RH7.3 works perfectly and detects both network interfaces every time. Is there anything I can do in the configuration somewhere to tell kudzu that the network cards are just fine, not to detect them again, and not to mess with the ocnfiguration? Cold booting works fine every time, so I don't get why a warm-boot makes it go crazy on both RH9 and Fedora. Thanks, Chris ----- Original Message ----- From: "Chris" <redhat-list@xxxxxxxxxxxxxxxxxxx> To: <redhat-list@xxxxxxxxxx> Sent: Monday, February 16, 2004 1:08 PM Subject: RH Fedora network interfaces > This issue appears to be affecting both RH9 and Fedora Core 1 on one server I am > working on and hopefully the fix is the same for both versions, hence I'm asking > here on a RH list. > > RH 7.3 was running fine on this particular server, Supermicro 6011D with dual > 10/100 ethernet ports built in. I just upgraded it to Fedora Core 1 and > everything works perfectly - other than when you do a soft-boot of the server. > It comes up with kudzu during startup, says both network cards have been removed > (they are built into the motherboard), and if you select ignore or do nothing, > it then finds two new network cards. But even telling it to delete the two > original cards and then setting up the two "new" cards doesn't work - it then > complains that the ethernet ports cannot be found, wrong IRQs, etc. I've tried > installing RH9 on this machine, with the exact same results. 7.3 works fine out > of the box, but for obvious reasons I don't want to run that old version > anymore. > > HOWEVER... Powering the server down completely and booting up makes Fedora (and > RH9) see the original network ports without problems. Every time. Cold-booting > makes RH9 and Fedora see the ports. Warm-booting makes both RH9 and Fedora go > crazy and not see the ports properly. I can reproduce this on every single > bootup, whether cold or warm, with the exact same results. > > Any ideas why this is happening and how to fix it? I've been pulling my hair > out for 2 days straight. If a cold boot sees these ethernet ports and > everything works PERFECTLY, why is warm-booting not working with properly > detecting the same ports?? > > Chris > > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
