Announcement

Collapse
No announcement yet.

AMDGPU-PRO 16.50 Rolls Out With GCN 1.0 Support, FreeSync

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

  • Amarildo
    replied
    bridgman OpenCL on Catalyst is broken on any Blender version, BTW. Make sure you test that with the next AMDGPU-PRO

    I'm ready to be a super-beta-tester for OpenCL.

    Leave a comment:


  • bridgman
    replied
    Originally posted by whitecat View Post
    I didn't test without EPEL7, I just followed the HOWTO-INSTALL instructions:
    The AMDGPU-Pro driver requires access to specific RPMs from Red Hat installation media as well as Extra Packages for Enterprise Linux (EPEL) for purposes of dependency resolution.
    Ahh, OK... sounds like we would have tested with EPEL 7 then. Thanks !

    Leave a comment:


  • whitecat
    replied
    Originally posted by bridgman View Post
    Does the crash happen without EPEL7 ? We definitely do QA prior to release but I'm not sure if we would have included EPEL7 in that testing.
    I didn't test without EPEL7, I just followed the HOWTO-INSTALL instructions:
    The AMDGPU-Pro driver requires access to specific RPMs from Red Hat installation media as well as Extra Packages for Enterprise Linux (EPEL) for purposes of dependency resolution.

    Leave a comment:


  • mokurai82
    replied
    I just wanted to say that I finally got Freesync to work! Specifically on Linux Mint 18.1 Cinnamon 64-bit. (Kernel 4.4.0-53-generic, other kernels like 4.8 don't work)
    The thing is not every game or app supports it. You also need to run the game, then alt tab to a terminal and enter the command Bridgeman supplied, then alt-tab back into the game.
    I got it running in Valley, Bioshock Infinite, Civ V and Metro Last light (albeit with flickering that one). Sometimes there is flickering in other apps when in freesync mode.
    It does not run in Witcher 2 (native steam) or Diablo 3 (playonlinux) at all. I also run in DRI:3 mode if that has anything to do with it. Thank You Bridgeman for your help!

    Leave a comment:


  • Amarildo
    replied
    bridgman Thanks. A freshly pulled/built Kernel fixes the cursor problem. However, mouse acceleration is screwed up now, it's not 1-to-1 with my hand, but I think that is related to Xorg and it's programs (currently 1.19.0-3). I'll check with more people to see if xf86-input-evdev is the cause of this, then open a ticket.

    EDIT: this solved the accel problem. I thought KDE would be able to hand that, but it's clearly not.
    Last edited by Amarildo; 17 December 2016, 12:37 AM.

    Leave a comment:


  • Amarildo
    replied
    Originally posted by bridgman View Post

    Hmm, that sounds like something the devs would want to know about, even if it is a non-obvious new or different kernel config parm. Do you happen to remember what the kernel parm was that made it boot, and for bonus points would there happen to be an fdo bugzilla ticket ?
    Sorry, I don't remember what it was. I looked at 10 threads about "Linux 4.9" but I assume the post where I mentioned the parameter was deleted because debianxfce and I were cussing at each other.

    Originally posted by bridgman View Post
    Re: mouse cursor issue, I just found a very recent (last couple of days) fix-for-a-fix related to cursor on DCE6 (among others) so might be worth pulling either latest amd-staging-4.7 or drm-next-4.10-wip. There are also a number of changes specific to SI desktop cards in there you might want. In both cases you need something less than 36 hours old.
    Thanks, I'll pull amd-staging-4.7 right now. Hopefully it works this time.

    Leave a comment:


  • bridgman
    replied
    Originally posted by Amarildo View Post
    Are you sure? Because last time I tried 4.9 and 4.10 I wasn't able to boot at all, getting a black screen. There was a kernel parameter to make the Kernel boot IIRC, but then I had no audio if I enabled that.
    Hmm, that sounds like something the devs would want to know about, even if it is a non-obvious new or different kernel config parm. Do you happen to remember what the kernel parm was that made it boot, and for bonus points would there happen to be an fdo bugzilla ticket ?

    Re: mouse cursor issue, I just found a very recent (last couple of days) fix-for-a-fix related to cursor on DCE6 (among others) so might be worth pulling either latest amd-staging-4.7 or drm-next-4.10-wip. There are also a number of changes specific to SI desktop cards in there you might want. In both cases you need something less than 36 hours old.

    Leave a comment:


  • Amarildo
    replied
    Are you sure? Because last time I tried 4.9 and 4.10 I wasn't able to boot at all, getting a black screen. There was a kernel parameter to make the Kernel boot IIRC, but then I had no audio if I enabled that.

    I'm only using amd-staging-4.7 because I found it has the best support for SI cards on amdgpu while still being trouble-free.

    Leave a comment:


  • bridgman
    replied
    Can I ask you to stop thinking about amd-staging as the universal solution ?

    It does have a purpose, and there are a number of specific scenarios where we have recommended giving it a try, but if you are running on a distro with a newer-than-4.7 kernel then IMO you are likely to have more success with a recent upstream tree. The amd-staging branches are raw development trees and I can pretty much guarantee that there will be regressions.

    The base kernel should be OK for 16.04 but please try a recent upstream kernel as well.
    Last edited by bridgman; 16 December 2016, 10:18 AM.

    Leave a comment:


  • Amarildo
    replied
    I did revert most of the userspace stuff back a few days, though I'm not 100% sure it was to the same version as when it was working. I could only revert the oldest packages in /var/cache/pacman/pkg, which was around 10 versions. Given that the buildserver builds new packages every 6 hours, and the fact that I didn't update every 6 hours, IMO those should be enough to go back to where it was working.

    What I don't remember reverting is xorg-server nor xf86-video-amdgpu (this last one was always pulled from git, always the latest).

    This is why I think the problem is in xf86-video-amdgpu-git.

    I'm on Ubuntu 16.04 right now and I'll compiled amd-staging, and use mesa-git from oibaf or padoka. If it fails too, I'm off to Windows.

    Leave a comment:

Working...
X