I built a DI where the initrd has both the PHY and the qcom_emac driver.
The d-i installer now loads both at803x and qcom_emac, but dhclient
fails to get a DHCP address. So, I am not sure what is going on with
qcom_emac.. is there another module dependency I am missing ?
~ # lsmod
Module Size Used by
mlx5_ib 204800 0
ib_core 249856 1 mlx5_ib
uas 28672 0
usb_storage 77824 1 uas
at803x 16384 0
mlx5_core 479232 1 mlx5_ib
devlink 36864 1 mlx5_core
ptp 28672 1 mlx5_core
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 link
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
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 8c:fd:f0:06:92:a5 brd ff:ff:ff:ff:ff:ff
3: enP1s2: <BROADCAST,MULTICAST> mtu 1500 qdisc mq qlen 1000
link/ether 24:8a:07:97:30:16 brd ff:ff:ff:ff:ff:ff
~ # dhclient -v eth0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/8c:fd:f0:06:92:a5
Sending on LPF/eth0/8c:fd:f0:06:92:a5
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xc271fe77)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xc271fe77)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xc271fe77)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xc271fe77)
............
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 (xid=0xc271fe77)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xc271fe77)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0xc271fe77)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
~ #
--
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
