| View previous topic :: View next topic |
| Author |
Message |
yem
n00b
Joined: 05 Nov 2002
Posts: 63
Location: Aotearoa
|
 Posted: Thu Aug 05, 2004 8:21 am Post subject: S3 Savage DDR TV-out |
 |
|
So apparently the savage driver supports TV out (at least since 1.1.25t). I have a Shuttle SK41G that has this chipset and an onboard S-Video out. I'm also using PAL, not NTSC, but I don't think that matters as you'll see.
From /var/log/Xorg.0.log:
| Code: | (II) SAVAGE: driver (version 1.1.27) for S3 Savage chipsets: Savage4,
Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133,
ProSavage PN133, ProSavage KN133, SuperSavage/MX 128,
SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128,
SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64,
SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR,
ProSavage DDR-K
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset ProSavage found
...
(**) SAVAGE(0): Depth 24, (--) framebuffer bpp 32
(==) SAVAGE(0): RGB weight 888
(==) SAVAGE(0): Default visual is TrueColor
(II) SAVAGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(**) SAVAGE(0): Option "UseBIOS" "off"
(**) SAVAGE(0): Option "TvOn"
(**) SAVAGE(0): Option "PAL"
(==) SAVAGE(0): Using HW cursor
(**) SAVAGE(0): Not using video BIOS to set modes
(**) SAVAGE(0): TV enabled in PAL format
...
(II) LoadModule: "vbe"
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.7
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 31680 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Graphics ProSavage DDR Family BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Garphics Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 3.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 0.0
(--) SAVAGE(0): Chip: id 8d04, "ProSavage DDR-K"
(--) SAVAGE(0): Engine: "ProSavage"
(--) SAVAGE(0): mapping MMIO @ 0xe0000000 with size 0x80000
(==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
(**) SAVAGE(0): videoram = 31680k
(--) SAVAGE(0): Detected current MCLK value of 14.318 MHz
(II) SAVAGE(0): My Monitor: Using hsync range of 31.50-35.10 kHz
(II) SAVAGE(0): My Monitor: Using vrefresh range of 40.00-150.00 Hz
(II) SAVAGE(0): Clock range: 10.00 to 220.00 MHz
(II) SAVAGE(0): Not using default mode "640x350" (hsync out of range)
(II) SAVAGE(0): Not using default mode "320x175" (hsync out of range)
...
(--) SAVAGE(0): Virtual size is 800x600 (pitch 800)
(**) SAVAGE(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) SAVAGE(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync
(**) SAVAGE(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) SAVAGE(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync
(**) SAVAGE(0): Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) SAVAGE(0): Modeline "400x300" 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync
(**) SAVAGE(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) SAVAGE(0): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync
(==) SAVAGE(0): DPI set to (75, 75) |
Then X comes up on the CRT instead. Note the "TV enabled in PAL format" line.
I've also tried the 1.1.27t and 1.1.27t (xfree 4.4) drivers from the Probo site. I'm running x11-base/xorg-x11-6.7.0-r1.
Any ideas? This box will be do TV recording and playback duties. I'd really like to get the onboard S-Video working if at all possible because the only other option is to install a low end nvidia card in the box which just adds more heat to the system.
Anyone sucessfully got TV-out working on the S3 Savage chipset? |
|
| Back to top |
|
 |
yem
n00b
Joined: 05 Nov 2002
Posts: 63
Location: Aotearoa
|
| Posted: Thu Aug 05, 2004 8:47 am Post subject: |
|
|
| Just rebooted with the CRT disconnected, which forces console output to the tv-out by default. Now, X still wont start with the savage driver. BUT it does start up if I use the vesa driver. I hear the vesa driver isn't the greatest in terms of performance and features though so still keen to get the savage driver working... |
|
| Back to top |
|
|
yem
n00b
Joined: 05 Nov 2002
Posts: 63
Location: Aotearoa
|
| Posted: Fri Aug 06, 2004 1:02 pm Post subject: |
|
|
This may be of some use to people or maybe I'm just dense. 
The savage driver does work for TV out, IF you boot without a CRT connected. At least with the SavageDDR chipset, it does support the xvideo extension so fullscreen playback doesn't tax the CPU for scaling. Sweeeet.
The resulting video still doesn't completely fill my TV screen when fullscreened, but I suspect this is due to the Unichrome TV encoder chipset - not software. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
