[blfs-support] Persistent device names problem

Bruce Dubbs bruce.dubbs at gmail.com
Sat Nov 3 20:21:19 PDT 2012

pete wrote:

>   >> forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x50ef @ 0, addr
>   >> 00:22:68:72:e6:a1
>   >> forcedeth 0000:00:07.0: highdma pwrctl mgmt lnktim msi desc-v3
>   >> cdc_ether 2-7:1.1: eth1: register 'cdc_ether' at usb-0000:00:02.0-7, CDC
>   >> Ethernet Device, 00:40:7b:71:9b:f3

>   > What is the output of lspci|grep Ethernet
> The output of lspci|grep Ethernet:
> 00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)

This doesn't look right.  The only thing you have is a bridge?  You 
should have two ethernet cards.

>   > Also what are the contents of /etc/udev/rules.d/70-persistent-net.rules?
> The contents of 70-persistent-net.rules is:
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
> # net device module
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:40:7b:71:9b:f3", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
> # net device module
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:22:68:72:e6:a1", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

This looks OK.

> Provided that the interfaces are recognised correctly at boot up, they
> both configure OK (etho via dhcpcd and eth1 via ipv4).

> There is no hotplugging available (as yet). When an interface is connected
> (except at boot up) it must be manually configured using "ifup ethx".

No, our scripts don't support hotplugging either.  There would have to 
be some way to call ifup automatically.

> This hardware setup has worked well for many years on various versions of
> LFS/BLFS builds (up to LFS-7.0), it is only on this latest version (LFS-7.2)
> that I have had problems.
> If there have not been any significant changes to the software since
> LFS-7.0, maybe I should try a rebuild.

I wouldn't think reinstalling the whole thing would be needed.  You 
could try installing an older version of udev, say version 173, using 
the LFS -7.0 instructions.

Another thing to try is to temporarily disable the udev and udev_retry 
scripts and reboot.  Then run '/lib/udev/udevd --debug' followed by 
'/sbin/udevadm trigger --action=add --type=subsystems' and see what is 
printed to stderr.

   -- Bruce

   -- Bruce

More information about the blfs-support mailing list