[Maverick] Auto eth0 not working after latest package upgrade

Bug #635475 reported by Petar Velkovski
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: network-manager

Description: Ubuntu maverick (development branch)
Release: 10.10

Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Version table:
 *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

After making upgrade to the following packages the auto eth0 is not working:

apparmor (2.5.1~pre1393-0ubuntu6) to 2.5.1~rc1-0ubuntu1
apparmor-utils (2.5.1~pre1393-0ubuntu6) to 2.5.1~rc1-0ubuntu1
apt (0.8.3ubuntu2) to 0.8.3ubuntu3
apt-transport-https (0.8.3ubuntu2) to 0.8.3ubuntu3
apt-utils (0.8.3ubuntu2) to 0.8.3ubuntu3
cups (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
cups-bsd (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
cups-client (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
cups-common (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
foomatic-db-compressed-ppds (20100906-0ubuntu1) to 20100910-0ubuntu1
grub-common (1.98+20100804-4ubuntu5) to 1.98+20100804-4ubuntu6
grub-pc (1.98+20100804-4ubuntu5) to 1.98+20100804-4ubuntu6
gstreamer0.10-alsa (0.10.30-1build1) to 0.10.30-2
gstreamer0.10-gnonlin (0.10.15-1) to 0.10.16-1
gstreamer0.10-plugins-base (0.10.30-1build1) to 0.10.30-2
gstreamer0.10-plugins-base-apps (0.10.30-1build1) to 0.10.30-2
gstreamer0.10-plugins-good (0.10.25-1ubuntu1) to 0.10.25-2ubuntu1
gstreamer0.10-pulseaudio (0.10.25-1ubuntu1) to 0.10.25-2ubuntu1
gstreamer0.10-x (0.10.30-1build1) to 0.10.30-2
gvfs (1.6.3-0ubuntu1) to 1.6.3-0ubuntu2
gvfs-backends (1.6.3-0ubuntu1) to 1.6.3-0ubuntu2
gvfs-fuse (1.6.3-0ubuntu1) to 1.6.3-0ubuntu2
humanity-icon-theme (0.5.3) to 0.5.3.1
indicator-sound (0.4.3-0ubuntu1) to 0.4.4-0ubuntu1
libapparmor-perl (2.5.1~pre1393-0ubuntu6) to 2.5.1~rc1-0ubuntu1
libapparmor1 (2.5.1~pre1393-0ubuntu6) to 2.5.1~rc1-0ubuntu1
libc-bin (2.12.1-0ubuntu4) to 2.12.1-0ubuntu6
libc-dev-bin (2.12.1-0ubuntu4) to 2.12.1-0ubuntu6
libc6 (2.12.1-0ubuntu4) to 2.12.1-0ubuntu6
libc6-dev (2.12.1-0ubuntu4) to 2.12.1-0ubuntu6
libcups2 (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
libcupscgi1 (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
libcupsdriver1 (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
libcupsimage2 (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
libcupsmime1 (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
libcupsppdc1 (1.4.4-3ubuntu1) to 1.4.4-3ubuntu2
libdconf0 (0.5-1ubuntu4) to 0.5-1ubuntu5
libgssdp-1.0-2 (0.7.2-2) to 0.7.2-2build1
libgstreamer-plugins-base0.10-0 (0.10.30-1build1) to 0.10.30-2
libgvfscommon0 (1.6.3-0ubuntu1) to 1.6.3-0ubuntu2
openprinting-ppds (20100906-0ubuntu1) to 20100910-0ubuntu1
python-gst0.10 (0.10.19-1) to 0.10.19-2
software-center (2.1.18) to 2.1.18.1
ubuntu-mono (0.0.20) to 0.0.21

My computer is connected on an internet ADSL router and after starting the computer and longing into Ubuntu automaticaly obtains an ip adress given by the router's DHCP server. After upgrading the packages mentioned above and restarting my computer, this doesn't happen any more. Network manager tries to get an IP adress and then it reports that there is no network connection.

ifconfig output:

ifconfig
eth0 Link encap:Ethernet HWaddr 00:27:0e:1c:f4:ab
          inet6 addr: fe80::227:eff:fe1c:f4ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2223 (2.2 KB) TX bytes:1026 (1.0 KB)
          Interrupt:43 Base address:0x4000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2221 (2.2 KB) TX bytes:2221 (2.2 KB)

But after doing this

petar@aurora:~$ sudo dhclient
[sudo] password for petar:
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:27:0e:1c:f4:ab
Sending on LPF/eth0/00:27:0e:1c:f4:ab
Sending on Socket/fallback
DHCPREQUEST of 192.168.1.66 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.66 from 192.168.1.254
bound to 192.168.1.66 -- renewal in 36959 seconds.

I get a connection!.

ifconfig
eth0 Link encap:Ethernet HWaddr 00:27:0e:1c:f4:ab
          inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::227:eff:fe1c:f4ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:810 errors:0 dropped:0 overruns:0 frame:0
          TX packets:857 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:265765 (265.7 KB) TX bytes:445093 (445.0 KB)
          Interrupt:43 Base address:0x4000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2221 (2.2 KB) TX bytes:2221 (2.2 KB)

Network Manager still reports an icon that says that there is no network connection but I have internet (and I'm able to send this bug report)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Sat Sep 11 05:25:31 2010
Gconf:

InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100831.2)
IpRoute:
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.66
 default via 192.168.1.254 dev eth0
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager

Revision history for this message
Petar Velkovski (pvelkovski) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Please see if you remove the line "no-auto-default=00:27:0e:1c:f4:ab," from /etc/NetworkManager/nm-system-settings.conf if the situation improves.

If you use NetworkManager only to manage your network connections, you should also be able to safely remove all entries for eth0 from /etc/network/interfaces:
# The primary network interface
auto eth0
#iface eth0 inet dhcp

Thanks!

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Petar Velkovski (pvelkovski) wrote :

The solution I found 2 days ago was to comment out "auto eth0" in /etc/network/interfaces:

Old /etc/network/interfaces was:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

The new /etc/network/interfaces is:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#auto eth0
#iface eth0 inet dhcp

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

I like your fix better because it allows me to connect using a DSL connection created in NetworkManager and also to connect using "Auto eth0". SO both solutions work buy your is much better!

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Should this be marked as fixed then?

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

Mathieu it is fixed for me, but the problem is that there is something that is causing it. This happened to me again yesterday. Although I know how to fix it manually I am still puzzled about the specific cause of it. It seams that after certain packages are upgraded on my system, some of their post-installation scripts are causing this problem to reappear. So I guess it's up to you. If you close this bug and I manage to find some more specific information about it, I guess I'll reopen it.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Factoring out NM completely, do you use the same system to dual boot with Windows Vista or 7? Also, when NM fails to connect and you would need to start dhclient manually, can you instead try the command 'ethtool -s eth0 autoneg off' (you will first need to install the 'ethtool' package)?

In light of reviewing syslog again, let's keep this bug open. It might be a duplicate of something else I've seen too.

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

No, I don't use Windows or any other OS other than Ubuntu. So we can rule that out too. Maverick beta was also cleanly installed, it wasn't an upgrade from Lucid, so some leftover configurations from previous system can be ruled out too.

I installed "ethtool" and wrote down the command in case this happens again.

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

This happened to me again. I got disconnected, and the list of configured connections disappeared from Network Manager. I ran the command you provided and they reappeared again (auto eth0 and T-home in my case) so I could click on one of them and connect again.

Still I have no idea what is causing this, but I know that this is not happening only to me.
I found this on Ubuntu Stackexchange website. http://ubuntu.stackexchange.com/questions/4014/
If you visit the link, you'll see that a user named "msw" encountered the same problem. Too bad there is no link that would help me contact him.

summary: - Auto eth0 not working after latest package upgrade
+ [Maverick] Auto eth0 not working after latest package upgrade
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Petar,

I'm sorry to have you confirm that again, but I wasn't exactly sure following your last comment. Running 'ethtool -s eth0 autoneg off' fixed your issue, correct? Are both 'Auto eth0' and 'T-home' ethernet connections?

It's an important piece of information, because if it works, this issue is more likely a kernel driver one.

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

Yes eth0 and T-Home are both ethernet connections. The difference is that my T-Home connection is set with my providers username and password and when I use it, my computer gets a public IP internet address (it's like using the router in modem mode).

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

This bug is affecting me as well on a fresh install of Ubuntu 10.10 x64.

I find that I can get eth0 to connect by using two terminal windows.

In the first terminal window I type:
    $ sudo dhclient
While this command is executing, in the second terminal window, I type:
    $ sudo service network-manager restart

This causes the dhclient command to print out "receive_packet failed on eth0: Network is down" in between the lines of "DHCPDISCOVER...", but eth0 becomes active.

(I am going to try Mathieu Trudel's suggestion and see if the issue goes away after reboot...)

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

Mathieu Trudel's suggestion did not work for me after coenting-out "no-auto-default=00:01:80:76:71:ca," from /etc/NetworkManager/nm-system-settings.conf and restarting.

Also, my /etc/network/interfaces only has the following lines. There is no reference to eth0, so, whti reference to Petar Velkovski's suggestion. there was nothing for me to comment out:

Here is my /etc/network/interfaces file...
    auto lo
    iface lo inet loopback

Even dhclient & network-manager restart "approach" is trial and error.

In my syslog, I see "bluez error getting default adapter: The name org.bluez was not provided by any .service files." I do not know if it related to this issue or is a separate problem.

Here is a portion of my syslog file that shows eth0 is brought up, and then it goes down (with reason 2 ???)...

Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: Ifupdown: get unmanaged devices count: 0
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: SCPlugin-Ifupdown: (33466944) ... get_connections.
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: SCPlugin-Ifupdown: (33466944) ... get_connections (managed=false): return empty list.
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: Ifupdown: get unmanaged devices count: 0
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> WiFi enabled by radio killswitch; enabled by state file
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> WWAN enabled by radio killswitch; enabled by state file
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> WiMAX enabled by radio killswitch; enabled by state file
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> Networking is enabled by state file
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): carrier is OFF
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): now managed
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): bringing up device.
Oct 17 04:44:48 Computer-1000 kernel: [ 894.570244] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): preparing device.
Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: <info> (eth0): deactivating device (reason: 2).

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

I installed Ubuntu on a second, similar, machine, and I am experiencing this bug on the second machine as well.

The two machines are:
1. AOpen MP965 (with x64 Intel CPU)
    Intel GM965 + ICH8M Chipset

2. AOpen MP945 (with x64 Intel CPU)
    Intel 945GM + ICH7-DH Chipset

Each machine has an onboard ethernet NIC built into it.

Each has computer has a fresh install of Ubuntu 10.10 Maverick Meerkat x64.

I experience this issue randomly on each machine, and have to try my luck by rebooting to see if eth0 comes up.

I have filtered syslog by "eth0" and attached it to this report.

Some lines of syslog that I think are relevant are...

 NetworkManager[1101]: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0)
 NetworkManager[1101]: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found.
 NetworkManager[1101]: <info> (eth0): carrier is OFF
 NetworkManager[1101]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
 NetworkManager[1101]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
 NetworkManager[1101]: <info> (eth0): now managed
 NetworkManager[1101]: <info> (eth0): device state change: 1 -> 2 (reason 2)
 NetworkManager[1101]: <info> (eth0): bringing up device.
 NetworkManager[1101]: <info> (eth0): preparing device.
 NetworkManager[1101]: <info> (eth0): deactivating device (reason: 2).
 NetworkManager[1101]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:19.0/net/eth0
 kernel: [ 13.171904] ADDRCONF(NETDEV_UP): eth0: link is not ready

Does anyone know what "carrier is OFF" means? (This is a desktop computer, so there is no on/off switch, as on laptop computers with wireless cards).

Also, it seems to be deactivating eth0 with "reason 2." What does "reason 2" mean?

The contents of /etc/network/interfaces is...
auto lo
iface lo inet loopback

The contents of /etc/NetworkManager/nm-system-settings.conf is...
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

I tried...

$ sudo ethtool -s eth0 autoneg off

...but it gives the error...

Cannot set new settings: Invalid argument
  not setting autoneg

Then I tried...

sudo ethtool -s eth0 speed 1000 duplex full autoneg off

...but this did not help either.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

@Petar, are you still seeing the issue?

@PJSing5000, are these computers connected to the same switch? The issue as you're describing it, it sounds like that's an issue with the network device the ethernet cable connects to, something like spanning tree waiting to bring the interface up on the other side (trying to figure out whether it's a computer or a switch). To be sure, try to plug them in to a different device at home, for example. You may want to contact your system administrator if you're in an office, and suggest turning on "spanning-tree portfast".

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

@Mathieu, I haven't had any problems for a long time.

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

I still have this issue.

I have four computers A, B, C, D that are wired through an 8 port switch to a Wireless/Wired Router/Gateway.
Computers A & B are both AOpen "XC Mini" PCs. They are different models, and were purchased at different times. These are the computers that have the issue:

    Computer A: AOpen MP945 "XC Mini" with Intel 945GM + ICH7-DH Chipset
    Computer B: AOpen MP965 "XC Mini" with Intel GM965 + ICH8M Chipset

Computers C and D, which are wired through the same 8 port switch, do not have a problem. I also have wireless computers & devices that connect wirelessly to the same Wireless/Wired Router/Gateway without issue. A television and another computer (E) also are also wired directly to the same Wireless/Wired Router/Gateway without issue.

    A, B, C, D ------> 8 Port Switch ---------------> Wireless/Wired Router/Gateway
    Wireless Computers & Devices ---------->
    E ----------------------------------------->
    TV ------------------------------------>

I do not think that this is a hardware failure problem on *both* the AOpen machines (A & B), since they were purchased over a year apart. For the on-board NIC to fail on both machines at the same time would be unlikely.

Additionally, these machines both connected flawlessly before I installed Ubuntu 10.10 x64. I previously had Kubuntu 10.04 x64 on both machines. Ubuntu 10.10 x64 is a fresh install on these machines. The live CD exhibits the same connectivity problem excessively, but I subjectively feel that the issue becomes somewhat reduced after I upgrade to the latest kernel 2.6.35-22, after installing Maverick 10.10.

To remedy the problem, I have to restart the machine, until I get an active ethernet connection. (With the Live CD, I have to repeatedly reboot from the Live CD).

On the back of the computer, I see that the ethernet adapter light comes on when I turn the machine on. Often, during the boot splash-screen, the ethernet adapter light turns off. If this happens, I know that the computer was unable to connect, so I must reboot. (The ethernet adapter light will not come on again, even if I do log into Ubuntu). If the ethernet adapter light is still on by the time the login screen is displayed, I then know the computer has connected successfully, so I can go ahead and login.

(If this were a switch problem, wouldn't the ethernet light on the back of the computer stay on?)

As I mentioned, the other computers on my home network, using the same switch and gateway, have no problem connecting. The switch and gateway work fine for the other machines on my network. Also these AOpen machines did not have this problem with Kubuntu 10.04, so I do not think this is a hardware failure. I believe something is different in release 10.10 or perhaps the newer Linux kernel that is not compatible with the Intel ICH* Chipsets in these machines and is causing this problem.

I do not know how to enable "spanning-tree portfast" but I will research this and see if I can do it. I will also try to pull out the 8 port switch and connect one of these AOpen machines directly to the gateway, as you suggested; I will report my results here.

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

Update: I bypassed my switch and connected directly to my Gateway. I experienced the same problem. I had to reboot multiple times until I got a connection. So I do not think this is a switch problem.

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

This looks very much like the problem described here: https://bbs.archlinux.org/viewtopic.php?pid=536382
Ubuntu may be thinking that the "killswitch" is activated, and simply disabling my network card hardware.

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

I believe I was able to resolve this issue by installing the latest drivers for my network adapter.

The older driver was...
 driver: e1000e
 version: 1.0.2-k4
 firmware-version: 0.3-0

The newer (working) driver is...
 driver: e1000e
 version: 1.2.17-NAPI
 firmware-version: 0.3-0
 bus-info: 0000:00:19.0

For anyone else having this issue, here are the steps I used.
(These instructions are included in a README file with the downloaded driver).

$ sudo apt-get install ethtool

# To find the name of the network adapter...
$ lspci -v | grep Ethernet -A 1
$ ethtool -i eth0
# You can also reference http://www.intel.com/support/network/sb/cs-008441.htm

# Navigate to http://sourceforge.net/projects/e1000
# Click on the "View all files" button.
# Download the latest driver matching the output of ethtool -i eth0
# In my case this was e1000e stable | 1.2.17

$ cd [DOWNLOAD LOCATION]
$ tar xvfz e1000e-1.2.17.tar.gz
$ cd ./e1000e-1.2.17/src

$ sudo modprobe -r e1000e
# Note: rmmod e1000e is equivalent to modprobe -r e1000e
$ sudo rm /lib/modules/`uname -r`/kernel/drivers/net/e1000e/e1000e.ko
$ sudo make install
$ sudo insmod /lib/modules/`uname -r`/kernel/drivers/net/e1000e/e1000e.ko
$ sudo dpkg-reconfigure linux-image-`uname -r`

# Reboot

Revision history for this message
warry (hawari86) wrote :

i have the same problem..
after upgrading,,
my wireless card cannot detect the wifi.
but its work fine with broadband...
i use 07:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
its seem like my wifi driver/firmware is missing...
what the problem actually?

me@me-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:d3:f1:50:ab
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:516 errors:0 dropped:0 overruns:0 frame:0
          TX packets:516 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:39608 (39.6 KB) TX bytes:39608 (39.6 KB)

ppp0 Link encap:Point-to-Point Protocol
          inet addr:10.177.103.226 P-t-P:10.64.64.64 Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
          RX packets:4744 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5011 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:2638282 (2.6 MB) TX bytes:909560 (909.5 KB)

vboxnet0 Link encap:Ethernet HWaddr 0a:00:27:00:00:00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:2052 (2.0 KB)

me@me-laptop:~$

--------------------------------------------------------------------------------------------

me@me-laptop:~$ sudo modprobe -r iwlagn; modprobe iwlagn
WARNING: Error inserting mac80211 (/lib/modules/2.6.35-22-generic-pae/kernel/net/mac80211/mac80211.ko): Operation not permitted
WARNING: Error inserting iwlcore (/lib/modules/2.6.35-22-generic-pae/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko): Operation not permitted
FATAL: Error inserting iwlagn (/lib/modules/2.6.35-22-generic-pae/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko): Operation not permitteed
me@m-laptop:~$

--------------------------------------------------------------------------------------------

warry@warry-laptop:~$ modprobe -r iwlagn; modprobe iwlagn
FATAL: Error removing iwlagn (/lib/modules/2.6.35-22-generic-pae/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko): Operation not permitted
warry@warry-laptop:~$

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

@warry, it's not the same issue, since we're trying to debug wired connections, not wireless connections. Looking at the stuff you copied there, it looks like you would want to run 'sudo modprobe iwlagn'. Operation not permitted means you need to run it as root :)

Please, go ahead and open a new bug against 'linux' for this issue if you believe your card is missing firmware or not being recognized, then we can work on debugging the issues. You can easily use the 'ubuntu-bug linux' command to achieve this.

@PJSingh5000, please also open a separate bug since if you upgraded the firmware version and it fixed it, it's definitely a kernel driver issue with driver e1000e. Since it's not the same driver as the original reporter's, it would be best if you could have a bug report just for your type of system to let kernel developers know about this. Again, the easy way to achieve this is to use the 'ubuntu-bug linux' command.

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

@Mathieu,

I created a linux bug report for this issue, per your suggestion:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/677701

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
gslack (gslack) wrote :

I am a relative noob to linux in general, admittedly most of my knowledge or experience in linux is a hodgepodge of miscellaneous things to fix what I have broken usually. Because of this I have found this same or similar problems on virtually every Debian/Ubuntu et al., board or forum I have seen. Seems its a really big issue that isn't just one port of the latest Debs. I had the same issue with the latest puppy linux from the live cd, and with all the tools and different utilities in it I got the same problem. I also read of a similar problem using Fedora, and Mandriva so perhaps its a source problem.

In my case, I had the idea to try the latest Debian stable "squeeze" and first had issues with it not writing grub2 at the install finish, then tried to go back to ubuntu only to have it take several tries to even install correctly. Ever since I have had various issues from faulty installations to undetected hardware and of course the networking card not connecting.

To be honest at this point I am ready to wipe this drive and go with either a Gentoo or in the very least a non-Deb distro. I don't know but maybe its not even an actual linux issue at all. Microsoft comes out with a new OS and suddenly the most popular distros have a rash of issues ranging from serious to bothersome, and to this point no real fixes for the lions share of them. Very odd I had no problems with any Ubuntu/Deb distro beyond the random xorg/ATI issue, until I replaced windows xp (kept on a separate disk for the kids and wife) with windows 7. I'm smelling a MS rat but then thats me, I don't trust them at all.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Marking Fix Released because the original reporter reported not seeing this issue anymore.

I'll address the other issues that stemed from this bug report in their individual bug numbers...

Changed in network-manager (Ubuntu):
status: Expired → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers