Loïc: the updated driver uses the 'platform' bus rather than 'virtual', so the device has moved in sysfs. Is this going to be a problem?
Also, could you see if NM works as it does for Paul? It's possible that the DRIVER property is being exposed through a different node in sysfs. Try a recursive query:
udevadm info --query=all --path=/class/net/eth0 --attribute-walk
Paul; IIRC, ifup will only work if you have an entry in /etc/network/interfaces, which would preclude NM from managing the device. If you want to try ifup/ifdown, you may need to add the following to /etc/network/interfaces:
auto eth0
iface eth0 inet dhcp
If all is OK with the updated driver, I will remove debug code and send a patch.
Loïc: the updated driver uses the 'platform' bus rather than 'virtual', so the device has moved in sysfs. Is this going to be a problem?
Also, could you see if NM works as it does for Paul? It's possible that the DRIVER property is being exposed through a different node in sysfs. Try a recursive query:
udevadm info --query=all --path= /class/ net/eth0 --attribute-walk
Paul; IIRC, ifup will only work if you have an entry in /etc/network/ interfaces, which would preclude NM from managing the device. If you want to try ifup/ifdown, you may need to add the following to /etc/network/ interfaces:
auto eth0
iface eth0 inet dhcp
If all is OK with the updated driver, I will remove debug code and send a patch.