Wired connection not established

Bug #1019652 reported by John B
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

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 tried installing WICD, uninstalled network manager, and rebooted. 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.

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

==============

The system is not a dual boot. Only Ubuntu. Below is more information

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:~$

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1019652/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
John B (j200477)
affects: ubuntu → network-manager-applet (Ubuntu)
Revision history for this message
Thomas Hood (jdthood) wrote : Re: wired connection fails on startup 12.04

@John: Please reboot, reproduce the problem, and run "apport-collect 1019652" to provide more information about the affected system.

affects: network-manager-applet (Ubuntu) → network-manager (Ubuntu)
Changed in network-manager (Ubuntu):
status: New → Incomplete
summary: - wired connection fails on startup 12.04
+ Wired connection not established
tags: added: precise
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
larytet (larytet-48904418) wrote :
Changed in network-manager (Ubuntu):
status: Expired → Confirmed
Revision history for this message
larytet (larytet-48904418) wrote :

Apport-collect returns error (report already closed?)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.