By accident during my update of my ASUS EEE (now successfully completed), I discovered that it connects automatically to the Internet when the physical connection is plugged in, while my desktop machine (AMD + Gigabyte mobo) has to be told by 'dhcpcd'.
The netbook's syslog reports (my comments marked by '# PP :') (the 'Dec 31' date is due to failure of the mobo battery, which forces me to enter the correct date by hand) : Dec 31 19:00:23 localhost dhcpcd[1323]: version 6.4.7 starting Dec 31 19:00:23 localhost dhcpcd[1323]: dev: loaded udev Dec 31 19:00:23 localhost dhcpcd[1323]: no interfaces have a carrier Dec 31 19:00:23 localhost dhcpcd[1323]: forked to background, child pid 1346 Dec 31 19:00:23 localhost kernel: atl1c 0000:01:00.0: Unable to allocate MSI interrupt Error: -38 Dec 31 19:00:23 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: waiting for carrier Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: carrier acquired Dec 31 19:00:23 localhost dhcpcd[1346]: DUID 00:01:00:01:03:c3:b8:97:00:26:18:79:64:16 Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: IAID 18:79:64:16 Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: carrier lost Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: using IPv4LL address 169.254.91.169 Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: adding route to 169.254.0.0/16 Dec 31 19:00:33 localhost dhcpcd[1346]: enp1s0: soliciting a DHCP lease ... Feb 8 18:54:59 localhost dhcpcd[1346]: enp1s0: carrier acquired ... Feb 8 18:54:59 localhost dhcpcd[1346]: enp1s0: IAID 18:79:64:16 Feb 8 18:54:59 localhost dhcpcd[1346]: enp1s0: soliciting a DHCP lease Feb 8 18:55:07 localhost dhcpcd[1346]: enp1s0: offered 192.168.1.3 from 192.168.1.1 Feb 8 18:55:11 localhost dhcpcd[1346]: enp1s0: leased 192.168.1.3 for 86400 seconds Feb 8 18:55:11 localhost dhcpcd[1346]: enp1s0: adding route to 192.168.1.0/24 Feb 8 18:55:11 localhost dhcpcd[1346]: enp1s0: adding default route via 192.168.1.1 Feb 8 18:55:11 localhost dhcpcd[1346]: enp1s0: deleting route to 169.254.0.0/16 ... # PP : remove/restore conn'n Feb 8 19:14:41 localhost dhcpcd[1346]: enp1s0: carrier lost Feb 8 19:14:41 localhost dhcpcd[1346]: enp1s0: deleting route to 192.168.1.0/24 Feb 8 19:14:41 localhost dhcpcd[1346]: enp1s0: deleting default route via 192.168.1.1 Feb 8 19:15:15 localhost dhcpcd[1346]: enp1s0: carrier acquired Feb 8 19:15:15 localhost kernel: atl1c 0000:01:00.0: atl1c: enp1s0 NIC Link is Up<100 Mbps Full Duplex> Feb 8 19:15:15 localhost dhcpcd[1346]: enp1s0: IAID 18:79:64:16 Feb 8 19:15:15 localhost dhcpcd[1346]: enp1s0: rebinding lease of 192.168.1.3 Feb 8 19:15:23 localhost dhcpcd[1346]: enp1s0: leased 192.168.1.3 for 86400 seconds Feb 8 19:15:23 localhost dhcpcd[1346]: enp1s0: adding route to 192.168.1.0/24 Feb 8 19:15:23 localhost dhcpcd[1346]: enp1s0: adding default route via 192.168.1.1 # PP : Dillo finds site The desktop machine's syslog reports : Feb 8 09:26:09 localhost dhcpcd[980]: version 6.6.7 starting Feb 8 09:26:09 localhost dhcpcd[980]: dev: loaded udev Feb 8 09:26:09 localhost dhcpcd[980]: no interfaces have a carrier Feb 8 09:26:09 localhost dhcpcd[980]: forked to background, child pid 997 Feb 8 09:26:09 localhost dhcpcd[997]: enp5s0: waiting for carrier Feb 8 09:26:09 localhost kernel: r8169 0000:05:00.0 enp5s0: link down Feb 8 09:26:09 localhost kernel: r8169 0000:05:00.0 enp5s0: link down Feb 8 09:26:09 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready Feb 8 09:26:11 localhost dhcpcd[997]: enp5s0: carrier acquired Feb 8 09:26:11 localhost kernel: r8169 0000:05:00.0 enp5s0: link up Feb 8 09:26:11 localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready Feb 8 09:26:11 localhost dhcpcd[997]: DUID 00:01:00:01:1a:1b:b4:7e:50:e5:49:c6:10:3a Feb 8 09:26:11 localhost dhcpcd[997]: enp5s0: IAID 49:c6:10:3a Feb 8 09:26:11 localhost dhcpcd[997]: enp5s0: rebinding lease of 192.168.1.2 Feb 8 09:26:14 localhost dhcpcd[997]: enp5s0: NAK: from 192.168.1.1 Feb 8 09:26:14 localhost dhcpcd[997]: enp5s0: soliciting a DHCP lease Feb 8 09:26:16 localhost dhcpcd[997]: enp5s0: offered 192.168.1.2 from 192.168.1.1 Feb 8 09:26:21 localhost dhcpcd[997]: enp5s0: leased 192.168.1.2 for 86400 seconds Feb 8 09:26:21 localhost dhcpcd[997]: enp5s0: adding route to 192.168.1.0/24 Feb 8 09:26:21 localhost dhcpcd[997]: enp5s0: adding default route via 192.168.1.1 Feb 8 09:26:22 localhost ntpd[837]: Listen normally on 2 enp5s0 192.168.1.2:123 ... # PP : 'ioff', remove conn'n Feb 8 18:54:26 localhost dhcpcd[11404]: sending signal ARLM to pid 997 Feb 8 18:54:26 localhost dhcpcd[11404]: waiting for pid 997 to exit Feb 8 18:54:26 localhost dhcpcd[997]: received signal ALRM from PID 11404, releasing Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: removing interface Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: releasing lease of 192.168.1.2 Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: deleting route to 192.168.1.0/24 Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: deleting default route via 192.168.1.1 Feb 8 18:54:26 localhost dhcpcd[997]: exited ... Feb 8 18:54:35 localhost kernel: r8169 0000:05:00.0 enp5s0: link down ... # PP : restore conn'n Feb 8 19:18:11 localhost kernel: r8169 0000:05:00.0 enp5s0: link up # PP : Firefox can't find site I've checked /etc/runlevels/default & /etc/udev in both machines, but can't see anything different between the two. IIRC the netbook didn't show this behaviour before the recent update, But both machines have similarly updated pkgs. The kernels are 3.17 & 3.18 ; desktop manager is Fluxbox. Can anyone explain what I need to do to get the desktop machine to behave as helpfully as the netbook does ? -- ========================,,============================================ SUPPORT ___________//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT `-O----------O---' purslowatchassdotutorontodotca
