Ubuntu
linux package

[Dell Latitude E6520] Wired and wireless networking don't work after upgrade

Bug #1161655 reported by Steveire
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I upgraded to raring this evening. After rebooting, my wireless and wired internet connections no longer work. I found that if I booted into an old kernel (3.5.0-16 I think) I can use wired networking.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-15-generic 3.8.0-15.25
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: stephen 2120 F.... pulseaudio
 /dev/snd/controlC0: stephen 2120 F.... pulseaudio
 /dev/snd/seq: timidity 1682 F.... timidity
Date: Thu Mar 28 23:54:32 2013
InstallationDate: Installed on 2012-08-07 (233 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
IwConfig:
 Error: command ['iwconfig'] failed with exit code -9: eth0 no wireless extensions.
MachineType: Dell Inc. Latitude E6520
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=7b8bf911-7666-4b3b-851b-c7a3c8f1322b ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-15-generic N/A
 linux-backports-modules-3.8.0-15-generic N/A
 linux-firmware 1.104
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-03-28 (0 days ago)
dmi.bios.date: 07/11/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0J4TFW
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Steveire (steveire) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Steveire (steveire) wrote : Re: Wired and wireless networking don't work after upgrade

Following the advice here: http://www.davidpashley.com/articles/network-troubleshooting.html

I get this output when running the 'broken' kernel. When running the older kernel the mii-tool shows the expected result instead.

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 5c:26:0a:7a:26:34 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT qlen 1000
    link/ether d0:df:9a:d8:2b:46 brd ff:ff:ff:ff:ff:ff
$ sudo mii-tool
[sudo] password for stephen:
SIOCGMIIPHY on 'eth1' failed: Operation not supported
no MII interfaces found

Revision history for this message
Steveire (steveire) wrote :
Download full text (5.1 KiB)

A slightly longer session:

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 5c:26:0a:7a:26:34 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT qlen 1000
    link/ether d0:df:9a:d8:2b:46 brd ff:ff:ff:ff:ff:ff
$ ip addr eth0
Command "eth0" is unknown, try "ip addr help".
$ sudo mii-tool
[sudo] password for stephen:
SIOCGMIIPHY on 'eth1' failed: Operation not supported
no MII interfaces found
$ sudo mii-tool -p eth0
SIOCGMIIPHY on 'eth1' failed: Operation not supported
no MII interfaces found
$ dmesg | grep wl
[ 4.429047] wl: module license 'MIXED/Proprietary' taints kernel.
[ 4.464325] INFO @wl_cfg80211_attach : Registered CFG80211 phy
$ dmesg | grep eth
[ 0.169331] reboot: PCI series board detected. Selecting Dell Latitude E6520-method for reboots.
[ 1.238195] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 5c:26:0a:7a:26:34
[ 1.238199] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.238256] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 4041FF-0FF
[ 4.084864] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4.550907] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.20.155.1 (r326264)
[ 5.874878] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.875343] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
$ service networking restart
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.47" (uid=1000 pid=2853 comm="stop networking ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.48" (uid=1000 pid=2850 comm="start networking ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
$ sudo service networking restart
networking stop/waiting
networking start/running
$ sudo mii-tool
SIOCGMIIREG on eth0 failed: Input/output error ...

Read more...

Revision history for this message
Steveire (steveire) wrote :
Download full text (4.6 KiB)

Here's a session after booting to the 'working' kernel which allows me to do wired networking:

$ sudo dhclient -v eth0
[sudo] password for stephen:
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/5c:26:0a:7a:26:34
Sending on LPF/eth0/5c:26:0a:7a:26:34
Sending on Socket/fallback
DHCPREQUEST of 192.168.1.3 on eth0 to 255.255.255.255 port 67 (xid=0x29a3e672)
DHCPACK of 192.168.1.3 from 192.168.1.1
RTNETLINK answers: File exists
bound to 192.168.1.3 -- renewal in 249326 seconds.

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 5c:26:0a:7a:26:34 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT qlen 1000
    link/ether d0:df:9a:d8:2b:46 brd ff:ff:ff:ff:ff:ff

$ ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 5c:26:0a:7a:26:34 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::5e26:aff:fe7a:2634/64 scope link
       valid_lft forever preferred_lft forever

$ sudo service networking restart
networking stop/waiting
networking start/running

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 5c:26:0a:7a:26:34 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether d0:df:9a:d8:2b:46 brd ff:ff:ff:ff:ff:ff
                                                  ...

Read more...

Revision history for this message
Steveire (steveire) wrote :

And the dmesg output with the working kernel:

$ dmesg | grep eth
[ 0.273146] Dell Latitude E6520 series board detected. Selecting PCI-method for reboots.
[ 0.895886] ACPI Error: Method parse/execution failed [\_SB_.EEAC] (Node ffff880232062550), AE_ALREADY_EXISTS (20120320/psparse-536)
[ 0.895894] ACPI: Marking method EEAC as Serialized because of AE_ALREADY_EXISTS error
[ 0.895897] ACPI Error: Method parse/execution failed [\_SB_.BAT2._STA] (Node ffff880232062b40), AE_ALREADY_EXISTS (20120320/psparse-536)
[ 0.895901] ACPI: Marking method _STA as Serialized because of AE_ALREADY_EXISTS error
[ 1.221517] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 5c:26:0a:7a:26:34
[ 1.221520] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 1.221581] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 4041FF-0FF
[ 5.031472] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.463465] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.20.155.1 (r326264)
[ 7.074305] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.074854] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.031251] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 12.031259] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 12.032772] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 183.536103] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready

Revision history for this message
Steveire (steveire) wrote :

I think I'm affected by https://bugzilla.kernel.org/show_bug.cgi?id=52021

https://bugzilla.kernel.org/show_bug.cgi?id=36132 indicates that it might be an effect of me having used powertop previously, which would explain why it's not an issue affecting everyone.

There seems to be a patch: https://lkml.org/lkml/2013/1/18/147

Info found via: https://bbs.archlinux.de/viewtopic.php?id=23638

Also: https://bbs.archlinux.org/viewtopic.php?id=159454 https://bbs.archlinux.org/viewtopic.php?id=134874 http://d-h-n.de/blog/siocgmiiphy-on-eth0-failed-operation-not-supported

(partly just leaving all links here for my reference)

Revision history for this message
Steveire (steveire) wrote :

I can confirm that

 echo on | sudo tee /sys/bus/pci/devices/0000\:00\:19.0/power/control

after booting my broken kernel makes wired networking work again.

Revision history for this message
Steveire (steveire) wrote :

Wireless networking still does not work, but that might just be a case of finding another entry to set to 'on'.

Revision history for this message
Steveire (steveire) wrote :

$ cat /sys/bus/pci/devices/*/power/control
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on

Still does not give me wireless networking.

Revision history for this message
Steveire (steveire) wrote :

Changing all settings from auto to on in /sys/bus/i2c/devices/*/power/control also does not give me wireless networking.

Revision history for this message
Steveire (steveire) wrote :

The problem doesn't seem to be related to power management for me, but I tried adding the file mentioned in http://uselessuseofcat.com/?p=67 but it did not help.

Revision history for this message
Steveire (steveire) wrote :

http://www.ubuntugeek.com/how-to-troubleshoot-wireless-network-connection-in-ubuntu.html looks potentially useful but I'm not sure I know how to use it. I don't seem to be able to turn off wpa on my wireless router.

Revision history for this message
Steveire (steveire) wrote :

Another link: http://ubuntuforums.org/showthread.php?t=571188

Revision history for this message
Steveire (steveire) wrote :

I tried following http://linux.icydog.net/wpa.php

It gives me a lot of output like this:

stephen@hal:~$ sudo wpa_supplicant -Dwext -ieth1 -cwirelessconf
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
eth1: Trying to associate with 1c:c6:3c:76:d8:8c (SSID='icanhearyouhavingsex' freq=2427 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
eth1: Association request to the driver failed
eth1: Associated with 1c:c6:3c:76:d8:8c
eth1: WPA: Key negotiation completed with 1c:c6:3c:76:d8:8c [PTK=CCMP GTK=CCMP]
eth1: CTRL-EVENT-CONNECTED - Connection to 1c:c6:3c:76:d8:8c completed (auth) [id=0 id_str=]
eth1: CTRL-EVENT-DISCONNECTED bssid=1c:c6:3c:76:d8:8c reason=0
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWSCAN]: Device or resource busy
eth1: Failed to initiate AP scan
ioctl[SIOCSIWSCAN]: Device or resource busy
eth1: Failed to initiate AP scan
eth1: Trying to associate with 1c:c6:3c:76:d8:8c (SSID='icanhearyouhavingsex' freq=2427 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
eth1: Association request to the driver failed
eth1: Associated with 1c:c6:3c:76:d8:8c
eth1: CTRL-EVENT-DISCONNECTED bssid=1c:c6:3c:76:d8:8c reason=0
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
eth1: Trying to associate with 1c:c6:3c:76:d8:8c (SSID='icanhearyouhavingsex' freq=2427 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
eth1: Association request to the driver failed
eth1: Associated with 1c:c6:3c:76:d8:8c
eth1: WPA: Key negotiation completed with 1c:c6:3c:76:d8:8c [PTK=CCMP GTK=CCMP]
eth1: CTRL-EVENT-CONNECTED - Connection to 1c:c6:3c:76:d8:8c completed (reauth) [id=0 id_str=]
eth1: CTRL-EVENT-DISCONNECTED bssid=1c:c6:3c:76:d8:8c reason=0
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWSCAN]: Device or resource busy
eth1: Failed to initiate AP scan
ioctl[SIOCSIWSCAN]: Device or resource busy
eth1: Failed to initiate AP scan
eth1: Trying to associate with 1c:c6:3c:76:d8:8c (SSID='icanhearyouhavingsex' freq=2427 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
eth1: Association request to the driver failed

And my dhclient still doesn't connect:

$ sudo dhclient -v eth1
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/d0:df:9a:d8:2b:46
Sending on LPF/eth1/d0:df:9a:d8:2b:46
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0x612d18d8)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4 (xid=0x612d18d8)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 (xid=0x612d18d8)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 (xid=0x612d18d8)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0x612d18d8)
^C

Revision history for this message
Steveire (steveire) wrote :

This seems to be a similar/the same problem: https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/220607

Revision history for this message
Steveire (steveire) wrote :

The bug linked at the end of that question has this workaround:

https://bugs.launchpad.net/ubuntu/+bug/1112751

sudo rmmod wl
sudo modprobe brcmsmac

I can confirm that it works for me.

I am confused though. If wl worked before, why does it not work now with the same hardware?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc4-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Steveire (steveire) wrote :

I tested the RC4. Wired networking worked.

Wireless networking still did not work, but I guess that's because those mainline kernels have no binary blobs.

Thanks,

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-fixed-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you happen to know if there is a difference whether or not you have AC connected to the system? This could be a duplicate of bug 1165248

Revision history for this message
Steveire (steveire) wrote :

Hi,

Yes, I checked that and reported in comment 12 that it does not affect the behavior for me: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1161655/comments/12

So, I don't believe it is a duplicate.

Thanks,

Revision history for this message
Manuel Hilbing (manuel-hilbing) wrote :

on my Thinkpad X230 i had the same problem... after the release update from 12.10 to 13.04
Small solution is to use the driver for the e1000e Version 2.3.2 from http://sourceforge.net/projects/e100...?source=navbar

Revision history for this message
penalvch (penalvch) wrote :

Steveire, as per http://www.dell.com/support/troubleshooting/us/en/19/Product/latitude-e6520 an update is available for your BIOS (A18). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-a18
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Wired and wireless networking don't work after upgrade
+ [Dell Latitude E6520] Wired and wireless networking don't work after
+ upgrade
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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