9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Scrolling considered harmful
Date: Mon,  6 May 2013 15:24:30 +0200	[thread overview]
Message-ID: <20130506132430.GA414@polynum.com> (raw)
In-Reply-To: <55d102273818f17528b64eab4ebd9b52@coraid.com>

So I have read the various man pages (starting from plan9.ini that only
sets environment values) to vga.

If I understand correctly, the vesa adjusting is only done if the
monitor variable is set to 'vesa', value that do not appear in the
database.

Previously, I have used other values for monitor, trying to match "more"
the monitor capacities. This ended up using vga.

With 'vesa', there is a setting done that is visibly "sent" to the
monitor by the video card (the monitor starts self-adjusting) and the
problem disappears. I have then set vgasize to the maximum value
reported by the VESA modes of the Radeon video card, and what is
announced to be supported by the monitor (the diverse informations
gathered from "aux/vga -p" could allow to add some entries to the video
database).

So, lesson: with a modern monitor, set monitor='vesa' to let the
software/video_card/monitor adjust themselves accordingly.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



      parent reply	other threads:[~2013-05-06 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 13:35 tlaronde
2013-04-23 13:37 ` erik quanstrom
2013-04-23 14:46   ` tlaronde
2013-04-23 15:18     ` erik quanstrom
2013-04-23 16:17       ` tlaronde
2013-05-03 18:51       ` tlaronde
2013-05-03 18:57         ` erik quanstrom
2013-05-03 19:11           ` tlaronde
2013-05-06 13:24           ` tlaronde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130506132430.GA414@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).