Date: Sun, 12 Apr 2020 17:17:36 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Grzegorz Junka <list1@gjunka.com>, freebsd-x11@freebsd.org Subject: Re: drm kmod with Vega 3 Message-ID: <e0d95bf8-babb-a9e3-60f8-6c90484067b4@FreeBSD.org> In-Reply-To: <6c8c7e81-8abd-a8d7-f4cf-3e26fc328bcd@gjunka.com> References: <2ca574c4-431e-7387-cea0-7563ef301df7@FreeBSD.org> <6c8c7e81-8abd-a8d7-f4cf-3e26fc328bcd@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/04/2020 15:31, Grzegorz Junka wrote: > > On 11/04/2020 09:15, Andriy Gapon wrote: >> I am trying to get FreeBSD going on Motile M141 notebook that has a Ryzen >> processor with integrated graphics: AMD Ryzen 3 3200U with Radeon Vega Mobile >> Gfx. >> >> So, far, X works only with scfb or vesa depending whether I boot in EFI or >> legacy mode. amdgpu driver from drm kmod package version 4.16.g20200320 does >> not detect the hardware. The driver from drm-devel-kmod version 5.0.g20200320 >> detects the hardware but fails to attach and that makes the screen freeze. >> >> The interesting part of the attach log: >> [drm] PSP loading VCN firmware >> [drm] reserve 0x400000 from 0xf400c00000 for PSP TMR SIZE >> [drm ERROR :psp_cmd_submit_buf] failed loading with status (-53233) and ucode id >> (10) >> [drm ERROR :psp_hw_init] PSP firmware loading failed >> [drm ERROR :amdgpu_device_fw_loading] hw_init of IP block <psp> failed -22 >> drmn0: amdgpu_device_ip_init failed >> drmn0: Fatal error during GPU init >> >> Does anyone have any suggestions or ideas? >> Thank you! >> >> P.S. >> I found this bug report >> https://bugs.freedesktop.org/show_bug.cgi?id=109206 >> but my error code is different and a workaround from the bug report does not >> help. >> >> P.P.S. >> Just in case anyone is interested, here are more details about the notebook: >> https://wiki.freebsd.org/Laptops/Motile_M141 > > > Which kernel / world version is it? Are you compiling kernel / world / packages > yourself or install from binary distributions? If you hint at possible kernel<->module binary incompatibility, then that should not be a problem. The symptoms are quite different. As far as I can see, 4.16.g20200320 simply does not have support for Picasso APUs. 5.0.g20200320 has it, but it appears to be incomplete. I see that the latest Linux driver reports the error (the message has a different format) but does not abort driver loading. I'll try to patch up the driver and test. Commit 466bcb75b0791b seems to be the earliest change in that area. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e0d95bf8-babb-a9e3-60f8-6c90484067b4>