Nvidia-Nforce ethernet

mukwuknuk · Posted: Sat May 08, 2004 4:37 am Post subject: Nvidia-Nforce ethernet

I did take the trouble to read several other threads on this subject before posting. While several came close to answering my question, none did. SO:

I've heard rumors that support for my Nvidia-Nforce ethernet card comes built into the 2.6 kernel (I'm runnning 2.6.5). Is this true? Is it there automagically or will I have to do genkernel? I'm guessing support *can* be in the 2.6.5 kernel if I want to rebuild it that way. Correct?

If not, then I'll soon be asking for help with "emerge nforce-net", since the emerge didn't work during the install process and it ain't working now. Crashes and quits fairly quickly, with complaints about NR_IRQS and NR_IRQ_VECTORS being undeclared. I wonder what that's all about.

So is it genkernel to get my ethernet working? How do I tell what's already in my kernel now? lsmod reveals very little.

Thanks for any help.
_________________
"If there are back-slashes in your path, you're heading down the wrong path ... backwards."

John2583 · Posted: Sat May 08, 2004 6:44 am Post subject:

I compiled the nforce ethernet support for my A7N8X deluxe board with 2.6.5 with Slackware, but the module is called forcedeth.
Device Drivers > Networking > Ethernet 10 or 100 mbit >Reverse Engineered nForce Ethernet support (EXPERIMENTAL)

Info: " To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called forcedeth.

Just compile your kernel again like you did to install the kernel the first time.

Edit: oh you want to know if you already have support for it: Well if it's a module then it might be in the same place mine is in: check here: /lib/modules/2.6.5/kernel/drivers/net if you have forcedeth.ko in there then just do a modprobe forcdeth and then you should be able to bing up your eth1 like this: ifconfig eth1 up
_________________
iBook G3 600 Mhz, 640MB, 40GB, airport, DVD/CD-RW Gentoo PPC
PC specs: MSI K8N Neo4/SLI, A64 X2 3800+ @ 2.4GHz 2x1GB Corsair XMS DDR 400, Nvidia 7800GT

blueworm · l33t Joined: 09 May 2003 Posts: 962

harmonicace · n00b Joined: 30 Dec 2003 Posts: 4

I had the same problem. I'll try the forcedeth thing. Is it because of this inclusion that emereg "nforce-net" doesn't work? I'm also haveing a very similar thing happen when I try to emerge "nforce-audio" how to I fix that?

blueworm · l33t Joined: 09 May 2003 Posts: 962

nvaudio is for 2.4 kernels only.
For 2.6 kernels use the alsa driver included in the kernel.
The module you need is allready selected by default.
just emerge alsa-lib and alsa-utils.

harmonicace · n00b Joined: 30 Dec 2003 Posts: 4

I just recompiled my kernel including the "Reverse Engineered nForce . . ." and I have to type "ifconfig eth0 up" before ifconfig will show it and even then I can't ping any servers and emerge doesn't work. So, I only assume somthing isn't quite right. My kernel is the mm-sources (kernel-2.6.6-rc3-mm1).

Next time I boot off the livecd (I'm quiting for tonight and going back to windows :oops:

) I'll emerge the alsa tools; I did include alsa in the kernel but haven't been able to check yet and see if it worked.

mukwuknuk · Posted: Sat May 15, 2004 5:53 pm Post subject:

OK "modprobe forcedeth" worked and "ifconfig eth0 up" worked (or at least it didn't give any error message)... but I still can't ping anything so I guess I'm not connected. Does anyone have an idea how I should diagnose the problem? Thanks for any help.
_________________
"If there are back-slashes in your path, you're heading down the wrong path ... backwards."

mukwuknuk · Posted: Sat May 15, 2004 6:14 pm Post subject:

On second thought, I guess my question is far too general. I do know that there are about half a dozen config files that have to be set correctly for network connectivity to succeed, and I did configure them, so I guess I'll just have to experiment with scores of settings until I find the problem. I suppose it's not practical to receive help on this.

But thanks for the "forcedeth" advice!!
_________________
"If there are back-slashes in your path, you're heading down the wrong path ... backwards."

vonhelmet · Posted: Sat May 15, 2004 10:59 pm Post subject:

Bluesmoke · n00b Joined: 14 May 2004 Posts: 20 Location: San Jose, CA

resolv.conf would be as follows:

nameserver < ipaddress of nameserver 1 >
nameserver < ipaddress of nameserver 2 >
search < name of your domain >

an alternate method would be just to enable DHCP if your on a network that has it. It would provide the info you need automaticaly.

mukwuknuk · Posted: Mon May 17, 2004 3:30 am Post subject:

resolv.conf looks good, thanks, but still can't connect.

I did notice I must do "modeprobe forcedeth" every time after a reboot. How can I install the module permanently?
_________________
"If there are back-slashes in your path, you're heading down the wrong path ... backwards."

Admiral LSD · Posted: Mon May 17, 2004 3:45 am Post subject:

There are two ways you can make the forcedeth module (or any module for that matter) load at start up: The first, and probably the easiest is to simply emerge hotplug and then add the hotplug init script to the boot runlevel (rc-update add hotplug boot). Then, on subsequent boots, modules for all your installed hardware will be loaded automatically without any user intervention. The second way is to open up the /etc/modules.autoload.d/kernel-2.6 file (or, if using 2.4, the 2.4 version in the same directory) and add put an entry for forcedeth in there.

To avoid having to ifconfig eth0 up all the time simply add the net.eth0 init script to the default runlevel (rc-update add net.eth0 default).
_________________
Wasurenaide...
...watashi ga iru koto o.
Itsudatte soba ni iru yo.

Registered Linux user #319839

raizyr · n00b Joined: 23 May 2004 Posts: 7 Location: Atlanta, Ga

I'm having the same problem with mm-sources both 2.6.6-r4 and 2.6.6-r5.

forcedeth loads, eth0 shows up in ifconfig but no ip. I use dhcp so it should be pulling an ip. it's not. I also tried setting the ip statically. I can not ping the .1 address of my network with the IP set static.

forcdeth works fine for me in gentoo-dev-sources 2.6.5-gentoo-r1

FokeyJoe · n00b Joined: 04 Jun 2004 Posts: 33 Location: Oxford, UK

Just to help anyone else looking at this thread to switch over to forcedeth, there may be an alias set to identify the module with the network interface. This is typically in the /etc/modules.d/aliases file, though could possibly be set in other files in this directory. Remember to run modules-update and then reboot.

HTH

crazyweber · n00b Joined: 01 Feb 2004 Posts: 58 Location: Lawrence, KS

Okay i have a nforce2 motherboard and i can not get internet to work. See this thread:
https://forums.gentoo.org/viewtopic.php?t=179827

I have given up that it has anything to do with /etc/conf.d/net or /etc/resolv.conf

when i found this thread i checked to make sure I had forcedeth built as a module in my kernel and I do. Then I went ahead and checked to make sure it was in

hw-tph · Posted: Mon Jun 07, 2004 9:12 am Post subject:

NightSpirit · Posted: Tue Jun 22, 2004 9:38 pm Post subject:

coelho · n00b Joined: 23 Jun 2004 Posts: 44

same problem !!!

LynZ · Apprentice Joined: 05 Jan 2004 Posts: 220 Location: MIPT

I'm using 2.6.7-gentoo-r5... forcedeth works just fine for me

DawgG · l33t Joined: 17 Sep 2003 Posts: 874

i have 2.6.8-rc1 on nforce3 gbit-lan and have support for forcedeth compiled directly inside the kernel (in the config forcedeth was mentioned only as a 100mbit-driver, but i enabled it anyway).
it doesn't work at all; and it's not even known to lspci. during boot there's a little msg that the driver is registering - that's it.
(luckily i have a spare nic - life sucks w/out network).

-will i have to patch the sources to be able to use the gbit-driver?
-is it better to compile the driver as a module?

DawgG · l33t Joined: 17 Sep 2003 Posts: 874

could have read that earlier - had to be patched with http://www.hailfinger.org/carldani/linux/patches/forcedeth/forcedeth_gigabit_try9.txt
patch applied ok - will test it later.

russryder · Tux's lil' helper Joined: 28 Aug 2002 Posts: 133

I had the same problem with 2.6.7
The easy fix is to just install an earlier kernel.
For example I installed 2.6.5 and the forcedeth module works beautifully.

!!Until this is fixed nforce owners beware 2.6.7 bad!!
_________________
System Specs
Athlon XP 2500+
1.5g ram
GeForce FX 5700 Ultra
Soundblaster Live
200gb hdd
gentoo-dev-sources 2.6.9 r4
screenshot http://russbox.sytes.net/screenshot.png

jonnevers · Posted: Sun Jul 18, 2004 4:34 am Post subject:

after you bring eth0 up do you run dhcpd to get an IP and nameserver?

DawgG · l33t Joined: 17 Sep 2003 Posts: 874

applied the patch and it runs now. gbit lan with nforce3.
might be a little confusing because with the patch the forcedeth-gbit-driver is still in the 100mbit-section, but who cares.
it's compiled directly in the kernel and it runs. haven't had a chance to REALLY check if it throughputs (?) 1 gbit, though.

btw, i use 2.6.8 (not MUCH choice with nforce3)

solja · n00b Joined: 20 Jul 2004 Posts: 67

this is wat worked for me: