Page 1 of 2 12 LastLast
Results 1 to 10 of 31

Thread: NVIDIA Outs New 334 Linux Driver With New Features, Fixes

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,373

    Default NVIDIA Outs New 334 Linux Driver With New Features, Fixes

    Phoronix: NVIDIA Outs New 334 Linux Driver With New Features, Fixes

    The NVIDIA 334.21 Linux graphics driver was released this morning and its change-log is quite lengthy...

    http://www.phoronix.com/vr.php?view=MTYxOTc

  2. #2
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    521

    Default

    With EGL and OpenGL ES support in the driver, what's missing until we can have Wayland or Mir using the proprietary nvidia driver, does anyone know?

  3. #3
    Join Date
    Jul 2010
    Posts
    12

    Default

    What about optimus? Still no native support which just works?

  4. #4
    Join Date
    Dec 2012
    Posts
    33

    Default

    Looks like they finally added some support for linux 3.13/3.14. Some stuff might still be missing though, as it doesn't compile on 3.14-rc5.

  5. #5
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,525

    Default

    Hmm, so 331.49 is only available on 3.11.6 for openSUSE, and not 3.11.10, which is the currently available kernel version... That is really odd, because this forces people to stay on an old buggy kernel. Unless there are issues with 331.49 on 3.11.10? Well, either way, I hope 334 gets packaged for 3.11.10...

  6. #6
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,582

    Default

    Quote Originally Posted by GreatEmerald View Post
    Hmm, so 331.49 is only available on 3.11.6 for openSUSE, and not 3.11.10, which is the currently available kernel version... That is really odd, because this forces people to stay on an old buggy kernel. Unless there are issues with 331.49 on 3.11.10? Well, either way, I hope 334 gets packaged for 3.11.10...
    Install it the "hard way" (I haven't bothered using the RPM's in years since the "hard way" is so damn simple to do). It usually takes a while for Stefan to update the RPM's and usually a bug report is required to be filed in Novell's bugzilla to do so.
    Last edited by deanjo; 03-03-2014 at 01:32 PM.

  7. #7
    Join Date
    Feb 2012
    Posts
    424

    Default

    Quote Originally Posted by [Knuckles] View Post
    With EGL and OpenGL ES support in the driver, what's missing until we can have Wayland or Mir using the proprietary nvidia driver, does anyone know?
    It's probably not the only thing, but a standard interface for modesetting is needed. Weston uses KMS. Don't know what KDE and Gnome use, probably KMS too. Nvidia wants to have some sort of modesetting API in EGL. Until there's a standard, every compositor would need to explicitly target Nvidia's modesetting in addition to KMS. Not very elegant.

    Quote Originally Posted by _artem_ View Post
    What about optimus? Still no native support which just works?
    As I said last time when someone asked this, native Optimus support will not be possible until Nvidia finishes their vendor-neutral opengl library. This library will allow having multiple opengl stacks simultaneously. Right now this is not possible, all you have right now is putting the different stacks in non-standard locations and then playing with LD_LIBRARY_PATH or LD_PRELOAD or similar hacks. Not very elegant.

  8. #8
    Join Date
    Jul 2010
    Posts
    12

    Default

    Quote Originally Posted by Gusar View Post
    It's probably not the only thing, but a standard interface for modesetting is needed. Weston uses KMS. Don't know what KDE and Gnome use, probably KMS too. Nvidia wants to have some sort of modesetting API in EGL. Until there's a standard, every compositor would need to explicitly target Nvidia's modesetting in addition to KMS. Not very elegant.

    As I said last time when someone asked this, native Optimus support will not be possible until Nvidia finishes their vendor-neutral opengl library. This library will allow having multiple opengl stacks simultaneously. Right now this is not possible, all you have right now is putting the different stacks in non-standard locations and then playing with LD_LIBRARY_PATH or LD_PRELOAD or similar hacks. Not very elegant.

    Why they don't open their complete driver sources? Is not a proprietary software or os, it's just a driver. If their brains aren't smart enough to make their hardware properly work just release the drivers' sources the community does it their own without reverse engendering the official driver. It's not a strategic object, it's not kinda atom launcher specifications it's just a video card driver

  9. #9
    Join Date
    Feb 2012
    Posts
    424

    Default

    Quote Originally Posted by _artem_ View Post
    Why they don't open their complete driver sources?
    Even if they could (there's probably NDAs and other assorted agreements, patents and just plain 3rd party code to which Nvidia doesn't own the copyright in the way), how would that help? It's still a different opengl stack that would clash with mesa.

    And having the code wouldn't help nouveau devs very much, because the nvidia driver is a big giant mess of application and game specific micro-optimizations and other assorted micro-optimizations, making it impenetrable. Saying "it's just a video card driver" is some serious underestimating of how complex today's GPUs and their drivers are.

    Also this appeal to the almighty community that will suddenly appear once code and/or docs get released doesn't work nowadays anymore. For example, look at how incomplete the Ironlake driver is (the pre-gen6 section at the bottom): http://wiki.freedesktop.org/dri/I965Todo/. And that's despite a fully open source driver and full docs being available.

  10. #10
    Join Date
    Jul 2012
    Posts
    707

    Default

    Quote Originally Posted by Gusar View Post
    Even if they could (there's probably NDAs and other assorted agreements, patents and just plain 3rd party code to which Nvidia doesn't own the copyright in the way), how would that help? It's still a different opengl stack that would clash with mesa.

    And having the code wouldn't help nouveau devs very much, because the nvidia driver is a big giant mess of application and game specific micro-optimizations and other assorted micro-optimizations, making it impenetrable. Saying "it's just a video card driver" is some serious underestimating of how complex today's GPUs and their drivers are.

    Also this appeal to the almighty community that will suddenly appear once code and/or docs get released doesn't work nowadays anymore. For example, look at how incomplete the Ironlake driver is (the pre-gen6 section at the bottom): http://wiki.freedesktop.org/dri/I965Todo/. And that's despite a fully open source driver and full docs being available.
    What he said, plus GPUs are patent minefields.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •