/etc/modules.conf or (what ever it is in 2.6.x kernel), is the e1000 module shown as an alias? If not try alias eth0 e1000 reboot and see if that now works automatically. If it is there, it suggests a non-standard piece of hardware the standard linux e1000 module is failing to see (not unknown with embedded NICS, Broadcom is really bad for this). Try getting a later version of the kernel if that is possible, if not try Intel's site for the specific 3rd party module and install it in the kernel. Regards thing -----Original Message----- From: James Lytle [mailto:james.lytle@xxxxxxxxxxx] Sent: Friday, 5 August 2005 8:35 a.m. To: redhat-list@xxxxxxxxxx Subject: Problem with NIC going inactive upon reboot Configurations for 2 identical machines are as follows: P4 3.0 GHz processor Intel 915GEVLK motherboard (Gigabit ethernet) 1 GB DDR2 memory 3Ware 8506-4LP 2 WD800 Fedora Core 4 Problem I am having is that when the machines are rebooted, the network connection show to be inactive. I have to manually activate it under the Network configuration in XWindows. More of an annoyance than anything. Thanks! James Lytle IS Director -- 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
