* [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
@ 2008-07-09 3:21 waltdnes
2008-07-09 7:44 ` Neil Bothwick
0 siblings, 1 reply; 9+ messages in thread
From: waltdnes @ 2008-07-09 3:21 UTC (permalink / raw
To: Gentoo Users List
I got a Dell last summer, in which I couldn't get the network chip
running, so I bought a cheap Via Rhine PCI network card and used that
for almost a year. I finally got the built-in chip working today on the
older 530. This post is being sent on it. It's a bastardized Intel
chip that shows up as "Intel Corporation 82562V-2 10/100 Network
Connection (rev 02)" under lspci, but uses gigabit driver (e1000e). Go
figure.
I finally stumbled across the *REAL* reason I couldn't get it working.
I always tried configuring eth0 for it... silly me. Apparently, the
chip *ALWAYS* comes up as eth1. Here are a couple of excerpts from
dmesg. The 1st one is about halfway through dmesg...
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:19.0 to 64
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1a:a0:8c:0d:b2
0000:00:19.0: eth0: Intel(R) PRO/10/100 Network Connection
0000:00:19.0: eth0: MAC: 5, PHY: 7, PBA No: ffffff-0ff
The next one is at the very end...
0000:00:19.0: eth1: Link is Up 100 Mbps Full Duplex, Flow Control: RX
0000:00:19.0: eth1: 10/100 speed: disabling TSO
0000:00:19.0: eth1: changing MTU from 1500 to 1452
0000:00:19.0: eth1: Link is Up 100 Mbps Full Duplex, Flow Control: RX
0000:00:19.0: eth1: 10/100 speed: disabling TSO
Here's /etc/conf.d/net I left in the eth0 entry. It generates an
error message, but doesn't cause any problems. And yes, *THE NETMASK
IS CORRECT*
config_eth1="192.168.123.250 broadcast 192.168.123.255 netmask 255.255.255.248 mtu 1452"
routes_eth1=("default via 192.168.123.254")
config_eth0="192.168.123.250 broadcast 192.168.123.255 netmask 255.255.255.248 mtu 1452"
routes_eth0=("default via 192.168.123.254")
I've made 4 changes in iptables to accomadate the change, but I'd
really like to know what's going on, and revert to eth0 if possible.
I've appended "nofirewire" to the boot paramters in lilo, but it doesn't
help.
--
Walter Dnes <waltdnes@waltdnes.org>
--
gentoo-user@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-09 3:21 [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530 waltdnes
@ 2008-07-09 7:44 ` Neil Bothwick
2008-07-12 23:55 ` Walter Dnes
0 siblings, 1 reply; 9+ messages in thread
From: Neil Bothwick @ 2008-07-09 7:44 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 512 bytes --]
On Tue, 8 Jul 2008 23:21:22 -0400, waltdnes@waltdnes.org wrote:
> I finally stumbled across the *REAL* reason I couldn't get it working.
> I always tried configuring eth0 for it... silly me. Apparently, the
> chip *ALWAYS* comes up as eth1.
Udev is doing this. If you have removed the second card,
delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit the file
to switch the assignments for the two NICs.
--
Neil Bothwick
Press any key to continue... <click> Except that one..
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-09 7:44 ` Neil Bothwick
@ 2008-07-12 23:55 ` Walter Dnes
2008-07-13 8:37 ` Alan McKinnon
2008-07-13 10:30 ` Neil Bothwick
0 siblings, 2 replies; 9+ messages in thread
From: Walter Dnes @ 2008-07-12 23:55 UTC (permalink / raw
To: gentoo-user
On Wed, Jul 09, 2008 at 08:44:51AM +0100, Neil Bothwick wrote
> > chip *ALWAYS* comes up as eth1.
>
> Udev is doing this. If you have removed the second card,
> delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit the file
> to switch the assignments for the two NICs.
Thanks. A "new and improved helpfull feature" that could've done
without.
--
Walter Dnes <waltdnes@waltdnes.org>
--
gentoo-user@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-12 23:55 ` Walter Dnes
@ 2008-07-13 8:37 ` Alan McKinnon
2008-07-13 10:30 ` Neil Bothwick
1 sibling, 0 replies; 9+ messages in thread
From: Alan McKinnon @ 2008-07-13 8:37 UTC (permalink / raw
To: gentoo-user
On Sunday 13 July 2008, Walter Dnes wrote:
> On Wed, Jul 09, 2008 at 08:44:51AM +0100, Neil Bothwick wrote
>
> > > chip *ALWAYS* comes up as eth1.
> >
> > Udev is doing this. If you have removed the second card,
> > delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit
> > the file to switch the assignments for the two NICs.
>
> Thanks. A "new and improved helpfull feature" that could've done
> without.
It's a trade-off for me. The interface might get a stupid name but at
least it's the *same* stupid name every time, as opposed to the old
method where interfaces were liable to change names based on what you
did with your hardware this morning or the phases of the moon...
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-12 23:55 ` Walter Dnes
2008-07-13 8:37 ` Alan McKinnon
@ 2008-07-13 10:30 ` Neil Bothwick
2008-07-14 6:43 ` [gentoo-user] [OT] " Daniel Iliev
1 sibling, 1 reply; 9+ messages in thread
From: Neil Bothwick @ 2008-07-13 10:30 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Sat, 12 Jul 2008 19:55:56 -0400, Walter Dnes wrote:
> > Udev is doing this. If you have removed the second card,
> > delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit the
> > file to switch the assignments for the two NICs.
>
> Thanks. A "new and improved helpfull feature" that could've done
> without.
It's hardly new, it's been around for some years. It is helpful if you
have two NICs because it means they are named consistently, which is
better than having your private network connected to the Internet
because the kernel decided to load the modules in a different order.
--
Neil Bothwick
This tagline is umop apisdn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] [OT] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-13 10:30 ` Neil Bothwick
@ 2008-07-14 6:43 ` Daniel Iliev
2008-07-14 10:25 ` Neil Bothwick
0 siblings, 1 reply; 9+ messages in thread
From: Daniel Iliev @ 2008-07-14 6:43 UTC (permalink / raw
To: gentoo-user
On Sun, 13 Jul 2008 11:30:56 +0100
Neil Bothwick <neil@digimed.co.uk> wrote:
> On Sat, 12 Jul 2008 19:55:56 -0400, Walter Dnes wrote:
>
> > > Udev is doing this. If you have removed the second card,
> > > delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit
> > > the file to switch the assignments for the two NICs.
> >
> > Thanks. A "new and improved helpfull feature" that could've done
> > without.
>
> It's hardly new, it's been around for some years. It is helpful if you
> have two NICs because it means they are named consistently, which is
> better than having your private network connected to the Internet
> because the kernel decided to load the modules in a different order.
>
>
IIRC:
1) You can explicitly tell the kernel the order in which load the
modules
2) If you build the the drivers in-kernel the the order is determined
by the PCI slot numbers
--
Best regards,
Daniel
--
gentoo-user@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] [OT] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-14 6:43 ` [gentoo-user] [OT] " Daniel Iliev
@ 2008-07-14 10:25 ` Neil Bothwick
2008-07-14 16:30 ` Alan McKinnon
0 siblings, 1 reply; 9+ messages in thread
From: Neil Bothwick @ 2008-07-14 10:25 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Mon, 14 Jul 2008 09:43:21 +0300, Daniel Iliev wrote:
> > It's hardly new, it's been around for some years. It is helpful if you
> > have two NICs because it means they are named consistently, which is
> > better than having your private network connected to the Internet
> > because the kernel decided to load the modules in a different order.
> 1) You can explicitly tell the kernel the order in which load the
> modules
And if the module for eth0 fails to load, the other card becomes eth0
instead of eth1. Using udev rules, the second card is always eth1,
whatever happens elsewhere in the system.
--
Neil Bothwick
If at first you don't succeed, call in an airstrike.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] [OT] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-14 10:25 ` Neil Bothwick
@ 2008-07-14 16:30 ` Alan McKinnon
2008-07-14 22:17 ` Neil Bothwick
0 siblings, 1 reply; 9+ messages in thread
From: Alan McKinnon @ 2008-07-14 16:30 UTC (permalink / raw
To: gentoo-user
On Monday 14 July 2008, Neil Bothwick wrote:
> On Mon, 14 Jul 2008 09:43:21 +0300, Daniel Iliev wrote:
> > > It's hardly new, it's been around for some years. It is helpful
> > > if you have two NICs because it means they are named
> > > consistently, which is better than having your private network
> > > connected to the Internet because the kernel decided to load the
> > > modules in a different order.
> >
> > 1) You can explicitly tell the kernel the order in which load the
> > modules
>
> And if the module for eth0 fails to load, the other card becomes eth0
> instead of eth1. Using udev rules, the second card is always eth1,
> whatever happens elsewhere in the system.
Consider this: if we could have assigned arbitrary names to interfaces
since day one, we would have the exact same behaviour udev gives,
everyone would agree this is a truly excellent thing and this thread
would not exist.
The single minor difference is that you can't call the interface
whatever you want directly, it just gets named the equally arbitrary
name of "eth1"
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] [OT] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
2008-07-14 16:30 ` Alan McKinnon
@ 2008-07-14 22:17 ` Neil Bothwick
0 siblings, 0 replies; 9+ messages in thread
From: Neil Bothwick @ 2008-07-14 22:17 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
On Mon, 14 Jul 2008 18:30:57 +0200, Alan McKinnon wrote:
> The single minor difference is that you can't call the interface
> whatever you want directly, it just gets named the equally arbitrary
> name of "eth1"
Unless you edit the rule file and change that.
--
Neil Bothwick
Q. Why do women have orgasms?
A: It gives them one extra reason to moan.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-07-14 22:18 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-09 3:21 [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530 waltdnes
2008-07-09 7:44 ` Neil Bothwick
2008-07-12 23:55 ` Walter Dnes
2008-07-13 8:37 ` Alan McKinnon
2008-07-13 10:30 ` Neil Bothwick
2008-07-14 6:43 ` [gentoo-user] [OT] " Daniel Iliev
2008-07-14 10:25 ` Neil Bothwick
2008-07-14 16:30 ` Alan McKinnon
2008-07-14 22:17 ` Neil Bothwick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox