From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 6 May 2013 15:24:30 +0200 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130506132430.GA414@polynum.com> References: <20130423133534.GC19997@polynum.com> <39c4acf762ed52f1b9ddfef167d8166a@brasstown.quanstro.net> <20130423144653.GB461@polynum.com> <84f73a4bc77a38e2f767aff4ef7ac020@coraid.com> <20130503185151.GA948@polynum.com> <55d102273818f17528b64eab4ebd9b52@coraid.com> Mime-Version: 1.0 In-Reply-To: <55d102273818f17528b64eab4ebd9b52@coraid.com> User-Agent: Mutt/1.4.2.3i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [9fans] Scrolling considered harmful Topicbox-Message-UUID: 5769ec58-ead8-11e9-9d60-3106f5b1d025 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 http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C