Using Nvidia MCP55 Ethernet [10de:0373] - no network at startup and cannot configure manually
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When I start gutsy, either from the cd or after I install it, either by CD or updateing through apt-get.it fails to detect my network.
In Feisty it detects the right ip address via dhcp from my router, but not in gutsy Gutsy tells me my ip, subnet, and broadcast are all 0.0.0.0. I try to manually configure it through network manager, but it doesn't work even after I change the ip, subnet and broadcast to the values that work in Feisty. Also, my network card disappears from the list of devices, and going through the menus it says "no devices detected" after I try to manually configure it.
This has been a problem in all versions of Gutsy up to and including the beta of 9/27/2007.I'm using the AMD64 version on my Pentium Duo.
My network comes up as nVidia Corp MCP55 Ethernet card
description: | updated |
description: | updated |
Changed in linux-source-2.6.22: | |
status: | Incomplete → New |
Changed in linux-source-2.6.22: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Thank you 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. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
Please include as attachments 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:/