 | | | Problem with NIC going inactive upon reboot | Problem with NIC going inactive upon reboot 2005-08-04 - By Smith, Albert
Back
> -- --Original Message-- --
> From: redhat-list-bounces@(protected)
> [mailto:redhat-list-bounces@(protected)] On Behalf Of Steven Jones
> Sent: Thursday, August 04, 2005 5:07 PM
> To: james.lytle@(protected); General Red Hat Linux discussion list
> Subject: RE: Problem with NIC going inactive upon reboot
>
> /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@(protected)]
> Sent: Friday, 5 August 2005 8:35 a.m.
> To: redhat-list@(protected)
> 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@(protected)?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
>
If you can reenable the device through xwindows then that tell's me that
the module is there but the onboot flag is incorrectly set.
Edit the ifcfg-ethx (x being the interface to be changed) file under
/etc/sysconfig/network-scripts
Look for the line that says ONBOOT
It probably has a NO next to it. Change it to a yes.
Then do a services network restart
You will see the device come down and back up.
Albert Smith
Sr. Unix Systems Administrator
HPCSA, RHCT
Genex Services
440 E. Swedesford Rd.
Wayne, PA 19087
albert.smith@(protected)
(610) 964-5154
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
Earn $52 per hosting referral at Lunarpages.
|
|
|