[Bug 199310] [TTM][DRM]Artifact in graphic/Font rendering problem(artifact/gaps/missing characters/black line instead text) with radeon on 10.2/10.3-RC2/3-RELEASE/10-STABLE

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Mar 24 02:38:23 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199310

sasamotikomi at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|www/firefox: Font rendering |[TTM][DRM]Artifact in
                   |problem on 10-STABLE        |graphic/Font rendering
                   |                            |problem(artifact/gaps/missi
                   |                            |ng characters/black line
                   |                            |instead text) with radeon
                   |                            |on
                   |                            |10.2/10.3-RC2/3-RELEASE/10-
                   |                            |STABLE

--- Comment #14 from sasamotikomi at gmail.com ---
(In reply to Koop Mast from comment #13)
This isn't font or firefox(gecko) it's cleanly TTM/DRM regression, same
situation reported with even more powerful graphic but intel(HD4000) on
@freebsd-x11 (with faster acceleration method SNA instead EXA font rendering
back again to normal state) :
1) Some commit to TTM broke it but due problem repeatable on intel graphic too 
it's possibly not TTM itself but AGP in TTM. 
2) Some commit to DRM broke it due I found it before long TTM AGP patch landed
this look reasonable. 
3) No AGP-speed support in sysctl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202408
4) Alternative acceleration method Glamor currently disabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207705
Possible solutions:
1) Update TTM/DRM code to last on (sync with kernel 4.5) due kernel before
~3.18-4.X contains many problems with old GPU.
2) Get to work Glamor.
3) Add sysctl for AGP.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-x11 mailing list