Jeremy, ah right, I expected the DRIVER property to be set on that other node;
the recursive query indeed shows the property on some nodes:
l...@babbage20:~$ udevadm info --query=all --path=/class/net/eth0
--attribute-walk
...
looking at device '/devices/platform/fec.0/net/eth0':
KERNEL=="eth0"
SUBSYSTEM=="net"
DRIVER==""
ATTR{addr_len}=="6"
ATTR{dev_id}=="0x0"
ATTR{ifalias}==""
ATTR{iflink}=="2"
ATTR{ifindex}=="2"
ATTR{features}=="0x0"
ATTR{type}=="1"
ATTR{link_mode}=="0"
ATTR{address}=="00:04:9f:00:cd:14"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{carrier}=="1"
ATTR{dormant}=="0"
ATTR{operstate}=="unknown"
ATTR{mtu}=="1500"
ATTR{flags}=="0x1003"
ATTR{tx_queue_len}=="1000"
looking at parent device '/devices/platform/fec.0':
KERNELS=="fec.0"
SUBSYSTEMS=="platform"
DRIVERS=="fec"
ATTRS{modalias}=="platform:fec"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
I did not try Network-Manager and can't try it out right now (not near the
board), it probably works according to other comments in this bug.
Thanks and well done!
--
FEC driver does not set "DRIVER" property in udev which makes network-manager
fail
https://bugs.launchpad.net/bugs/438687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
