[9fans] vga and vmware

[9fans] vga and vmware

[Tim Newsham]

When booting plan9 in vmware the graphics seem to work fine up
to 1024x768x8, but higher resolutions cause a panic trying to
write to a non-existant address.  (Didnt map enough memory for
the screen maybe?)  It seems to put the card in the right mode
and even print out the stack trace onto the highres screen.
Anyone know whats going on here?

-----
panic: kernel fault: bad address pc=0xf01eb43e addr=0xe03c0000
panic: kernel fault: bad address pc=0xf01eb43e addr=0xe03c0000

acid points to libmemdraw/line.c:351

at 1024x768x aux/vga -p says:
vga->attr: vid=0x15AD
vga->attr: did=0x0405
vga misc             E3
vga feature          00
vga sequencer        03 01 0F 00 0A
vga crt              A3 7F 88 9A 86 1A 24 FD - 00 60 00 00 00 00 00 00
                      03 29 FF 80 60 03 04 A3 - FF
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 virtual         0 0
vga panning         off
vga vm a b                  0 3489660928
vga apz             134217728
vga linear                  1
vmware ID            90000002
vmware Enable        00000001
vmware Width         00000400
vmware Height        00000300
vmware MaxWidth      00000938
vmware MaxHeight     000006ea
vmware Depth         00000018
vmware Bpp           00000020
vmware PseudoColor   00000000
vmware RedMask       00ff0000
vmware GreenMask     0000ff00
vmware BlueMask      000000ff
vmware Bpl           00001000
vmware FbStart       d0000000
vmware FbOffset      00000000
vmware FbMaxSize     08000000
vmware FbSize        00300000
vmware Cap           001fc3e2
vmware MemStart      d8000000
vmware MemSize       00200000
vmware ConfigDone    00000001
vmware Sync          00000001
vmware Busy          00000000
vmware GuestID       00005010
vmware CursorID      00000001
vmware CursorX       000002bf
vmware CursorY       000000bd
vmware CursorOn      00000001
vmware HostBpp       00000020
vmware chan          x8r8g8b8
vmware depth         32
vmware linear


Tim Newsham
http://www.thenewsh.com/~newsham/

Re: [9fans] vga and vmware

[Devon H. O'Dell]

2009/8/16 Tim Newsham <newsham@lava.net>:
> When booting plan9 in vmware the graphics seem to work fine up
> to 1024x768x8, but higher resolutions cause a panic trying to
> write to a non-existant address.  (Didnt map enough memory for
> the screen maybe?)  It seems to put the card in the right mode
> and even print out the stack trace onto the highres screen.
> Anyone know whats going on here?

For what it's worth, I'm getting essentially the same in ESXi with
anything over 640x480x8

--dho

Re: [9fans] vga and vmware

[Tim Newsham]

> When booting plan9 in vmware the graphics seem to work fine up
> to 1024x768x8, but higher resolutions cause a panic trying to
[...]
> panic: kernel fault: bad address pc=0xf01eb43e addr=0xe03c0000
> panic: kernel fault: bad address pc=0xf01eb43e addr=0xe03c0000

/dev/vgactl says 0xe0000000 has 0x3c0000 mapped.  Enough for
1024x768x4 bytes but not enoug hfor 1280x1024x4 bytes.  I
patched vgavmware.c line 179 to allocate 2*vmrd(vm, Rfbsize)
instead of vmrd(vm, Rfbsize) and now I'm able to go into 1280x1024x8
mode.  This is obviously just a hack, I don't know what a
real solution would be (is it possible that the hardware register
returns a different size after changing the mode?)

Tim Newsham
http://www.thenewsh.com/~newsham/

Re: [9fans] vga and vmware

[erik quanstrom]

> /dev/vgactl says 0xe0000000 has 0x3c0000 mapped.  Enough for
> 1024x768x4 bytes but not enoug hfor 1280x1024x4 bytes.  I
> patched vgavmware.c line 179 to allocate 2*vmrd(vm, Rfbsize)
> instead of vmrd(vm, Rfbsize) and now I'm able to go into 1280x1024x8
> mode.  This is obviously just a hack, I don't know what a
> real solution would be (is it possible that the hardware register
> returns a different size after changing the mode?)

why would 8 bit color require 4 bytes-per-pixel?

- erik

Re: [9fans] vga and vmware

[Tim Newsham]

>> /dev/vgactl says 0xe0000000 has 0x3c0000 mapped.  Enough for
>> 1024x768x4 bytes but not enoug hfor 1280x1024x4 bytes.  I
>> patched vgavmware.c line 179 to allocate 2*vmrd(vm, Rfbsize)
>> instead of vmrd(vm, Rfbsize) and now I'm able to go into 1280x1024x8
[...]

> why would 8 bit color require 4 bytes-per-pixel?

I don't know.  I just know that the libdraw primitives were
going off the edge of allocated memory and the ctl file said
something about "x8r8g8b8" so I got out the calculator and
noticed that if there are 4 bytes per pixel then I would
expect 1024x768 to fit and 1280x1024 not to.  I plead ignorance
on how the plan9 vga system is actually set up.

> - erik

Tim Newsham
http://www.thenewsh.com/~newsham/