[intrepid] wired network don't work after last upgrade

Bug #273869 reported by Daniel Stoyanov on 2008-09-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

System : Intrepid up to date

After upgrade of all packages today I have no more wired network. Network-manager is reporting the available wireless networks, but no wired network connection possible.

$ sudo ifup eth0

eth0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up eth0.

I booted on 2.6.27-3 and local network works. The latest packages I have upgraded are :

binutils ( to
binutils-static ( to
firefox (3.0.2+build3+nobinonly-0ubuntu2) to 3.0.2+build6+nobinonly-0ubuntu1
firefox-3.0 (3.0.2+build3+nobinonly-0ubuntu2) to 3.0.2+build6+nobinonly-0ubuntu1
firefox-3.0-branding (3.0.2+build3+nobinonly-0ubuntu2) to 3.0.2+build6+nobinonly-0ubuntu1
firefox-3.0-gnome-support (3.0.2+build3+nobinonly-0ubuntu2) to 3.0.2+build6+nobinonly-0ubuntu1
firefox-gnome-support (3.0.2+build3+nobinonly-0ubuntu2) to 3.0.2+build6+nobinonly-0ubuntu1
gnome-icon-theme (2.23.92-0ubuntu1) to 2.24.0-0ubuntu1
gnome-mag (1:0.15.3-0ubuntu1) to 1:0.15.4-0ubuntu1
gnome-power-manager (2.23.91-0ubuntu2) to 2.24.0-0ubuntu2
gthumb (3:2.10.9-0ubuntu1) to 3:2.10.10-0ubuntu1
gthumb-data (3:2.10.9-0ubuntu1) to 3:2.10.10-0ubuntu1
landscape-client (1.0.21-0ubuntu1) to 1.0.21-0ubuntu2
landscape-common (1.0.21-0ubuntu1) to 1.0.21-0ubuntu2
libasound2 (1.0.17a-0ubuntu2) to 1.0.17a-0ubuntu3
libcanberra-gtk-module (0.6-0ubuntu1) to 0.6-0ubuntu2
libcanberra-gtk0 (0.6-0ubuntu1) to 0.6-0ubuntu2
libcanberra0 (0.6-0ubuntu1) to 0.6-0ubuntu2
libgnome-mag2 (1:0.15.3-0ubuntu1) to 1:0.15.4-0ubuntu1
libgnome-speech7 (1:0.4.21-0ubuntu2) to 1:0.4.21-0ubuntu3
libpulse-browse0 (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
libpulse0 (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
libpulsecore5 (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
libvolume-id0 (124-3) to 124-5
module-init-tools (3.3-pre11-4ubuntu9) to 3.3-pre11-4ubuntu11
pulseaudio (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
pulseaudio-esound-compat (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
pulseaudio-module-gconf (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
pulseaudio-module-hal (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
pulseaudio-module-x11 (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
pulseaudio-utils (0.9.10-2ubuntu4) to 0.9.10-2ubuntu6
pxljr (1.1-0ubuntu2) to 1.1-0ubuntu3
python-pyorbit (2.14.3-2ubuntu1) to 2.24.0-0ubuntu1
startup-tasks (0.3.9-6) to 0.3.9-7
system-services (0.3.9-6) to 0.3.9-7
tomboy (0.11.3-0ubuntu1) to 0.12.0-0ubuntu1
ubufox (0.6~b1-0ubuntu2) to 0.6~b1-0ubuntu3
udev (124-3) to 124-5
upstart (0.3.9-6) to 0.3.9-7
upstart-compat-sysv (0.3.9-6) to 0.3.9-7
upstart-logd (0.3.9-6) to 0.3.9-7
xulrunner-1.9 ( to
xulrunner-1.9-gnome-support ( to

linux-headers-2.6.27-4 (2.6.27-4.5) to 2.6.27-4.6
linux-headers-2.6.27-4-generic (2.6.27-4.5) to 2.6.27-4.6
linux-image-2.6.27-4-generic (2.6.27-4.5) to 2.6.27-4.6
linux-libc-dev (2.6.27-4.5) to 2.6.27-4.6

On 2.6.27-3 kernel, when network works :
$ dmesg | grep eth0

[ 2.550565] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1e:37:8a:91:08
[ 2.550567] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 2.550601] 0000:00:19.0: eth0: MAC: 6, PHY: 6, PBA No: 1008ff-0ff
[ 14.241118] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 35.964988] 0000:00:19.0: eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[ 35.964991] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 35.965213] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 46.880075] eth0: no IPv6 routers present

If you need more info , don't hesitate to ask.

pnr (rusyaev-gmail) wrote :

I can confirm the same issue with wired network on Dell Inspiron 530 after upgrade to 2.6.27-4. On 2.6.27-3 the wired network connection functions properly.

E1000e driver is now in the blacklist since it has potential risk to

h1l4nd0r (chupan) wrote :

I confirm the same behaviour on Vaio Z11mrn\B

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

Other bug subscribers