From: mds@bogus.nodomain.nowhere   
      
   Jimmy Johnson  writes:   
      
   > I just installed 'arandr' from the link I gave you, none of the stuff I   
   > snipped was needed, now it's easy to setup my monitors in a GUI   
   > application. You may want to give it a try. Then you can think me. :)   
      
   s/ink/ank/ ? :-)  Don't get me wrong, I'm grateful for any help I can   
   get.  But we seem to be having an orthogonal conversation.   
      
   AFAICT, arandr and xrandr do monitor tricks for X.  Not for ttyn.   
      
   I have X working fine with Slack 14.2, the i915 chipset and HP L1950   
   5:4 monitor.  I can write a shell script to do the only mode switch   
   within X that might occasionally be needed.  I've already done that   
   for my 24" 16:9 with Slack 15.   
      
   My problem remains that when switching from X to a console, say tty2,   
   the top two lines of the screen are bit garbage while the software --   
   emacs, less, whatever -- thinks there're two lines there.  If stty or   
   fbset should be able to fix that, I haven't figured out how yet.  The   
   "ioctl FBIOPUT_VSCREENINFO: invalid argument" error message from fbset   
   seems to be a stumper.  /dev/fb0 exists but console reports itself as   
   tty2.   
      
   I'm getting a rendering on the screen that doesn't match what the   
   software thinks is there.  I'd like to know how to fix the text   
   console as nicely as xrandr has already fixed the X display.   
      
   > ...now it's easy to setup my monitors in a GUI application. You may   
   > want to give it a try.   
      
   Not keen on GUI alternatives.  Use X, twm, no desktop.  Command line   
   and shell scripts the favored mode.  Cranky old geezer, y'know? ;-)   
      
   --   
   Mike Spencer                  Nova Scotia, Canada   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)