| 1 |
--- Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
|
| 3 |
> On Tue, 15 Apr 2008 12:57:43 -0700 (PDT), maxim |
| 4 |
> wexler wrote: |
| 5 |
> |
| 6 |
> > Also, just noticed this little bit: "udev: renamed |
| 7 |
> > eth0 to eth1". Why did it do that? |
| 8 |
> |
| 9 |
> Because you have a udev rule to do this? Take a look |
| 10 |
> in /etc/udev/rules.d/70-persistent-net.rules |
| 11 |
> |
| 12 |
|
| 13 |
Looks like there's two rules pointing to the same |
| 14 |
device: |
| 15 |
|
| 16 |
# PCI device 0x10de:0x00df (forcedeth) |
| 17 |
SUBSYSTEM=="net", DRIVERS=="?*", |
| 18 |
ATTRS{address}=="00:e0:18:99:88:77", NAME="eth0" |
| 19 |
|
| 20 |
# PCI device 0x10de:0x00df (forcedeth) |
| 21 |
SUBSYSTEM=="net", DRIVERS=="?*", |
| 22 |
ATTR{address}=="00:13:8f:33:32:e2", NAME="eth1" |
| 23 |
|
| 24 |
|
| 25 |
From a forum I learned to rm the link eth0 in |
| 26 |
/etc/init.d and make a new one, eth1 that points to |
| 27 |
net.lo. So now the ethernet is up but there's still a |
| 28 |
lot of complaining on the boot console, "can't find |
| 29 |
eth0" etc. |
| 30 |
|
| 31 |
BTW I was wrong about mii, forcedeth *is* the |
| 32 |
appropriate module. The confusion arose because I was |
| 33 |
expecting eth0 to be set up. |
| 34 |
|
| 35 |
Maxim |
| 36 |
|
| 37 |
|
| 38 |
____________________________________________________________________________________ |
| 39 |
Be a better friend, newshound, and |
| 40 |
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
| 41 |
-- |
| 42 |
gentoo-user@l.g.o mailing list |
Archives