[gentoo-amd64] eth device vanished

[gentoo-amd64] eth device vanished

[Daiajo Tibdixious]

I was running on 3.0.6 kernel, when after a problem with the phone
line internet was down for 3 weeks, when it came back up I had no
network. I upgraded to 3.7.9 and had a network device but I had to
bring it up manually: ifconfig eth0 up, then run dhcp, and that worked
for a month.

Today had a powerfailure, after rebooting, no /dev/eth*:
ifconfig -a
gives enp2s0, lo, sit0

I downloaded the r8168 driver from realtek (my if is RTL811/8168B),
installed modprobe'd it,
but still no eth device.

I'm really mystified, as there were no kernel changes, it should have
rebooted with the network if it had it before.

Re: [gentoo-amd64] eth device vanished

[Forrest Schultz]

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

You can use lspci or something like that to enumerate your network cards,
right? Maybe your port is shot or something.


On Mon, Apr 15, 2013 at 8:59 AM, Daiajo Tibdixious <daiajo@gmail.com> wrote:

> I was running on 3.0.6 kernel, when after a problem with the phone
> line internet was down for 3 weeks, when it came back up I had no
> network. I upgraded to 3.7.9 and had a network device but I had to
> bring it up manually: ifconfig eth0 up, then run dhcp, and that worked
> for a month.
>
> Today had a powerfailure, after rebooting, no /dev/eth*:
> ifconfig -a
> gives enp2s0, lo, sit0
>
> I downloaded the r8168 driver from realtek (my if is RTL811/8168B),
> installed modprobe'd it,
> but still no eth device.
>
> I'm really mystified, as there were no kernel changes, it should have
> rebooted with the network if it had it before.
>
>

[-- Attachment #2: Type: text/html, Size: 1207 bytes --]

Re: [gentoo-amd64] eth device vanished

[Vítor Brandão]

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

Most likely this is due to a udev upgrade.

Please check the udev upgrade guide:
http://wiki.gentoo.org/wiki/Udev/upgrade


2013/4/15 Forrest Schultz <f.schultz0@gmail.com>

> You can use lspci or something like that to enumerate your network cards,
> right? Maybe your port is shot or something.
>
>
> On Mon, Apr 15, 2013 at 8:59 AM, Daiajo Tibdixious <daiajo@gmail.com>wrote:
>
>> I was running on 3.0.6 kernel, when after a problem with the phone
>> line internet was down for 3 weeks, when it came back up I had no
>> network. I upgraded to 3.7.9 and had a network device but I had to
>> bring it up manually: ifconfig eth0 up, then run dhcp, and that worked
>> for a month.
>>
>> Today had a powerfailure, after rebooting, no /dev/eth*:
>> ifconfig -a
>> gives enp2s0, lo, sit0
>>
>> I downloaded the r8168 driver from realtek (my if is RTL811/8168B),
>> installed modprobe'd it,
>> but still no eth device.
>>
>> I'm really mystified, as there were no kernel changes, it should have
>> rebooted with the network if it had it before.
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 1818 bytes --]

Re: [gentoo-amd64] eth device vanished

[Daiajo Tibdixious]

Its still coming up with the same thing:
02:00:0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL811/8168 PCI Express Gigabit Ethernet controller (rev 02)

Typed that manually (using lappy atm, with desktop beside me)

On 4/15/13, Forrest Schultz <f.schultz0@gmail.com> wrote:
> You can use lspci or something like that to enumerate your network cards,
> right? Maybe your port is shot or something.
>
>
> On Mon, Apr 15, 2013 at 8:59 AM, Daiajo Tibdixious <daiajo@gmail.com>
> wrote:
>
>> I was running on 3.0.6 kernel, when after a problem with the phone
>> line internet was down for 3 weeks, when it came back up I had no
>> network. I upgraded to 3.7.9 and had a network device but I had to
>> bring it up manually: ifconfig eth0 up, then run dhcp, and that worked
>> for a month.
>>
>> Today had a powerfailure, after rebooting, no /dev/eth*:
>> ifconfig -a
>> gives enp2s0, lo, sit0
>>
>> I downloaded the r8168 driver from realtek (my if is RTL811/8168B),
>> installed modprobe'd it,
>> but still no eth device.
>>
>> I'm really mystified, as there were no kernel changes, it should have
>> rebooted with the network if it had it before.
>>
>>
>

Re: [gentoo-amd64] eth device vanished

[Mark Knecht]

On Mon, Apr 15, 2013 at 6:09 AM, Vítor Brandão
<vitorbrandao.pt@gmail.com> wrote:
> Most likely this is due to a udev upgrade.
>
> Please check the udev upgrade guide:
> http://wiki.gentoo.org/wiki/Udev/upgrade
>
>

+1

mark@c2stable ~ $ eselect news list
News items:
  [1]      2012-09-09  make.conf and make.profile move
  [2]      2012-11-06  PYTHON_TARGETS deployment
  [3]      2013-01-23  (2013-01-23-udev-upgrade - removed?)
  [4]      2013-03-29  Upgrading udev to version >=200
mark@c2stable ~ $ eselect news read 4
2013-03-29-udev-upgrade
  Title                     Upgrading udev to version >=200
  Author                    Samuli Suominen <ssuominen@gentoo.org>
  Posted                    2013-03-29
  Revision                  2

This replaces the earlier news item about the udev 197 upgrade and
describes the predictable network interface names in more detail.

If you skip anything in this news item, your system will not be
bootable, or your networking will be down, or both.

Pay attention also to every message printed by emerge of sys-fs/udev
and sys-fs/udev-init-scripts as this news item may not be complete.

1. udev-postmount init script:

Remove the udev-postmount init script from your runlevels.

2. devtmpfs support:

You need at least version 2.6.32 of the kernel for devtmpfs
functionality. Once you have this, make sure CONFIG_DEVTMPFS=y is set
in the kernel configuration. See the gentoo udev guide for the option in
make menuconfig [1].

If you have a line for /dev in /etc/fstab, make sure it is configured
for file system type devtmpfs (not tmpfs or any other type). Also, you
can remove this line if you prefer, since devtmpfs is mounted
automatically.

3. Old interface naming rules:

If the system still has old network interface renaming rules in
/etc/udev/rules.d, like 70-persistent-net.rules, those will need
to be either modified or removed.

If you choose to modify them, you must use free namespace (like net*
or internet*) instead of kernel namespace (like eth* or wlan*)
because in-place renaming has been deprecated, see small
documentation of it if you like[2].

The file 70-persistent-net.rules, like the 70-persistent-cd.rules
should be removed, so if you modify, rename the file also to something
else like 70-my-network.rules to silence the deprecation warning
coming
from the end of the sys-fs/udev emerge.

This is the old format with reserved namespace:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="eth1"

This is the new format with free namespace:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="net0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="net1"

4. predictable network interface names:

If /etc/udev/rules.d/80-net-name-slot.rules is an empty file or a
symlink to /dev/null, the new names will be disabled and the kernel
will
do all the interface naming, and the resulting names may vary by
kernel
configuration, hardware configuration and kernel version.

Also, the forementioned old 70-persistent-net.rules might interfere with
the new predictable interface names.

You can get attributes of your network interfaces using a command like
the following (replace eth0 with the name of the appropriate interface):

# udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null

You can copy /lib/udev/rules.d/80-net-name-slot.rules to
/etc/udev/rules.d and specify the attributes and in which order
they will be used for naming. See upstream wiki[3] for detailed list
of options.

You can prepare the system for the new names before booting for example
by renaming /etc/init.d/net.* symlinks, editing /etc/conf.d/net, etc.

The feature can also be completely disabled using net.ifnames=0 on the
kernel command line.

If you only have one interface card, you don't necessarily have much
use for this feature as the name almost always stays at eth0, you can
easily disable it using forementioned methods.

This feature can also replace the functionality of sys-apps/biosdevname,
but you can still keep using it if you want.

In a normal new installation there are no files in /etc/udev/rules.d
and if you haven't edited any files you have in there, you should most
likely backup and delete them all if they don't belong to any packages.

The official wiki has a dedicated page for udev upgrade notes[4].

[1] http://www.gentoo.org/doc/en/udev-guide.xml
[2] http://www.kernel.org/doc/htmldocs/device-drivers/API-device-rename.html
[3] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
[4] http://wiki.gentoo.org/wiki/Udev/upgrade

mark@c2stable ~ $

Re: [gentoo-amd64] eth device vanished

[Randy Barlow]

On Mon, 2013-04-15 at 23:13 +1000, Daiajo Tibdixious wrote:
> Its still coming up with the same thing:
> 02:00:0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL811/8168 PCI Express Gigabit Ethernet controller (rev 02)
> 
> Typed that manually (using lappy atm, with desktop beside me)
> >> Today had a powerfailure, after rebooting, no /dev/eth*:
> >> ifconfig -a
> >> gives enp2s0, lo, sit0

This enp2s0 is very likely the eth device you are looking for. The new
udev names network interfaces differently.

-- 
R

Re: [gentoo-amd64] eth device vanished

[Daiajo Tibdixious]

Ah udev. I had done some of the upgrade steps but not all.
The network startup is still failing for some reason.
I did find out that my network device is enp2s0, and I can bring it up manually.
I'll sort out the startup problems later.
Thank you for pointing out what should have been obvious.

On Mon, Apr 15, 2013 at 11:09 PM, Vítor Brandão
<vitorbrandao.pt@gmail.com> wrote:
> Most likely this is due to a udev upgrade.
>
> Please check the udev upgrade guide:
> http://wiki.gentoo.org/wiki/Udev/upgrade
>
>
> 2013/4/15 Forrest Schultz <f.schultz0@gmail.com>
>>
>> You can use lspci or something like that to enumerate your network cards,
>> right? Maybe your port is shot or something.
>>
>>
>> On Mon, Apr 15, 2013 at 8:59 AM, Daiajo Tibdixious <daiajo@gmail.com>
>> wrote:
>>>
>>> I was running on 3.0.6 kernel, when after a problem with the phone
>>> line internet was down for 3 weeks, when it came back up I had no
>>> network. I upgraded to 3.7.9 and had a network device but I had to
>>> bring it up manually: ifconfig eth0 up, then run dhcp, and that worked
>>> for a month.
>>>
>>> Today had a powerfailure, after rebooting, no /dev/eth*:
>>> ifconfig -a
>>> gives enp2s0, lo, sit0
>>>
>>> I downloaded the r8168 driver from realtek (my if is RTL811/8168B),
>>> installed modprobe'd it,
>>> but still no eth device.
>>>
>>> I'm really mystified, as there were no kernel changes, it should have
>>> rebooted with the network if it had it before.
>>>
>>
>

Re: [gentoo-amd64] eth device vanished

[Frank Peters]

On Mon, 15 Apr 2013 06:13:56 -0700
Mark Knecht <markknecht@gmail.com> wrote:

> 
> If you skip anything in this news item, your system will not be
> bootable, or your networking will be down, or both.
>
> [snip]
> [snip]
> [snip]
> [snip]
> [snip]
> [snip]
> [snip]
>

Whoa!  I'm so glad I made the choice to not use that mess known as udev.

-- and I hope I will always have that choice.

Frank Peters

Re: [gentoo-amd64] eth device vanished

[Mark Knecht]

On Mon, Apr 15, 2013 at 9:04 AM, Frank Peters <frank.peters@comcast.net> wrote:
> On Mon, 15 Apr 2013 06:13:56 -0700
> Mark Knecht <markknecht@gmail.com> wrote:
>
>>
>> If you skip anything in this news item, your system will not be
>> bootable, or your networking will be down, or both.
>>
>> [snip]
>> [snip]
>> [snip]
>> [snip]
>> [snip]
>> [snip]
>> [snip]
>>
>
> Whoa!  I'm so glad I made the choice to not use that mess known as udev.
>
> -- and I hope I will always have that choice.
>
> Frank Peters


Ya know, personally I wish I'd never heard or seen or used udev. On
the other hand, I haven't had any real problems with any of the stuff
in that news flash. I'm still using eth0 and all my systems are still
booting & working. I am careful to only update 1/day so that if
something goes wrong I'll have others to work out what happened, but
amazingly none of what's quoted seems to have been required to keep
this machine running correctly. Then again, maybe today will be the
day! ;-)

Re: [gentoo-amd64] eth device vanished

[Barry Schwartz]

Frank Peters <frank.peters@comcast.net> skribis:
> Whoa!  I'm so glad I made the choice to not use that mess known as udev.
> 
> -- and I hope I will always have that choice.

I do, too. Fortunately the kernel folk don’t get caught up in these
fads that grip upon the minds of some userspace developers; and
fortunately Gentoo is very, very conservative.

I was running udev but switched to a sort of middle ground before it
was too late, Gentoo’s own eudev.

Re: [gentoo-amd64] eth device vanished

[Mark Knecht]

On Mon, Apr 15, 2013 at 9:46 AM, Barry Schwartz
<chemoelectric@chemoelectric.org> wrote:
> Frank Peters <frank.peters@comcast.net> skribis:
>> Whoa!  I'm so glad I made the choice to not use that mess known as udev.
>>
>> -- and I hope I will always have that choice.
>
> I do, too. Fortunately the kernel folk don’t get caught up in these
> fads that grip upon the minds of some userspace developers; and
> fortunately Gentoo is very, very conservative.
>
> I was running udev but switched to a sort of middle ground before it
> was too late, Gentoo’s own eudev.
>
>

I guess from the tone of your response eudev is going OK for you? I
was interested in trying it but the documentation seems weak at this
point:

http://www.gentoo.org/proj/en/eudev/

Is this still the best Gentoo page on the project? (I hope not!) The
fork was announced last December so it's been 4 months. As a (mostly)
stable user I'm hesitant to invest the time without more info.

Thanks,
Mark

Re: [gentoo-amd64] eth device vanished

[Barry Schwartz]

Mark Knecht <markknecht@gmail.com> skribis:
> On Mon, Apr 15, 2013 at 9:46 AM, Barry Schwartz
> <chemoelectric@chemoelectric.org> wrote:
> > I was running udev but switched to a sort of middle ground before it
> > was too late, Gentoo’s own eudev.
> >
> >
> 
> I guess from the tone of your response eudev is going OK for you? I
> was interested in trying it but the documentation seems weak at this
> point:
> 
> http://www.gentoo.org/proj/en/eudev/
> 
> Is this still the best Gentoo page on the project? (I hope not!) The
> fork was announced last December so it's been 4 months. As a (mostly)
> stable user I'm hesitant to invest the time without more info.

I don’t know. I just switched without paying much attention, rather
than go through the upgrade to the latest systemd-chauvinist versions
of udev. It was either that or freeze my udev version for as long as
possible, to avoid getting caught in the whirlpool. I did have trouble
finding documentation and instead just played around until I got
successfully switched over.

Re: [gentoo-amd64] eth device vanished

[Barry Schwartz]

Incidentally I have my ethernet devices configured with some udev
rules to assign specific names to the given mac addresses, and I use
static routing. This is for an ordinary desktop computer. I view the
automatic stuff as useful to get going in a hurry, but for long term
nothing beats taking as much control as possible.

Re: [gentoo-amd64] eth device vanished

[Rich Freeman]

On Mon, Apr 15, 2013 at 4:06 PM, Barry Schwartz
<chemoelectric@chemoelectric.org> wrote:
> Incidentally I have my ethernet devices configured with some udev
> rules to assign specific names to the given mac addresses, and I use
> static routing. This is for an ordinary desktop computer. I view the
> automatic stuff as useful to get going in a hurry, but for long term
> nothing beats taking as much control as possible.

I think the real pain with udev and network interfaces is the
limitation in linux (well, unix) that allows only one name for any
particular interface.  Udev symlinks for device nodes can be quite
handy (/dev/disk/...), and normally they can just add new symlinks
without messing with the old ones.  I think plan9 made network
interfaces part of the filesystem, but I'm not quite sure how they
went about it - if network interfaces were just device nodes then we'd
be able to have the best of both worlds.

Rich