From: "Gary V. Vaughan" <gary@gnu.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rio startup fails in VMWare Fusion 2.0.0
Date: Wed, 24 Sep 2008 11:25:39 +0800 [thread overview]
Message-ID: <90D4E691-8006-4488-AD5D-EFED4A932B65@gnu.org> (raw)
In-Reply-To: <32d987d50809231103m5fcbc055x4cc6a96b2f8d5d11@mail.gmail.com>
Hi Frederico,
Thanks for the response!
On 24 Sep 2008, at 02:03, Federico G. Benavento wrote:
> On Tue, Sep 23, 2008 at 2:08 PM, Gary V. Vaughan <gary@gnu.org> wrote:
>> ...so I thought I'd upgrade to the latest and greatest Fusion
>> release, but
>> things are even worse.
>>
>> If I boot from the iso, and select option '2' for the livecd option
>> and
>> taking the defaults of ps2 mouse, 640x480x8 resolution and xga
>> monitor, I
>> get the following error messages:
>>
>> aux/vga: vgactlw: <linear 0x3e80000 0x0>: unknown vmware id 0740
>> rio: can't open display: initdisplay /dev/draw/new: no frame buffer
>> init: rc exit status: rio 9: display open
>>
>> And then the boot sequence starts /bin/rc, and I get a 'term%'
>> prompt.
>>
>> Is this also related to bit rotted vmware drivers?
>
> try "vesa" for monitor and play with different resolutions
> "aux/vga -m vesa -p" should give you some info.
Using "vesa" for monitor along with all of the resolutions I tried
actually
hangs (i.e. I don't even get a text-mode term% prompt), as does "aux/
vga -m vesa -p"
if I type it at the text mode prompt.
Cheers,
Gary
--
Email me: gary@gnu.org ._(()
Read my blog: http://blog.azazil.net \' )
And my other blog: http://www.machaxor.net =( \
...and my book: http://sources.redhat.com/autobook _(~_)'
next prev parent reply other threads:[~2008-09-24 3:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 16:08 Gary V. Vaughan
2008-09-23 18:03 ` Federico G. Benavento
2008-09-24 3:25 ` Gary V. Vaughan [this message]
2008-09-24 3:30 ` erik quanstrom
2008-11-19 9:53 ` Richard Miller
2008-11-19 11:55 ` Rodolfo kix García
2008-12-14 8:25 ` Ben Calvert
2008-12-14 12:43 ` erik quanstrom
2008-12-14 23:16 ` Ben Calvert
2008-12-14 23:25 ` Ben Calvert
2008-12-22 11:30 ` Tharaneedharan Vilwanathan
2008-12-22 13:39 ` Richard Miller
2008-12-22 14:32 ` Jeff Sickel
2008-12-23 0:15 ` Tharaneedharan Vilwanathan
2008-12-23 4:13 ` Skip Tavakkolian
2008-12-23 11:14 ` Charles Forsyth
2008-12-24 12:46 ` Tharaneedharan Vilwanathan
2008-12-23 0:05 ` Tharaneedharan Vilwanathan
2008-12-23 19:58 ` Richard Miller
2008-12-24 12:27 ` Tharaneedharan Vilwanathan
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=90D4E691-8006-4488-AD5D-EFED4A932B65@gnu.org \
--to=gary@gnu.org \
--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).