Forgot your password?
typodupeerror
Graphics Software Hardware Linux

GPL'ed Drivers For NVIDIA nForce Ethernet Devices 33

Posted by timothy
from the makes-sff-even-more-attractive dept.
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."
This discussion has been archived. No new comments can be posted.

GPL'ed Drivers For NVIDIA nForce Ethernet Devices

Comments Filter:
  • Thats nice! (Score:4, Interesting)

    by pagercam2 (533686) on Wednesday November 05, 2003 @02:44PM (#7398574)
    Its great that drivers are available for this new chipset, but is this really worth being a /. topic???
    • Re:Thats nice! (Score:5, Insightful)

      by schapman (703722) on Wednesday November 05, 2003 @02:51PM (#7398651)
      yes... im picking up an nForce2 board shortly, and its nice to know that when i install linux, I'll have an option. I have found in the past that certain manufacturers make crappy drivers (Creative + SBlive platinum + winxp) and its nice to see that the people out there w/ the skills are willing to contribute. Also, a pro-open source and pro-linux site like slashdot is a great place for these people to be recognized for their work.
    • Re:Thats nice! (Score:4, Interesting)

      by Cecil (37810) on Wednesday November 05, 2003 @06:51PM (#7401346) Homepage
      Yes. Yes it is.

      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.
      • I have considered my nForce boards impossible to install Linux on because I am not willing to spend days downloading, burning, and installing ISOs...

        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

      • WTF? Gentoo 1.4 livecd works (as of August 15th) with my nforce2 ethernet port. I can book livecd and ping out just fine...
      • You could use a spare NIC in a PCI slot until you get the proprietary crap to set up the NVidia NIC.

        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 :) apt-get install jigdo-file. Not that that makes it much easier, since you still have to get the proprietary NV crap onto the system somehow.
    • It is. This was a complete showstopper for me buying an nforce2 motherboard which is the best Athlon XP motherboard right now.

      Thanks to the authors!
      • I've got and nforce2 and if you only need one ethernet port then you are sorted anyway because one of the ports is a 3com NIC which works out of the box. It's nice to have both working though.
        • That's on the ASUS A7N8X Deluxe board [asus.com] (which I'm planning on picking up this weekend, actually) and possibly others, but not necessarily all nForce boards, even other [asus.com] ASUS [asus.com] boards [asus.com].

          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)

    by jamessan (244547) <vega DOT james AT gmail DOT com> on Wednesday November 05, 2003 @02:48PM (#7398613)
    Wow, I didn't know the kernel left -test status and increased 9 versions since yesterday. Andrew Morton must be on top of things to get a -mm patch out that quick, too.

    Good job editors. ;)
  • Woo-Hoo (Score:3, Interesting)

    by eriksson (4162) on Wednesday November 05, 2003 @02:49PM (#7398622) Homepage
    This is great - now I just need to get the XFree86 nv driver to play nice with my nForce2 w/ integrated video, and I'll be able to run a non-tainted kernel.

    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 :(
    • I have an nforce2, but it's not integrated video. It's the abit NF7-S and I have a geforce FX5900 in it. The nvidia driver I'm running on gentoo works fine. 3d things work, just not fast. The nvidia logo pops up when X starts and X works just fine. So all fingers point to the driver being correctly installed and running. But I can't tell if the fact that 3d works is due to my fast cpu or due to hardware accelleration from the video card. My frame rates are definitely much slower than in windows, so I'
      • But I can't tell if the fact that 3d works is due to my fast cpu or due to hardware accelleration from the video card. My frame rates are definitely much slower than in windows, so I'm unsure.

        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)

        by Crazy Eight (673088)
        `glxinfo | grep direct'
        If that shell command returns, "direct rendering: Yes" then you've got hardware GL.
      • Re:Woo-Hoo (Score:3, Informative)

        by mickwd (196449)
        If you desperately need Serial ATA support on an NF7-S, it's available in 2.4 kernels.

        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.
  • I always thought most modern ethernet cards were compatible with some generic brands.. like ne2000.
    • 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.

      • by MBCook (132727) <foobarsoft@foobarsoft.com> on Wednesday November 05, 2003 @03:22PM (#7399020) Homepage
        Not only is skipping the PCI bus important for speed, but even for slower things (like 10/100 ethernet) not being on the bus is good. It means that the chip can talk to memory or the CPU without waiting for the PCI bus to be free for it to use. Basically, it gets to skip the bus contention.

        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.

        • The transactions occur across a much faster interconnect (which can go by different names according to the chipset design), but it's still linear and you still access resources in a PCI-like manner. Just faster.

          The only bus that was different was ISA.
        • Fail-safe mode. (Score:1, Interesting)

          by Anonymous Coward
          All true, however in the context of the story. Having GPL drivers means that people with ethernet connections to the internet i.e. Cable or DSL can connect and get the drivers they need from Nvidia's site. The VESA standard and the 'nv' drivers allows one to have the basic functionality to at least get the OS installed and get 'something' done.

          When NVDIA's binary drivers are with every distribution, then the GPL driver will be of less concern.
          • It's not just important for 'fail-safe mode.' There will probably never be a time when every distribution has NVIDIA's binary drivers included in their distribution, especially during the install. Also, there are people that won't use NVIDIA's drivers either because of stability problems or legal/moral grounds. This provides a welcome alternative.
        • by Anonymous Coward
          I know integrated sound cards sap a much larger portion of CPU time then PCI cards, making them a poor choice for gamers. I've avoided using integrated Ethernet on the same principle. Should I reconsider?
          • No, you shouldn't.
            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.
  • by ActiveSX (301342) on Wednesday November 05, 2003 @07:44PM (#7401979) Homepage
    How much I care on the Y, title index on the X.
    ____
    / |
    / |
    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.
  • Under 2.6.0-test9-mm2 this driver works good for me. I am managing to download from the net at full speeds (120kb/sec), and transfer large files over my lan at 11mb/sec (which is as good as I got with the nvidia binary driver).

    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).
  • Apart from the non-GPL'd status, I'm not aware of big problems with ethernet drivers for nForce boards - as noted elsewhere in this thread they seem to be functionally supported out of the box.

    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
  • Reverse engineering the binary driver for the ethernet chip and making a GPL'd source tree for anyone to review is great.
    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
    • 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.

What is wanted is not the will to believe, but the will to find out, which is the exact opposite. -- Bertrand Russell, "Skeptical Essays", 1928

Working...