drm2 again

[Niclas Zeising]

On 11/1/18 3:55 PM, Steve Kargl wrote:
> On Thu, Nov 01, 2018 at 09:12:32AM +0100, Niclas Zeising wrote:
>> On 10/31/18 11:32 PM, Steve Kargl wrote:
>>> If I compare Xorg.0.log for drm-legacy-kmod to drm-stable-kmod,
>>> the black screen of death seems to be related to this failure in legacy
>>>
>>>    (II) RADEON(0): Setting screen physical size to 508 x 285
>>>    failed to add FB for modeset
>>>    (WW) RADEON(0): Failed to set mode on CRTC 0
>>>    (EE) RADEON(0): Failed to enable any CRTC
>>>
>>> The only other difference in the Xorg.log file are
>>>
>>> legacy contains
>>>
>>>    (II) RADEON(0): mem size init: gart size :1fdef000 vram size: s:40000000
>>>    visible:3f7d7000
>>>    (II) RADEON(0): VRAM usage limit set to 928850K
>>>
>>> while stable has
>>>
>>>    (II) RADEON(0): mem size init: gart size :3fdde000 vram size: s:40000000
>>>    visible:3f4b4000
>>>    (II) RADEON(0): VRAM usage limit set to 925959K
>>>
>>> Note, the system does not have an /etc/X11/Xorg.org file.
>>>
>>
>> Hi!
>> When using drm-legacy-kmod with drm-legacy-kmod you might need to
>> install xf86-video-ati-legacy instead of xf86-video-ati, because of
>> changes in how the kernel drivers work between versions.
>> Regards
> 
> I'll try xf86-video-ati-legacy later today.  This suggests that
> drm-legacy-kmod is not a direct move/replacement of the in-tree
> drm2 into the ports infrastructure as I've always used
> xf86-video-ati.
> 

xf86-video-ati was recently updated, together with xf86-video-amdgpu, to 
provide better support for more modern graphics cards utilizing the new 
drm-kmod drivers.  Unfortunately there were some regressions when using 
the old base driver or drm-legacy-kmod, which prompted us to create 
xf86-video-ati-legacy which is at the version xf86-video-ati was before 
the update.  There's more information about this issue here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231884

Regards
-- 
Niclas Zeising