Brian Corrie (bcorrie++at++cs.anu.edu.au)
Wed, 14 Oct 1998 12:30:15 +1000
It looks like the multipipe issue was the cause. gfxinfo output included
below. Managed and displayed area is the same, but it looks like perfly
comes up in multi-pipe mode by default. If I run with perfly -M 0 things
work fine. So the bottom line is that perfly is trying to be too smart and
use our second pipe which isn't connected to anything (yet...). At least
that looks like what is happening to me, correct me if I am wrong 8-)
Thanks for the help folks...
Brian
Graphics board 0 is "KONAL" graphics.
Managed (":0.0") 1280x1024
Display has 2 channels
4 GEs (of 4), occmask = 0x0f
4MB external BEF ram, 32bit path
2 RM7 boards (of 2) 1/1/0/0
Texture Memory: 64MB/64MB/-/-
Medium pixel depth
32K cmap
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 72.00Hz (1280x1024_72.vfo)
Graphics board 1 is "KONAL" graphics.
Managed (":0.1") 1280x1024
Display has 2 channels
4 GEs (of 4), occmask = 0x0f
4MB external BEF ram, 32bit path
2 RM7 boards (of 2) 1/1/0/0
Texture Memory: 64MB/64MB/-/-
Medium pixel depth
32K cmap
Channel 0:
Origin = (0,0)
Video Output: 1280 pixels, 1024 lines, 60.00Hz (1280x1024_60.vfo)
Channel 1:
Channel's Source Size: 1280 pixels, 1024 lines; Origin = (0,0)
Video Output: 640 pixels, 486 lines, 29.97Hz (640x486_30i.vfo)
This archive was generated by hypermail 2.0b2 on Tue Oct 13 1998 - 19:30:29 PDT