Re: drm-kmod: AMD Ryzen Vega 8?

Grzegorz Junka <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]>
On 06/08/2019 01:23, Greg V wrote:
> On August 5, 2019 9:19:20 PM GMT+03:00, Grzegorz Junka <[email protected]> wrote:
>> On 05/08/2019 16:21, Greg V wrote:
>>> Though ACPI/EFI/etc related memory mapping improvements happened very
>>> very recently. I'll retest once again.
> Update: still, not disabling efifb and launching a display server causes a corrupted image and freezes the system.


Does it give any clue why it works on my desktop? I see a message about 
switching efifb to fb, is that the disabling you mean here?

Should I expect any problems when switching to drm 5 later?


>> I think the
>> amdgpu module loads but fails to initialize the graphics card since
>> after that I don't see any other drm messages. I am getting the same
>> message ([drm] amdgpu kernel modesetting enabled.) when I try to load
>> amdgpu manually from the command line after the system is fully booted
>> ("kldload amdgpu").
> No no no, if a GPU driver *fails*, it makes a lot of noise. If it only shows "enabled", it did not find any supported GPUs at all.
>
> Which would make sense if you're on the packaged 4.16 drm, as support for VegaM was added later. You need to install 5.0 from git.
>
> By the way: loading amdgpu only on that laptop would probably be pointless, you need to keep i915kms loaded and then kldload amdgpu.
>

Yes, of course, I don't load amdgpu, just i915. Otherwise the graphics 
isn't accelerated.

Do you mean that with drm 5 I will be able to use amdgpu instead of 
i915? What about switching between the two graphics cards, which I 
thought isn't supported?

Thanks
GrzegorzJ

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
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.