[plug] no eth0, but drivers load...

[Lucas van Staden]

Thank you to all for the help.

I grepped the files in /etc/udev for 'eth0',
and found the file in question to be rules.d/z25_persistent-net.rules

it has the contents of :

# PCI device 0x14e4:0x167d (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:10:c6:dc:ca:24", 
NAME="eth0"

# PCI device 0x8086:0x1229 (e100)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:d0:59:c5:0e:65", 
NAME="eth1"

# PCI device 0x8086:0x1229 (e100)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:d0:59:7f:8f:d2", 
NAME="eth2"

So I adjusted the file accordingly.

 From other posts I tried:

$ sudo udevadm --trigger
$ sudo: udevadm: command not found

so, udevadm must either not be part of Debian, or I require another 
package installed,
so I went with /etc/init.d/udev restart

udev reports it restarted, but I stayed on eth2.

So a reboot....

and back onto eth0 now :)

-Lucas


Phillip Twiss wrote:
> Hiya :}
>
> 	Have a look at udev, I have had similar issues in the past and it related to udev :}
>
> 	Not sure with debian, but with slackware you would look in the /etc/udev/rules.d directory and the file you would be interested in would be 75-network-devices.rules
>
> 	Don't have a debian box handy to check how they do it :}
>
> 	Regards
> 	
> 	Phill Twiss
>
>
> -----Original Message-----
> From: plug-bounces at plug.org.au [mailto:plug-bounces at plug.org.au] On Behalf Of Lucas van Staden
> Sent: Tuesday, 16 December 2008 11:40 PM
> To: plug at plug.org.au
> Subject: Re: [plug] no eth0, but drivers load...
>
> Daniel Pittman wrote:
>   
>> Lucas van Staden <lvs at dedmeet.com> writes:
>>
>>
>>     
>>> I have an old compaq evo N400 laptop, which I had turned into a
>>> picture frame a few years back.  Today I decided to revamp it a bit,
>>> (new frame, new install)
>>>
>>> Part of the process was to remove DSL and go with Debian R4.
>>>
>>> When booting, the system detects the onboard ethernet, and load the
>>> e100 driver, which reports the card is fine (calls it eth0), and gives
>>> the mac address, and irq however, there is no eth0 device available,
>>> only lo.
>>>
>>>       
>> Does the eth0 device show up if you run 'ifconfig -a' as root?
>>
>>     
> Thank you, ifconfig -a show it as eth2, strange as the dmesg of the
> driver loading names it as eth0, so I have been looking only for eth0,
> and I did try eth1, but not eth2
>
> But now thinking about it, it does make sense, as the thinkpad laptop
> has eth0 (wired), and eth1 (wireless), thus the 'new' nic on the
> pictureframe will be eth2
>
> Anyone know what I must edit to move it back to eth0, just a nice to
> have, not crucial.
>   
>> What turns up in dmesg after installing the e100 driver, or related to
>> the Ethernet side of things?
>>
>> My guess is that it isn't configured by the system, so is present but
>> down, although that is a pretty wild guess at this point.
>>
>> Regards,
>>         Daniel
>> _______________________________________________
>> PLUG discussion list: plug at plug.org.au
>> http://www.plug.org.au/mailman/listinfo/plug
>> Committee e-mail: committee at plug.linux.org.au
>>
>>     
>
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://www.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
>
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://www.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
>