FAI with pre-release bullseye yielding inconsistent network names

fai1107 at macrotex.net fai1107 at macrotex.net
Fri Jan 15 19:42:33 CET 2021

On 1/15/2021 10:11 AM, Stefan Möding wrote:
> fai1107 at macrotex.net writes:
>> I do the initial FAI imaging using a buster NFS root and install buster in
>> /target. When I then run "chroot /target udevadm info /sys/class/net/eth0"
>> I see about 27 lines including a bunch of ID_NET_NAME_* values.
>> I do the above again, but this time with a bullseye NFS root and install
>> bullseye in /target. When I then run "chroot /target udevadm info
>> /sys/class/net/eth0" I see only about 6 lines and, in particular, no
>> ID_NET_NAME_* values.
> This is the reason why the script does not pick up the correct name.
>> I created the bullseye NFS root in the same way as for buster (I think). Why
>> is there this large difference in the outputs of udevadm info?
> Does the following show more output on Bullseye?
> # chroot /target udevadm info --query=all /sys/class/net/eth0

No. The output is identical to "chroot /target udevadm info 

P: /devices/pci0000:00/0000:00:16.0/0000:0b:00.0/net/eth0
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/net/ens192

That's all of it.

> --
> Stefan

More information about the linux-fai mailing list