on my qdf2400 server. Looks like dhclient is able to get a lease and ifconfig displays the ip address.
ubuntu@ubuntu:~$ sudo dhclient -v eth0 [sudo] password for ubuntu: 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=0x1b76e36a) DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x1b76e36a) DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x1b76e36a) DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x1b76e36a) DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x1b76e36a) DHCPREQUEST of 10.228.66.113 on eth0 to 255.255.255.255 port 67 (xid=0x6ae3761b) DHCPOFFER of 10.228.66.113 from 10.228.66.3 DHCPACK of 10.228.66.113 from 10.228.66.3 bound to 10.228.66.113 -- renewal in 268 seconds. ubuntu@ubuntu:~$ ifconfig enP1s2 Link encap:Ethernet HWaddr 24:8a:07:97:30:16 inet addr:10.228.66.114 Bcast:10.228.66.255 Mask:255.255.255.0 inet6 addr: fe80::268a:7ff:fe97:3016/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5290 errors:0 dropped:0 overruns:0 frame:0 TX packets:1752 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3115155 (3.1 MB) TX bytes:368794 (368.7 KB) eth0 Link encap:Ethernet HWaddr 8c:fd:f0:06:92:a5 inet addr:10.228.66.113 Bcast:10.228.66.255 Mask:255.255.255.0 inet6 addr: fe80::8efd:f0ff:fe06:92a5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:950 (950.0 B) TX bytes:2436 (2.4 KB) Interrupt:40 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:160 errors:0 dropped:0 overruns:0 frame:0 TX packets:160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11840 (11.8 KB) TX bytes:11840 (11.8 KB) ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.10.0-19-generic #21ubuntuRC04+patchset.1-Ubuntu SMP Mon Apr 10 17:09:12 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux ubuntu@ubuntu:~$ -- 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
