nForce nvidia network driver can't link up when plugin wire

Bug #230099 reported by Yann Sionneau
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned
Nominated for Hardy by Yann Sionneau
Nominated for Intrepid by Yann Sionneau

Bug Description

This bug happened when i upgraded from gutsy to hardy
bug description : when i plug an ethernet wire it does nothing, nothing appears like "eth0: link up, 100Mbps, full-duplex" in dmesg
so i cannot use the network interface ... cannot get an ip via dhcp ... cannot use static ip... can do nothing.
seeing that networking didn't work i thought the upgrade from gutsy went wront so i installed from scratch with Hardy ISO but it still doesn't work.
Same problem on the Hardy live CD with linux 2.6.24-16-generic
It works very well on Windows XP and on Ubuntu Feisty Fawn and Ubuntu Gutsy Gibbon.

Information about the system and configuration :
uname -r : 2.6.24-16-generic
lsb_release -rd :
Description: Ubuntu 8.04
Release: 8.04
network-manager is in roaming mode
i tried using console command ifconfig and dhclient but without success (which is normal because there is no wire recognized)
i put in attachement :
lspci -v
lsmod
dmesg after bootup
tail -f /var/log/syslog while plugging in wire
content of /etc/network/interfaces
output of ethtool eth0 and ethtool eth1 (which is the same before and after pluging in a wire (no wire detected )).

Revision history for this message
Yann Sionneau (yann-sionneau) wrote :
Revision history for this message
Yann Sionneau (yann-sionneau) wrote :

here is the dmesg attachement.

Revision history for this message
Yann Sionneau (yann-sionneau) wrote :

here is the lspci -v attachement.

description: updated
description: updated
Revision history for this message
Yann Sionneau (yann-sionneau) wrote :
description: updated
Revision history for this message
Yann Sionneau (yann-sionneau) wrote :
Revision history for this message
Yann Sionneau (yann-sionneau) wrote :
Revision history for this message
Yann Sionneau (yann-sionneau) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

most likely a low level thing. moving to linux package.

Revision history for this message
Yann Sionneau (yann-sionneau) wrote :

i found out this bug is a duplicate of this one : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136836
The solution explained worked well (adding two options msi=0 msix=0 while modprobing the module forcedeth)
here is what i did :
i put this line in the file /etc/modprobe.d/options
options forcedeth msi=0 msix=0
and i did :
sudo update-initramfs -u
and then reboot, and it worked well configuring interface with dhcp.

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.