https://bugzilla.novell.com/show_bug.cgi?id=331609#c9
--- Comment #9 from Felix Miata
These new RANDR 1.2 drivers are *very* special. Try xrandr --dpi <dpi>/<output> on the running Xserver.
Is there something I'm not understanding about the "/<output>" part of what you
wrote? Is that different from "...xrandr can be used to set a good DPI..." from
comment 0? It was late and I was tired and frustrated by failed workaround
attempts and rereading bug 257746 and the many other other Intel video bugs by
the time I was writing this bug last night. Maybe I failed to clearly spell out
impact of 'xrandr --dpi <dpi>', though indirectly it seems I did via
http://qa.mandriva.com/show_bug.cgi?id=33935#c35. It may show up in attachment
176641, as I ran 'xrandr -dpi 144' just before closing that X session.
As implied in comment 0, I can run 'xrandr -dpi <dpi>' after X starts, e.g. in
Konsole, but it doesn't survive closing the session and so post-session start
it is apparently useless for Kicker and autostarted apps from saved sessions.
How can it be run before KDM/KDE starts so that they are affected by the result
of it too?
To rephrase this bug's summary as if it were an enhancement request, can X
startup be made to automatically call 'xrandr --fbmm' using DisplaySize
dimensions or 'xrandr -dpi' from something like 'Option "DPI"
"