Announcement

Collapse
No announcement yet.

NVIDIA Updates Legacy Drivers With X.Org Server 1.19 Support

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

  • #11
    agd5f

    He thinks that these branches are more stable than released kernels on kernel.org. So i guess upon testing and proving that those "works for me" he decided to recommend them to anybody... Same way also anybody who use kernels from kernel.org is wrong.

    At least that is how understand him, so kernels from kernel.org are per him always half baked, but your branches are always full baked and when someone say "recent amdgpu" debianxfce jump right on him and say no that is not recent kernels from kernel.org are not recent, people should use your brances to be recent and stable... And not only that, he also think that AMD developers should start recommending these to anybody.

    Also whoever does not agree with him is an idiot, because he can't be wrong
    Last edited by dungeon; 02-15-2017, 12:56 PM.

    Comment


    • #12
      dungeon I do believe agdf5's Kernels are very stable too. I did a 'git diff' between a current grsec patch (at the time) and agdf5's 4.7-staging Kernel, and I was surprised: despite being labled "4.7", agdf5's Kernel is somewhat comparable to linux-git: it was not as "old" as 4.7, it had the latest drivers, AND had a ton of security and other patches backported.

      IMO agdf5's Kernels should be an official branch at Kernel.org.

      Comment


      • #13
        Originally posted by Amarildo View Post
        dungeon I do believe agdf5's Kernels are very stable too. I did a 'git diff' between a current grsec patch (at the time) and agdf5's 4.7-staging Kernel, and I was surprised: despite being labled "4.7", agdf5's Kernel is somewhat comparable to linux-git: it was not as "old" as 4.7, it had the latest drivers, AND had a ton of security and other patches backported.

        IMO agdf5's Kernels should be an official branch at Kernel.org.
        Ha, ha, and you are also wrong, that won't happen... even if that is true for you at random point at time, no way that should be recommended

        These are so called internal branches, or post internal or pre pushed to drm to Dave or... these just happen to be open well because it is opensource,

        You might try them of course in case you have some bug in current or if you like to test things early... but shouldn't be recommended to average Joe for no particular reason of course
        Last edited by dungeon; 02-15-2017, 04:00 PM.

        Comment


        • #14
          Originally posted by agd5f View Post

          I'm not sure I understand what you are getting at. I have a wip kernel tree for every kernel release (4.7, 4.8, 4.9, etc.). They contain code that is going upstream in the next kernel cycle. The code in 4.11-wip is going upstream in 4.11, the code in 4.12-wip will go upstream in kernel 4.12. That is how kernel development works. There will always be a delta of stuff that is on its way upstream.
          It takes months for new amdgpu code to end to kernel.org. Amd should use this:
          https://cgit.freedesktop.org/~agd5f/...-next-4.11-wip
          instead of this:
          kernel.org
          here:
          http://developer.amd.com/tools-and-sdks/open-source/

          Kernel bugzilla has many bugs for the amdgpu driver in stock kernels. It seems that amd developers do not want that people are testing wip code. Remove then this:
          https://cgit.freedesktop.org/~agd5f/...-next-4.11-wip

          People will buy more Nvidia cards then.
          Last edited by debianxfce; 02-16-2017, 03:24 AM.

          Comment


          • #15
            I'm pretty sure the staging branch is for development purposes only, so they won't be advertising something that could break at any time. Instead, they advertise regular kernel.org branches.

            Comment


            • #16
              Originally posted by Amarildo View Post
              I'm pretty sure the staging branch is for development purposes only, so they won't be advertising something that could break at any time. Instead, they advertise regular kernel.org branches.
              Amd developers breaks the stock kernel amdgpu driver when not using all of the wip code.

              Comment


              • #17
                Originally posted by smitty3268 View Post

                Only if you ignore the Mesa drivers.
                Problem is some GCN cards, especifically the ones with hardvested hardware , doesn't work with Mesa drivers. They also don't work with AMDGPU-PRO and have flickering and microstuttering problems with fglrx, so even staying in an old XOrg with fglrx is not a solution.

                I really appreciate that AMD is putting so much effort in the open source drivers, but if bugs that blocks entire cards for working never get fixed and the closed source drivers come in "doesn't work at all" and "works bad and only with old packages", you can figure out that the users suffering this problems can see NVidia closed source drivers like something to envy, a warranty your hardware will work in Linux.

                Comment


                • #18
                  Originally posted by madmalkav View Post
                  Problem is some GCN cards, especifically the ones with hardvested hardware , doesn't work with Mesa drivers..
                  When you search with the word amdgpu in the kernel buzilla, almost all problems are solved. Use the latest adg5f wip kernel and make a bug report when you find a new bug. Use the latest Mesa git too.

                  Comment


                  • #19
                    Originally posted by debianxfce View Post

                    When you search with the word amdgpu in the kernel buzilla, almost all problems are solved. Use the latest adg5f wip kernel and make a bug report when you find a new bug. Use the latest Mesa git too.
                    The bug was opened more than 4 years ago. In this time multiple users have done all tests asked by AMD developers on mailing list and IRC channel to try to debug the problem, with no success.

                    You should humbly ask for more info or do some search yourself before assuming you are the only user in the world that know what is the proper procedure to report a bug.

                    Comment


                    • #20
                      Originally posted by debianxfce View Post

                      When you search with the word amdgpu in the kernel buzilla, almost all problems are solved. Use the latest adg5f wip kernel and make a bug report when you find a new bug. Use the latest Mesa git too.
                      No adg5f wip kernel nor latest mesa need to be used in this case , madmalkav already participated in a Tahiti LE not working bug opened since 4 years ago, as you can see there that is still not fixed:

                      https://bugs.freedesktop.org/show_bug.cgi?id=60879

                      Comment

                      Working...
                      X