[Bug 27649] [R300 KMS] S-video output could not be enabled with "load detection"

[bugzilla-daemon at freedesktop.org]

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

Tomasz Czapiewski <xeros at irc.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #15 from Tomasz Czapiewski <xeros at irc.pl> 2010-04-18 15:39:20 PDT ---
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?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.