[mythtv-users] Video card problem (Geforce2 vs. Savage 2000)

[James Fidell]

Quoting Ray Olszewski (ray at comarre.com):

> Yes: the standard Savage X driver supports TV-out, though you may need the 
> "s3switch" utility to turn TV-out on.

Well, setting TvOnly and PAL options in XFree86Config turn off the
display on the monitor at least, so perhaps I won't need that.

> No: The Savage X driver does not support xv (xVideo) on the Savage 2000. 
> The developer classes this as an unresolved bug, but it has been unresolved 
> for a long time now, so don't hold your breath. xShm works (with xine, for 
> example), but it consumes a lot of CPU cycles so is probably not a good 
> option for Myth.

This does appear to be a problem.  I've downloaded the latest X drivers
and get a blank screen with the correct sound when I try to watch anything.
The Savage driver web page suggests that this is only a problem in 24-bit
mode.  It doesn't work for me in 16-bit or 8-bit mode though.

Can myth be forced to use xShm (and if so, how)?  Or do I have to remember
how X works and do some coding to make that happen?

As an aside, the strangest thing is this output from the X logs:

(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 32768 kB
(II) SAVAGE(0): VESA VBE OEM: NV Incorporated. MX / MX400
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: NV Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: MX / MX400 
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev C
(--) SAVAGE(0): Chip: id 9102, "Savage2000"
(--) SAVAGE(0): Engine: "Savage2000"
(--) SAVAGE(0): mapping MMIO @ 0xef800000 with size 0x80000
(==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
(--) SAVAGE(0): probed videoram:  32768k

Clearly the card is recognised as a Savage 2000, but it definitely *says*
it's an nVidia card.

James