9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jim Niemira <urmane@urmane.org>
To: 9fans@cse.psu.edu
Subject: [9fans] Plan9 in VMware?
Date: Mon,  5 Feb 2001 09:56:54 +0000	[thread overview]
Message-ID: <95k9is$j6e$1@bob.news.rcn.net> (raw)


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

in my vgadb, which *almost* works.  I can see the video, but it's got
alternating black bands interspersed with the picture pixels, and I can
see, eg, the bar graphs repeated several times diagonally across the
picture, like it's just out of sync or something, but I can't make it any
better.  Tried many other settings and chipsets, to no avail.  Has anyone
made this work? (Under vmware 1, I don't have 2)

I've seen others mention that enabling VMware's ethernet controller causes
it to throw an exception under Plan9; any luck on that?

I'm running XFree86 Version 4.0.1 on a Matrox G400 at 1600x1200x24@75Hz
(but changing that doesn't change the VMware screen's behavior).  Here's my
vgainfo.txt (long):

main->snarf
vga->snarf
trio64->snarf
trio64->snarf->s3generic
vga->dump
vga misc             67
vga feature          00
vga sequencer        03 00 03 00 02
vga crt              5F 4F 50 82 55 81 BF 1F - 00 4F 0D 0E 00 00 05 F0
                     9C 8E 8F 28 1F 96 B9 A3 - FF
vga graphics         00 00 00 00 00 10 0E 00 - FF
vga attribute        00 01 02 03 04 05 14 07 - 38 39 3A 3B 3C 3D 3E 3F
                     0C 00 0F 08 00
vga vmz               4194304
vga apz                     0
vga linear                  0
vga->attr: 0xC002D=PhoenixView(tm) VGA-Compatible BIOS Version
trio64->dump
trio64 Crt30         00 00 00 00 00 00 00 00 - 00 00 00 00 00 00
trio64 Crt40         00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
trio64 Crt50         00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
trio64 Crt60         00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
trio64 hde          280   640
trio64 shb          288   648
trio64 ehb          2AA   682
trio64 ht           320   800
trio64 vde          190   400
trio64 vrs          19C   412
trio64 vre          19E   414
trio64 vt           1C1   449
trio64 Seq08         00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                     00
trio64 Crt2D         00 00 00
trio64 dclk m n r    14318180        0       -        0        0
ibm8514->dump
ibm8514 Advfunc          FFFF
ibm8514 Subsys           FFFF

vmf 0 vmdf 40000000 vf1 0 vbw 75000000
trio64->options
vga->init
s3hwgc->init
s3hwgc->resyncinit on 0x00000800 off 0x00000000
vga->init 0x00000811
trio64->init
trio64->init->s3generic
dbdumpmode
type=multisync75, size=800x600x8
frequency=40000000
x=800 (0x320), y=600 (0x258), z=8 (0x8)
ht=1056 (0x420), shb=840 (0x348), ehb=1000 (0x3E8)
shs=840 (0x348), ehs=1000 (0x3E8)
vt=633 (0x279), vrs=605 (0x25D), vre=607 (0x25F)
hsync=0, vsync=0, interlace=0
vga->dump
vga flag             Uenhanced|Fdump|Finit|Fsnarf
vga misc             EF
vga feature          00
vga sequencer        03 01 0F 00 0A
vga crt              7F 63 68 9D 69 9D277 F0 - 00 60 00 00 00 00 00 00
                    25D 2F257 64 6025D25E A3 -7FF
vga graphics         00 00 00 00 00 50 05 0F - FF
vga attribute        00 01 02 03 04 05 06 07 - 08 09 0A 0B 0C 0D 0E 0F
                     41 FF 0F 00 00
vga clock[0] f       40000000
vga clock[0] d i m      25821        0       -      121
vga clock[0] n p q r        9        0       -        0        2
vga clock[1] f      135000000
vga clock[1] d i m          0        0       -      127
vga clock[1] n p q r       31        0       -        0        3
vga vm a b            8388608        0
vga vmz               4194304
vga apz                     0
vga linear                  0
vga->attr: 0xC002D=PhoenixView(tm) VGA-Compatible BIOS Version
trio64->dump
trio64 flag
Hlinear|Uenhanced|Henhanced|Hpclk2x8|Fdump|Finit|Foptions|Fsnarf
trio64 Crt30         00 8D 40 20 10 00 00 00 - 00 00 10 7A 00 00
trio64 Crt40         00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
trio64 Crt50         80 00 00 00 E8 00 00 00 - 98 00 0A 00 00 00 40 00
trio64 Crt60         FF 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
trio64 Seq08         00 00 00 00 00 00 00 00 - 00 00 49 79 00 02 00 00
                     00
trio64 Crt2D         00 00 00
trio64 dclk m n r    40025821      121       -        9        2
ibm8514->dump
ibm8514 flag         Uenhanced|Fdump
ibm8514 Advfunc          FFFF
ibm8514 Subsys           FFFF

main->exits

--
Jim Niemira                          "Gee, Doc, all I can see is a frog and
urmane@urmane.org            a bear in a rainbow-colored Studebaker."
http://www.urmane.org/~urmane         Max, The Muppet Movie


             reply	other threads:[~2001-02-05  9:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05  9:56 Jim Niemira [this message]
2001-02-05 14:22 ` Ish Rattan
2001-02-13 14:20   ` Jim Niemira
2001-02-13 15:13     ` Christian Smith
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='95k9is$j6e$1@bob.news.rcn.net' \
    --to=urmane@urmane.org \
    --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).