Re: X11 not working on 11-STABLE with AMDGPU

Jung-uk Kim <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]>
On 18. 8. 3., Greg V wrote:
> On Fri, Aug 3, 2018 at 2:16 AM, CL Moonriver
> <[email protected]> wrote:
>> Thanks for the heads up.
>>
>> Are you sure this is still relevant in drm-next? I don't see any dmesg
>> error about disabling GPU acceleration. I did what you suggested, but
>> nothing seems to have changed except I get no text until radeonkms has
>> loaded (I don't get garbage I get nothing at all). I still get dmesg
>> errors regarding ring test failures and such, so turning the EFI
>> framebuffer off doesn't appear to have actually changed anything.
> 
> Interesting. Are you 100% sure you're booting with UEFI, not CSM/legacy?
> 
> Maybe radeonkms doesn't conflict anymore. Maybe this depends on the GPU
> model or something?
> 
> For amdgpu (RX 480), it's not an error about disabling acceleration, the
> amdgpu driver *completely* fails to load when EFI framebuffer is active.
> And I retested a few weeks ago. No one fixed this specifically yet, so
> I'm not expecting it to magically stop conflicting…

It wasn't fixed and some MMIO test still fails.  Actually, both
radeonkms and amdgpu still do not work properly when UEFI is active.  I
don't think it is too hard to fix but I didn't dig deeper at the time.

Jung-uk Kim
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAltodV0ACgkQfJ+WJvzb
8UbZdgf/X2oReJkSWHMYx7nLYED3GD1rGiqVhI5A6RyYKrhfVqLpQeEw2b5dJs/o
dDo2j0pos2nk1TRPsfigvzJxVvIKQRC+SqXt2mPndEQOwaI+FclqFyyXuDL9ZsHe
JfDloliRpWy25QmiPNErCzcz5JjhQkNzUAtUNqywJxOCyoqi4/XuzlLNCYEAjMJ5
34amWg8LAfGIdbOEtpQZ6r/S0MTtnhPrRhjKNpNtZipkH8dh3wdisWkPt6m7loLB
A2B5ZzP40Rlk0C5IkU1yzRM9ONE3rDiKvy2Gk/pgsOTOb1ScZd/f61nIn4YyfodJ
D/OLom8ZrK/jcKe94YtcdWf371SCyg==
=wEOV
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.