Ethernet will not activate when booting

Asked by brian W

My Ubuntu 6.06 boots ok but the ethernet internet connection is not automatically activated. Each time I have to go into; system.. administration.. networking.. select.. ethernet then click deactive follow by activate, this then connects the ethernet. Return to Firefox the the internet works.
This is a recent problem, previosly the ethernet connection was automatically activated at boot up.
My router is a "Belkin ADSL2 Modem with Wireless G Router" used with a direct ethernet internet connection. My motherboard is a Gigabyte nForce4SLI with an AMD Athon 3800 processor. I cannot solve the problem

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Christoph Langner
Solved:
Last query:
Last reply:
Revision history for this message
brian W (bc-woodhouse) said :
#1

I dual boot with Windows 2000 and this problem does not occur when booting into Widows, Firefox is ready right away.

Revision history for this message
Ralph Janke (txwikinger) said :
#2

Thanks for your question.

Could you please post here the contents of

/etc/network/interfaces

and the output of

sudo lshw -class network

Thanks

Revision history for this message
brian W (bc-woodhouse) said :
#3
Revision history for this message
Ralph Janke (txwikinger) said :
#4

Somehow your last message was empty. Could you paste the results in the textbox again please (I think attachments don't work here).

Thanks

Revision history for this message
brian W (bc-woodhouse) said :
#5

auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth0
also I cannot make terminal give a response to "sudo lshw -class network" many thanks brianW

Revision history for this message
Ralph Janke (txwikinger) said :
#6

I don't know if this solves the problem. However, usually the "auto eth0" line is just in front of the "iface eth0 inet dhcp" line.

Maybe you could paste the output of

ifconfig -a

just after reboot before you manually activate the connection.

Thanks, I hope this solves the problem

Revision history for this message
brian W (bc-woodhouse) said :
#7

brian W here are the outputs of ifconfig -a before and after manually setting up the internet connection

Output of ifconfig -a just after booting but before manually activating the connection to etho 0

eth0 Link encap:Ethernet HWaddr 00:14:85:3F:50:8F
          inet6 addr: fe80::214:85ff:fe3f:508f/64 Scope:Link
          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:468 (468.0 b)
          Interrupt:217 Base address:0x2000

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:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:272 (272.0 b) TX bytes:272 (272.0 b)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 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)

Output of ethconfig -a after manually setting etho 0

brian@brian-desktop:~$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:14:85:3F:50:8F
          inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::214:85ff:fe3f:508f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:342 (342.0 b) TX bytes:1278 (1.2 KiB)
          Interrupt:217 Base address:0x2000

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:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:372 (372.0 b) TX bytes:372 (372.0 b)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 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)

Revision history for this message
Best Christoph Langner (chrissss) said :
#8

This is a typical problem with ubuntu dapper and mainboards with a nforce4 chipset. Make sure you're using a -k7 kernel. I'm preety sure you're not using one.

# sudo apt-get install linux-k7

CU
Christoph

Revision history for this message
brian W (bc-woodhouse) said :
#9

Thanks Christoph Langner, that solved my question.