Felix Miata posted on Sun, 20 Jul 2014 22:50:27 -0400 as excerpted:
> The way I remember it, since I've not tried in a long time, is that
including a display subsection is totally pointless when the driver in
> use is KMS, meaning FOSS, for intel, nouveau & radeon. Since KMS went
> mainstream, I have had display subsections configured only for legacy
> intel (810), r128, mga and sis gfxchips, all of which see little
> uptime here any more. For those old chips virtual still works, but
> with KMS, panning since server 1.10.3 or whatever was latest when
> https://bugs.freedesktop.org/show_bug.cgi?id=39949
> was filed only works via xrandr, hence the quoted bug report.
Thanks. That's very possibly what I ended up doing here too, because as
I said I don't quite remember whether I ended up having to use xrandr
or whether I got the display subsection stuff working. Tho whichever I
used I did get the big virtual desktop working, but of course that was on
a full kde session since I do a CLI login and then startx.
If I were to guess what might be necessary to get *dm working that way
with xrandr as well, obviously before login, I'd guess the script would
have to run as root, probably using the $DISPLAY variable to point at the
appropriate VT to apply the xrandr commands to.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
