Problems with nForce410 networking.

[rubinho]

I'm using the one bundled with Mandriva One's kernel (2.6.12 i guess), i'll check the exact version later. With Kanotix and SuSE i used NVnet bundled with nvidia's Linux driver 0310 (AMD64 version).

In Windows XP SP2, i'm using the latest nForce4x0 driver (8.22 from november).


motherboard is an ASRock K8NF4G-SATA2 with bios version 1.50 (this problem has been occuring ever since I bought the board, which was in bios version 1.20 back then).

[netllama]

rubinho, you'll need to upgrade to a much more recent kernel (which includes a much more recent forcedeth), or problems are to be expected. I don't know whether Mandriva is shipping any kernels with a recent (0.49 or later) version of forcedeth in their official kernels.

Thanks,
Lonni

[kenyee]

Lonni,

FYI, the 0.49 Forcedeth driver also has this issue (boot into windows, then warm boot to Linux and network doesn't work). If you do an ifconfig, you'll also see that zero packets are transmitted....packets are only received on the network port...

A cold boot (use switch on back of power supply) fixes this...it's been a fairly known C51 motherboard issue since last September and has been mentioned on avsforum, anandtech, here, etc.

There's some new register/bit in the C51 that the forcedeth drivers aren't initializing but the Windows drivers do; if you could ask your Windows network driver coders to have a quick glance at the forcedeth driver code, it might help...

[gerick]

Originally Posted by netllama

Which version of forcedeth is everyone using?

Thanks,
Lonni

I have had the issue with forcedeth 0.47 and 0.48.
I am not sure which version I have now, but it is kernel 2.6.15-r7 of Gentoo AMD64.

edit: Forcedeth 0.48 is in kernel 2.6.15-r7 of Gentoo AMD64.

[rubinho]

But i'm having the same problem with the latest official nVidia driver as well.
It doesn't happen only with linux' forcedeth.

(that's also why I experimented with lots of distributions, always trying to use the bleeding-edge kernel, etc)


--editing...

just now i noticed I posted in the wrong section. sorry

[rubinho]

Updating...
The same problem occur with the latest Kubuntu (6.04 alpha6), it works properly when freshly-booted, but doesn't after rebooting from windows.

[rlwconsulting]

Originally Posted by rubinho

I have an ASRock board with the GeForce6100+nForce 410 chipsets (ASRock K8NF4G-SATA2) using a Sempron 3100+.
It works nicely in Windows, but I'm having a hard time to get it to work with Linux...

None of the distributions I have tried seem to properly use the network (onboard) port, some of them even recognize it and try to use the forcedeth driver, with no success.

Distros I have tried:

Ubuntu 5.04 (old kernel, which doesn't even start X with VESA)
Kurumin 5.0
SuSE 10.1 beta (amd64)
Kanotix 2005.4 (amd64)
Mandriva One 2006 (recognizes MCP51 network device, but doesn't work, also, doesn't come with kernel sources...)

I had the most success with SuSE and Kanotix, managing to get 3D and sound to work properly.
Network, on the other hand no, despite trying both forcedeth and then nForce 3.10 drivers.

[...snip...]

I've had trouble with forcedeth and nvnet on SUSE 10.0 as well. After installing latest nvnet module (had to recompile kernel--part of driver install), went to YAST Control Center and set module to nvnet (set to use DHCP)--worked well. Rebooted--did not work. Took a while to figure out the network interface detection was timing out and failed. But, oddly, the network would come up after I reset network services. Failed again after booting. Took a while to figure out (RTFM) that apparently, a hardware detection routine that was run when upon installation never could set up the interface and it never ran again. Manual mentioned the hwup command, so I tried it. On SUSE, in

/etc/sysconfig/network

typed the command

hwup bus-pci-0000:00:14.0 (the device identifier--interface name for my integrated NIC).

Upon reboot, the network interface no longer times out and eth0 comes up. Don't know if that helps anyone, but hope so.

[playaz]

The dual boot issue with the ethernet port has been fixed. Forcedeth driver has been updated with the fix (version 53).

[kenyee]

Cool. Thanks for the update, playaz.
And thanks Lonni (I assume you had a hand in helping w/ this ;-)

[simonimf]

I've got an ASUS A8n-la motherboard (GeForce 6150 graphics + 430 chipset), and I'm running FC5 x86_64 with the latest kernel 2.6.16-1.2111 with the kernel-devel also installed. I'm also using dual boot with Windows XP media center.

I'm having the same networking dual-boot must-power-off problem with the nforce430 chipset. You mention a version 53 to forcedeth, I'm running version 0.49. I tried to locate version 53 but couldn't find it anywhere. Were you being sarcastic or serious about this new version?

Also, I tried to use the nvnet driver to see if this would fix the problem. Now, I'm having issues trying to get the nvnet driver to load. It installs fine, and I've updated the modprobe.conf file with the appropriate aliases to turn forcedeth off and nvnet on. However, every time I reboot it still loads the forcedeth driver.

Any help would be appreciated.

[qinlejun]

Thank you for this post, it help me slove the network problem after a power plug-off.

Now in FC5, the sound device can be detect but it can not work, no sound come out, but it can work well in Suse 10.1, don't know the reason.