radeonhd + TVOut

[null56]

Yes, you was right... but my xorg outputs all screen in one display.
How to split it?

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1400 x 1400
S-video connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
DVI-1 disconnected (normal left inverted right x axis y axis)
DIN disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm

My xorg.conf

Section "ServerLayout"
        Screen      0  "Screen0" 0 0
EndSection

Section "Monitor"
        Identifier   "Monitor0"
EndSection

Section "Monitor"
        Identifier   "Monitor-TV"
        Option       "PreferredMode" "800x600"
#       Option      "RightOf" "Monitor0"
EndSection

Section "Device"
        Option      "ATOMTvOut"                 "true"
        Option      "Screen"                   "2"
        Option      "Monitor-DVI-0"             "Monitor0"
        Option      "Monitor-S-video"           "Monitor-TV"
        Identifier  "Card0"
        Driver      "radeon"
        VendorName  "ATI Technologies Inc"
        BoardName   "RV570 [Radeon X1950 Pro]"
        BusID       "PCI:1:0:0"
EndSection

Section "Screen"
        Identifier "Screen1"
        Device     "Card0"
        Monitor    "Monitor-TV"
        DefaultDepth     24
        SubSection "Display"
                Depth   24
                Modes   "1024x768"
        EndSubSection
        SubSection "Display"
                Depth     24
                Modes    "800x600"
        EndSubSection
EndSection

Option works, if I want to right of or other... BUT to the Screen0, my lcd display. No picture on tv after load the driver...
Virtaul terminals works, but in the pink color...

How to split output to diffrerent displays... My lcd and tv?

PS: log file

(II) RADEON(0): Output S-video using monitor section Monitor-TV
(**) RADEON(0): Option "PreferredMode" "800x600"
(II) RADEON(0): Default TV standard: NTSC
(II) RADEON(0): TV standards supported by chip: NTSC NTSC-J PAL PAL-M
....
(II) RADEON(0): Port0:
  XRANDR name: S-video
  Connector: S-video
  TV1: INTERNAL_KLDSCP_DAC2
  DDC reg: 0x0
Using TV scaler 1 3
forcing TV scaler
scaler 0 setup success
Set CRTC 0 Source success
crtc 0 YUV enable setup success
Output DAC2 setup success
Output TV setup success
Output TV1 enable success
Enable CRTC 0 success
Unblank CRTC 0 success
Blank CRTC 0 success
Disable CRTC 0 success
Lock CRTC 0 success
Output TV1 disable succes

[null56]

just updateted to
x11-base/xorg-server-1.5.3-r5
x11-drivers/xf86-video-ati-6.12.1
same problem...
xorg-x11 not installed... is it may be a problem?

https://bugs.freedesktop.org/show_bug.cgi?id=20650

[fermulator]

I'm having troubles with this also.

EDIT: Specs:
* Ubuntu 9.04 (2.6.28-11-server)
* Radeon X1950 (r570)
* xserver-xorg-video-radeon 1:6.12.1-0ubuntu2
* xserver-xorg-video-ati 1:6.12.1-0ubuntu2
* libxrandr2 2:1.3.0-1build1

With default settings

xrandr -q

retured:

Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 3360 x 1050
DVI-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
DVI-0 disconnected (normal left inverted right x axis y axis)

Then I found this thread and learned about "ATOMTvOut" ... :

My xorg.conf now contains the line in the device section:
Option "ATOMTvOut" "true"

, and

xrandr -q

now returns:

Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 3360 x 1050
S-video connected (normal left inverted right x axis y axis)
1360x768 59.8
1024x768 59.9
800x600 60.3 59.9
848x480 59.7
720x480 59.7
640x480 59.9 59.4
DVI-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
DVI-0 disconnected (normal left inverted right x axis y axis)

Using gnome-display-properties also sees the TV now! Great.

But ... (of course) ... when I try:

xrandr --output S-video --mode 800x600

The TV flickers (like it would normally when getting a new Line In signal) ... but doesn't show any output. Also, after running that command, my primary LCD monitor image gets REALLY messed up. It's like htere's a line distortion and it's not quite right. I can still read text ... but the picture is very messed up.

What to try next?

[bridgman]

I'm just checking through the commit logs, but last I remember TVout on 5xx was still causing problems. There was a commit on 3/18 but not sure if that made it into the driver version you are using :

http://cgit.freedesktop.org/xorg/dri...5b3b85cf8e9205

I think agd5f and airlied got it kind-of working on the older and newer boards but 5xx was still a problem even after (theoretically) setting it up the same way fglrx does. Hopefully someone with recent experience using the driver will jump in.

Can you try composite out ? One of the outputs didn't work yet but don't remember if that was S-video or component. Composite is definitely most likely to work though.

[agd5f]

Component doesn't work yet. S-video works pretty well on r1xx-r3xx and r6xx/r7xx chips. S-video is kind of hit or miss on r4xx/r5xx/rs6xx chips.

[stivn]

hey, i got exactly the same problem as fermulator on my r500 (X1400 mobility). also driving jaunty with os driver 6.12.1... is there anything i could try? i really need my svideo out to get work (still got an old tv without hdmi input).

[fermulator]

Can you try composite out ?

Unfortunately I don't have any TV with composite inputs. Just S-video. hehe, my TV is old.

Component doesn't work yet. S-video works pretty well on r1xx-r3xx and r6xx/r7xx chips. S-video is kind of hit or miss on r4xx/r5xx/rs6xx chips.

So what is the problem then you think? Is the fix already committed and we can use the latest driver, or has "all the work been done that you're planning on doing for TV-out", and we need to figure out these corner cases ourselves? (I guess my point is here I'm not going to veer off the Ubuntu repository driver unless the latest driver would actually work for this task). I think that makes sense.

[bridgman]

Unfortunately I don't have any TV with composite inputs. Just S-video. hehe, my TV is old.

Composite is older than S-video; it's that single yellow RCA jack beside the S-video DIN connector.

Composite combines colour and luminance info onto a single wire; S-video uses a separate wire for colour (chroma) so the luminance info doesn't need to be low-pass filtered to keep it from interfering with the chroma subcarrier.

Your TV might be too old for component, but that's turned off anyways right now

So what is the problem then you think? Is the fix already committed and we can use the latest driver, or has "all the work been done that you're planning on doing for TV-out", and we need to figure out these corner cases ourselves? (I guess my point is here I'm not going to veer off the Ubuntu repository driver unless the latest driver would actually work for this task). I think that makes sense.

I think the answer is "we don't know, in theory everything is set right but it doesn't work properly and more tinkering is needed".

[anderssl]

Component doesn't work yet. S-video works pretty well on r1xx-r3xx and r6xx/r7xx chips. S-video is kind of hit or miss on r4xx/r5xx/rs6xx chips.

@agd5f: does this mean that the radeonhd driver can be used for r100-r300 cards? I'm asking because the documentation at http://wiki.x.org/wiki/radeonhd only says that r500 and up are supported. And I have a r300 card... Sure would be nice to get TV-out working!

[bridgman]

You need to use the radeon (xf86-video-ati) driver for r100-r300 cards, and that's where you would find r300 tvout.

Radeonhd covers r500-r700, radeon covers r100-r700.