So, I'm at my office and I'm ready to check everything which may help us
solve this problem. First, here is the output of xrandr:
$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 8192 x 8192
DVI-I-1 connected 1600x1200+0+0 (normal left inverted right x axis y axis)
352mm x 264mm
1600x1200 85.0*+ 75.0 70.0 65.0 60.0
1280x1024 85.0 + 75.0 60.0
[...]
DVI-I-2 disconnected (normal left inverted right x axis y axis)
So the card works in 1600x1200. BUT if I execute this:
xrandr --output DVI-I-1 --mode 1600x1200 --scale 0.8x0.8533, xrandr gives
this (just a part again):
$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
DVI-I-1 connected 1600x1200+0+0 (normal left inverted right x axis y axis)
352mm x 264mm
1600x1200 85.0*+ 75.0 70.0 65.0 60.0
1280x1024 85.0 + 75.0 60.0
[...]
and fonts are rendered in a much better (i.e. readable) way.
What may be even more important, if I just use 1280x1024 mode directly
(xrandr --output DVI-I-1 --mode 1280x1024), fonts are crisp and perfectly
rendered. This is why I suppose, that somehow internally, font rendering
either works with a wrong DPI, or wrong resolution. By the way, I'm using
internal font renderer of Xorg, not the external xfs.
> It's most likely about rendering ARGB visuals in the compositor.
> Fonts should be rendered in SW and make no difference. Since konsole is
> by default one of the few ARGB windows and hardly contains anything but
> fonts, it's what you see. But fonts are likely rendered in the client
> (so make no difference from anything else) and showing the picture will
> happen in a 24bit window.
>
> a) what if you suspend compositing (shift+alt+f12, given you're using
> kwin)
It is exactly the same.
> b) what if you use the xrender compositor ("kcmshell4
> kwincompositing", last tab)
Still the same, no difference, just some desktop effects are not available.
> c) what if you run konsole in RGB mode
> ("konsole --nofork --notransparency")
Same here, no difference.
> if all or any of this fixes it, you'll have to clarify whether this
> happens on kwin (GLX) or kwin_gles (guess what) and in the GLX case
> when using OpenGL 2 shaders or not (or that's irrelevant)
>
> If it was on nvidia only i'd btw. guess you've FXAA enabled, but the way
> it is, it actually will rather be a bug in either nouveau or kwin. We
> however got to figure "where".
It happens only with nouveau. With proprietary NVidia drivers there are no
problems.
I'm at office till 4pm (CET), I'm willing to answer all your questions and
check all suggestions for this topic. I hope we'll solve this puzzle
together.
--
Łukasz Maśko _o)
Lukasz.Masko(at)ipipan.waw.pl /\\
Registered Linux User #61028 _\_V
Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana"
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
