[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635475 Title: [Maverick] Auto eth0 not working after latest package upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635475 Title: [Maverick] Auto eth0 not working after latest package upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635475 Title: [Maverick] Auto eth0 not working after latest package upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
@Mathieu, I created a linux bug report for this issue, per your suggestion: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/677701 -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
@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. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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? m...@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 loLink 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) m...@me-laptop:~$ m...@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 m...@m-laptop:~$ wa...@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 wa...@warry-laptop:~$ -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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: :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 -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
@Mathieu, I haven't had any problems for a long time. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
@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". -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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/pci:00/:00:19.0/net/eth0, iface: eth0) NetworkManager[1101]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found. NetworkManager[1101]: (eth0): carrier is OFF NetworkManager[1101]: (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2) NetworkManager[1101]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[1101]: (eth0): now managed NetworkManager[1101]: (eth0): device state change: 1 -> 2 (reason 2) NetworkManager[1101]: (eth0): bringing up device. NetworkManager[1101]: (eth0): preparing device. NetworkManager[1101]: (eth0): deactivating device (reason: 2). NetworkManager[1101]: Added default wired connection 'Auto eth0' for /sys/devices/pci:00/: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 ** Attachment added: "syslog filtered for eth0" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/635475/+attachment/1702168/+files/syslog-eth0.txt -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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]: WiFi enabled by radio killswitch; enabled by state file Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: WWAN enabled by radio killswitch; enabled by state file Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: WiMAX enabled by radio killswitch; enabled by state file Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: Networking is enabled by state file Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): carrier is OFF Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2) Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): now managed Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): device state change: 1 -> 2 (reason 2) Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): bringing up device. Oct 17 04:44:48 Computer-1000 kernel: [ 894.570244] e1000e :00:19.0: irq 40 for MSI/MSI-X Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): preparing device. Oct 17 04:44:48 Computer-1000 NetworkManager[2046]: (eth0): deactivating device (reason: 2). -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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...) -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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). -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
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. -- [Maverick] Auto eth0 not working after latest package upgrade https://bugs.launchpad.net/bugs/635475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
