From: Christian Smith <csmith@micromuse.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 in VMware?
Date: Tue, 13 Feb 2001 15:13:17 +0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0102131510070.9468-100000@erol.dev.net> (raw)
In-Reply-To: <96bdci$52l$1@bob.news.rcn.net>
Grr, all plan9 needs is a VESA 2.0 video driver. I know someone has talked
about doing this (can't remember the reference,) and I intend to have a go
myself once I've got plan9 up and running. Then we can dump all this
reliance on bios signatures etc.
I have to say, the way plan9 handles this stuff is surprisingly archaic!
Christian (frustrated at not being able to use dumb frame buffers!)
On Tue, 13 Feb 2001, Jim Niemira wrote:
>Ish Rattan wrote:
>> On Mon, 5 Feb 2001, Jim Niemira wrote:
>> > I can run Plan9 in VMware, but cannot get the video running correctly.
>> > Can it be done? I've got:
>> >
>> > monitor=multisync75
>> > vgasize=800x600x8
>> >
>> > in my plan9.ini file (monitor=vga and 640x480 gives the same results),
>> > and:
>> >
>> > ctlr
>> > 0xC002D="PhoenixView(tm) VGA-Compatible BIOS Version"
>> > link=vga
>> > hwgc=s3hwgc
>> > ctlr=trio64
>> > link=ibm8514
>>
>> Under Vmware the actual hardware is not available. You have to use the
>> the hardware emulated.. No idea about graphics crad but ether is NE2001
>> (AMD Lance)
>
>
>I know this; the gfx card is that text line in the ctlr stanza, which I
>pulled out of vgainfo.txt. But it looks like the refresh rate is off (if
>there is such a thing for vmware). I've tried lots of different settings;
>has anyone got one that works? Thanx!
>
>jim
>
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
next prev parent reply other threads:[~2001-02-13 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 9:56 Jim Niemira
2001-02-05 14:22 ` Ish Rattan
2001-02-13 14:20 ` Jim Niemira
2001-02-13 15:13 ` Christian Smith [this message]
2001-02-13 19:56 Russ Cox
2001-02-13 21:28 ` Christian Smith
2001-02-13 21:34 ` Scott Schwartz
2001-02-13 22:24 forsyth
2001-02-14 12:49 rog
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=Pine.LNX.4.21.0102131510070.9468-100000@erol.dev.net \
--to=csmith@micromuse.com \
--cc=9fans@cse.psu.edu \
/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).