Web lists-archives.com

/etc/udev/rules.d/*net* versus hwinfo --netcards

root@joule:~# cat /etc/udev/rules.d/*net*
# joule:/etc/udev/rules.d/70-persistent-net.rules
# 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.
# PCI device
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
 ATTR{address}=="00:07:e9:78:a8:b0", ATTR{dev_id}=="0x0", \
 ATTR{type}=="1", KERNEL=="eth*", NAME="mainboard"
# USB device 0x:0x (asix)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
# ATTR{address}=="00:1d:7e:00:ee:9f", ATTR{dev_id}=="0x0", \
# ATTR{type}=="1", KERNEL=="eth*", NAME="LocLCS1788"
root@joule:~# hwinfo --netcards
20: PCI 208.0: 0200 Ethernet controller
  [Created at pci.378]
  Unique ID: vVa_.4AMaVDpEyvF
  Parent ID: 6NW+.c7JTK_YUBi2
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:08.0
  SysFS BusID: 0000:02:08.0
  Hardware Class: network
  Model: "Intel 82562EZ 10/100 Ethernet Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x1050 "82562EZ 10/100 Ethernet Controller"
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x0155
  Revision: 0x02
  Driver: "e100"
  Driver Modules: "e100"
  Device File: LocLCS1788
  Memory Range: 0xfceff000-0xfcefffff (rw,non-prefetchable)
  I/O Ports: 0xddc0-0xddff (rw)
  IRQ: 20 (2 events)
  HW Address: 00:07:e9:78:a8:b0
  Permanent HW Address: 00:07:e9:78:a8:b0
  Link detected: no
  Module Alias: "pci:v00008086d00001050sv00001028sd00000155bc02sc00i00"
  Driver Info #0:
    Driver Status: e100 is active
    Driver Activation Cmd: "modprobe e100"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #10 (PCI bridge)

Appears that udev ignores the rule which should assign "mainboard".
How does "Device File: LocLCS1788" become associated with the 
mainboard Ethernet hardware?  A cache from an old configuration?
A cache in wicd?

Not surprisingly, configuration of the mainboard interface fails.
peter@joule:~$ systemctl status networking.service
b networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese
   Active: failed (Result: exit-code) since Sat 2019-05-25 08:17:49 PDT; 2min 6s
     Docs: man:interfaces(5)
  Process: 368 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1
  Process: 360 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [
 Main PID: 368 (code=exited, status=1/FAILURE)

May 25 08:17:47 joule systemd[1]: Starting Raise network interfaces...
May 25 08:17:49 joule ifup[368]: Cannot find device "mainboard"
May 25 08:17:49 joule ifup[368]: ifup: failed to bring up mainboard
May 25 08:17:49 joule systemd[1]: networking.service: Main process exited, code=
May 25 08:17:49 joule systemd[1]: Failed to start Raise network interfaces.
May 25 08:17:49 joule systemd[1]: networking.service: Unit entered failed state.
May 25 08:17:49 joule systemd[1]: networking.service: Failed with result 'exit-c


Thanks,                ... Peter E.

Composed and transmitted by software designed to avoid the 
complication and vulnerability of antivirus software.
Pender Is., BC: +1 604 670 0140
Bcc: peter at easthope. ca