The qcom_emac driver in the installer is able to get a DHCP lease once I
blacklisted the mlx5_core module.

~ # lsmod
Module                  Size  Used by
uas                    28672  0
usb_storage            77824  1 uas
at803x                 16384  1
devlink                36864  0
ptp                    28672  0
pps_core               24576  1 ptp
ahci_platform          16384  0
libahci_platform       20480  1 ahci_platform
libahci                45056  2 ahci_platform,libahci_platform
qcom_emac              49152  0
sdhci_acpi             16384  0
sdhci                  65536  1 sdhci_acpi
xhci_plat_hcd          16384  0
~ # ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 8c:fd:f0:06:92:a5 brd ff:ff:ff:ff:ff:ff
    inet brd scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::8efd:f0ff:fe06:92a5/64 scope link 
       valid_lft forever preferred_lft forever
~ # cat /proc/cmdline 
BOOT_IMAGE=/ubuntu-installer/arm64/linux module_blacklist=mlx5_core --- quiet
~ #

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [Zesty] d-i: replace msm_emac with qcom_emac

Status in linux package in Ubuntu:

Bug description:
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to