Ethernet Config not sticking..... Please help
 

i cant figure out why my config errant sticking (doesn't come up on boot), i tried turning off NetworkManager but that didn't help. the only way i can get it come up by service network restart


here is my setup:


FC9 32bit no GUI
1. Dual Intel® Xeon®
2. Intel® E7500 Chipset
3. Intel® 82546EB Dual Port Gigabit Ethernet Controller
4. 6x 64-bit PCI-X expansion slots
5. ATI RageXL 8MB PCI Graphic Controller

http://www.supermicro.com/products/m...0/P4DP8-G2.cfm

here is eth0 's config:

DEVICE=eth0
BOOTPROTO=static
HWADDR=00:30:48:2b:9a:96
ONBOOT=yes
IPADDR=192.168.1.102
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
TYPE=Ethernet
NM_CONTROLLED=no


oh yeah i'm a noob he he so any help is appreciated

Perhaps your network card is not being correctly initialised at boot.
For further help you should supply more detail of your setup e.g. distribution, hardware.
For hardware, the output of 'lspci' is usually very useful.
For setup, the output of 'lsmod', after boot and then after service network restart may be informative.

i tried that but i don't see anything changes, i don't think it's a hardware issue (wouldn't it tell me that device is missing in the install)

here is my hardware

1. Dual Intel® Xeon®
2. Intel® E7500 Chipset
3. Intel® 82546EB Dual Port Gigabit Ethernet Controller
4. 6x 64-bit PCI-X expansion slots
5. ATI RageXL 8MB PCI Graphic Controller
6. raid card forget what version

This chassis is server class board RH5 was installed for a client with no driver issue

Somethings to try:-

1. try commenting out NM config from the ifcfg-eth0 file.
2. Check for the software module once the server comes up (lsmod) to figure out if the network driver is loaded or not.
3. TG3 network driver is buggy on some specific hardware like Dell. Better use bcm drivers.

Rahul Khare

It depends on which of the 2(maybe three) config files you are changing. If you do not change the correct one (or all of them at the same time) they will not survive a reboot.

Googling your NIC, I see that it should be supported by the e1000 kernel module. Check that this is being loaded ('lsmod').
Apparently this NIC can be problematic.
http://fixunix.com/hardware/8418-int...ler-hangs.html

Did u tried removing the NIC & again installed the driver

Hi ThinkingEvo,

The few times I've encountered something similar has been due to the IPV6 module. If instead of the configured a IPV4 address you find that ifconfig output contains an IPV6 address. Blacklist this module