GPL'ed Drivers For NVIDIA nForce Ethernet Devices 33
An anonymous reader writes "Manfred Spraul has released a GPLed driver for the ethernet device found in motherboards based on the Nvidia Nforce/Nforce2/Nforce3 chipsets. Drivers provided by Nvidia on the other hand, are closed. Andrew Morton has integrated this driver in the 2.6.9-mm2 release of his mm tree. And if you are using a 2.4x kernel, you may want to check out this post."
Thats nice! (Score:4, Interesting)
Re:Thats nice! (Score:5, Insightful)
Re:Thats nice! (Score:4, Interesting)
Perhaps you don't understand the magnitude of not having ethernet drivers available on any Linux install, and having to download them from the Internet, which is difficult, since you have no ethernet connection.
Until now, I have considered my nForce boards impossible to install Linux on because I am not willing to spend days downloading, burning, and installing ISOs and installing all the development tools that I don't need, downloading the drivers, rebuilding the kernel to finally tweak the thing into working and then uninstalling all the development tools when I have a debian packages mirror sitting on my fileserver.
This is good news.
Re:Thats nice! (Score:1)
Installation was a pain, but it was manageable. I can't quite remember how I did it though. :-( I think I (1) cross-compiled a patched kernel on another machine; (2) installed bare-bones Debian and Windows, both from CD; (3) transferred the Debianized kernel to the Windows partition; (4) mounted the partition under Linux; (5) installed the new kernel; (6) fi
Re:Thats nice! (Score:2)
Re:Thats nice! (Score:2)
BTW, if you already have a debian mirror locally, why can't you use jigdo against it to build a CD image quickly. (and burn it to a CDRW, since Sarge is coming soon
Re:Thats nice! (Score:2)
Thanks to the authors!
Re:Thats nice! (Score:1)
Re:Thats nice! (Score:1)
In my case even if I don't get one with the dual ethernet, I've still got my PCI card that I can use to get the drivers, but is still not as good a solution as full open-source drivers in the distro.
2.6.9? (Score:5, Funny)
Good job editors.
Re:2.6.9? (Score:1)
Woo-Hoo (Score:3, Interesting)
Has anybody else had problems with X on such a board? There's apparantly a bug somewhere in the rendering code that crops up because the nv driver doesn't use hardware acceleration as much as the nvidia driver. I filed bug #811 on bugzilla, but no resolution yet
Re:Woo-Hoo (Score:1)
Re:Woo-Hoo (Score:1)
Do you have nvidia-glx also emerged? The program 'glxgears' will give you framerate info on pure 3D drawing instructions, and there's another program that starts with 'glx' that dumps info; there's a line that tells you if you're using hardware acceleration or not. 'glxinfo', maybe?
I have a mere geForce2 GTS, and
Re:Woo-Hoo (Score:2, Informative)
If that shell command returns, "direct rendering: Yes" then you've got hardware GL.
Re:Woo-Hoo (Score:3, Informative)
Mine works pretty well under Mandrake 9.1, perfectly under Mandrake 9.2, and perfectly under Gentoo if your use the Alan Cox kernel sources (not the "standard" Gentoo kernel, unless it's been updated since I last tried it).
My SATA transfer rates are actually quicker (timed using "hdparm -tT") under 2.4 than 2.6.
nvidia ethernet drivers aren't backwards compat? (Score:2, Interesting)
Re:nvidia ethernet drivers aren't backwards compat (Score:3, Interesting)
If I understand correctly, the Ethernet is built right onto the mainboard, with the chipset.
Audio processing went down this route a while back. Old soundcards aren't needed when the functionality was built into the chipset.
For high speed networking (like GigE), avoiding the PCI bus can potentially be faster.
Re:nvidia ethernet drivers aren't backwards compat (Score:5, Interesting)
A good analogy would be there are 5 people all trying to call one guy, and Mr. Ethernet is one of the people. By being in the chipset and not on the bus, he doesn't have to keep trying to call and getting a busy signal, he can just say his message. This is because Mr. CPU could talk to 3 or 4 people at a time (he's that fast), but the phone (PCI bus) only has one line. He just skipps the problem.
OK, that's a bit simplified, but the fact is that not waiting on bus contention is good. The ethernet doesn't have to wait for/fight against the sound card, the tv tuner, and the add in raid controller.
On a side note, while NE2000 is a standard, it's for ISA, and as far as I know the NE2000 PCI standard never got big. I could be wrong. And even then, that's like using VESA to controll your GeForce FX video card. You can do it, but you could lose alot of the performance and features that you paid for because VESA doesn't know about 'em.
Built-in-chipset devices don't "skip" the PCI bus. (Score:3, Informative)
The only bus that was different was ISA.
Fail-safe mode. (Score:1, Interesting)
When NVDIA's binary drivers are with every distribution, then the GPL driver will be of less concern.
Re:Fail-safe mode. (Score:1)
Re:nvidia ethernet drivers aren't backwards compat (Score:1, Interesting)
Re:nvidia ethernet drivers aren't backwards compat (Score:1)
The reason for this is that the vast majority of 'integrated sound cards' are not really dsp's, but are mere codecs. Thus they hog the CPU for many, if not all sound processing tasks.
On the other hand, integrated ethernet devices aren't codecs - they're just those ethernet chips planted onto the main motherboard PCB instead of a separate card. They can have a slight performance benefit because of a high-speed interconnection with the chipset, too.
And now, a chart. (Score:5, Funny)
____
/ |
/ |
1.0| / |
| / |
0.5| / |
| _________________/ |
0.0|/_ _ _ _ _ _ _ _ _ _ _ _ _ _|_ _
GPL'ed Drivers for NVIDIA nForce...
Way to get my hopes up, Slashdot. I guess my kernel will continue to be tainted.
First impressions (Score:1)
For an alpha driver, I think thats pretty impressive. I wasn't even expecting it to work.
However, I did read someone saying that under heavy network load, the driver did not perform as well as the nvidia binary one (he was running a FTP server or something).
GPL'd nForce Audio Drivers would be good too... (Score:1)
But getting the sound components of the nForce board to work is altogether more challenging - the nVidia drivers are very basic and don't always work. Various patches exist (e.g. this entry [gentoo.org] from the Gentoo Discussion Forum [gentoo.org]) and some people report installing SBLive type cards to get around the problem.
Apparently one
NVidia policy for making drivers (Score:2, Insightful)
However, I don't think that it offers much except for hypothetical multiplatform portability. Without any specs it would be extremely hard to modify the driver and it's even harder to add new features.
Now I just hope someone has the time and skills to reverse engineer the NVidia video driver and GL libraries so that my 2.6.0-test9-mm2 kernel wouldn't give me pages of tracebacks every tim
Re:NVidia policy for making drivers (Score:1)
This isn't just hypothetical, if the driver is GPL'ed, the kernel developers are able to fix problems, as they have the source code.
The traceback messages you mention are the ones that would be used to help fix the problems.
It's even better if the hardware specs are open, because they can make the driver work with the hardware correctly, rather than trying to make good guesses.