wired network won't connect unless plugged in at startup

Bug #99541 reported by Patrick Valencia
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

If I start my computer without the ethernet cable plugged in, network-manager will not detect eth0 when I do plug it in. I've tried to ifdown eth0, then ifup it again, and it tells me that there were no DHCP offers.

When I start it with it plugged in, however, it finds it fine. I have all the newest updates. Everything worked fine in edgy.

ProblemType: Bug
Architecture: i386
Date: Sat Mar 31 15:53:30 2007
DistroRelease: Ubuntu 7.04
Uname: Linux PatsUbuntuLaptop 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 GNU/Linux

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
Patrick Valencia (pvalencia357) wrote :

I knew I would need more information, I just wasn't sure exactly what. Thanks for the quick response.

pvalencia@PatsUbuntuLaptop:~$ uname -a
Linux PatsUbuntuLaptop 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 GNU/Linux

Note: this information is from when the ethernet was plugged in at start up. If necessary, I'll attach the same responses from when it was not.

Revision history for this message
Patrick Valencia (pvalencia357) wrote :

Here's the lspci -vvnn output, also when the ethernet was attached at startup.

Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

Yes, please attach dmesg from when ethernet was not plugged in at start up. Thanks.

Revision history for this message
Patrick Valencia (pvalencia357) wrote :

Here's dmesg from when it was disconnected at startup.

Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Patrick Valencia (pvalencia357) wrote :

I see the status has changed. I really appreciate you guys looking into this. What have you found so far?

Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.