From: mz721@gmx.com   
      
   On 2/05/2023 4:35 pm, Mike Spencer wrote:   
   > Finally dumped my big 19" 4:3 CRT monitors.  Happy with a new 24" 16:9   
   > for the new(er) Slack 15.0 box.  Now have the old 14.2 Pentium 4 on a   
   > nice used HP L1950 monitor I was given.  It defaults to using 1024x768   
   > where text is big enough for old eyes but it's a 5:4 monitor and images   
   > are distorted.  Thanks to pointers here on a.o.l.s to xrandr, this   
   >   
   > bogus% cvt -v 1280 1024   
   >   
   >        Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 \   
   >        1034 1063 -hsync +vsync   
   >   
   > bogus% xrandr --newmode "1280x1024_60.00"  109.00  1280 1368 1496 1712 \   
   >         1024  1027  1034 1063 -hsync +vsync   
   >   
   > bogus% xrandr --addmode VGA1        1280x1024_60.00   
   > bogus% xrandr --output  VGA1 --mode 1280x1024_60.00   
   >   
   > fixes X when it matters.  At the cost of smaller text, round things   
   > aren't egg-shaped. All good with X.   
   >   
   >   
   > But the console is still a problem.  Two lines of text at the top of   
   > the screen are random bits and text on those lines is invisible   
   > although the software -- emacs, less etc. -- thinks it's using them.   
   > Is there away to convince the system to render the two lines of text   
   > that are "there" but not rendered?   
   >   
   > bogus% stty -a                    rows 24   
   >   
   > bogus% stty rows 26               'standard input': Invalid argument   
   >   
   > bogus% tty   
   >         /dev/tty2   
   >   
   > bogus% stty -F /dev/tty2 rows 26    /dev/tty2: Invalid argument   
   >   
   >   
   > I obviously don'tknow what I'm doing with stty.  Any suggestions?   
   >   
   >   
   >   
   On 2/05/2023 4:35 pm, Mike Spencer wrote:   
    > Finally dumped my big 19" 4:3 CRT monitors.  Happy with a new 24" 16:9   
    > for the new(er) Slack 15.0 box.  Now have the old 14.2 Pentium 4 on a   
    > nice used HP L1950 monitor I was given.  It defaults to using 1024x768   
    > where text is big enough for old eyes but it's a 5:4 monitor and images   
    > are distorted.  Thanks to pointers here on a.o.l.s to xrandr, this   
    >   
    > bogus% cvt -v 1280 1024   
    >   
    >        Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024   
   1027 \   
    >        1034 1063 -hsync +vsync   
    >   
    > bogus% xrandr --newmode "1280x1024_60.00"  109.00  1280 1368 1496 1712 \   
    >         1024  1027  1034 1063 -hsync +vsync   
    >   
    > bogus% xrandr --addmode VGA1        1280x1024_60.00   
    > bogus% xrandr --output  VGA1 --mode 1280x1024_60.00   
    >   
    > fixes X when it matters.  At the cost of smaller text, round things   
    > aren't egg-shaped. All good with X.   
    >   
    >   
    > But the console is still a problem.  Two lines of text at the top of   
    > the screen are random bits and text on those lines is invisible   
    > although the software -- emacs, less etc. -- thinks it's using them.   
    > Is there away to convince the system to render the two lines of text   
    > that are "there" but not rendered?   
    >   
    > bogus% stty -a                    rows 24   
    >   
    > bogus% stty rows 26               'standard input': Invalid argument   
    >   
    > bogus% tty   
    >         /dev/tty2   
    >   
    > bogus% stty -F /dev/tty2 rows 26    /dev/tty2: Invalid argument   
    >   
    >   
    > I obviously don'tknow what I'm doing with stty.  Any suggestions?   
    >   
    >   
      
   I am much less of an expert than most here, so this is likely to be   
   useless, but FWIW ... from my experience, if you do not want/need   
   framebuffer graphics in the ttys (eg you don't want/need fim, fbgs,   
   netsurf-fb etc), you can run them as text-only consoles by blacklisting   
   any framebuffer kernel modules. X will AFAIK work fine without a   
   framebuffer device (that is, no /dev/fb0), so should not be affected.   
      
   If I was having your issue and  the framebuffer _was_ enabled, I would   
   disable it and reboot (lsmod | grep *fb should show you if you have a   
   framebuffer module loaded -- if /dev/fb0 exists, you probably do). You   
   could also try using a differnt framebuffer kernel module.   
      
   If I was having your issue and the framebuffer _was not_ enabled, I   
   would enable it -- maybe unblacklist a suitable fb module. You can test   
   that using modprobe. Just load a suitable fb module -- is is vesafb or   
   uvesafb or something -- and see if it looks any better.   
      
   Easy and worth a try.   
      
   If it is a really old video card, you can try the old 'named' fb   
   drivers, like s3fb and all that. I have a very old laptop that works   
   with sisfb, for example.   
      
   PS I like CRTs. But I like to use them with light text on black (like   
   the old green or amber on black VTs), so no brightness issues there no   
   matter what the monitor technology!   
      
      
      
    >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)