Announcement

Collapse
No announcement yet.

An Ubuntu Kernel Built With The Latest AMDGPU DC Support

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

  • #21
    Is Freesync supposed to be working at this point? I built the latest amd-staging-drm-next which has a number of freesync patches from ~45h ago.

    The props show up:
    $ xrandr --prop | grep freesync
    freesync_capable: 1
    freesync: 1
    freesync_capable: 0
    freesync: 0

    But my monitor OSD says nope in various games. While it does show freesync is enabled under windows.
    Running R9 290 here, AMDGPU-PRO not tested, because the 1.19 Xorg is too shiny for it.

    Comment


    • #22
      Originally posted by dwagner View Post
      I am currently using a kernel I compiled from "amd-staging-drm-next" ( https://cgit.freedesktop.org/~agd5f/...aging-drm-next ), and it works better than other kernels for me as I need to drive a 4k monitor at 60Hz via HDMI. Allowing for audio via HDMI is a nice add-on. It also seems to not crash easily when the connected monitor is switched off - something I experienced a lot of times with linux-4.12.

      Hardware video decoding works fine. However, trying to use hardware video encoding is sure to crash the machine within seconds. There are also still lots of scary log messages like "[drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* Unable to reserve buffer" - I guess it makes no sense for now to file bug reports on them, given the early stage of development.
      The amd-staging-drm-next tree is still a WIP as far as I know, but if you are seeing the same problems with amd-staging-4.12 (which should be pretty much the same code) I think we would want to know about it. Which hardware are you using ?

      Originally posted by RobinIT View Post
      Is Freesync supposed to be working at this point? I built the latest amd-staging-drm-next which has a number of freesync patches from ~45h ago.

      The props show up:
      $ xrandr --prop | grep freesync
      freesync_capable: 1
      freesync: 1
      freesync_capable: 0
      freesync: 0

      But my monitor OSD says nope in various games. While it does show freesync is enabled under windows.
      Running R9 290 here, AMDGPU-PRO not tested, because the 1.19 Xorg is too shiny for it.
      I think you still need the -PRO stack for now - needs some code in either libdrm or the X driver IIRC - but there should be a spin of 17.30 coming out in the next week or so which supports 16.04.3 (and I believe 16.04.3 uses X 1.19).
      Last edited by bridgman; 08-12-2017, 02:04 PM.

      Comment


      • #23
        bridgman

        Comment


        • #24
          bridgman I'm on Ubuntu 17.04 hence attempting to downgrade to Xorg 1.18 sounds like too much of a pain to attempt. Out of curiosity I'll be sure to keep an eye on the new driver though. I'm sure with the Xorg 1.19 support we can coerce it into Ubuntu 17.04 as well.

          Since I've been in a driver debugging spree lately I wondered if this freesync issue was something worth looking closer at or whether it's still too early. Some of these patches have commit messages suggesting it should work on Raven. While others call it broken legacy stuff.

          Comment


          • #25
            Originally posted by bridgman View Post
            The amd-staging-drm-next tree is still a WIP as far as I know, but if you are seeing the same problems with amd-staging-4.12 (which should be pretty much the same code) I think we would want to know about it. Which hardware are you using ?
            I'm using an RX 460 (and a Ryzen 1800X CPU), and the video encoding function made the driver crash the system with every kernel version I tried so far (some time ago that was also amd-staging-4.12).
            What would be the best communication channel to provide a bug report?

            (There are other bugs I also experience that do not seem to have gained much attention, such as https://bugs.freedesktop.org/show_bug.cgi?id=100375 )

            Comment


            • #26
              Originally posted by dwagner View Post
              What would be the best communication channel to provide a bug report?
              bugs.freedesktop.org, either Mesa/Gallium3D/radeonsi or DRI/DRM/amdgpu - choosing between those would depend on what error messages / log info you get from the crash

              Originally posted by dwagner View Post
              (There are other bugs I also experience that do not seem to have gained much attention, such as https://bugs.freedesktop.org/show_bug.cgi?id=100375 )
              That one seems to have been waiting for a response from the OP for ~4 months - developer response time was same day most of the time, 4 days for initial response. I realize that might not have been a good example though.

              Comment


              • #27
                Originally posted by msotirov View Post
                Didn't work on my KDE neon 5.10.4 and I had to revert back to kernel 4.10. It was giving me an ACPI Error, something about "Invalid PCI ROM header signature, expecting 0xaa55, got 0xffff".
                That is not an error and AMD should remove that testing message.

                Comment


                • #28
                  Originally posted by bridgman View Post
                  I think you still need the -PRO stack for now - needs some code in either libdrm or the X driver IIRC - but there should be a spin of 17.30 coming out in the next week or so which supports 16.04.3 (and I believe 16.04.3 uses X 1.19).
                  You did wrote that the open source driver is for gaming. Why there is no freesync support in Mesa drivers then?

                  Comment


                  • #29
                    Agree, we need to get it there. Just a few higher priorities that needed to be done first - getting initial Vega support ready before the HW shipped, getting all the internal kernel trees aligned and then caught up with upstream, getting DAL ready for upstreaming, things like that.

                    Comment


                    • #30
                      Originally posted by bridgman View Post
                      Agree, we need to get it there. Just a few higher priorities that needed to be done first - getting initial Vega support ready before the HW shipped, getting all the internal kernel trees aligned and then caught up with upstream, getting DAL ready for upstreaming, things like that.
                      I and many others are not planning to buy Vega. Monitor speakers are crap so there is no use for hdmi audio either in a high end gaming/multimedia pc. Many people do play the Rocket League game and are planning to buy a freesync monitor. Amd should think priorities again.

                      I did buy a cheap spdif optical DAC for my Amlogic S912 tv box, that has no hdmi (or analog) audio support in the mainline Linux kernel either. The Amlogic Meson spdif driver is very simple and fast compared to the Linux hdmi drivers, so if you want to use digital audio, use spdif.
                      Last edited by debianxfce; 08-13-2017, 01:42 AM.

                      Comment

                      Working...
                      X