1002:4150 [R300 KMS] [Lucid] S-video output could not be enabled with "load detection"

Bug #563983 reported by Tomasz Czapiewski
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-driver-ati
Fix Released
Medium
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Lucid
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-ati

I can't enable S-video output with KMS on RV350 card on Kubuntu Lucid.

I'm trying to enable S-video output with commands:
$ xrandr --output S-video --set "load detection" 1
$ xrandr --output S-video --set "tv standard" pal
$ xrandr --output S-video --same-as DVI-0
$ xrandr --addmode S-video 800x600
$ xrandr --output S-video --mode 800x600
and I get no errors in console but S-video connection is still disconnected.

I've got connected LCD monitor to DVI-0 and CRT TV to S-video and I've used
this configuration (with different naming on UMS: load_detection and
tv_standard) with UMS before (before upgrade from Kubuntu 9.10 to 10.04).

For clarify logs reading, I use two R3xx graphic cards (RV350 and RV370) for
multiseat.
LCD 17" monitor (1280x1024) is connected to DVI-0 and 28" CRT TV (800x600) to
S-video of RV350 (clone mode) and LCD TV 32" (1920x1080) is connected to DVI-0
with DVI-HDMI cable to RV370 (second head on second X-server).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu Apr 15 17:56:34 2010
MachineType: System manufacturer System Product Name
ProcCmdLine: root=UUID=82e29357-9603-403e-86ed-b37dcc794d6b ro ipv6.disable=1 quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-ati
dmi.bios.date: 08/17/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0704
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P4V800D-X
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.XX
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd08/17/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4V800D-X:rvrRevX.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Created an attachment (id=35035)
xorg.conf

Revision history for this message
In , agd5f (agd5f) wrote :

please attach your xorg log and the output of xrandr.

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Created an attachment (id=35037)
xrandr -q --verbose

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Created an attachment (id=35038)
lspci -vvv

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Created an attachment (id=35039)
Xorg.0.log

Revision history for this message
In , agd5f (agd5f) wrote :

xrandr --output S-video --set "tv standard" pal
xrandr --output S-video --addmode 800x600
xrandr --output S-video --mode 800x600

should enable the S-video port.

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

distribution: Kubuntu 10.04 (post beta2 up-to-date)
xserver-xorg-video-radeon: 6.13.0
xserver-xorg: 7.5
xserver-xorg-core: 1.7.6
kernel: 2.6.32-20-generic

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Created an attachment (id=35041)
dmesg after added and selected mode 800x600 on S-video

Those commands:
$ xrandr --output S-video --set "tv standard" pal
$ xrandr --addmode S-video 800x600
$ xrandr --output S-video --mode 800x600
added video mode of 800x600 to S-video port but even then S-video could not be enabled as shown in dmesg (attachment).
$ xrandr
Screen 0: minimum 320 x 200, current 800 x 600, maximum 4096 x 4096
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 800x600+0+0 (normal left inverted right x axis y axis) 330mm x 270mm
   1280x1024 60.0 +
   1024x768 60.0
   800x600 60.3*
   640x480 60.0 59.9
S-video disconnected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   800x600 60.3*

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Might those logs in dmesg come from second graphic card? (RV370):

[18814.237220] [drm] 2: conflicting encoders switching off SVIDEO-1
[18814.237224] [drm] in favor of DVI-I-1

This card (on display :1) does not have S-video port:
$ xrandr -display :1 -q
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 4096 x 4096
VGA-1 disconnected (normal left inverted right x axis y axis)
DVI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 708mm x 398mm
   1920x1080 50.0*+ 60.0
   1280x1024 75.0 60.0
   1360x765 59.8
   1280x720 50.0
   1024x768 75.1 70.1 60.0
   800x600 72.2 75.0 60.3
   720x576 50.0
   720x480 59.9
   640x480 72.8 75.0 60.0

but my primary RV350 (with logs attached before) on display :0 has it.

Does "S-video disconnected 800x600+0+0" really mean that it's disconnected by the driver or it's unimportant?
I've got problems with enabling S-video output before on UMS but there were related rather to choosing TV standard or something else, but not load detection (it said "connected" after --set load_detection 1 on UMS).
I mean if should I try to mix those commands in script many times (as before I've did on UMS) to see anything on TV even if xrandr shows "disconnected" or it doesn't make sense? ;-)

Revision history for this message
In , agd5f (agd5f) wrote :

this looks like a drm bug in the connector code.

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Should I give you more verbose/debug information? How to do it? Any kernel boot parameter?

Revision history for this message
In , agd5f (agd5f) wrote :

(In reply to comment #11)
> Should I give you more verbose/debug information? How to do it? Any kernel boot
> parameter?

It just need to be debugged and fixed. I'll take a look today.

Revision history for this message
In , agd5f (agd5f) wrote :

Created an attachment (id=35067)
fix

This drm patch fixes the issue. I've sent it upstream to Dave.

Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Thank you very much for this very quick fixing this issue. I'll try to test it ASAP (somehow).

Revision history for this message
Tomasz Czapiewski (xeros) wrote : [R300 KMS] [Lucid] S-video output could not be enabled with "load detection"

Binary package hint: xserver-xorg-video-ati

I can't enable S-video output with KMS on RV350 card on Kubuntu Lucid.

I'm trying to enable S-video output with commands:
$ xrandr --output S-video --set "load detection" 1
$ xrandr --output S-video --set "tv standard" pal
$ xrandr --output S-video --same-as DVI-0
$ xrandr --addmode S-video 800x600
$ xrandr --output S-video --mode 800x600
and I get no errors in console but S-video connection is still disconnected.

I've got connected LCD monitor to DVI-0 and CRT TV to S-video and I've used
this configuration (with different naming on UMS: load_detection and
tv_standard) with UMS before (before upgrade from Kubuntu 9.10 to 10.04).

For clarify logs reading, I use two R3xx graphic cards (RV350 and RV370) for
multiseat.
LCD 17" monitor (1280x1024) is connected to DVI-0 and 28" CRT TV (800x600) to
S-video of RV350 (clone mode) and LCD TV 32" (1920x1080) is connected to DVI-0
with DVI-HDMI cable to RV370 (second head on second X-server).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu Apr 15 17:56:34 2010
MachineType: System manufacturer System Product Name
ProcCmdLine: root=UUID=82e29357-9603-403e-86ed-b37dcc794d6b ro ipv6.disable=1 quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-ati
dmi.bios.date: 08/17/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0704
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P4V800D-X
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.XX
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd08/17/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4V800D-X:rvrRevX.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

Revision history for this message
Tomasz Czapiewski (xeros) wrote :
Bryce Harrington (bryce)
tags: added: kubuntu
Revision history for this message
Bryce Harrington (bryce) wrote :

[According to the upstream bug report, this is a bug in the kernel drm code]

affects: xserver-xorg-video-ati (Ubuntu) → linux (Ubuntu)
Revision history for this message
Bryce Harrington (bryce) wrote :

Kernel patch is at https://bugs.freedesktop.org/attachment.cgi?id=35067
which is commit 837feb147c531219c7315857a6f17e145af8f750 by Alex Deucher in the drm tree

tags: added: patch xorg-needs-kernel-patch
Revision history for this message
Tomasz Czapiewski (xeros) wrote :

It looks like todays kernel upgrade (linux-image-2.6.32-21-generic_2.6.32-21.32) doesn't have this patch yet.

Changed in linux (Ubuntu Lucid):
status: New → Confirmed
Revision history for this message
In , Tomasz Czapiewski (xeros) wrote :

Sorry for so late testing. Since I've get information that no more patches will be applied to Ubuntu Lucid until kernel update after release, I've just recompiled stock Ubuntu 2.6.32-21-generic (2.6.32.11+drm33.2) kernel with this patch and now S-video is connected out of the box (no need to set "load detection") and my both screens resolution was set to 800x600 by default (I could change my LCD resolution to it's native later). Thanks a lot for this fix.

Unfortunately I thought that my other problems will disappear with new driver, too, but they don't...
I mean problems with "tv standard" change/enable - I still need to make a loop of xrandr commands:
$ for i in `seq 1000`; do xrandr --output S-video --set "tv standard" pal; xrandr --output S-video --set "tv standard" ntsc; done
until I get proper video on S-video (the same was on Karmic or even earlier distributions (I'm not 100% sure about which earlier versions)).
I've done more testing and when I run this loop I've got video after few seconds in NTSC (I'm interrupting script after I get video and try to change to PAL or NTSC to see what standard I have enabled) and later I've managed to try if I can get PAL after more time running script. After few minutes later I've got PAL, but NTSC was unavailable then. [I've wrote on this issue in Kubuntu Karmic some time ago at Phoronix forums]
Should I write a new bug report for it?

Revision history for this message
Tomasz Czapiewski (xeros) wrote : Re: [R300 KMS] [Lucid] S-video output could not be enabled with "load detection"

This patch applied to linux-image-2.6.32-21-generic_2.6.32-21.32 sources and kernel recompilation fixes the problem.

Revision history for this message
In , agd5f (agd5f) wrote :

(In reply to comment #15)

> Should I write a new bug report for it?

Yes.

Revision history for this message
Tomasz Czapiewski (xeros) wrote : Re: [R300 KMS] [Lucid] S-video output could not be enabled with "load detection"

I've patched and compiled kernel in my PPA:
https://edge.launchpad.net/~xeros/+archive/xeros-test

Steps to add PPA and test:
$ sudo add-apt-repository ppa:xeros/xeros-test
$ sudo apt-get update
$ sudo apt-get install linux-image-2.6.32-22xeros-generic linux-headers-2.6.32-22xeros-generic

The kernel in this PPA is tested and works properly for me and 3 other people.

The difference from Ubuntu kernel are two patches from 2.6.34-rc5:
1. drm/radeon/kms: disable the tv encoder when tv/cv is not in use (minor changes to adapt it for 2.6.32 Ubuntu kernel)
2. drm/radeon/kms: fix tv dac conflict resolver (applies cleanly).

Changed in xserver-xorg-driver-ati:
importance: Unknown → Medium
status: Unknown → Fix Released
Changed in xserver-xorg-driver-ati:
importance: Medium → Unknown
Changed in xserver-xorg-driver-ati:
importance: Unknown → Medium
penalvch (penalvch)
summary: - [R300 KMS] [Lucid] S-video output could not be enabled with "load
- detection"
+ 1002:4150 [R300 KMS] [Lucid] S-video output could not be enabled with
+ "load detection"
Revision history for this message
penalvch (penalvch) wrote :

Won't Fix as Lucid is EoL since May 9, 2013. As I don't have Won't Fix permissions at this point, marking Invalid.

tags: added: latest-bios-704 needs-upstream-testing
removed: kms patch radeon xorg-needs-kernel-patch
Changed in linux (Ubuntu Lucid):
status: Confirmed → Invalid
Revision history for this message
penalvch (penalvch) wrote :

Tomasz Czapiewski, 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 images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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 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. 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. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

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

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

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

Other bug subscribers

Remote bug watches

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