On Thu, 21 May 2020 16:07:59 +0200
Laurent Vivier <laurent(a)vivier.eu> wrote:
Le 21/05/2020 à 15:57, Laurent Vivier a écrit :
> Le 21/05/2020 à 14:40, Maurizio M a écrit :
>> I made the fix, and submitted it to the kernel. AMD then accepted
>> and merged it. Void Linux ships the fix ahead of time (included in
>> 5.6.8 there) but other distros are free to pick it up if they want
>> to. Or eventually, it'll appear in some 5.6 bugfix release, I
>> don't know which.
>
> According to;
>
>
https://forums.raptorcs.com/index.php/topic,100.msg915.html#msg915
>
> Seems to be:
>
>
https://lists.freedesktop.org/archives/amd-gfx/2020-April/049082.html
>
> it has been merged upstream in kernel v5.7-rc5:
>
> 59dfb0c64d38 ("drm/amd/display: work around fp code being emitted
> outside of DC_FP_START/END")
And in linux stable v5.6.13:
6f0d234dad15 ("drm/amd/display: work around fp code being emitted
outside of DC_FP_START/END")
and the Void Linux guy confirmed to me a while ago it works OK in the
mainline 5.6.13. So Maurizio must have some other issue as well and we
need more information.
https://wiki.raptorcs.com/wiki/Enabling_Navi_10_On_Fedora_31 says the
fast-reboot feature must be disabled, because the cards can't
reinitialize with a different firmware version.
Maurizio, what hardware do you use? Talos, Blackbird, ...? Do you use
the AMD card for the skiroot environment (to control petitboot)? Do you
have a firmware loaded in BOOTKERNFW partition in the PNOR flash
(
https://wiki.raptorcs.com/wiki/Add_GPU_Firmware_To_BOOTKERNFW)? What
symptoms do have (kernel crash, no output at all, ...)?
Dan