1002:5955 ati radeon xpress 200M no s-video output, no tv screen detected

Bug #573550 reported by Rodrigue V.
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xorg

I can't manage to make the s-video output working. It was working fine out of the box in 8.10, it was hard with 9.10 with this thread http://ohioloco.ubuntuforums.org/showthread.php?p=9020936, but now, with 10.04, i don't find any solution.

With karmic, this script do the trick :
#!/bin/bash
#This little script will toggle svideo out for Radeon open source driver.

xrandr -s 800x600
xrandr --newmode 800x600
xrandr --addmode S-video 800x600
xrandr --output S-video --mode 800x600

I use a laptop compaq presario v5000 with an ATI RADEON XPRESS 200M. Lucid Lynx is the version in use, upgraded from karmic (9.10).

In fact the xorg.conf seems to be completely bypass. If i use one or remove it, it works the same way.

I use the open drivers shipped with ubuntu. Note that 3D rendering and everything else work fine.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sun May 2 11:07:01 2010
DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type
GdmLog:
 Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: /home/puce/.themes/Variance/gtk-2.0/gtkrc:523: Unable to locate image file in pixmap_path: "gap-bottom-start.png"
 /home/puce/.themes/Variance/gtk-2.0/gtkrc:525: Unable to locate image file in pixmap_path: "gap-bottom-end.png"
 /home/puce/.themes/Variance/gtk-2.0/gtkrc:545: Unable to locate image file in pixmap_path: "gap-right-start.png"
 /home/puce/.themes/Variance/gtk-2.0/gtkrc:547: Unable to locate image file in pixmap_path: "gap-right-end.png"
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard Presario V5000 (ES281EA#ABF)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=94a84584-5a5a-4e81-9382-9b8df4354e13 ro quiet splash
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 02/24/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.name: 30AE
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 49.38
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd02/24/2006:svnHewlett-Packard:pnPresarioV5000(ES281EA#ABF):pvrF.33:rvnHewlett-Packard:rn30AE:rvr49.38:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario V5000 (ES281EA#ABF)
dmi.product.version: F.33
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

Revision history for this message
Rodrigue V. (rodrigue-villetard) wrote :
Bryce Harrington (bryce)
Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Rodrigue V. (rodrigue-villetard) wrote :

I've also tried with avitvout, but I always received this message : "VBE call failed."

Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Bryce Harrington (bryce)
tags: added: tv-out
Revision history for this message
Marcelo Magalhaes (m-maga) wrote :

This bug affects me the same way. I have a Compaq model 2404us, with the same Ati Xpress 200m.

Revision history for this message
Alex Lopez (alfitovdkiv) wrote :

I am running an ati mobility radeon x700 (rv400).
I finally get svideo output detected setting kms parameter at boot:
video=SVIDEO-1:e
This enables tv out correctly, I can set up modes through xrandr but.... i cannot get image correctly, just b&n flashing image...
The cable is should be ok, because it works on win7. ¿or could be any reason????
Please check that setting at boot and let us know if it works.
¿any ideas why I get that screen? none modes work: ntsc, pal, all types tested...

Regards.

Revision history for this message
igor (igor-campus) wrote :

I SOLVED as follows:

In /etc/default/grub set this line:

GRUB_CMDLINE_LINUX="nomodeset"

And in /etc/modprobe.d/radeon-kms.conf set this line:

options radeon modeset=0

If the radeon-kms.conf file does not exist, create it.

Rebooting

After login connect svideo and run this:

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

now svideo is enable!!!!

Sorry for my bed English and Good luck everyone!

Revision history for this message
Alex Lopez (alfitovdkiv) wrote :

All right, I will try that.
Meanwhile... which card are you working with? did you get correct color output?

Thanks

Revision history for this message
igor (igor-campus) wrote :

My card is ati radeon xpress 200M, and color output is correct, both the television on pc.

Revision history for this message
rr (robertoavp2) wrote :

I TREID THAT YOU SAID, BUT I CAN'T RUN /etc/default/grub, OR CREATE radeon-kms.conf, THAT IT DOESN'T EXIST, IT SAYS THAT I AM NOT THE ROOT, SO I DON'T HAVE PERMISSIONS.... ABY HELP??????
I CAN'T EXPORT TO MI TV

rr (robertoavp2)
Changed in xserver-xorg-video-ati (Ubuntu):
status: Confirmed → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Nathan Norman (taffynay-deactivatedaccount) wrote :

I followed igor's suggestion and it almost worked for me

I'm guessing that xrandr is assuming NTSC as the default output mode and as such can cause issues for people using PAL tv's. A typical symptom of this is the TV picture being in black and white, and in some cases exhibiting extreme flickering as well.

If you have this problem, just append the last command with:

--set tv_standard pal

Hope this helps anyone.

Revision history for this message
Nathan Norman (taffynay-deactivatedaccount) wrote :

@rr

Expanding on igor's guide, the commands you want to run are the following (exactly what I did)

user@linux:~$ sudo cp /etc/default/grub /etc/default/grub-ORIG
user@linux:~$ sudo nano /etc/default/grub

Look for this:
GRUB_CMDLINE_LINUX=

And change the end to this:
"nomodeset"

Save the file with Ctrl+X (press Y to write to the file)

Now type:

user@linux:~$ ls /etc/modprobe.d/

and look for this file:
radeon-kms.conf

If it does not exist, create it:

user@linux:~$ sudo touch /etc/modprobe.d/radeon-kms.conf

Then open the file in nano:

user@linux:~$ sudo nano /etc/modprobe.d/radeon-kms.conf

Add this line:
options radeon modeset=0

Save it with Ctrl+X (press Y to write to the file)

Reboot the machine

After login connect svideo and run this:

xrandr -s 800x600
xrandr --addmode S-video 800x600
xrandr --output S-video --mode 800x600 (don't forget to set the PAL option here if you need to)

Revision history for this message
penalvch (penalvch) wrote :

doddo, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this 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 please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: karmic needs-upstream-testing regression-release
removed: tv-out
affects: xserver-xorg-video-ati (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Fix Released → Incomplete
summary: - ati radeon xpress 200M no s-video output, no tv screen detected
+ 1002:5955 ati radeon xpress 200M no s-video output, no tv screen
+ detected
Revision history for this message
Rodrigue V. (rodrigue-villetard) wrote : Re: [Bug 573550] Re: ati radeon xpress 200M no s-video output, no tv screen detected
Download full text (3.7 KiB)

Hi,

I’ve totally forgotten this bug… I can’t tell you if it’s still an issue
while I don’t have tv to plug on this computer anymore…

I’m sorry that I can’t try.

cheers,
Rodrigue

On 4 August 2012 14:42, Christopher M. Penalver <
<email address hidden>> wrote:

> doddo, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this 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 please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Please do not test the kernel in
> the daily folder, but the one all the way at the bottom. Once you've tested
> the upstream kernel, please comment on which kernel version specifically
> you tested and remove the tag:
> needs-upstream-testing
>
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the text:
> needs-upstream-testing
>
> If this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> If you are unable to test the mainline kernel, please comment as to why
> specifically you were unable to test it and add the following tags:
> kernel-unable-to-test-upstream
> kernel-unable-to-test-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> Please let us know your results. Thank you for your understanding.
>
> Helpful Bug Reporting Links:
> https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
>
> https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
>
> https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
>
> https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug
>
> ** This bug is no longer a duplicate of bug 563983
> [R300 KMS] [Lucid] S-video output could not be enabled with "load
> detection"
>
> ** Tags removed: tv-out
> ** Tags added: karmic needs-upstream-testing regression-release
>
> ** Package changed: xserver-xorg-video-ati (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Fix Released => Incomplete
>
> ** Su...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

doddo, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/573550/comments/12 regarding you no longer having hardware to test for this problem. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.