S-video is missing entirely on xrandr report - unable to use S-video

[Derek White]

Binary package hint: xserver-xorg-video-ati

Recent install of Karmic. Have 'options radeon modeset=1' in a file under the /etc/modprobe.d directory to enable KMS. I have had no problems with compiz/glxgears/Xv - everything works perfectly (no crashes/artifacts/problems of any kind) & "graphics/video stay inside their windows". Prior to Karmic I had a tv-out script to enable my S-Video output & move the Xv output to it using xrandr/xvattr; however, in karmic xrandr does not recognize that there is an S-video connection on my card (Radeon 9550 RV350).

$ xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 408mm x 255mm
   1440x900 59.9*+
   1280x1024 75.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 75.0 60.3 56.2
   640x480 75.0 60.0
   720x400 70.1
   0x0 0.0

Previously, there would have been an entry similar to "S-video disconnected (normal left inverted right x axis y axis)" after the DVI-0 listings. This is now gone. Even forcing the connection gives an error:

$ xrandr --output S-video --set load_detection 1
X Error of failed request: BadRROutput (invalid Output parameter)
  Major opcode of failed request: 149 (RANDR)
  Minor opcode of failed request: 15 (RRGetOutputProperty)
  Serial number of failed request: 24
  Current serial number in output stream: 24

I am using all default configurations (xorg.conf doesn't exist), except for the KMS switch being set to on.

Attachment: Xorg.0.log - Sorry it's so big, I did a few VT switches and it likes to re-log all the EDID data each time...

[Derek White (d-man97)]

I implied it, but I forgot to actually say that, for me, this is a regression from Jaunty's radeon driver.

[Bryce Harrington (bryce)]

Hi d-man97,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.