Announcement

Collapse
No announcement yet.

The Strange Behavior Of My Radeon R9 290 Is Still There

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

  • Frogging101
    replied
    I'll be thrilled if we have this nailed

    Leave a comment:


  • Michael
    replied
    Originally posted by agd5f View Post
    Michael can you try the latest radeon bonaire uvd firmware from the linux firmware tree? http://git.kernel.org/cgit/linux/ker...x-firmware.git
    Yep will be giving it a shot within next few days as soon as I have the R9 290 in the system again.

    Leave a comment:


  • agd5f
    replied
    Michael can you try the latest radeon bonaire uvd firmware from the linux firmware tree? http://git.kernel.org/cgit/linux/ker...x-firmware.git

    Leave a comment:


  • bridgman
    replied
    OK, this is starting to make sense.

    The -PRO driver includes a firmware package that would presumably have replaced whatever firmware came with the distro.

    Leave a comment:


  • nuetzel
    replied
    Progress:
    It seems that Ubuntu hasn't have the latest firmware 'onboard'.
    Have a look, here:

    Leave a comment:


  • Frogging101
    replied
    Leo Liu (I think that's his name) from AMD posted a firmware blob that fixes the problem for me. On my Mint 18 system, I put it in /lib/firmware/radeon/ and ran "update-initramfs -uk all" (it is crucial that you do this or equivalent on your OS, or the new firmware won't be loaded). It's on the bug report posted earlier (I'm John Brooks): https://bugs.freedesktop.org/show_bug.cgi?id=98988#c3
    Last edited by Frogging101; 19 December 2016, 01:48 PM.

    Leave a comment:


  • nuetzel
    replied
    Originally posted by plasmasnake View Post

    I wonder if you're experiencing the same DPM-related bug reported here: https://bugs.freedesktop.org/show_bug.cgi?id=98988

    To test it, delete /lib/firmware/radeon/hawaii_uvd.bin, and then re-install your kernel .deb files. You need to do the reinstall, because then it will rebuild initrd, where the firmware file is cached, and you'll receive a warning that the firmware file is missing.

    After you reboot, you'll see an error in your dmesg saying that the hawaii_uvd.bin file wasn't found (this was added in 4.7), and it will fall back to the old HAWAII_uvd.bin file.
    GOOD hint!

    Now, after the starting R7 260X (BONAIRE) there is now a >>> R9 290 <<< with same symptoms _bisected_ to the same commit!

    @Michael:
    Please try a quick test (commenting out the bisected commit our delete bonaire_uvd.bin (maybe hawaii_uvd.bin, too to be sure)) before you get in your own 'besecting mode'.

    Leave a comment:


  • MrCooper
    replied
    Originally posted by plasmasnake View Post

    I wonder if you're experiencing the same DPM-related bug reported here: https://bugs.freedesktop.org/show_bug.cgi?id=98988

    To test it, delete /lib/firmware/radeon/hawaii_uvd.bin,
    hawaii_uvd.bin is only used by the amdgpu kernel driver. With the radeon kernel driver, one would have to delete bonaire_uvd.bin instead, even with a Hawaii GPU.

    and then re-install your kernel .deb files. You need to do the reinstall, because then it will rebuild initrd, [...]
    FWIW, there's no need to re-install the kernel package for that, you can just run "update-initramfs -u -k <kernel version>" to update the initrd.

    Leave a comment:


  • funfunctor
    replied
    Michael just post the card to AMD.. @bridgm

    Leave a comment:


  • plasmasnake
    replied
    Originally posted by bridgman View Post
    Now that is seriously weird. Thanks for noting that; there's a chance it might be a clue re: why this doesn't reproduce easily.
    Yes... Same thing here on my R7 260X. Sometimes it would just start working fine after a suspend/resume cycle.


    Originally posted by bridgman View Post
    I'm thinking that there has to be more to this than just kernel driver since the problem does not show on AMDGPU-PRO - maybe X driver or microcode.
    In my case, I'm 100% sure it's the microcode. Because I'm running 4.9 and when I force it to use the old microcode, it works fine: https://bugs.freedesktop.org/show_bug.cgi?id=98988

    Leave a comment:

Working...
X