Nvidia Nforce2 Integrated NIC

**Orb360** · 05-09-2004, 04:46 PM

are there any cheatcodes to allow me to use the integrated nic on my Nforce2 board, or am I going to have to go d/l a driver. Knoppix just says no NIC found

**iscarib** · 05-16-2004, 07:09 PM

I have the same problem but booting from the HD Installation. In the boot screen, It seems everything goes well since appear a line telling "eth0 devices found, sending dhcp broadcast (backgrounding)" or something like that. I made lsmod and I can see "forcedeth" loaded, i made "modprobe forcedeth" and nothing happened (I think this is Ok, isn't it?). But, in KDE, I ran the configure network card script in the knoppix menu and it said "sending dhcp brodcast to eth0: failed", and in the control center I only can see the active loopback in the network interfaces screen.
What I am forgotten? What I made wrong?
Can anybody help me?
Thanks a lot!!!!!

AMD XP2600+ 512 Mb nForce2 Knoppix 3.4 kernel 2.6.5

**mzilikazi** · 05-17-2004, 01:44 AM

Those NICs should *just work* as that driver is part of the kernel now. Orb360 try:
lsmod
and see if forcedeth is there.

iscarib try:

dhclient eth0

**Orb360** · 05-18-2004, 10:51 PM

I downloaded the new image and it works fine... But I'd still like to use my previous image (Knoppix-STD) with my new mobo.... but since I don't have a HD to spare to remaster the new image.... I guess I'll just have to wait until Knoppix STD remaster's theirs...

**iscarib** · 05-22-2004, 03:33 PM

mzilikazi,
Thanks for your tip, but it doesn't work for me or I don't know how to do it work. When I try with "dhclient eth0" in console, an error message "command dhclient not found" appear. Have I include this command in any file?

Orb360,
Are you booting from CD or from HD installation?
Did the new Knoppix image recognize the nForce NIC well?

All of them,
In modconf I see the forcedeth module loaded. Also, I see forcedeth in lsmod, but I can't see the nForce NIC in the control center, in the network interfaces appart. Have anybody any idea?
Thanks a lot in advance!!!

Rodrigo.

**OErjan** · 05-22-2004, 03:55 PM

should it not be pump eth0?
check if the module is loaded (lsmod) and then check what is said about network (ifconfig) post here if uncertain.

**iscarib** · 05-22-2004, 05:17 PM

OErjan,
Thanks a lot! I will try it, but, I have to type "pump eth0" in console or I must put this line into any file?
Thanks!

**OErjan** · 05-22-2004, 06:25 PM

just in console for now. output from the two comands

Code:

dmesg|grep eth

and

Code:

ifconfig

may further help me help you.
my guess is that you might have to edit the setup of your runlevel to get it to autoconfigure corectly, it might be down for some reason, check if

Code:

 ifconfig eth0 up

THEN

Code:

pump eth0

works (as root).
the comand could be written in one line like so:

Code:

sudo ifconfig eth0 up&&pump eth0

.

**iscarib** · 05-22-2004, 08:56 PM

Oerjan,
look at this:

Code:

root@cawendio:~# dmesg|grep eth
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
eth0: forcedeth.c: subsystem: 01695:1000 bound to 0000:00:04.0
root@cawendio:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:04:61:50:60:A4
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4116 (4.0 KiB)  TX bytes:1368 (1.3 KiB)
          Interrupt:20 Base address:0x5000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:500 (500.0 b)  TX bytes:500 (500.0 b)

When I tried with the other "combined command" line, i get the next error message:

Code:

root@cawendio:~# ifconfig eth0 up&&pump eth0
pump: no extra parameters are expected

What do you think?
Notice that in the boot screen say "network device eth0 detected. sending DHCP broadcasting (backgrounding)" or something like that. Why kernel detect eth0 in the booting and when I am in KDE I don't find any eth0?
I'm a complete newbie in linux, and I don't know what's happen!
Thanks!