Red Hat Bugzilla – Bug 85538
Font rendering much worse than 8.0
Last modified: 2008-05-01 11:38:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211
Description of problem:
I had a Dell Latitude C810 (1.13Mhz PIII) with a 16MB NVidia Geforce2Go running
Redhat 8 using the NVidia binary drivers. I recently upgraded this system to
Phoebe Beta 3.
After applying the appropriate patches to make the Nvidia driver compile with
the Phoebe 2.4.20-2.48 kernel and disabling TLS everything seems to work fine
overall except for font rendering.
Compared to Redhat 8 the font rendering in Phoebe is significantly worse. It
appears to be some type of issue with sub-pixel rendering not fully working or
at least not working as well as the fonts have outlines of blue and red (it
almost make my laptop display look like a CRT with bad convergence).
Playing with the sub-pixel rendering settings does improve the view but in no
case is it anywhere near as clear as with Redhat 8. The problem is also much
less noticable if I run the screen at it's maximum resolution (1600x1200),
however, I usually run at a much lower 1024x768.
I'm not sure what other information I can provide but let me know what else I
can do to help. I don't see any significant changes to the core font rendering
and wonder if the problem could come from the Xserver itself.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot up into 1024x768 mode on Dell Latitude Laptop
Actual Results: Characters are not very clear on laptop display
Expected Results: Characters should be at least as clear as Redhat 8
This appears to be somehow related to an interaction with the NVidia binary
drivers and XFree86 4.3 and not directly related to fontconfig. I downgraded my
XFree to 4.2 from Redhat 8.0 and the font rendering is back to normal. The
standard nv that comes with 4.3 also seems to work correctly.
I will report this issue to NVidia.
Sorry for the eroneous report, I thought I had tested this with the default 'nv'
driver before reporting this, apparently I had not.