Ubuntu

wired connection fails on startup 12.04

Asked by John B on 2012-06-30

Hi. I have a brand new Asus X53E laptop running only Ubuntu 12.04 and have a problem with establishing a wired internet connection at startup. I usually have to reboot several times before a connection is established. Once it is establshed, there is no problem and the connection lasts. If I manually disconnect a working connection, the same problem exists.

The wired connection on my desktop, running a previous version of Ubuntu works fine. I am trying to figure out if the problem is with the laptop hardware or with the software. Any suggestions?

The system log errors for one cycle of disconnect and connect are:

Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) starting connection 'Wired connection 1'
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> dhclient started with pid 1993
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Beginning IP6 addrconf.
Jun 30 08:29:28 john-K53E vpnagent[1018]: Function: tableCallbackHandler File: RouteMgr.cpp Line: 1694 Invoked Function: recv Return Code: 11 (0x0000000B) Description: unknown
Jun 30 08:29:28 john-K53E dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R4
Jun 30 08:29:28 john-K53E dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 30 08:29:28 john-K53E dhclient: All rights reserved.
Jun 30 08:29:28 john-K53E dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 30 08:29:28 john-K53E dhclient:
Jun 30 08:29:28 john-K53E vpnagent[1018]: A network interface has gone down.
Jun 30 08:29:28 john-K53E vpnagent[1018]: Function: logInterfaces File: RouteMgr.cpp Line: 2076 Invoked Function: logInterfaces Return Code: 0 (0x00000000) Description: IP Address Interface List:
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 30 08:29:28 john-K53E vpnagent[1018]: Function: tableCallbackHandler File: RouteMgr.cpp Line: 1694 Invoked Function: recv Return Code: 11 (0x0000000B) Description: unknown
Jun 30 08:29:28 john-K53E vpnagent[1018]: A new network interface has been detected.
Jun 30 08:29:28 john-K53E vpnagent[1018]: Function: logInterfaces File: RouteMgr.cpp Line: 2076 Invoked Function: logInterfaces Return Code: 0 (0x00000000) Description: IP Address Interface List: FE80:0:0:0:CA60:FF:FE50:211A
Jun 30 08:29:28 john-K53E NetworkManager[805]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Jun 30 08:29:28 john-K53E dhclient: Listening on LPF/eth0/c8:60:00:50:21:1a
Jun 30 08:29:28 john-K53E dhclient: Sending on LPF/eth0/c8:60:00:50:21:1a
Jun 30 08:29:28 john-K53E dhclient: Sending on Socket/fallback
Jun 30 08:29:28 john-K53E dhclient: DHCPREQUEST of 10.0.1.12 on eth0 to 255.255.255.255 port 67
Jun 30 08:29:29 john-K53E vpnagent[1018]: Function: tableCallbackHandler File: RouteMgr.cpp Line: 1694 Invoked Function: recv Return Code: 11 (0x0000000B) Description: unknown
Jun 30 08:29:30 john-K53E vpnagent[1018]: Function: tableCallbackHandler File: RouteMgr.cpp Line: 1694 Invoked Function: recv Return Code: 11 (0x0000000B) Description: unknown
Jun 30 08:29:31 john-K53E dhclient: DHCPREQUEST of 10.0.1.12 on eth0 to 255.255.255.255 port 67
Jun 30 08:29:38 john-K53E kernel: [ 445.465187] eth0: no IPv6 routers present
Jun 30 08:29:39 john-K53E dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 30 08:29:42 john-K53E dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 30 08:29:45 john-K53E dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jun 30 08:29:49 john-K53E NetworkManager[805]: <info> (eth0): IP6 addrconf timed out or failed.
Jun 30 08:29:49 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 30 08:29:49 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 30 08:29:49 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 30 08:29:50 john-K53E dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Jun 30 08:30:00 john-K53E dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Jun 30 08:30:14 john-K53E NetworkManager[805]: <warn> (eth0): DHCPv4 request timed out.
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> (eth0): canceled DHCP transaction, DHCP client pid 1993
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> Marking connection 'Wired connection 1' invalid.
Jun 30 08:30:14 john-K53E NetworkManager[805]: <warn> Activation (eth0) failed.
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 30 08:30:14 john-K53E NetworkManager[805]: <info> (eth0): deactivating device (reason 'none') [0]
Jun 30 08:30:14 john-K53E vpnagent[1018]: Function: tableCallbackHandler File: RouteMgr.cpp Line: 1694 Invoked Function: recv Return Code: 11 (0x0000000B) Description: unknown

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
2012-06-30
Last query:
2012-06-30
Last reply:
2012-06-30

Can you give the output of:

sudo lshw -C network; lsb_release -a; uname -a; sudo rfkill list

Thanks

Also do you dual boot the system?

Thanks

John B (j200477) said : #2

Sure. It is not a dual boot. Only Ubuntu.

john@john-K53E:~$ sudo lshw -C network; lsb_release -a; uname -a; sudo rfkill list
[sudo] password for john:
  *-network DISABLED
       description: Wireless interface
       product: AR9485 Wireless Network Adapter
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlan0
       version: 01
       serial: 44:6d:57:21:09:b1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=3.2.0-26-generic-pae firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
       resources: irq:17 memory:de800000-de87ffff memory:de880000-de88ffff
  *-network
       description: Ethernet interface
       product: AR8151 v2.0 Gigabit Ethernet
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: eth0
       version: c0
       serial: c8:60:00:50:21:1a
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=atl1c driverversion=1.0.1.0-NAPI duplex=full firmware=N/A ip=10.0.1.12 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:53 memory:dd400000-dd43ffff ioport:a000(size=128)
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Linux john-K53E 3.2.0-26-generic-pae #41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 i686 i386 GNU/Linux
0: phy0: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
1: asus-wlan: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
john@john-K53E:~$

Could install wicd and uninstall network manager and reboot

HTH

John B (j200477) said : #4

Thanks actionparsnip. I tried your suggestion, installed WICD, uninstalled network manager, and reboot. Same problem. So I reinstalled gnome network manager and uninstalled WICD. Again, same problem.

However, I did find that by bypassing the router, the wired network will establish communication via gnome network manager on my laptop. The problem is not entirely in the router, however, because my desktop, running an older version of Ubuntu, can establish a wired connection via the router.

I also found that although the laptop connection cannot be easily established with the router in place, a wireless connection can be easily established. So for some reason, the problem is only with the wired connection when using the router.

Lastly, just to make sure the problem is not in the LAN cable, I unplugged the working cable from my desktop and tried it with my laptop, and same problem. So it is not the cable.

Any more suggestions?

Are you intending to use wired connection and always use DHCP?

John B (j200477) said : #6

Yes, I would like the option of using a wired connection. I would use it if it worked. And I assume I would need to use DHCP, as that seems to be the default for my network.

But is that all the system will ever use?

John B (j200477) said : #8

I don't understand the question. I would like to be able to use either wired or wireless connections. There may be times when either could come in handy. I don't know about the DHCP part. I assume that my Internet provider uses DHCP.

will the system only use the wired connection in it's life and nothing else?

John B (j200477) said : #10

No. As I said, I would like the ability to use both the wired and wireless at different times.

All I can suggest is report a bug. If you were only using wired you can remove all gui apps and use interfaces file to use DHCP on the interface. Makes the SO sleeker

John B (j200477) said : #12

OK, thanks actionparsnip. From the information I provided, can we rule out that it is a hardware problem specific to my laptop?

John B (j200477) said : #13

Thanks actionparsnip, that solved my question.