Also we tried the workaround in comment #16 and blacklisting the mlx5_core module during the install and eth0 was not available.
[ 16.198090] Atheros 8031 ethernet QCOM8070:00:04: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=QCOM8070:00:04, irq=-2) [ 16.198153] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 18.258062] 803x_aneg_done: SGMII link is not ok -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677297 Title: [Zesty] d-i: replace msm_emac with qcom_emac Status in linux package in Ubuntu: Incomplete Bug description: [Impact] 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 drivers/net/ethernet/qualcomm/emac/ 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
