[Bug 1968111] Re: uc22 rpi3 ethernet getting renamed on every boot

[Juerg Haefliger]

Needs new Pi firmware to handle longer os_prefix pathnames.

** Also affects: linux-firmware-raspi (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux-raspi (Ubuntu)
       Status: New => Invalid

** Changed in: snapd
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to linux-firmware-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1968111

Title:
  uc22 rpi3 ethernet getting renamed on every boot

Status in snapd:
  Invalid
Status in linux-firmware-raspi package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  On rpi3 with uc22 (just confirmed on the latest image from
  20220406.1), the built-in ethernet interface should use generic names
  (i.e. eth0). On rpi4 this works as it should, and it uses eth0.

  On the rpi3b+ I'm testing on, I saw it get enxea1a4588e236 on the
  first boot. On the second boot though, it got renamed to
  enx3a583dc734b6

  The result of this, is that on rpi3 with uc22, if you only configure ethernet, then it will no longer work after you reboot. Since console-conf only runs on first boot, it will be stuck thinking it was unable to get an address.  The netplan config file that is generated by console-conf references the device name, so it will still be looking for that original name:
  network:
    ethernets:
      enxea1a4588e236:
        dhcp4: true
    version: 2
  ...

  Fortunately, the wifi interface gets named wlan0 and does not get renamed every boot. So I was able to configure that interface and still get in to gather some information about this.
  However, unless you use wifi, rpi3 devices will be useless after the first boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1968111/+subscriptions