On Thu, Jun 03, 2021 at 01:12:16PM +0000, Joakim Tjernlund wrote:
Seems like old eth interface names cannot read name_assign_type:
cat /sys/class/net/eth0/name_assign_type
cat: /sys/class/net/eth0/name_assign_type: Invalid argument
Have you done a git bisect to figure out which change broke it?
The 5.10 kernel on my Debian desktop has this issue. So it is older
than that.
Andrew
On Thu, 2021-06-03 at 16:16 +0200, Andrew Lunn wrote:
On Thu, Jun 03, 2021 at 01:12:16PM +0000, Joakim Tjernlund wrote:
quoted
Seems like old eth interface names cannot read name_assign_type:
cat /sys/class/net/eth0/name_assign_type
cat: /sys/class/net/eth0/name_assign_type: Invalid argument
Have you done a git bisect to figure out which change broke it?
The 5.10 kernel on my Debian desktop has this issue. So it is older
than that.
Andrew
No, I have not used systemd before, also on 5.10.latest, I am setting up a new FW @home and decided to try out systemd.
Jocke
On Thu, Jun 03, 2021 at 02:29:38PM +0000, Joakim Tjernlund wrote:
On Thu, 2021-06-03 at 16:16 +0200, Andrew Lunn wrote:
quoted
On Thu, Jun 03, 2021 at 01:12:16PM +0000, Joakim Tjernlund wrote:
quoted
Seems like old eth interface names cannot read name_assign_type:
cat /sys/class/net/eth0/name_assign_type
cat: /sys/class/net/eth0/name_assign_type: Invalid argument
Have you done a git bisect to figure out which change broke it?
The 5.10 kernel on my Debian desktop has this issue. So it is older
than that.
Andrew
No, I have not used systemd before, also on 5.10.latest, I am setting up a new FW @home and decided to try out systemd.
Debian systemd does not seem to mind not being able to read
/sys/class/net/eth0/name_assign_type. At least my Ethernet interface
is working O.K.
Andrew