maintainer-feedback requested: [Bug 249357] graphics/drm-fbsd12.0-kmod: Doesn't work on AMD E-300 (Radeon HD 6310/PALM) laptop

[bugzilla-noreply at freebsd.org]

Bugzilla Automation <bugzilla at FreeBSD.org> has asked freebsd-x11 (Nobody)
<x11 at FreeBSD.org> for maintainer-feedback:
Bug 249357: graphics/drm-fbsd12.0-kmod: Doesn't work on AMD E-300 (Radeon HD
6310/PALM) laptop
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249357



--- Description ---
I have this old laptop that I've ran FreeBSD on since the 10.x-RELEASE days,
and although slow, it generally works for my needs.  It's powered by an AMD
E-300 APU w/ embedded Radeon HD 6310 GPU (PALM).  On a late ~2019 ZFS BE with
xorg-server-1.18, running 12.1-RELEASE, everything, including
hardware-accelerated compositing, still works.

However, after the xorg-server-1.20 update, hardware-accelerated compositing no
longer works.  It looks like glamor fails to initialize (eglInitialize()
fails), so compiz falls back to software rendering, which is unusable.	I tried
a variety of things, including building xorg-server and mesa from ports, but
nothing works, so all I am left with is trying to get newer KMS drivers to
work.

However, trying drm-fbsd12.0-kmod, when /boot/modules/radeomkms.ko is loaded
during boot (via /etc/rc.conf), the screen will get "frosty", is about how I
can describe it.  It literally looks like it ices over, with this white haze
that quickly spreads out from the edges of the LCD inwards to the center.  The
console text inverts to a medium'ish gray color, like attempting to read a sign
in heavy, dense fog, and the machine is completely locked up.  The only way to
recover is to hard-power the machine off by holding the power button down for
~5 seconds.

I have gone as far as building branch drm-v5.0-fbsd12.1 from the kms-drm github
repo.  Same effect as above.  drm-legacy-kmod is the only KMS drivers that will
work.  I am primarily using the modesetting driver, but have also tried the
radeon driver from x11-drivers/xf86-video-ati to no avail.  I have also updated
the base system to 12.2-BETA1, and that hasn't helped any either.

Open to any ideas for testing.	I'll likely end up just retiring the machine
and moving the drive to something newer, but figured to at least open a bug in
case it turns out to be a silly quick fix.