From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <90D4E691-8006-4488-AD5D-EFED4A932B65@gnu.org> From: "Gary V. Vaughan" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <32d987d50809231103m5fcbc055x4cc6a96b2f8d5d11@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 24 Sep 2008 11:25:39 +0800 References: <32d987d50809231103m5fcbc055x4cc6a96b2f8d5d11@mail.gmail.com> Subject: Re: [9fans] rio startup fails in VMWare Fusion 2.0.0 Topicbox-Message-UUID: 13a83f5a-ead4-11e9-9d60-3106f5b1d025 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 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: : 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 _(~_)'