hi charles,
thanks for the details.
via draw.) this is on a 1.2Ghz core duo on ubuntu 8.04. it "didn't seem
> too bad"
> (ie, not unusable) but it probably isn't as responsive as under plan 9
> proper
yes, in cases like this, it is usable but the noticeable lag and the
relatively slow updates m
hi richard,
thanks for the info. both 1280x768x8 and 1280x768x24 work for me. i am
working on some (unrelated) issues, after which i will try more
combinations.
thanks
dharani
On Tue, Dec 23, 2008 at 11:58 AM, Richard Miller <9f...@hamnavoe.com> wrote:
> > btw, what was your plan9.ini config? di
> btw, what was your plan9.ini config? did it look like:
>
> vgasize=1280x800
> monitor=macbook (or xga?, sorry i am not sure about this)
Before changing vgadb, I had success with:
vgasize=1280x768x24
monitor=cinema
> and, since we are in VM, does the native resolution really ma
>tested so far, drawterm, 9vx are all so slow in updating inferno screen (i
i tried running inferno in an 1152x900 x8r8g8b8 within 9vx. (the window is
controlled by rio in 9vx but even then emu's draw operations go direct to the
9vx kernel
via draw.) this is on a 1.2Ghz core duo on ubuntu 8.04.
if you setup dedicated machines for cpu+auth and fs, then booting a pc kernel
on a vmware and booting from fs works very well as a term.
> hi jeff,
>
> i agree. somewhere down the line, i will probably stick to this method.
>
> but my problem is i use inferno and acme in inferno a lot. to the ex
hi jeff,
i agree. somewhere down the line, i will probably stick to this method.
but my problem is i use inferno and acme in inferno a lot. to the extent i
tested so far, drawterm, 9vx are all so slow in updating inferno screen (i
think it becomes a matter of screen area updates all the time inst
hi richard,
i tried various combinations:
1280x1024
1280x800
1152x768
1920x1200
(i tried combinations like with x8, x24, x32 (not x16 i think)). nothing
seems to help. 1920x1200 looked like it turned the graphics mode on but then
it crashed.
btw, what was your plan9.ini config? did it look like:
On Dec 22, 2008, at 8:39 AM, Richard Miller <9f...@hamnavoe.com> wrote:
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
> 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
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.
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, b...@flyingwalrus.net wrote:
Am encountering the same problem,
well, i have a prompt.
i'll google about and see if i come up with instructions for compiling
the kernel...
On Dec 14, 2008, at 4:43 AM, erik quanstrom wrote:
On Sun Dec 14 03:28:08 EST 2008, b...@flyingwalrus.net wrote:
Am encountering the same problem, even though i've just pulled down
t
On Sun Dec 14 03:28:08 EST 2008, b...@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
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
On Nov 19, 2008, at 3:55 AM, Rodolfo kix García wrote:
Thanks Richard.
  aux/vga: vgactlw: : unknown vmware id
0740
It was picking up
Thanks Richard.
>>Â Â aux/vga: vgactlw: : unknown vmware id 0740
>
> It was picking up the wrong pci device - 15AD/0740 is a "virtual machine
> communication interface", not the virtual vga controller.
>
> Fixed by new version of /sys/src/9/pc/vgavmware.c now on sources.
>
>
>
--
Rodolfo Garc
> aux/vga: vgactlw: : unknown vmware id 0740
It was picking up the wrong pci device - 15AD/0740 is a "virtual machine
communication interface", not the virtual vga controller.
Fixed by new version of /sys/src/9/pc/vgavmware.c now on sources.
> 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.
ah! vmware seems to be doing a much
better job these days of emulating real
live har
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 <[EMAIL PROTECTED]> 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,
try "vesa" for monitor and play with different resolutions
"aux/vga -m vesa -p" should give you some info.
On Tue, Sep 23, 2008 at 2:08 PM, Gary V. Vaughan <[EMAIL PROTECTED]> wrote:
> ...so I thought I'd upgrade to the latest and greatest Fusion release, but
> things are even worse.
>
> If I boot
19 matches
Mail list logo
