From: "Vladimir G. Ivanovic" <vladimir@acm.org>
To: rsc@plan9.bell-labs.com
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] vmware video
Date: Mon, 29 Apr 2002 13:13:44 -0700 [thread overview]
Message-ID: <200204292013.g3TKDir14406@bach.leonora.org> (raw)
In-Reply-To: Your message of "Mon, 29 Apr 2002 14:41:01 EDT." <a31ae3a9522ffb72f5d464179dcf0632@plan9.bell-labs.com>
Russ,
Arrrgh! I've tried
640x480x8
1280x1024x8 [no entry in /lib/vgadb]
1024x768x8
and the value that was set in plan9.ini in vmware.tar.bz2 originally,
1024x768x16
with my X server set to 16 bpp and 24 bpp and I still get the same
display: windows/frames, pastel colors, but no text. My current X screen
is 1600x1200x24.
Any suggestions on what to do next? Is there some info that can be
gleamed from `aux/vga' that would be helpful? (I'm looking at the v3
manuals from Vita Nuova.)
--- Vladimir
[VMware Plan 9 v4 guest and Linux RedHat 7.2 (2.4.17-1smp) host]
--------
Vladimir G. Ivanovic http://leonora.org/~vladimir
2770 Cowper St. vladimir@acm.org
Palo Alto, CA 94306-2447 +1 650 678 8014
"RC" == Russ Cox <rsc@plan9.bell-labs.com> writes:
RC> You can edit the vga resolution by editing
RC> plan9.ini on the 9fat partition. To do this,
RC> log in as none instead of glenda. You'll get
RC> a term% shell prompt. Type:
RC> 9fat:
RC> ed /n/9fat/plan9.ini
RC> and then edit plan9.ini (see ed(1) if you're
RC> not familar with ed). For example
RC> term% ed /n/9fat/plan9.ini
RC> 152
>>> /vgasize
RC> vgasize=640x480x8
>>> s/640x480x8/1024x768x8
RC> vgasize=1024x768x8
>>> w
RC> 153
>>> q
RC> term%
RC> The >> lines are ones you type.
RC> Russ
next parent reply other threads:[~2002-04-29 20:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a31ae3a9522ffb72f5d464179dcf0632@plan9.bell-labs.com>
2002-04-29 20:13 ` Vladimir G. Ivanovic [this message]
2002-04-30 5:18 ` Taj Khattra
2002-05-03 15:01 Russ Cox
2002-05-07 12:00 ` Quentin Fennessy
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 21:37 Russ Cox
2002-04-30 16:35 ` FODEMESI Gergely
2002-05-03 8:45 ` Quentin Fennessy
2002-04-29 10:45 nigel
2002-04-29 5:46 Vladimir G. Ivanovic
2002-04-28 17:45 Russ Cox
2002-04-28 19:01 ` David P. Boswell
2002-04-28 21:09 ` paurea
2002-04-28 21:57 ` Taj Khattra
2002-04-29 9:44 ` Vladimir G. Ivanovic
2002-04-28 4:15 [9fans] 4th edition vmware install problem Russ Cox
2002-04-28 5:11 ` [9fans] vmware video vic
2002-04-28 7:57 ` paurea
2002-04-28 12:25 ` paurea
2002-04-29 9:40 ` didi
2002-04-29 9:44 ` Vladimir G. Ivanovic
2002-04-29 16:08 ` Vangoh
2002-04-29 9:40 ` vic
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=200204292013.g3TKDir14406@bach.leonora.org \
--to=vladimir@acm.org \
--cc=9fans@cse.psu.edu \
--cc=rsc@plan9.bell-labs.com \
/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).