Using Nvidia MCP55 Ethernet [10de:0373] - no network at startup and cannot configure manually

Bug #145835 reported by EricIndieRocks on 2007-09-27
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
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

EricIndieRocks (ecason2) on 2007-09-27
description: updated
description: updated
Brian Murray (brian-murray) wrote :

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.
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://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

EricIndieRocks (ecason2) wrote :

Here is the info

Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux

EricIndieRocks (ecason2) wrote :
EricIndieRocks (ecason2) on 2007-09-27
Changed in linux-source-2.6.22:
status: Incomplete → New
Brian Murray (brian-murray) wrote :

Looking at your dmesg.log file the adapters seem to be detected. Could you please also provide the output of 'ifconfig -a' and 'sudo ethtool eth0' and 'sudo ethtool eth1'? Thanks again.

Changed in linux-source-2.6.22:
status: New → Incomplete
EricIndieRocks (ecason2) wrote :

I saw this in this file

inet addr:169.254.6.125 Bcast:169.254.255.255 Mask:255.255.0.0

the ip should be 192.168.1.2 and the Bcast 192.168.1.255 (because of my router) That what it is in Feisty. When I changed them with network manager, nothing chnaged

EricIndieRocks (ecason2) wrote :
Changed in linux-source-2.6.22:
status: Incomplete → New
EricIndieRocks (ecason2) wrote :

Here is what my feisty ifconfig.log looks like. It has an extra line in the first section with the net info that is right.

Brian Murray (brian-murray) wrote :

This is quite odd it seems that your system is not getting the DHCP ip address from your router when you are running Gutsy. Could you please also add the log file '/var/log/daemon.log' after a fresh boot and not getting an IP address? Thanks again for all of your assistance.

Changed in linux-source-2.6.22:
status: New → Incomplete
EricIndieRocks (ecason2) wrote :

Here it is.

Changed in linux-source-2.6.22:
status: Incomplete → New
Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: New → Triaged
Motarion (motarion) wrote :

I have the same problem with Hardy Heron ...

Alexander Sack (asac) wrote :

network manager 0.7 (in ubuntu intrepid) supports system settings which allow you to configure connections that get upped without a user logging in.

Changed in network-manager:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers