[SOLVED] howto activate the NIC in CentOS 6.4?

lleb · 08-21-2013, 07:25 PM

I have the MSI 970A-G43 up and running with the old HDDs from my CentOS
6.4 server. Everything seems to be fine EXCEPT the NIC. After digging
the googles it turns out the RealTek onboard NIC is a royal PITA for Linux
in general especially for my kernel:

2.6.32-358.14.1.e16.x86_64 SMP

I picked up a PCIe Intel 10/100/1000 NIC that should work in my system,
but I can not get it to run. Again hitting the googles i found the
drivers for my kernel, but i dont have the devel packages for my kernel.

Is there something more I need to do to fix my system to get the NIC running?

Here is my /etc/sysconfig/network-scripts/ifcfg-eth0 (the only thing i
commented out was the MAC address:

Code:

DEVICE="eth0"
TYPE="Ethernet"
#HWADDR=00:15:F2:E7:5B:9F  <just commented out this line still no eth0 found, this is the MAC address of the old NIC from the old motherboard.  i am unable to see the mac addy of either of the new cards.>
NAME="System eth0"
ONBOOT="yes"
#BOOTPROTO="dhcp"
BOOTPROTO="static"
NM_CONTROLLED="no"
IPADDR=192.168.2.125
NETMASK=255.255.255.0
USERCTL="no"
#DEFROUTE=yes
#PEERROUTES=yes
#PEERDNS=yes
IPV4_FALIURE_FATAL=yes
IPV6INIT=no

ifconfig only displays the loopback and nothing more.

lspci shows both the Realtex and the Intel Gigabit network cards:

Code:

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

Yes i have a good solid link light on the Intel card when I plug in the
cable and yes it is a known good working cable and port on the local
switch.

i do not have NetworkManager installed on the system.

edit to add that my /etc/sysconfig/network is properly configured still for my LAN.

lleb · 08-21-2013, 07:39 PM

SOLVED:::

for those wanting to know what I did...

Code:

[root@centos ~]# ifconfig -a
eth3      Link encap:Ethernet  HWaddr D4:3D:7E:9B:6E:10  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth4      Link encap:Ethernet  HWaddr 68:05:CA:18:00:8B  
          inet addr:192.168.2.125  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::6a05:caff:fe18:8b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:152 errors:0 dropped:0 overruns:0 frame:0
          TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:20628 (20.1 KiB)  TX bytes:16448 (16.0 KiB)
          Interrupt:17 Memory:fd1c0000-fd1e0000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:840 (840.0 b)  TX bytes:840 (840.0 b)

that is what saved me. Now if i understood why the new NICs are labeled eth3/4 instead of 0/1 as that is what is physically connected. Is there anyway to get the system to rename them back to 0/1 from 3/4?

All i needed to do was copy eth0 to eth4 then change ONBOOT=yes to no restart the network services and poof its up and running. Many thanks, hope this helps others down the line.