Hi,

I have a server running kernel 2.6.18-6-686, and awhile ago the motherboard blew a capacitor, was working great prior to this. Anyway, now it is back and I can't get any kind of ip to the nic(s), they are Intel Pro/1000 on a ASUSTek motherboard. Ifconfig produces on a printout of "lo" loopback. I have tried adding e1000, PRO/1000 to /etc/modules. ifup eth0 gives
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags : no such device
eth0: ERROR while getting interface flags : no such device
Bind socket to interface: no such device
Failed to bring up eth0
ifup eth1 gives
Ignoring unknown interface eth1=eth1
In /etc/network/interfaces I have:
auto lo
iface lo inet loopback

allow-hotplug eth0 eht1
iface eth0 inet dhcp

I have another server that is supposed to be running dhcp, which is working with all my workstation clients just fine.

I need help,,,

Thanx Lisa

#lspci

#ifconfig -a

#lshw

If it cannot be found ...as it seems to be the case,
try with a live CD (systemrescue CD for eg)

The mainboard may be partly out of order

also

dmesg | grep -i eth

and

lsmod

dmesg |grep -i eth reports
e1000: eth0: e1000_probe: Intel (R) PRO/1000 Network Connection
e1000: eth1: e1000_probe: Intel (R) PRO/1000 Network Connection

ifconfig -a reports eth2, eth3, lo and sit0 all report no ip addresses except lo with 127.0.0.1, I have not configured any of these!?!?

lspci, shows lots but this is an on-board nic, still wont info from this?

lshw command not found

I have downloaded and followed these instructions: but was unable to use make install, command not found!?!?
From the internet::
Download the appropriate Linux driver for your Intel Ethernet card (either e100 or e1000) from the Intel web site.

Find out what kernel version you are using: uname -r

e.g., if the kernel version is 2.4.27-2-386

aptitude install kernel-headers-2.4.27-2-386

cd /usr/src/kernel-headers-2.4.27-2-386
mkdir intel
cd intel

place the Intel driver at /usr/src/kernel-headers-2.4.27-2-386/intel

tar zxvf e100-3.5.10.tar.gz
cd e100-3.5.10
cd src
make install


That is where it is at now,,,,

Lisa

It looks like you don't have make installed.
Some errors that I've seen here suggest that it can be a driver issue.
Strange thing is that ifconfig shows eth2 and eth3 but before it didn't show eth at all.
Anyway,ifconfig works on the kernel level,not like ifup or ifdown,so maybe reinstalling that driver could solve the problem,since you already have it.Try to setup your nics like eth2 and eth3.
In my opinion this is a motherboard failure.

Was this the COMPLETE output of that command ?
I would have thought there would be a few more lines output. This is showing you have DUAL Gigabit Intel Ethernet adapters identified as eth0 and eth1.


notice in my dmesg output the intel card is initially assigned as eth0, then it is later automatically remapped by the system as eth1..
Thats why I was asking if you showed the entire output of the command, in case the system has remapped the devices..



Did lsmod show the e1000 module as being loaded ?

if not did you modprobe e1000 ? that driver is a standard driver in Linux (unless your adapters are a newer intel chipset which is why we need the info from lspci)


The output of lspci is important, so we can see WHICH intel NICs are in that machine. how about the following..
lspci | grep -i eth that should trim it down to just the important parts.

Did you download the new driver from here: http://sourceforge.net/projects/e1000
Not sure what you downloaded as the instructions for it are old since they refer to the 2.4 kernel and e100 driver and you have NIC's that need the e1000 driver

Please provide more info..


A few other commands you might consider running
aptitude install build-essential module-assistant lshw
m-a update
m-a prepare


That will make sure you have everything you need in case you need to successfully compile

lshw -C network

If you are using the same Debian install as you were using with the old motherboard (with an onboard nic), then it's quite likely you're setup is looking for the old NIC's MAC address and not finding it.

Look in /etc/udev/rules.d for the file z25_persistent-net.rules. It probably has eth0 setup with the old NIC's MAC address (assuming you just plugged the old system drive into the new motherboard without installing the OS again). When this happened to me, I had the old NIC's MAC listed as eth0 and the new NIC's MAC as eth1. I commented out eth0 and renamed eth1 to eth0, rebooted and found everything back to normal, network-wise. Maybe this is your problem too debian newbie. edit: maybe not though as the interface should have been brought up with "ifup eth1" in that case...

Thanx to all the tried to help, it is working again. The fix::
Came from lurko, I did what was suggested and we are up and running again. I have run into a different problem now, but I have an ip address!!

If anyone is interested or have a quick suggestion, I am receiving this message upon booting the server!!
Thanx again,,

Lisa

A SparesMissing event had been detected on md device /dev/md3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1]
md5 : active raid1 sda8[0] sdc8[2](S) sdb8[1]
195286016 blocks [2/2] [UU]

md4 : active raid1 sda7[0] sdc7[2](S) sdb7[1]
48829440 blocks [2/2] [UU]

md3 : active raid1 sda6[0] sdb6[1]
58596992 blocks [2/2] [UU]

md2 : active raid1 sda5[0] sdc5[2](S) sdb5[1]
5855552 blocks [2/2] [UU]

md1 : active raid1 sda2[0] sdc2[2](S) sdb2[1]
96320 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdc1[2](S) sdb1[1]
1951744 blocks [2/2] [UU]

unused devices: <none>

I didn't know that you haven't done a fresh new install of Debian,that's way I've said that I think it's a motherboard failure.Anyway,just one advice from me,since I'm not a raid expert and I can't help you with that,please,in the future,when you've been asked to post the output of some command or something else,do it,because those people that have asked you to do so and want to help you,they know why they are asking you to do so.Also,please try to give as much information as you can.
I'm glad that you have solved your original problem.