Announcement

Collapse
No announcement yet.

Drivers for linux are rubbish

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

  • Originally posted by adamk View Post
    I don't use vlc (except in Windows). Even with the little tearing that I have noticed once in a while, though, fglrx is still more functional and reliable for me than the nvidia drivers were. Unlike nvidia, at least fglrx doesn't result in a full system lockup.

    Adam
    And if for you you had lockups with nVidias blobs it's as valid to state that as it is to state that you have to use specific software to playback video with fglrx.

    ...Or is mentioning that you had lockups with nVidia bashing nVidia?

    Comment


    • I haven't accused anyone of AMD bashing (or nvidia bashing).

      Personally, I have no problems with people stating specific problems they've had with any software. It's when they do things like insist that one piece of software is always the better option, or always sucks, or is always rubbish that the conversation turns from intelligent discourse to bashing.

      Adam

      Comment


      • Originally posted by adamk View Post
        I haven't accused anyone of AMD bashing (or nvidia bashing).

        Personally, I have no problems with people stating specific problems they've had with any software. It's when they do things like insist that one piece of software is always the better option, or always sucks, or is always rubbish that the conversation turns from intelligent discourse to bashing.

        Adam
        Well I see a fair bit of posting regarding fglrx's performance as compared to nVidia's blob that on the balance of probabilities you're likely to have a better experience with nVidia than ATI at the moment and there's nothing controversial about that to me.

        Comment


        • Originally posted by droidhacker View Post
          Not really... cuda is proprietary whereas openCL is open. That's enough to make all the difference.
          I know cuda is propietary, but it seems that is used vastly on parallel computing programing and that is more easy to implement and has more performance than opencl, but not by a great margin. You can use google scholar and search some articles here. Although, I admit that I have a very vague idea, based on a few articles I read. I guess that in the future openCL will be the way to go because is open.

          Originally posted by droidhacker View Post
          AMD has this too, even intel for that matter. They just use a different name for it.
          Nvidia implemented VDPAU, and it seems much better than VAAPI and XBVA. This has been widely said by a lot of people. Now VDPAU (as API) is open and any vendor can use it.

          Comment


          • I have definitely had problems with nvidia recently. Their vdpau stuff cuttoff was basically one model card beyond mine so that does nothing for me.

            However their driver quality has been falling off pretty quickly over the last few years for 2D stuff. They keep adding interesting new features but the driver seems to be more unstable. Most of the time you still can't go to the terminal from inside x (Ctrl-Alt-F1) for instance without it completely glitching up and often completely locking the computer up.

            So if something goes wrong and x locks up in some strange way which has become more common with the nvidia driver and xinerama if you want to fix it you have to go to another machine and ssh in to fix it.

            Comment


            • @ mugginz

              You mixed some quotes, you qouted me on things I have no said.

              Man / boy / whatever, you are just tedious. Do you know exactly what is the shape, pros and cons of fglrx and nvidia since long time ago. What do you want? Do you want us to erect a monument to nvidia better drivers? your song is always the same.

              Comment


              • Originally posted by Jimbo View Post
                Nvidia implemented VDPAU, and it seems much better than VAAPI and XBVA.
                What do you base this statement on?
                From my observations, regardless of whose implementation you use, you put compressed video in one side and it plays back full screen HD on the other without sucking up your CPU.

                From my EXPERIENCE, VDPAU simply *does not work*. Not saying that it won't work for anyone, but after spending several hours struggling with a GPU that was supposed to be supported, I decided that it just wasn't worth it -- it wasn't working for me, and there was no sign that it would ever (and FYI: I'm an engineer, not a newb).

                Also, VAAPI is to be the general API for video decoding (at least this is the way things appear to be moving). VDPAU or XVBA are just two backends. Some applications are configured to access the backend directly, but that doesn't make it appropriate behavior. Nvidia sure TRIED to get THEIR API to be accepted as the general interface, but that doesn't look to be happening for them.

                Note: The REASON they want their API to be accepted has to do with MARKETING. It would be valuable to them to say that they led AMD and Intel into conforming with THEM. From an open source freedom perspective, unless nvidia actually contributed to open source drivers, and SERIOUSLY (like AMD does), then it would be unsuitable to use any of their API, free or not.

                This has been widely said by a lot of people. Now VDPAU (as API) is open and any vendor can use it.
                Does it give you that warm fuzzy feeling to use something developed by the closed steel trap company?

                Right now, the only SERIOUS user of VDPAU (as an api) is nvidia itself. The other user of it is S3, but we all know that they're not going anywhere. XVBA is used more appropriately as a backend under VAAPI. Intel implements backend for VAAPI more directly rather than exposing their backend to the user. VAAPI frontend exists for VDPAU (for those lucky enough to get it to work). So in the end, VAAPI should theoretically get you where you need to go and the backend implementation becomes irrelevant -- they all do the same thing (assuming that they work). VAAPI is most definitely ahead of VDPAU (as an API) in this regard... because VAAPI bas backends for AMD, Intel, AND VDPAU (which includes Nvidia *as well as* S3). There is NO AMD or Intel backend to VDPAU.

                Comment


                • Originally posted by Jimbo View Post
                  @ mugginz

                  You mixed some quotes, you qouted me on things I have no said.

                  Man / boy / whatever, you are just tedious. Do you know exactly what is the shape, pros and cons of fglrx and nvidia since long time ago. What do you want? Do you want us to erect a monument to nvidia better drivers? your song is always the same.
                  I want people who are saying forgive fglrx, it's better now to not forget to mention it's still not perfect. I don't want people to build an expectation that can't currently be met. If you tell people they'll have no problems with fglrx and they then go and spend their money and then have problems that are well known by some then that's bad.

                  Comment


                  • @droidhacker are you serious?

                    VDPAU is working with all kind of video type (MPEG-1, MPEG-2, MPEG-4 ASP (MPEG-4 Parte 2), MPEG-4 AVC ...)

                    Comment


                    • @droidhacker are you serious?

                      VDPAU is working with all kind of video type (MPEG-1, MPEG-2, MPEG-4 ASP (MPEG-4 Parte 2), MPEG-4 AVC, etc) since long ago. Some linux programmers have said that is a very good api and well implemented.

                      XVBA, just work with a few video cocdecs (backend under VAAPI), just with with HD4000, and the programmer has explicity said on this forums that XBVA driver is plenty of bugs. Maybe if some day ati implements it correctly it will be fully functional. The hardware has the potential is just the api & driver is not yet working. And it seems that it will not work in short term

                      VAAPI I don't know exactly how good bad it is, but i guess is worst than VDPAU.

                      I am not speaking about the APIs itselfs, but about the API and Driver implementation and functionality together.

                      Comment


                      • AMD have not officially released xvba - they might work on it and properly release it in the future, but there's been no word from them on that subject.
                        I've also had issues with vdpau - full X crashes actually. However this is on my nettop, so to say vdpau alone isn't entirely accurate - vdpau with xbmc is causing problems for me.

                        Comment


                        • Originally posted by mugginz
                          I want people who are saying forgive fglrx, it's better now to not forget to mention it's still not perfect.
                          This is not the problem.

                          But recently, people have been claiming that FGLRX can't do any powersaving, that FGLRX crashes as soon as it renders a triangle, and all sorts of other nonsense.

                          It would be more fair to say that there are issues with tear-free playback and Xv colours, and that WINE in particular has some issues with 3d.

                          That would be a fair assessment, having read about the topic for months now.

                          Yet every week a new guy comes here and claims that he read on this and that forum that fglrx will blow up your computer.

                          It's getting very old.

                          Comment


                          • Originally posted by pingufunkybeat View Post
                            This is not the problem.

                            But recently, people have been claiming that FGLRX can't do any powersaving, that FGLRX crashes as soon as it renders a triangle, and all sorts of other nonsense.
                            If someone says fglrx doesn't do power saving of any kind then they're plainly wrong and there's nothing wrong with correcting them here.

                            If someone says fglrx crashes immediately upon rendering a single triangle then I'd hope that sound ridiculous to everyone and I'd have no problem with someone saying it's ridiculous.

                            Originally posted by pingufunkybeat View Post
                            It would be more fair to say that there are issues with tear-free playback and Xv colours, and that WINE in particular has some issues with 3d.

                            That would be a fair assessment, having read about the topic for months now.
                            I agree. Driver installation issues can and should be worked on by distros.

                            Originally posted by pingufunkybeat View Post
                            Yet every week a new guy comes here and claims that he read on this and that forum that fglrx will blow up your computer.
                            Anyone claiming that is taking pretty serious creative license at best but I also don't think that's what anyone's trying to get at at all.

                            Originally posted by pingufunkybeat View Post
                            It's getting very old.
                            And people wanting to sweep issues with <inset favourite vendor here> add nauseum is a bit old as well.

                            Comment


                            • Originally posted by pingufunkybeat View Post
                              This is not the problem.

                              But recently, people have been claiming that FGLRX can't do any powersaving, that FGLRX crashes as soon as it renders a triangle, and all sorts of other nonsense.
                              Yet every week a new guy comes here and claims that he read on this and that forum that fglrx will blow up your computer.
                              Yet more straw men. Who's saying these things?

                              It would be more fair to say that there are issues with tear-free playback and Xv colours, and that WINE in particular has some issues with 3d.
                              But that's what we ARE saying. Please pay attention.

                              That would be a fair assessment, having read about the topic for months now.
                              The big problem is that it hasn't been a problem for months, it's been years. That's what some people, including me, get worked up about.

                              Comment


                              • Originally posted by albatorsk View Post
                                Yet more straw men. Who's saying these things?
                                I don't need to name users and start flamewars again, but both the powersaving and the triangle one came in the last few days here on Phoronix.

                                The "blow up" one is my hyperbolic satire.

                                Comment

                                Working...
                                X