Announcement

Collapse
No announcement yet.

Nouveau vs. NVIDIA Linux Comparison Shows Shortcomings

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kano
    replied
    @XorEaxEax

    It is incorrect that nouveau always uses the lowest clockspeed. It just uses the clockspeed thats set by the vga bios on boot when you don't enforce reclocking. That can be a higher clock as well than the lowest one and could be different from vendor to vendor even for the same model.

    Leave a comment:


  • Kano
    replied
    @brosis

    Call it how you like but when something is not enabled by default and works automatically only a few users will even notice it existance. I personally could use it but i have to think about the Kanotix user base as well - even if it is possible they usually dont use it. I do NOT intend to tell em how it works when i provide already binary drivers that can do the job better - it would be completely lost time to do so when it is not even 100% sure that it works.

    Leave a comment:


  • XorEaxEax
    replied
    Originally posted by wargames View Post
    Nouveau is basically wasted man power. They really need documentation on how Nvidia graphic cards work if they want to make something remotely usable.
    Bullshit, I've been using Nouveau exclusively for the past 6 months and everything has been running smoothly on both my machines (9600GT/9800GT), including 3d modeling/sculpting in Blender. Obviously I can get better performance of the NVidia binary but Nouveau is certainly 'usable'.

    Apart from 3d stuff I do alot of 2d stuff aswell as some video editing, and Nouveau is perfectly competent for that. No, I do not play typical AAA games, but most of the indie bundle games I've played have ran just fine, though some of they have had graphical glitches. Was quite a while ago though so I should probably check to see if those have been fixed by now.

    And as for the performance differences, as has been repeated over and over again, Nouveau operates at the lowest clock frequency while the proprietary drivers re-clock at higher frequencies when you are running 3d intesive applications. The Nouveau devs are working on re-clocking but since this can be cause damage to your card unless done correctly they can't enable it until they are sure (within reason) that it actually works.

    Most definitely the proprietary driver will still come out on top and by a good margin, and for those who wants/needs the best possible performance it's great that the NVidia driver exists, for my needs Nouveau is already adequate, and with re-clocking enabled sometime in the future it will be even more so.

    And finally one more thing, while Linux is 'blessed' with proprietary driver support from the likes of Nvidia / AMD, there are other platforms which will NEVER have any official support, one of those which I'm very fond of is Haiku, and here Nouveau serves a huge purpose as a possible means to support NVidia 3d hardware acceleration in the future.

    Originally posted by wargames View Post
    Of course the Nouveau team is free to do whatever they want with their time, but in the end they will realise they have wasted a precious time in their life.
    Alot less than you wasted with this worthless post of yours, as I and many others out there are already finding great worth in their work.

    We all would like to have open source Nvidia drivers, because they make great graphics cards, but this is not going to work.
    Again bullshit, it is already WORKING.

    Leave a comment:


  • smitty3268
    replied
    Originally posted by brosis View Post
    Kano, powermanagement works with radeon. Its automatical powerstate switching that is not implemented or even better load-based powerswitching. But user can manually switch the powerstates.
    Perhaps you mean "powermanagement is complete" instead of "fully working", because its fully working, but is not complete featurewise ...
    I don't think that's true on the newer APU parts - they aren't allowed to run at full speed at all, because of PM issues.

    Leave a comment:


  • smitty3268
    replied
    lol

    let the trolling begin.

    Leave a comment:


  • brosis
    replied
    Originally posted by Kano View Post
    Until powermanagement is fully working with every oss driver i would always prefer binary drivers - but radeon is interesting now too because of the new uvd/vdpau support that does not exist in the binary one.

    http://kanotix.com/files/fix/tmp/tf2/tf2-benchmarks.txt
    Kano, powermanagement works with radeon. Its automatical powerstate switching that is not implemented or even better load-based powerswitching. But user can manually switch the powerstates.
    Perhaps you mean "powermanagement is complete" instead of "fully working", because its fully working, but is not complete featurewise ...

    Leave a comment:


  • brosis
    replied
    Wow, I didn't realise it was a developer! Oh my gosh...
    Michael should really post an article about this...


    Subliminal message: "We don't care if this driver works at all"
    Resolution: Workaround allows to work around the problem, so people can still work, waiting for a real fix. Ignoring workarounds equals to not caring about anyone who uses the software. Thats a kick in userbase butt.
    Originally posted by calim View Post
    That's not a fix, it's a workaround. If you had a fix, we might just care.

    Subliminal message: "We don't care about quality of this driver at all"
    Resolution: This is as "hobby" as it gets.
    Originally posted by calim View Post
    Myself I really don't care (well, I do, but not to the point where I'd do something about it), my ~2000 hours of wasted free time on this project would be even more wasted (on the personal level anyway)

    Subliminal message: "We don't care about Linux user base. They can go to hell."
    Resolution: If someone refuses even to accept free cards in order to make Linux more attractive to new users, he definately gives a brick about Linux userbase. Expect nothing even close to serious from this crowd. The code he pushes this way is "mess" in all forms.
    Originally posted by calim View Post
    Myself I really don't care (well, I do, but not to the point where I'd do something about it), my ~2000 hours of wasted free time on this project would be even more wasted (on the personal level anyway) if I'd spent them with the annoying bugs of users with cards I don't have (which is the factor that makes fixing things really hard, but don't suggest sending cards to me I don't have the time or nerve), instead of focusing on the fun stuff.

    Subliminal message: "Our driver will always be constantly broken"
    Resolution: -
    Originally posted by calim View Post
    It's either progress or stability, and we seem to focus very much on progress over stability overall.

    Subliminal message: "We don't code, we don't improve, we don't want to organize anything. We just hang around, breaking stuff for fun. And we like to make fun of AMD developers. Because, they, unlike us, actually write STABLE CODE. We - either write mess, or don't write anything. Hell, we better off watch TV drinkin beers. Linux sucks anyways --.. and not because of us! Rly."
    Resolution: -
    Originally posted by calim View Post
    Of course, "no docs" is just an excuse, even with docs things wouldn't be moving along much faster at this point because there's no one there to do the time-consuming part, i.e. actually implementing things. That's their biggest advantage, AMD hires devs (and what ever happened to "the community will write the driver" ?)


    Suggestion:
    Linus - Please REMOVE NOUVEAU out of kernel. Reiserfs is much more worthy of attention than this.
    Distributions - under NO WAY build or include nouveau. Use either VESA or nvidia. This is sure way to immediately kill your userbase with nvidia cards.
    Developers - unless you want to join Nvidia, its much better to join forces who actually CARE about code they write. That means on x86 - Intel or AMD.
    Nvidia users - under NO CIRCUMSTANCE donate your hardware to nouveau. Please, SELL it. At least, you will not waste your money.
    Last edited by brosis; 04-23-2013, 08:41 PM.

    Leave a comment:


  • brent
    replied
    Originally posted by calim View Post
    That's not a fix, it's a workaround. If you had a fix, we might just care.
    It's certainly a workaround if acceleration is important. But consider Live CDs and the like. These simply won't boot properly on these GPUs right now, so you can't even install a modern Linux-based OS! No acceleration is still preferable to crashing. I just don't see the point in not applying the workaround, after this has been broken for such a long time with no proper fixes in sight.

    Leave a comment:


  • Kano
    replied
    I tested Nv GTX 295 and Nv GT630 OEM (Kepler) with TF2 and Mesa 9.1 final some weeks ago. Interestingly the Kepler based card had much fewer rendering errors than the much older one. I did not check the clocks while testing and just used the default settings. Some would guess that nouveau is better for older cards but that does not seem to be the case, maybe with the exception of some very slow onboard solutions like ION. In general you get what you want with the official Nv drivers if speed is what really matters, nouveau is usally fine enough to see something and use composite effects for kde/compiz/gnome3. My GTX 295 however gets really hot using nouveau and i would not use it for long time - if you have got a better card than a very lowend one. Same applies more or less to radeon as well - with binary drivers you can still save energy/money. Basically Intel is still the way to go when it comes to oss only drivers, sometimes you need to fix applications too to get it stable however (for Intel+Mesa 9.1 i had to patch the kde-workspace package - basically only kwin). Until powermanagement is fully working with every oss driver i would always prefer binary drivers - but radeon is interesting now too because of the new uvd/vdpau support that does not exist in the binary one.

    http://kanotix.com/files/fix/tmp/tf2/tf2-benchmarks.txt

    Leave a comment:


  • ArchLinux
    replied
    I must admit I'm a little surprised not only to see regular people calling Nouveau a total waste, but to think that an actual _dev_ comes here to confirm it. I mean that's just.. amazing.

    And Nouveau is nowhere near perfect. It never will be. Something will always be broken, so including phrases like "shortcomings" in the title is just pure ignorance.

    Was the goal of this thing ever to even catch up to the proprietary driver anyway or to just mainly add things like KMS support for Nvidia and then graphics acceleration as the situations come along?

    I don't see the reason to, if it's not _just_ as fast as the binary version, call it a "waste". A waste is something that turned out to be pointless work. I think it's plain r*tarded to call an open source display driver _pointless_ on the grounds of its performance not equalling the original one.
    Last edited by ArchLinux; 04-23-2013, 07:12 PM.

    Leave a comment:

Working...
X