drm2 again

[Johannes Lundberg]

On Thu, Nov 1, 2018 at 2:57 PM Steve Kargl <sgk at troutmask.apl.washington.edu>
wrote:

> On Thu, Nov 01, 2018 at 08:30:08AM +0000, Johannes Lundberg wrote:
> > On Wed, Oct 31, 2018 at 10:32 PM Steve Kargl <
> > sgk at troutmask.apl.washington.edu> 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.
> > >
> >
> > As for legacy I can't find any functional changes for the kernel
> drivers..
> > I will look over the firmware code again today, see if I find anything.
> >
> > Just out of curiosity, did you try drm-devel-kmod?
> >
>
> I haven't tried drm-devel-kmod.  I assumed that if my hardware
> wasn't supported by drm-stable-kmod, it would not be supported
> in -devel-.  I'll try -devel- later today.
>

Recently -devel has been improved to include i386 support. It might also
have other improvements that could help in your case.
There are also reports in the ML from someone using -stable or -devel on
the same hardware as you. Maybe that was -devel?

-- 
> Steve
> 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
> 20161221 https://www.youtube.com/watch?v=IbCHE-hONow
>