9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Tharaneedharan Vilwanathan" <vdharani@gmail.com>
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: Mon, 22 Dec 2008 03:30:41 -0800	[thread overview]
Message-ID: <dac0a5820812220330h555ceda0n9b829f60b6c8a07@mail.gmail.com> (raw)
In-Reply-To: <476F09F6-4CF9-43BF-A15C-BC3A7C08B77A@flyingwalrus.net>

[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]

hi all,
not sure if this discussion is continued elsewhere, but i thought i will
share what i found.

i just installed vmware fusion 2.0.1 (128865), downloaded new plan9 CD image
(that probably geoff made yesterday and the one that probably has richard's
vmware vga fix) and tried to install plan9.

vgasize: 640x480x8, monitor: xga - this combo works
vgasize: 1024x768x8, monitor: xga - this combo works

i tried 1280x1024x8 and 1280x1024(?!). it seems to hang. no luck with vesa
also.

is anyone able to get any better resolution with vmware fusion in mac (or
parallels for mac 4.0, if it works for plan9)?

i have 1920x1200 widescreen LCD monitor with DVI and i would like to make
good use of more screen space. so i am trying to go up as much as possible.

with parallels for mac 3.0, i was able to use 1920x1200 but i used this
setup sparingly so far. i also noticed mouse jumps, poor performance or slow
screen updates (e.g. if i open acme window, it would sometimes take 10+
seconds to show the prompt) and some other incomplete screen draw, etc

any help appreciated.

thanks
dharani

On Sun, Dec 14, 2008 at 3:25 PM, Ben Calvert <ben@flyingwalrus.net> wrote:

> Actually, maybe i'm not being fully clear --
>
> rio starts up during the install, but i get the 'vmware id 0740' error when
> logging on afterwards.
>
> On Dec 14, 2008, at 4:43 AM, erik quanstrom wrote:
>
>  On Sun Dec 14 03:28:08 EST 2008, ben@flyingwalrus.net wrote:
>>
>>> Am encountering the same problem, even though i've just pulled down
>>> the latest sources.  Is there something special i should be doing?
>>>
>>> thanks,
>>>
>>> ben
>>>
>>
>> the kernels on sources have not been rebuilt since this
>> patch was put up so it's pretty likely that the kernel on
>> the cd is also older than the patch, too.  the solution is
>> to build your own kernel, but this may be difficult if you
>> don't have a running machine.
>>
>> - erik
>>
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2865 bytes --]

  reply	other threads:[~2008-12-22 11:30 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
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 [this message]
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=dac0a5820812220330h555ceda0n9b829f60b6c8a07@mail.gmail.com \
    --to=vdharani@gmail.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).