From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Scrolling considered harmful
Date: Tue, 23 Apr 2013 16:46:53 +0200 [thread overview]
Message-ID: <20130423144653.GB461@polynum.com> (raw)
In-Reply-To: <39c4acf762ed52f1b9ddfef167d8166a@brasstown.quanstro.net>
On Tue, Apr 23, 2013 at 09:37:14AM -0400, erik quanstrom wrote:
> >
> > Indeed, nasty things arise when some program is spitting a huge amount
> > of text; window is blocking while there is more; I then, in the middle
> > of the process, switch to scrolling.
> >
> > The nasty thing is writing in memory in the wrong place, since the
> > machine is hard frozen, and even soft reboot does no cure (I need to
> > halt and switch power off to have a really cold reboot).
>
> what driver are you using? i assume that this is the standard pc kernel?
Yes, it is the standard pc kernel. And I'm using vesa:
mouseport=ps2
monitor=vesa
vgasize=800x600x16
with a:
ATI Technologies Radeon 9200SE 5964 (rev. 0x01)
BTW, I had no problem before having to change the monitor. The new one
is a 20" LCD, and the thing can "decide" parameters on its own. With the
old monitor, I had not this...
Since the new monitor is also with "screen" ratio (1600x900), I wonder
if my untouched:
vgasize=800x600x16
can not be a problem (because I can also switch to scrolling and
resizing the window because lines wrap...). If the ratio is not to its
taste, there may be a buffer reserved for some size, with the hardware
(monitor/card) deciding for something else?
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2013-04-23 14:46 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 [this message]
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
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=20130423144653.GB461@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).