LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 08-07-2009, 12:07 PM   #1
flamingsole
LQ Newbie
 
Registered: Jul 2007
Location: Atlanta, GA, US
Distribution: Ubuntu
Posts: 14

Rep: Reputation: 0
Ubuntu Ethernet often does not connect on boot


Hello,

I have a box that predominantly runs Ubuntu 9.04, though it does have Windows around as well (I've happily gotten to the point where I rarely load Windows). It has an integrated Ethernet card (a nvidia) on the motherboard (was eth0 though it is no longer enabled), as well as a separate one, an Intel(R) PRO/100 M Desktop Adapter, (eth1).

The integrated one no longer works at all, as the system was struck by lightning a few years ago. In Windows, for the sake of comparison, it is disabled so that the separate one (the Intel) is the only one ever detected. I have also tried disabling it in the BIOS, and this seemed to work well.

However, in Ubuntu, I'd say 40-50% of the time, when I boot the system it says the eth1 card is disconnected. If I restart, it usually connects properly, though sometimes it takes two restarts.

My original thought was that Ubuntu must be detecting the card that no longer works, but this does not seem to be the case.

When it is not working, it still detects the right card, but I cannot seem to do anything to get it to connect, aside from rebooting.

What kind of things can I do to figure out what the issue might be, and how to fix it?

Thanks for any help,
Jon
 
Old 08-07-2009, 12:50 PM   #2
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,151

Rep: Reputation: 331Reputation: 331Reputation: 331Reputation: 331
What happens when you try sudo ifup eth1 after it fails to connect during the boot?

What is the output of dmesg | grep -i eth after a connection failure during boot?
 
Old 08-07-2009, 01:29 PM   #3
flamingsole
LQ Newbie
 
Registered: Jul 2007
Location: Atlanta, GA, US
Distribution: Ubuntu
Posts: 14

Original Poster
Rep: Reputation: 0
Thanks for your help on this. To answer the questions:

Quote:
What happens when you try sudo ifup eth1 after it fails to connect during the boot?
Code:
Ignoring unknown interface eth1=eth1
Quote:
What is the output of dmesg | grep -i eth after a connection failure during boot?
Code:
[   1.069442] Driver 'sd' needs updating - please use bus_type methods
[   1.069449] Driver 'sr' needs updating - please use bus_type methods
[   3.198770] e100: eth0: e100_probe: addr 0x7021000, irq 10, MAC addr ------ (mac address of card)
[   10.775235] udev: renamed network interface eth0 to eth1
[   24.600082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.040329] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   32.044230] e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
[   32.062551] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   42.668024] eth1: no IPV6 routers present
Thanks again,
Jon
 
Old 08-07-2009, 02:01 PM   #4
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
This probably relates to the latest udev persistent rules which has been sneaked in and is, in my opinion, a pain in the rear end.

Take a look at /etc/udev/rules.d/70-persistent-net.rules and see if the card is being listed there.

I have been having similar problems with a server continually not bringing up a connection because of this. I found that when this happens using ifconfig -a will show all the devices available and invariably it has changed the eth numbering. This means either editing the rule file or editing the /etc/network/interfaces file.
 
Old 08-07-2009, 02:10 PM   #5
flamingsole
LQ Newbie
 
Registered: Jul 2007
Location: Atlanta, GA, US
Distribution: Ubuntu
Posts: 14

Original Poster
Rep: Reputation: 0
Thanks for looking into this.
Quote:
Take a look at /etc/udev/rules.d/70-persistent-net.rules and see if the card is being listed there.
When I do this, both the eth0 card that doesn't work, and eth1 that does work, are listed. I tried commenting out eth0, to see if that makes a difference. Does that seem like it might be helpful?
 
Old 08-07-2009, 02:19 PM   #6
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
Try that but the system may just create a new entry (which I am seeing i.e. multiple entries for the same device). When it happens check what is going on with ifconfig -a.
 
Old 08-07-2009, 02:34 PM   #7
flamingsole
LQ Newbie
 
Registered: Jul 2007
Location: Atlanta, GA, US
Distribution: Ubuntu
Posts: 14

Original Poster
Rep: Reputation: 0
Right. The commenting out didn't do anything.

ifconfig -a results:
Code:
eth1      Link encap:Ethernet HWaddr 00:0e:0c:66:64:04
          inet6 addr: fe80::20e:cff:fe66:6404/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:5 dropped:0 overruns:0 frame:5
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:2178 (2.1 KB)

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:80 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4804 (4.8 KB)  TX bytes:4804 (4.8 KB)

pan0      Link encap:Ethernet HWaddr 4e:b4:2a:39:c4:d5
          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:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0) B
Thanks for your help
Jon
 
Old 08-07-2009, 03:26 PM   #8
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
There may be a possible solution based on the theory of how this is supposed to work;

udev is supposed to identify the card by the mac code. Now you can edit the identity by changing the name of the device in the 70-persistent-net.rules by for example changing NAME = "broken_nvidia".

I would also suggest trying to fool the system by adding a dummy entry in your interfaces file on a different subnet address like;
auto broken_nvidia
iface broken_nvidia inet static
address 10.0.010
netmask 255.0.0.0

So in theory if the system does locate this card it knows its name and can relate a network entry for it and therefore not interfere with the other device. Since it is a dummy connection it doesn't matter whether the device works or not.
 
Old 08-07-2009, 03:47 PM   #9
flamingsole
LQ Newbie
 
Registered: Jul 2007
Location: Atlanta, GA, US
Distribution: Ubuntu
Posts: 14

Original Poster
Rep: Reputation: 0
That seems to have had an effect, at least. Now, when it seems like it would ordinarily be a use case where there is no connection, the system indicates that it is connected, but it can't connect to anything.

In case it is relevant, some of the output for the commands I ran initially is different:

sudo ifup eth1:
Code:
ifup: interface eth1 already configured
dmesg | grep -i eth:
Code:
[   1.069444] Driver 'sd' needs updating - please use bus_type methods
[   1.069451] Driver 'sr' needs updating - please use bus_type methods
[   3.183340] e100: eth0: e100_probe: addr 0xe7021000, irq 10, MAC addr 00:0e:0c:66:64:04
[   10.447693] udev: renamed network interface eth0 to eth1
[   24.632979] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.032536] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   32.036228] e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
[   32.046512] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   42.512017] eth1: no IPv6 routers present
[   53.816312] e100: eth1: e100_watchdog: link down
[   55.816227] e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
[   59.816306] e100: eth1: e100_watchdog: link down
[   61.816221] e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
Thanks for all this help.
 
  


Reply

Tags
ethernet, intel, networking


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
want ubuntu 8.10 to connect to network on BOOT, but still have Network Manager work monkeyman2000 Ubuntu 0 02-13-2009 03:22 PM
how do i connect my blue tooth headset to Ubuntu, it is unable to connect. salfuser Linux - Hardware 2 01-12-2009 10:28 AM
Cannot connect through ethernet after restart abhinandan Linux - Wireless Networking 2 05-02-2008 10:09 AM
connect 2 PCs via ethernet kpachopoulos Linux - Networking 3 05-05-2006 07:10 AM
How to connect with an ethernet card? nawaz Linux - Networking 1 06-04-2002 05:05 AM


All times are GMT -5. The time now is 04:03 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration