* [gentoo-user] mobo replaced; eth0 fails
@ 2011-11-11 20:28 Allan Gottlieb
2011-11-11 21:04 ` Florian Philipp
` (2 more replies)
0 siblings, 3 replies; 10+ messages in thread
From: Allan Gottlieb @ 2011-11-11 20:28 UTC (permalink / raw
To: gentoo-user
My dell laptop E6510 had its motherboard replaced (as it turned out, for
no good reason) and now the wired ethernet fails.
ajglap gottlieb # /etc/init.d/net.eth0 restart
* Bringing up interface eth0
* ERROR: interface eth0 does not exist
* Ensure that you have loaded the correct kernel module for your hardware
* ERROR: net.eth0 failed to start
I am hoping it is some wrong setting in the bios, but the only one I see
says the ethernet can be disabled enabled enabled (with pxe)
I tried both of the enabled variants with the same outcome.
I don't think I changed the kernel during that time, but I did try two
older kernels; again with no change. I believe I have the correct
driver built into the kernel
ajglap gottlieb # lspci -v
[snip]
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
Subsystem: Dell Device 040b
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at e9600000 (32-bit, non-prefetchable) [size=128K]
Memory at e9680000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 8040 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Any help would be appreciated.
thanks,
allan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-11 20:28 [gentoo-user] mobo replaced; eth0 fails Allan Gottlieb
@ 2011-11-11 21:04 ` Florian Philipp
2011-11-11 21:08 ` Alan McKinnon
2011-11-12 2:41 ` Allan Gottlieb
2 siblings, 0 replies; 10+ messages in thread
From: Florian Philipp @ 2011-11-11 21:04 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Am 11.11.2011 21:28, schrieb Allan Gottlieb:
> My dell laptop E6510 had its motherboard replaced (as it turned out, for
> no good reason) and now the wired ethernet fails.
>
> ajglap gottlieb # /etc/init.d/net.eth0 restart
> * Bringing up interface eth0
> * ERROR: interface eth0 does not exist
> * Ensure that you have loaded the correct kernel module for your hardware
> * ERROR: net.eth0 failed to start
>
[...]
Try `/sbin/ifconfig -a`. If you are lucky, it will show you an eth1
interface or something alike. The issue is that udev keeps track of
network interfaces. If it finds a new one, it asigns it a new number
instead of reusing the old one. You can change this, but to get
everything running fast, just copy your config from eth0 to eth1, create
a symlink between /etc/init.d/net.lo and /etc/init.d/net.eth1 and start
that one.
Hope this helps,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-11 20:28 [gentoo-user] mobo replaced; eth0 fails Allan Gottlieb
2011-11-11 21:04 ` Florian Philipp
@ 2011-11-11 21:08 ` Alan McKinnon
2011-11-11 21:12 ` Michael Mol
2011-11-12 2:41 ` Allan Gottlieb
2 siblings, 1 reply; 10+ messages in thread
From: Alan McKinnon @ 2011-11-11 21:08 UTC (permalink / raw
To: gentoo-user; +Cc: gottlieb
On Fri, 11 Nov 2011 15:28:26 -0500
Allan Gottlieb <gottlieb@nyu.edu> wrote:
> My dell laptop E6510 had its motherboard replaced (as it turned out,
> for no good reason) and now the wired ethernet fails.
>
> ajglap gottlieb # /etc/init.d/net.eth0 restart
> * Bringing up interface eth0
> * ERROR: interface eth0 does not exist
> * Ensure that you have loaded the correct kernel module for
> your hardware
> * ERROR: net.eth0 failed to start
>
> I am hoping it is some wrong setting in the bios, but the only one I
> see says the ethernet can be disabled enabled enabled (with pxe)
>
> I tried both of the enabled variants with the same outcome.
>
> I don't think I changed the kernel during that time, but I did try two
> older kernels; again with no change. I believe I have the correct
> driver built into the kernel
>
> ajglap gottlieb # lspci -v
>
> [snip]
>
> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit
> Network Connection (rev 05) Subsystem: Dell Device 040b
> Flags: bus master, fast devsel, latency 0, IRQ 42
> Memory at e9600000 (32-bit, non-prefetchable) [size=128K]
> Memory at e9680000 (32-bit, non-prefetchable) [size=4K]
> I/O ports at 8040 [size=32]
> Capabilities: [c8] Power Management version 2
> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [e0] PCI Advanced Features
> Kernel driver in use: e1000e
Seeing as it's gentoo, my first guess is that the new motherboard
doesn't have the same hardware as the old one - Dell can easily fit any
wireless card with the same specs - and that you don't have the correct
module loaded.
In the BIOS the option you want is plain "enabled", if you need pxe you
will certainly know all about that already.
Any clues in dmesg about the hardware?
--
Alan McKinnnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-11 21:08 ` Alan McKinnon
@ 2011-11-11 21:12 ` Michael Mol
2011-11-11 23:20 ` Mick
0 siblings, 1 reply; 10+ messages in thread
From: Michael Mol @ 2011-11-11 21:12 UTC (permalink / raw
To: gentoo-user
On Fri, Nov 11, 2011 at 4:08 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Fri, 11 Nov 2011 15:28:26 -0500
> Allan Gottlieb <gottlieb@nyu.edu> wrote:
>
>> My dell laptop E6510 had its motherboard replaced (as it turned out,
>> for no good reason) and now the wired ethernet fails.
>>
>> ajglap gottlieb # /etc/init.d/net.eth0 restart
>> * Bringing up interface eth0
>> * ERROR: interface eth0 does not exist
>> * Ensure that you have loaded the correct kernel module for
>> your hardware
>> * ERROR: net.eth0 failed to start
>>
>> I am hoping it is some wrong setting in the bios, but the only one I
>> see says the ethernet can be disabled enabled enabled (with pxe)
>>
>> I tried both of the enabled variants with the same outcome.
>>
>> I don't think I changed the kernel during that time, but I did try two
>> older kernels; again with no change. I believe I have the correct
>> driver built into the kernel
>>
>> ajglap gottlieb # lspci -v
>>
>> [snip]
>>
>> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit
>> Network Connection (rev 05) Subsystem: Dell Device 040b
>> Flags: bus master, fast devsel, latency 0, IRQ 42
>> Memory at e9600000 (32-bit, non-prefetchable) [size=128K]
>> Memory at e9680000 (32-bit, non-prefetchable) [size=4K]
>> I/O ports at 8040 [size=32]
>> Capabilities: [c8] Power Management version 2
>> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>> Capabilities: [e0] PCI Advanced Features
>> Kernel driver in use: e1000e
>
> Seeing as it's gentoo, my first guess is that the new motherboard
> doesn't have the same hardware as the old one - Dell can easily fit any
> wireless card with the same specs - and that you don't have the correct
> module loaded.
>
> In the BIOS the option you want is plain "enabled", if you need pxe you
> will certainly know all about that already.
>
> Any clues in dmesg about the hardware?
On that note, find the udev rule for persistent networking and wipe it.
--
:wq
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-11 21:12 ` Michael Mol
@ 2011-11-11 23:20 ` Mick
0 siblings, 0 replies; 10+ messages in thread
From: Mick @ 2011-11-11 23:20 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 2383 bytes --]
On Friday 11 Nov 2011 21:12:29 Michael Mol wrote:
> On Fri, Nov 11, 2011 at 4:08 PM, Alan McKinnon <alan.mckinnon@gmail.com>
wrote:
> > On Fri, 11 Nov 2011 15:28:26 -0500
> >
> > Allan Gottlieb <gottlieb@nyu.edu> wrote:
> >> My dell laptop E6510 had its motherboard replaced (as it turned out,
> >> for no good reason) and now the wired ethernet fails.
> >>
> >> ajglap gottlieb # /etc/init.d/net.eth0 restart
> >> * Bringing up interface eth0
> >> * ERROR: interface eth0 does not exist
> >> * Ensure that you have loaded the correct kernel module for
> >> your hardware
> >> * ERROR: net.eth0 failed to start
> >>
> >> I am hoping it is some wrong setting in the bios, but the only one I
> >> see says the ethernet can be disabled enabled enabled (with pxe)
> >>
> >> I tried both of the enabled variants with the same outcome.
> >>
> >> I don't think I changed the kernel during that time, but I did try two
> >> older kernels; again with no change. I believe I have the correct
> >> driver built into the kernel
> >>
> >> ajglap gottlieb # lspci -v
> >>
> >> [snip]
> >>
> >> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit
> >> Network Connection (rev 05) Subsystem: Dell Device 040b
> >> Flags: bus master, fast devsel, latency 0, IRQ 42
> >> Memory at e9600000 (32-bit, non-prefetchable) [size=128K]
> >> Memory at e9680000 (32-bit, non-prefetchable) [size=4K]
> >> I/O ports at 8040 [size=32]
> >> Capabilities: [c8] Power Management version 2
> >> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> >> Capabilities: [e0] PCI Advanced Features
> >> Kernel driver in use: e1000e
> >
> > Seeing as it's gentoo, my first guess is that the new motherboard
> > doesn't have the same hardware as the old one - Dell can easily fit any
> > wireless card with the same specs - and that you don't have the correct
> > module loaded.
> >
> > In the BIOS the option you want is plain "enabled", if you need pxe you
> > will certainly know all about that already.
> >
> > Any clues in dmesg about the hardware?
>
> On that note, find the udev rule for persistent networking and wipe it.
+1
rm /etc/udev/rules.d/70-persistent-net.rules
then reboot.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-11 20:28 [gentoo-user] mobo replaced; eth0 fails Allan Gottlieb
2011-11-11 21:04 ` Florian Philipp
2011-11-11 21:08 ` Alan McKinnon
@ 2011-11-12 2:41 ` Allan Gottlieb
2011-11-12 11:57 ` Albert W. Hopkins
2 siblings, 1 reply; 10+ messages in thread
From: Allan Gottlieb @ 2011-11-12 2:41 UTC (permalink / raw
To: gentoo-user
On Fri, Nov 11 2011, Allan Gottlieb wrote:
> My dell laptop E6510 had its motherboard replaced (as it turned out, for
> no good reason) and now the wired ethernet fails.
Thank you florian, alan, michael, and mick.
This list is one of gentoo's strongest advantages.
To summarize the responses and my actions.
1. Indeed the system had assigned the new wired ethernet device
a new name (eth2, my wireless is eth1, previous wired was eth0).
2. /etc/udev/rules.d/persistent-net.rules does tell the story.
This file ensures that the same PHYSICAL device keeps the same name.
Once you change the hardware, the same "logical device" (in my case
wired ethernet) gets a new permanent name.
3. Some advised blowing away .../persistent-net.rules.
I chose to modify it so that the new device is now eth0 and the old
device is gone.
Thank you again. The result was error solved and knowledge gained.
allan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-12 2:41 ` Allan Gottlieb
@ 2011-11-12 11:57 ` Albert W. Hopkins
2011-11-12 13:44 ` Allan Gottlieb
0 siblings, 1 reply; 10+ messages in thread
From: Albert W. Hopkins @ 2011-11-12 11:57 UTC (permalink / raw
To: gentoo-user
On Fri, 2011-11-11 at 21:41 -0500, Allan Gottlieb wrote:
> 3. Some advised blowing away .../persistent-net.rules.
> I chose to modify it so that the new device is now eth0 and the
> old
> device is gone.
Removing it does the same thing. The device file is re-created with the
currently probed hardware and indexes start from 0. It's just that most
people prefer to just remove it because it's less typing and less prone
to errors.
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-12 11:57 ` Albert W. Hopkins
@ 2011-11-12 13:44 ` Allan Gottlieb
2011-11-12 14:03 ` Neil Bothwick
0 siblings, 1 reply; 10+ messages in thread
From: Allan Gottlieb @ 2011-11-12 13:44 UTC (permalink / raw
To: gentoo-user
On Sat, Nov 12 2011, Albert W. Hopkins wrote:
> On Fri, 2011-11-11 at 21:41 -0500, Allan Gottlieb wrote:
>> 3. Some advised blowing away .../persistent-net.rules.
>> I chose to modify it so that the new device is now eth0 and the
>> old
>> device is gone.
>
> Removing it does the same thing. The device file is re-created with the
> currently probed hardware and indexes start from 0. It's just that most
> people prefer to just remove it because it's less typing and less prone
> to errors.
I was worried that then eth0 might be wireless and eth1 wired,
but I should have tried it and only changed names if the switch
happened.
thanks,
allan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-12 13:44 ` Allan Gottlieb
@ 2011-11-12 14:03 ` Neil Bothwick
2011-11-12 14:21 ` Allan Gottlieb
0 siblings, 1 reply; 10+ messages in thread
From: Neil Bothwick @ 2011-11-12 14:03 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Sat, 12 Nov 2011 08:44:16 -0500, Allan Gottlieb wrote:
> > Removing it does the same thing. The device file is re-created with
> > the currently probed hardware and indexes start from 0. It's just
> > that most people prefer to just remove it because it's less typing
> > and less prone to errors.
>
> I was worried that then eth0 might be wireless and eth1 wired,
> but I should have tried it and only changed names if the switch
> happened.
No, that was a valid worry, you did the right thing. Removing the file is
easiest, but only 100% safe if you have only one eth device.
--
Neil Bothwick
Love and Trust: Oral sex between cannibals.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [gentoo-user] mobo replaced; eth0 fails
2011-11-12 14:03 ` Neil Bothwick
@ 2011-11-12 14:21 ` Allan Gottlieb
0 siblings, 0 replies; 10+ messages in thread
From: Allan Gottlieb @ 2011-11-12 14:21 UTC (permalink / raw
To: gentoo-user
On Sat, Nov 12 2011, Neil Bothwick wrote:
> On Sat, 12 Nov 2011 08:44:16 -0500, Allan Gottlieb wrote:
>
>> > Removing it does the same thing. The device file is re-created with
>> > the currently probed hardware and indexes start from 0. It's just
>> > that most people prefer to just remove it because it's less typing
>> > and less prone to errors.
>>
>> I was worried that then eth0 might be wireless and eth1 wired,
>> but I should have tried it and only changed names if the switch
>> happened.
>
> No, that was a valid worry, you did the right thing. Removing the file is
> easiest, but only 100% safe if you have only one eth device.
Thanks for the confirmation.
allan
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-11-12 14:22 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-11 20:28 [gentoo-user] mobo replaced; eth0 fails Allan Gottlieb
2011-11-11 21:04 ` Florian Philipp
2011-11-11 21:08 ` Alan McKinnon
2011-11-11 21:12 ` Michael Mol
2011-11-11 23:20 ` Mick
2011-11-12 2:41 ` Allan Gottlieb
2011-11-12 11:57 ` Albert W. Hopkins
2011-11-12 13:44 ` Allan Gottlieb
2011-11-12 14:03 ` Neil Bothwick
2011-11-12 14:21 ` Allan Gottlieb
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox