Nvidia-Nforce ethernet

Message

mukwuknuk · Post by **mukwuknuk** » Sat May 08, 2004 4:37 am

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.

John2583 · Post by **John2583** » Sat May 08, 2004 6:44 am

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

blueworm · Post by **blueworm** » Sat May 08, 2004 6:02 pm

mukwuknuk wrote: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?

forcedeth has been included in 2.6 kernel since 2.6.2

harmonicace · Post by **harmonicace** » Wed May 12, 2004 6:08 pm

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 · Post by **blueworm** » Wed May 12, 2004 6:19 pm

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 · Post by **harmonicace** » Thu May 13, 2004 4:13 am

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

) 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 · Post by **mukwuknuk** » Sat May 15, 2004 5:53 pm

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.

mukwuknuk · Post by **mukwuknuk** » Sat May 15, 2004 6:14 pm

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!!

vonhelmet · Post by **vonhelmet** » Sat May 15, 2004 10:59 pm

mukwuknuk wrote: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!!

Check your /etc/resolv.conf file. I don't know the structure of it, and can't check offhand as I'm not at my Gentoo box, but that is probably a good place to start.

Bluesmoke · Post by **Bluesmoke** » Sun May 16, 2004 7:02 pm

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 · Post by **mukwuknuk** » Mon May 17, 2004 3:30 am

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?

Admiral LSD · Post by **Admiral LSD** » Mon May 17, 2004 3:45 am

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).

raizyr · Post by **raizyr** » Thu May 27, 2004 2:58 am

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 · Post by **FokeyJoe** » Fri Jun 04, 2004 9:23 pm

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 · Post by **crazyweber** » Mon Jun 07, 2004 5:15 am

Okay i have a nforce2 motherboard and i can not get internet to work. See this thread:
http://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

Code: Select all

/lib/modules/2.6.5/kernel/drivers/net

it was in there as well

after that I then did

Code: Select all

modprobe forcedeth.ko

when I did this I recieve an error

Code: Select all

FATAL: Module forcedeth.ko not found.

could anybody help me with this......

hw-tph · Post by **hw-tph** » Mon Jun 07, 2004 9:12 am

crazyweber wrote:after that I then did
Code: Select all
modprobe forcedeth.ko
when I did this I recieve an error
Code: Select all
FATAL: Module forcedeth.ko not found.
could anybody help me with this......

You need to specify the module name. forcedeth.ko is the filename, the name of the module doesn't have a file extension. So type modprobe forcedeth and it should load properly. If it does, simply add "forcedeth" (without the quotes) to /etc/modules.autoload.d/kernel-2.6 and it will load on boot.

Håkan

NightSpirit · Post by **NightSpirit** » Tue Jun 22, 2004 9:38 pm

raizyr wrote: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

Ditto, I have been using 2.6.5-mm6 fine with forcedeth for a while. Attempted to upgrade to 2.6.7-rc3-mm2 with make oldconfig and forcedeth refuses to work

coelho · Post by **coelho** » Sat Jun 26, 2004 5:43 am

same problem !!!

LynZ · Post by **LynZ** » Sat Jun 26, 2004 7:17 am

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

Code: Select all

Device Drivers->

Networking support->      Ethernet (10 or 100Mbit)  ---><*>   Reverse Engineered nForce Ethernet support (EXPERIMENTAL)

Check if you have THIS switched on..... if true you don't even need do load a module

Btw. I thought forcedepth was added in 2.4 too

DawgG · Post by **DawgG** » Sun Jul 18, 2004 1:40 am

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 · Post by **DawgG** » Sun Jul 18, 2004 2:18 am

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

russryder · Post by **russryder** » Sun Jul 18, 2004 2:40 am

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!!

jonnevers · Post by **jonnevers** » Sun Jul 18, 2004 4:34 am

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

DawgG · Post by **DawgG** » Mon Jul 19, 2004 12:50 pm

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 · Post by **solja** » Fri Aug 06, 2004 7:36 pm

this is wat worked for me:

Code: Select all

modprobe forcedeth

Code: Select all

dhcpcd eth1

if you have a nforce2 mb firewire is detected as your eth0 so you have to switch to eth1 instead.

Nvidia-Nforce ethernet

Nvidia-Nforce ethernet

similar prob w/ gbit :: doesn't work at all

SOLVED :: had to be patched

forcedeth w/ gbit