Wired internet connection does not start at boot.

Bug #154207 reported by bclintbe
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running regular 7.10 ( 2.6.22-14-generic) on a AMD64 computer (don't want to use the 64-bit version of Ubuntu for reasons like flash) , onboard NIC using the forcedeth driver.

I seem to be having intermittent problems with my wired connection since switching to 7.10. Sometimes my wired connection just does not start at boot up. From where I sit I can see my router, and on these occasions no lights for that wired connection. When I log in to Ubuntu, no internet connection (the icon shows no wired connection).

If I do a hard boot, sometimes the connection starts at bootup, and everything's fine when I log in. Sometimes the hard boot doesn't help.

The connection worked fine before 7.10, and I have tried different cables, restarting the router, etc. I still get these random failures to even recognize the connection at boot up. Everything works fine when I'm not using Ubuntu 7.10. One thing that did work once was unplugging and replugging in to the NIC after logging in to Ubuntu. Viola, router lights come on and I have a connection.

If there's any more info I can give, please let me know, as I'd like to get this resolved.

Revision history for this message
bclintbe (bclintbe) wrote :

Also wanted to mention that on the occasions that I do not have an internet connection, the LEDs on the NIC on the computer are not on either. It appears that Ubuntu is not waking up the NIC on boot up.

Revision history for this message
bclintbe (bclintbe) wrote :

Seeing others in the forums having similar problems, I noticed one other trend. Not only was my video card nVidia, but so was my onboard NIC. When I disabled the restricted drivers for the nVidia graphics card, my internet started working again after a hard boot. I don't want to give up on the 3D desktop, so I disabled the onboard NIC, installed an old ethernet card that I had lying around (which Ubuntu sees as eth1), and then reinstalled the restricted graphics. Everything is working fine now.

Revision history for this message
Michael Nagel (nailor) wrote :

i want to confirm this bug.
i have a 32-bit desktop pc with a D-Link DFE-550TX/FX wired network card. i used to be connected when i logged in (either into gnome or even on plain console). since gutsy (and with hardy, too) i have to log into gnome, click the network-applet and select "wired network" everything works fine then.
this problem is not a driver problem as the connections works out of the box if i click the button manually. it is reproducable with gutsy and hardy live-cds, so it is nothing i misconfigured manually. it used to work from dapper to edgy... :(
any further information required?

Revision history for this message
Michael Nagel (nailor) wrote :

had some success with this one, it's still bothering me? any idea what package to file this bug against so that some dev will have a look at it?

Revision history for this message
Michael Nagel (nailor) wrote :

i disabled n-m and manually set the device from roaming mode to dhcp and now everything works as expected...

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) 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 if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
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.