DHCP/Network Works From LiveCD, Not From HDD Install

Bug #47026 reported by gavin
10
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned

Bug Description

When I run the Live CD I can connect to the internet just fine. However once I install Ubuntu to my hard drive and reboot. I can not connect to the internet. This caused by incorrectly detecting and handling my DHCP from my Linksys router. It appears to relate to incorrect choosing of the ethernet drivers. I use the onboard ethernet from my motherboard. It is a Gigabyte GA-K8U motherboard. This problem is present on 6.06 LTS Ubuntu.

Revision history for this message
gavin (brian-gr-2001) wrote :

My version in 6.06 Release Canidate.

Revision history for this message
Tim Butler (timbutler) wrote :

Could you provide the output of the dhcpclient by running "sudo dhclient". This should show if there are any problems within the dhcp side of things.

Revision history for this message
gavin (brian-gr-2001) wrote :

I am not a linux expert but here is what I am seeing...

If I reboot my computer, the internet will not connect.
If type 'sudo dhclient', then the internet starts to work. The problem returns again when I reboot the computer. Is the startup script supposed to run dhclient? I have not installed any extra software besides what happend during the hard drive install, and I have now run the Update Manager.

Here is what I see with "sudo dhclient"
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:0f:ea:42:62:31
Sending on LPF/eth0/00:0f:ea:42:62:31
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPNAK from 192.168.57.254
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPNAK from 192.168.57.254
DHCPACK from 192.168.1.1
bound to 192.168.1.100 -- renewal in 42743 seconds.

Revision history for this message
gavin (brian-gr-2001) wrote :

After testing it some more I am going change my statement a little. The "Live CD" still has worked every time I have tried.(10 times) Unfortunately "sudo dhclient" does not always fix the problem.
Here is the output from a failed attempt.

Listening on LPF/eth0/00:0f:ea:42:62:31
Sending on LPF/eth0/00:0f:ea:42:62:31
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.57.254
SIOCADDRT: Network is unreachable
bound to 192.168.57.134 -- renewal in 696 seconds.

Revision history for this message
TimJ (t-r-jordan) wrote :

Just to add info, this problem is occurring for other users. See http://www.ubuntuforums.org/showthread.php?t=182618&page=3

Revision history for this message
smallphox (launchpad-foxwell) wrote :

I have the exact same problem. Started running Dapper LiveCD today, network worked fine out of the box. Did the install, network is dead.

The "Sudo dhclient" thing doesn't seem to be working for me.

Also (if not slightly unrelated), my Logitech MX900 BT mouse worked from LiveCD when I did "sudo hidd --search" and pressed the connect button on my mouse. Every time. Now it's dead. Related? Probably not. Still a problem, though.

There are two threads about this (DHCP problem) that I've seen now, the one mentioned above, and this one: http://www.ubuntuforums.org/showthread.php?t=184152

Hope this gets fixed soon, was looking forward to my first linux machine and now I'm all sobbing in the corner and stuff... *sniffle*

Revision history for this message
gavin (brian-gr-2001) wrote :

I have installed the offical release of ubuntu 6.06, and the DHCP works!!!! I consider this bug to be fixed for me.

The problem was related to the ethernet drivers. When I installed the 'nvidia-glx' drivers the DNS and DHCP started to work for the release candiate. I have a Gigabyte GA-K8U motherboard.

Note: for offical release. I did not have to install the nvidia drivers. It work on both the 'Live CD' and when installed to the hard drive.

Revision history for this message
gavin (brian-gr-2001) wrote :

Ugh I was wrong. The bug is still there present. It is back again same as before.

Revision history for this message
smallphox (launchpad-foxwell) wrote :

I have the exact same problem. Started running Dapper LiveCD today, network worked fine out of the box. Did the install, network is dead.

The "Sudo dhclient" thing doesn't seem to be working for me.

Also (if not slightly unrelated), my Logitech MX900 BT mouse worked from LiveCD when I did "sudo hidd --search" and pressed the connect button on my mouse. Every time. Now it's dead. Related? Probably not. Still a problem, though.

There are two threads about this (DHCP problem) that I've seen now, the one mentioned above, and this one: http://www.ubuntuforums.org/showthread.php?t=184152

Hope this gets fixed soon, was looking forward to my first linux machine and now I'm all sobbing in the corner and stuff... *sniffle*

Revision history for this message
Fabio (fabiomb) wrote :

same problem

possible issue with tulip driver, see if it's working with: lsmod

20-30 seconds of connection, and then lost it.

The Live CD Works fine, excelent, no problems, a complete hour, installing, downloading language packs, but when i started from the hard disk, the network sucks.

i think there are differences between the LiveCD Kernel and the installed Kernel, the problem is only in Dapper, (RC and final release), not Breezy or Windows or Debian.

i reported this bug on forums, no answers, before this release, probably there's a fix updating the kernel, but... to get the network running i must to unplug the network cable!!!
http://www.ubuntuforums.org/showthread.php?t=182618&page=3

if i unplug the cable, the network it's working again, that's terrible! what it means?

More info:

1.- it's a driver problem? tulip driver it's in my kernel (lsmod)
2.- do not happens on older versions of Ubuntu/Kubuntu
3.- the network adapter sends packets 20-30 seconds, then it receives packets but do not send any more.
4.- if i unplug the network cable, the network is up again WTF?

Revision history for this message
smallphox (launchpad-foxwell) wrote :

I just tried booting from my liveCD again, network works like a charm. I formatted the drive I had previously installed Dapper on, and did a re-install. Reboot without LiveCD, network is dead. I've tried [sudo dhclient], doesn't work. Unplugging and reconnecting network cable doesn't work. Tried restarting the network manually [sudo /etc/init.d/networking restart], doesn't work.

Also, when I was running from LiveCD, I mounted my logitech MX900 BT mouse by: sudo hidd --search, and then pressing the connect button, which makes it work just fine. When I rebooted to the newly installed version of Dapper, I noticed this: the few seconds the mouse was on the screen before the login dialog shows up, *the mouse was working fine*. Then the login dialog shows up, mouse stops working, and it is impossible to mount it, either using the above mentioned method or using --connect xx:xx:xx:xx:xx:xx with the mouse's BT address. Nothing works. I'll go make a different bug report about this, just wanted to mention it because it seems to be a different symptom of the same problem: Some stuff works from LiveCD but not from install.

There are obviously some differences between the kernel that gets installed and the one running from LiveCD. Are there really not any more of us having this problem? It's really frustrating not being able to start playing with Dapper because of dead mouse and network...

Revision history for this message
smallphox (launchpad-foxwell) wrote :

Should we maybe change the bug title?

"DHCP/Network Works From LiveCD, Not From HDD Install" or something to that effect seems a better description to me than "DHCP for router being detected incorrectly". A more descriptive title would make it easier for others with the same problem to find the bug listing...

Revision history for this message
smallphox (launchpad-foxwell) wrote :

News from the forums: found a fix that works for me!

From this post: http://www.ubuntuforums.org/showthread.php?t=186430

Seems the problem may have been DMFE and TULIP both loaded which caused problems. Here's the workaround h3h timo posted in the forums:

[sudo gedit /etc/modules] opens file in editor, add [dmfe] in a new line (without the brackets). Save, exit. Then,

[sudo gedit /etc/modprobe.d/blacklist] opens file in editor, add [blacklist tulip] in a new line (no brackets). Save, exit, reboot. Voilà! =D

Hope this works for you guys as well! Finally I can start playing with Ubuntu!! ^^

Revision history for this message
gavin (brian-gr-2001) wrote :

Mine appears to be simalar to smalphox. I have a Gigabyte GA-K8U motherboard, and was using the onboard ethernet when I had this problem.

When installed an old ethernet card and I am using it instead the DHCP works fine with this card.

description: updated
Revision history for this message
RdSnt (probbins) wrote :

I've encountered the same problem with a Linksys WRT54G.
Blacklisting of Tulip as described here doesn't work.
My workaround has been to unplug the power of the router briefly, when it reconnects the link is established with Ubuntu.
I've the latest release.
When the router isn't "working" I can still get to the internal control of the router, it just won't go any further.

Revision history for this message
Roland Kaye (r0k) wrote :

Hello, i have a very similar issue. Network works like a charm with the live CD, but when running from the HD, it works SOMETIMES and sometimes it doesn't work. I don't understand why. At least when the connection works, it doesn't go down on it's own. But somtimes i boot and the network is OK, sometimes i boot and network is out.

I have a gigabyte K8 Triton GA-K8NS motherboard (nforce3 250 chip) and i'm using the onboard ethernet controller (CK8S Ethernet Controller).

I'm totally new to troubleshooting anything, so just tell me if what additional informations i can provide. I will try the dhclient workaround next time my connection is off.

Revision history for this message
Fabio (fabiomb) wrote : Re: [Bug 47026] Re: DHCP/Network Works From LiveCD, Not From HDD Install

Bob:
the best workaround i find is to analize what modules of the kernel are running

lsmod (to see what modules are running)

sudo rmmod tulip (to remove the tulip driver, it's my case)

sudo ifdown eth0 (down the interface)

sudo rmmod dmfe (remove the dmfe driver, previous to add)

sudo modprobe dmfe (add the dmfe driver)

sudo ifup eth0 (up the inteface)

the problem (mine) is in the tulip driver.

sorry for my english, i'm from Argentina.

Fabio

On 7/8/06, Bob Morane <email address hidden> wrote:
> Hello, i have a very similar issue. Network works like a charm with the
> live CD, but when running from the HD, it works SOMETIMES and sometimes
> it doesn't work. I don't understand why. At least when the connection
> works, it doesn't go down on it's own. But somtimes i boot and the
> network is OK, sometimes i boot and network is out.
>
> I have a gigabyte K8 Triton GA-K8NS motherboard (nforce3 250 chip) and
> i'm using the onboard ethernet controller (CK8S Ethernet Controller).
>
> I'm totally new to troubleshooting anything, so just tell me if what
> additional informations i can provide. I will try the dhclient
> workaround next time my connection is off.
>
> --
> DHCP/Network Works From LiveCD, Not From HDD Install
> https://launchpad.net/bugs/47026
>

Revision history for this message
trollord (trollenlord) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

The issue that you reported is one that should be reproducable with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/

Revision history for this message
Fabio (fabiomb) wrote :

Trollord, is the same problem in bug [Bug 31914]

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.