(edit: no idea what sax2 is, even after looking at the website... /edit)
nvtv is not going to work on your card, it's too new. I have a similar hardware setup to you (nforce2, 6600gt), though I'm using KDE (I assume you're using gnome). When I first setup TV out, it was with a dual-screen setup which had a separate desktop on the TV, virtually above my monitor. like so:
Code:
Section "ServerLayout"
Identifier "dual"
Screen 0 "CRT" 0 0
Screen 1 "TV" Above "CRT"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
Option "Xinerama" "off"
EndSection
with this setup, I would browse to, and run the file I wanted to play on the TV's desktop. This turned out to be rather tedious(nothing fits on the screen at 640x480, and it's impossible to read text at higher resolutions), but it's the best option (that I know of at least) if you want to use the TV to play video and do things on the monitor(s) at the same time.
now though, I just use a regular single-monitor setup for my desktop, and launch another X server to the TV when I want to watch something, instead of having a desktop on the TV all the time. I use mplayer, but I'm sure you could use whatever player you want.
my current serverlayout(s) look like this:
Code:
Section "ServerLayout"
Identifier "default"
Screen "CRT"
InputDevice "mouse" "CorePointer"
InputDevice "keyboard" "CoreKeyboard"
EndSection
Section "ServerLayout"
Identifier "TV"
Screen "TV"
InputDevice "mouse" "CorePointer"
InputDevice "keyboard" "CoreKeyboard"
EndSection
and I use a basic script to launch an X server to display :1 with -layout TV, run mplayer, and set some nvidia settings so the video syncs to the TV and doesn't tear on panning shots and high-motion stuff.
Code:
#!/bin/sh
/usr/X11R6/bin/X :1 -layout TV &
export DISPLAY=:1
xhost localhost
# or modify startx to create 2 magic cookies at startup:
# authdisplay=${display:-:0 :1} <--edit in the :1
# and prepend DISPLAY=:1 to all commands to be run on :1
nvidia-settings -a :1.0/SyncToVBlank=1 &
nvidia-settings -a :1.0/AllowFlipping=1 &
nvidia-settings -a :1.0/XVideoTextureSyncToVBlank=1 &
nvidia-settings -a :1.0/XVideoBlitterSyncToVBlank=0&
nvidia-settings -a :1.0/XVideoSyncToDisplay=256 &
nvidia-settings -a :1.0/TVOverScan[TV-0]=20 &
#sleep 1 &
mplayer -fs -vo gl2 -cache 20000 -stop-xscreensaver "$*"
this is no good if you want to play a video on the TV and work on the monitor at the same time though, and if you VT-switch from the TV to monitor and back, the nvidia-settings are un-set (reminding me of how unimpressed I was with nvidia's drivers on windows, but that's a whole other rant).
A couple notes on nvidia's drivers: with the last version (8762), the nvidia-settings would not always get set, it was hit and miss (that's why the sleep command was in there, not that it helped), the new version (8774) doesn't have this issue (yay). The issue the current version retains however is this: if you go back and forth from X to standard VTs a lot, get used to the idea of not use the framebuffer console - once you run something on a display connected through s-video, attempting to leave X to go to the console will result in a
totally borked display, but you'll still be able to enter commands and such (to reboot obviously), you just won't be able to see any typos you make(ctrl alt del works nicely here). using a standard VGA console eliminates this issue. not as nice as a 1024x768 framebuffer console, but thems the breaks I guess.
not sure of any other ways to do it, hope that helps. I'll to try help more if I can, but I got this set up basically through trial-and-error so no promises.
If I can do some minimal thread-hijacking here, can anyone tell me if there's a simple way I can tie the X server in my script to mplayer, so that when mplayer gets to the end of the video and quits, it takes down the X server with it??