gatos-devel Mailing List for GATOS

no, Xorg hasn't any support for the TV-in :-(
I think km worked 85%, with sound, but with a little corrupt video
(interferred with the desktop)

The AccleratedX has-Server support, the video is fine, but no sound...

P.S. I would help to get this running, e.g. by providing a ssh-access to
the pc. I would do it myself, but I haven't ever programmed drivers, only
a few userspace things...

| From: Rune Petersen <ru...@me...>

| D. Hugh Redelmeier wrote:

| > I didn't set the VertRefresh to 60 in my previous attempt.  The reason
| > is that I misinterpreted this wording:
| > 
| > +It's important that you are aware of the fact that, when TV output is active,
| > +the monitor is driven at the same vertical refresh frequency as that of the
| > +TV output. This means 50 or 60 Hz according to the standard you're using.
| > +NO CHECK IS DONE IN THE DRIVER ABOUT THE CAPABILITY OF THE MONITOR TO
| > +SUSTAIN THESE FREQUENCIES. You should look up in the monitor manual
| > +and check that 50/60 Hz is within the limits. IT IS POTENTIALLY HARMFUL
| > +TO THE MONITOR TO BE DRIVEN AT A FREQUENCY OUTSIDE ITS OPERATING RANGE.
| > 
| > I read this to say that the patch or the TVOut circuitry, when active,
| > would force the vertical refresh rate to 60Hz.  Otherwise, what is the
| > point of the warning?
| 
| The order is reverse:
| The TV output is driven at the same vertical refresh frequency as that
| of the monitor.

I think that the wording could be more clear.  Here's my attempt:

================
When TV output is active, both the TV and the computer monitor (if
any) are be driven at the same vertical refresh frequency.  The
relevant TV standard will dictate either 60Hz or 50Hz.  This has two
consequences:

(1) you must make sure that your computer monitor can accept that
    frequency (many accept 60Hz; fewer accept 50Hz).  Beware:
    this frequency can actually damage some monitors.  The driver
    does not check for this.  BE CAREUL: YOU ARE RESPONSIBLE
    FOR MAKING SURE THAT THIS WILL NOT FRY THE MONITOR.

(2) you must make sure that X uses the appropriate refresh rate.
    Usually, this means modifying the xorg.conf file in two ways:
    Add the following line to the Device section:
	Option     "IgnoreEDID" "true"
    Add the following to the monitor section (use 50 in place of 60 if
    your TV standard calls for it):
       	HorizSync    30.0 - 40.0
       	VertRefresh  60
================

Ken Smith wrote:
>> Ken Smith wrote:
>>> Hi, this is my first post to this list and I hope you can help with a
>>> little guidance.
>> *snip*
>>> My xorg.conf can be seen here:- http://www.kensnet.org/xorg.conf
>>> The log file can be seen here:- http://www.kensnet.org/Xorg.0.log
>>>
>>> Problem:
>>>
>>> TV Output is present but it seems that the refresh rates are wrong. The
>>> LCD says its 31.4 Khz / 60Hz, the display from the WinTV card looks as
>>> you would expect at this refresh rate. I have it in NTSC mode at the
>>> moment so it can attempt sync at the 60Hz vertical rate.
>> Someone is lying!
>>
>> Xorg.log:
>> (**) RADEON(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
>>
>> Xorg radeon driver is running a 75 Hz.
>>
>>> What I've Tried:
>>>
>>> I have tried specifying the refresh rates of 15.6 Khz and 50Hz in the
>>> xorg.conf and the X client complains that the radeon driver can't
>>> support those rates
>>>
>>> I've put the Option "IgnoreEDID" "true" into xorg.conf.
>> Good first step.
>>
>> you'll also need to set:
>> VertRefresh  60
>> HorizSync    35.0 - 40.0
>>
>> this is intended for tv-out, not the monitor. as long as these ranges
>> are within the supported ranges of your monitor (which they are) you are
>> safe.
>>
>>> I've tried starting X via the normal way from Run Level 5 and startx
>>> from Run Level 3 and running X from the command line in RL3. In Gnome I
>>> have set the resolution to 800x600 and 640x480.
>>>
>>> I've tried plugging in a old 640x480 60 Hz monitor.
>>>
>>> I've tried running X without a monitor, just with the TV S-Video
>>> connection.
>>>
>>> Ideas:
>>>
>>> It seems that something is determining the refresh rates other than the
>>> settings in xorg.conf. Starting X in the various ways that I have tried
>>> I have seen a variety of rates but not the 15.625/50Hz that a PAL output
>>> would require.
>> You also set 60 Hz for PAL 50. which is a good thing since most monitors
>> don't support 50 Hz, yours included, you may break even your monitor.
>>
>>> I know X is a bit clever with these things and seems to calculate its
>>> own Mode Lines. How is this overcome? Any assistance most welcome
>> It isn't all that clever it needs a little coercion to do the right thing
>> =)
>> On the other hand it wasn't made with TV-out in mind.
>>
>>
>> Rune Petersen
>>
> Thank you Rune,
> 
> I will try your suggestions on Tuesday when I next get a chance to work on
> that machine and let you know the results.
> 
> As you say something is lying. The 31.4KHz/60Hz was seen when running
> Gnome with its own configuration set to 640x480.

Oh ok.
Anyway the correct modeline is:
(**) RADEON(0):  Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) RADEON(0): Modeline "800x600"   40.00  800 840 968 1056  600 601
605 628 +hsync +vsync
> 
> What RPM contains xmkmf? I'd like to build the command line application.
start getting the tv-out to work first =)

but google says:
http://rpmfind.net/linux/rpm2html/search.php?query=xmkmf


Rune Petersen

> Ken Smith wrote:
>> Hi, this is my first post to this list and I hope you can help with a
>> little guidance.
> *snip*
>>
>> My xorg.conf can be seen here:- http://www.kensnet.org/xorg.conf
>> The log file can be seen here:- http://www.kensnet.org/Xorg.0.log
>>
>> Problem:
>>
>> TV Output is present but it seems that the refresh rates are wrong. The
>> LCD says its 31.4 Khz / 60Hz, the display from the WinTV card looks as
>> you would expect at this refresh rate. I have it in NTSC mode at the
>> moment so it can attempt sync at the 60Hz vertical rate.
>
> Someone is lying!
>
> Xorg.log:
> (**) RADEON(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
>
> Xorg radeon driver is running a 75 Hz.
>
>>
>> What I've Tried:
>>
>> I have tried specifying the refresh rates of 15.6 Khz and 50Hz in the
>> xorg.conf and the X client complains that the radeon driver can't
>> support those rates
>>
>> I've put the Option "IgnoreEDID" "true" into xorg.conf.
> Good first step.
>
> you'll also need to set:
> VertRefresh  60
> HorizSync    35.0 - 40.0
>
> this is intended for tv-out, not the monitor. as long as these ranges
> are within the supported ranges of your monitor (which they are) you are
> safe.
>
>>
>> I've tried starting X via the normal way from Run Level 5 and startx
>> from Run Level 3 and running X from the command line in RL3. In Gnome I
>> have set the resolution to 800x600 and 640x480.
>>
>> I've tried plugging in a old 640x480 60 Hz monitor.
>>
>> I've tried running X without a monitor, just with the TV S-Video
>> connection.
>>
>> Ideas:
>>
>> It seems that something is determining the refresh rates other than the
>> settings in xorg.conf. Starting X in the various ways that I have tried
>> I have seen a variety of rates but not the 15.625/50Hz that a PAL output
>> would require.
>
> You also set 60 Hz for PAL 50. which is a good thing since most monitors
> don't support 50 Hz, yours included, you may break even your monitor.
>
>>
>> I know X is a bit clever with these things and seems to calculate its
>> own Mode Lines. How is this overcome? Any assistance most welcome
>
> It isn't all that clever it needs a little coercion to do the right thing
> =)
> On the other hand it wasn't made with TV-out in mind.
>
>
> Rune Petersen
>
Thank you Rune,

I will try your suggestions on Tuesday when I next get a chance to work on
that machine and let you know the results.

As you say something is lying. The 31.4KHz/60Hz was seen when running
Gnome with its own configuration set to 640x480.

What RPM contains xmkmf? I'd like to build the command line application.

Many thanks

Ken

Ken Smith wrote:
> Hi, this is my first post to this list and I hope you can help with a 
> little guidance.
*snip*
> 
> My xorg.conf can be seen here:- http://www.kensnet.org/xorg.conf
> The log file can be seen here:- http://www.kensnet.org/Xorg.0.log
> 
> Problem:
> 
> TV Output is present but it seems that the refresh rates are wrong. The 
> LCD says its 31.4 Khz / 60Hz, the display from the WinTV card looks as 
> you would expect at this refresh rate. I have it in NTSC mode at the 
> moment so it can attempt sync at the 60Hz vertical rate.

Someone is lying!

Xorg.log:
(**) RADEON(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz

Xorg radeon driver is running a 75 Hz.

> 
> What I've Tried:
> 
> I have tried specifying the refresh rates of 15.6 Khz and 50Hz in the 
> xorg.conf and the X client complains that the radeon driver can't 
> support those rates
> 
> I've put the Option "IgnoreEDID" "true" into xorg.conf.
Good first step.

you'll also need to set:
VertRefresh  60
HorizSync    35.0 - 40.0

this is intended for tv-out, not the monitor. as long as these ranges
are within the supported ranges of your monitor (which they are) you are
safe.

> 
> I've tried starting X via the normal way from Run Level 5 and startx 
> from Run Level 3 and running X from the command line in RL3. In Gnome I 
> have set the resolution to 800x600 and 640x480.
> 
> I've tried plugging in a old 640x480 60 Hz monitor.
> 
> I've tried running X without a monitor, just with the TV S-Video connection.
> 
> Ideas:
> 
> It seems that something is determining the refresh rates other than the 
> settings in xorg.conf. Starting X in the various ways that I have tried 
> I have seen a variety of rates but not the 15.625/50Hz that a PAL output 
> would require.

You also set 60 Hz for PAL 50. which is a good thing since most monitors
don't support 50 Hz, yours included, you may break even your monitor.

> 
> I know X is a bit clever with these things and seems to calculate its 
> own Mode Lines. How is this overcome? Any assistance most welcome

It isn't all that clever it needs a little coercion to do the right thing =)
On the other hand it wasn't made with TV-out in mind.


Rune Petersen

D. Hugh Redelmeier wrote:
> | From: Rune Petersen <ru...@me...>
> | Date: Mon, 14 Aug 2006 20:09:21 +0200
> 
> Sorry for the slow reply.
sorry for the late reply... =)
> 
> | from your log:
> | >(--) RADEON(0): Virtual size is 800x600 (pitch 832)
> | >(**) RADEON(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
> | 
> | Refresh rate should be 60Hz not 85Hz.
> | one or more of these may be needed:
> | 
> | 	"Device" section:
> | 		Option     "IgnoreEDID" "true"
> 
> In my case, the VGA monitor is behind a KVM switch that blocks this
> information anyway.  So I don't need to add this bit
> 
> | 	"Monitor" section:
> |         	HorizSync    30.0 - 40.0
> |         	VertRefresh  60
> 
> That fixed it!  Well, the picture is shifted a bit, but that probably
> just requires tweeking of settings (a quite different problem).
> 
> I didn't set the VertRefresh to 60 in my previous attempt.  The reason
> is that I misinterpreted this wording:
> 
> +It's important that you are aware of the fact that, when TV output is active,
> +the monitor is driven at the same vertical refresh frequency as that of the
> +TV output. This means 50 or 60 Hz according to the standard you're using.
> +NO CHECK IS DONE IN THE DRIVER ABOUT THE CAPABILITY OF THE MONITOR TO
> +SUSTAIN THESE FREQUENCIES. You should look up in the monitor manual
> +and check that 50/60 Hz is within the limits. IT IS POTENTIALLY HARMFUL
> +TO THE MONITOR TO BE DRIVEN AT A FREQUENCY OUTSIDE ITS OPERATING RANGE.
> 
> I read this to say that the patch or the TVOut circuitry, when active,
> would force the vertical refresh rate to 60Hz.  Otherwise, what is the
> point of the warning?

The order is reverse:
The TV output is driven at the same vertical refresh frequency as that
of the monitor.

The warning is when you force the driver to run a curtain frequency you
may break the monitor.

Also it should always be 60 Hz.

> 
> Also: it seems funny to me that the symptom of a out-of-range refresh
> rate would be a non-terminating look in readFIFO.

Funny yes.
Hardware some problems appear to show chaos theory quite well.

> 
> Thanks very much for your help!
you are welcome.
> 
> It would be nice if this code were adopted by x.org.

There is a few hurdles in getting that to happen, one being the
reliability of getting TV-out.. which is more or less impossible for me
to do on my current setup.

I can remove a sizable chunk of code an still get TV-out. It doesn't
care about what you throw at it. And it frustrating and depressing to do
remote debugging.


Rune Petersen

Hi, this is my first post to this list and I hope you can help with a 
little guidance.

I'm building a MythTV box and I'd like to use the TVout of the Radeon if 
I possibly can. The aim is to use PAL as I'm in the UK.

Configuration:

Intel MB, P4 2G CPU, 1G RAM, 300G of disk in LVM
Radeon 7000 with two VGA ports and S-Video.
100M Ethernet card
FC5, latest updates
TVOut patch applied by building my own RPM with the patch - if this 
works you are welcome to have it.
An LCD monitor connected to one of the VGA ports on the 7000. The LCD 
identifies itself a Model M199D but I have removed that from the 
xorg.conf file that I'm using for testing. The LCD manual says that the 
refresh rates it can handle are H 30-80Khz V 55-75Hz. The LCD is only 
connected during testing, in the final setup it does not have to work. I 
would be quite happy to use an old VGA monitor, or none at all, once the 
system is in production.
TVOutput connected via S-Video to a WinTV card in another machine for 
testing.

lspci looks like this

00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset 
Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP 
Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 05)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 05)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 05)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 05)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 05)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 05)
00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 
Audio (rev 05)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QZ 
[Radeon 7000/VE]
02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)

My xorg.conf can be seen here:- http://www.kensnet.org/xorg.conf
The log file can be seen here:- http://www.kensnet.org/Xorg.0.log

Problem:

TV Output is present but it seems that the refresh rates are wrong. The 
LCD says its 31.4 Khz / 60Hz, the display from the WinTV card looks as 
you would expect at this refresh rate. I have it in NTSC mode at the 
moment so it can attempt sync at the 60Hz vertical rate.

What I've Tried:

I have tried specifying the refresh rates of 15.6 Khz and 50Hz in the 
xorg.conf and the X client complains that the radeon driver can't 
support those rates

I've put the Option "IgnoreEDID" "true" into xorg.conf.

I've tried starting X via the normal way from Run Level 5 and startx 
from Run Level 3 and running X from the command line in RL3. In Gnome I 
have set the resolution to 800x600 and 640x480.

I've tried plugging in a old 640x480 60 Hz monitor.

I've tried running X without a monitor, just with the TV S-Video connection.

Ideas:

It seems that something is determining the refresh rates other than the 
settings in xorg.conf. Starting X in the various ways that I have tried 
I have seen a variety of rates but not the 15.625/50Hz that a PAL output 
would require.

I know X is a bit clever with these things and seems to calculate its 
own Mode Lines. How is this overcome? Any assistance most welcome

Thanks

Ken

| From: Rune Petersen <ru...@me...>
| Date: Mon, 14 Aug 2006 20:09:21 +0200

Sorry for the slow reply.

| D. Hugh Redelmeier wrote:
| > | From: Rune Petersen <ru...@me...>

| > | D. Hugh Redelmeier wrote:
| > 
| > | > So it looks as if the routine readFIFO in theater_out.c is waiting for
| > | > a hardware status bit (VIP_HOST_RD_WT_CNTL_RD_ACK) to come up.  But it
| > | > is not coming up.

| > | Could you tell me if it happens the first time or the N'th  time
| > | readFIFO is called?
| > 
| > How would you recommend that I figure this out?
| > 
| > I don't (yet?) know how to start the X server properly from GDB:
| > startx and xinit are somewhat convoluted.  It is hard to attach gdb
| > after the server has started and yet before the xorg.conf has been
| > processed.
| 
| You don't have to start everything =)
| use:
| 	gdb /usr/bin/Xorg

Good to know.  I guess in this case, we want to set a breakpoint
within a loadable module.  That's a bit hard.

| > I could add a static variable and use it as a call counter in readFIFO
| > and print out its value (from GDB) when the sever has hung.  Is that
| > reasonable?
| 
| That is how I would do it, requires the least work.

OK.  Luckily, I didn't have to do that (using rpmbuild makes it a bit
more awkward).

| from your log:
| >(--) RADEON(0): Virtual size is 800x600 (pitch 832)
| >(**) RADEON(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
| 
| Refresh rate should be 60Hz not 85Hz.
| one or more of these may be needed:
| 
| 	"Device" section:
| 		Option     "IgnoreEDID" "true"

In my case, the VGA monitor is behind a KVM switch that blocks this
information anyway.  So I don't need to add this bit

| 	"Monitor" section:
|         	HorizSync    30.0 - 40.0
|         	VertRefresh  60

That fixed it!  Well, the picture is shifted a bit, but that probably
just requires tweeking of settings (a quite different problem).

I didn't set the VertRefresh to 60 in my previous attempt.  The reason
is that I misinterpreted this wording:

+It's important that you are aware of the fact that, when TV output is active,
+the monitor is driven at the same vertical refresh frequency as that of the
+TV output. This means 50 or 60 Hz according to the standard you're using.
+NO CHECK IS DONE IN THE DRIVER ABOUT THE CAPABILITY OF THE MONITOR TO
+SUSTAIN THESE FREQUENCIES. You should look up in the monitor manual
+and check that 50/60 Hz is within the limits. IT IS POTENTIALLY HARMFUL
+TO THE MONITOR TO BE DRIVEN AT A FREQUENCY OUTSIDE ITS OPERATING RANGE.

I read this to say that the patch or the TVOut circuitry, when active,
would force the vertical refresh rate to 60Hz.  Otherwise, what is the
point of the warning?

Also: it seems funny to me that the symptom of a out-of-range refresh
rate would be a non-terminating look in readFIFO.

Thanks very much for your help!

It would be nice if this code were adopted by x.org.

D. Hugh Redelmeier wrote:
> | From: Rune Petersen <ru...@me...>
> 
> Thanks for helping!
> 
> | D. Hugh Redelmeier wrote:
> 
> | > So it looks as if the routine readFIFO in theater_out.c is waiting for
> | > a hardware status bit (VIP_HOST_RD_WT_CNTL_RD_ACK) to come up.  But it
> | > is not coming up.
> 
> | Have you had this card working before with tv-output?
> 
> No.  This is my first attempt at using it with Linux.  I don't have a
> MS Windows box with which to test it either.

if we can't get it to work, it would be nice if you could test it with
windows
> 
> | Could you tell me if it happens the first time or the N'th  time
> | readFIFO is called?
> 
> How would you recommend that I figure this out?
> 
> I don't (yet?) know how to start the X server properly from GDB:
> startx and xinit are somewhat convoluted.  It is hard to attach gdb
> after the server has started and yet before the xorg.conf has been
> processed.

You don't have to start everything =)
use:
	gdb /usr/bin/Xorg

> 
> I could add a static variable and use it as a call counter in readFIFO
> and print out its value (from GDB) when the sever has hung.  Is that
> reasonable?

That is how I would do it, requires the least work.

from your log:
>(--) RADEON(0): Virtual size is 800x600 (pitch 832)
>(**) RADEON(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz

Refresh rate should be 60Hz not 85Hz.
one or more of these may be needed:

	"Device" section:
		Option     "IgnoreEDID" "true"

	"Monitor" section:
        	HorizSync    30.0 - 40.0
        	VertRefresh  60



Rune Petersen

| From: Rune Petersen <ru...@me...>

Thanks for helping!

| D. Hugh Redelmeier wrote:

| > So it looks as if the routine readFIFO in theater_out.c is waiting for
| > a hardware status bit (VIP_HOST_RD_WT_CNTL_RD_ACK) to come up.  But it
| > is not coming up.

| Have you had this card working before with tv-output?

No.  This is my first attempt at using it with Linux.  I don't have a
MS Windows box with which to test it either.

| Could you tell me if it happens the first time or the N'th  time
| readFIFO is called?

How would you recommend that I figure this out?

I don't (yet?) know how to start the X server properly from GDB:
startx and xinit are somewhat convoluted.  It is hard to attach gdb
after the server has started and yet before the xorg.conf has been
processed.

I could add a static variable and use it as a call counter in readFIFO
and print out its value (from GDB) when the sever has hung.  Is that
reasonable?

| And could you send me the entire log?

I have sent a copy to Rune.  I don't want to swamp the rest of you.

Guys, can we patch Avview so that the numerical pad is not affected by
the favorite channel list? It causes hideous problems, because the
numerical pad's numbers are re-mapped on the fly ("2" now makes "3"
and so forth).
Favorite channels should be for the up/down navigation, not the numerical pad.

D. Hugh Redelmeier wrote:
*lots of interesting information *
> 
> So it looks as if the routine readFIFO in theater_out.c is waiting for
> a hardware status bit (VIP_HOST_RD_WT_CNTL_RD_ACK) to come up.  But it
> is not coming up.

Have you had this card working before with tv-output?

Could you tell me if it happens the first time or the N'th  time
readFIFO is called?
And could you send me the entire log?



Rune Petersen

[This is my first post to this list since 1999.  I fell off the list when 
it was moved in 2000.  Rune: great to see you are still active.]

Summary: TVOut for Radeon 9000pro does not work for me.  X is stuck
starting up and is using 100% of the CPU.

I wish to use TV out for a MythTV box I'm setting up.  It has a Radeon
9000 Pro with S-Video out.  I learned that stock Fedora Core 5's xorg
does not support this.  Luckily, I found Rune's page for adding
supoort: http://megahurts.dk/rune/tv_output.html

Here's what I did:

- fetched and installed the Source RPM to FC5's current ATI driver for
  xorg: xorg-x11-drv-ati-6.5.8.0-1.src.rpm

- added rune's patch to the SOURCE subdirectory of the rpm-building
  arena:
	http://megahurts.dk/rune/stuff/xorg7-6.5.8.0-tv_output.patch.gz

- some additional information came from
	http://gatos.sourceforge.net/theater_out.php

- made a couple of changes to the .spec to apply the patch:
    [hugh@redburn x-radeon-tv-out]$ rcsdiff -u ~/rpmbuilds/SPECS/xorg-x11-drv-ati.spec
    ===================================================================
    RCS file: /home/hugh/rpmbuilds/SPECS/RCS/xorg-x11-drv-ati.spec,v
    retrieving revision 1.1
    diff -u -r1.1 /home/hugh/rpmbuilds/SPECS/xorg-x11-drv-ati.spec
    --- /home/hugh/rpmbuilds/SPECS/xorg-x11-drv-ati.spec	2006/08/11 21:22:17	1.1
    +++ /home/hugh/rpmbuilds/SPECS/xorg-x11-drv-ati.spec	2006/08/11 22:03:03
    @@ -24,6 +24,7 @@
     Source2:   r128.xinf
     Source3:   radeon.xinf
     Patch0:    xorg-x11-drv-ati-6.5.7.3-radeon-metamodes-SEGV-fix.patch
    +Patch1:    xorg7-6.5.8.0-tv_output.patch
     
     ExclusiveArch: %{ix86} x86_64 ia64 ppc alpha sparc sparc64
     
    @@ -42,6 +43,7 @@
     %prep
     %setup -q -n %{tarball}-%{version}
     #%patch0 -p2 -b .radeon-metamodes-SEGV-fix
    +%patch1 -p1 -b .radeon-tv-output-fix
     
     %build
     %configure --disable-static
    @@ -79,6 +81,7 @@
     %{moduledir}/multimedia/theatre200_drv.so
     %{moduledir}/multimedia/theatre_detect_drv.so
     %{moduledir}/multimedia/theatre_drv.so
    +%{moduledir}/multimedia/theater_out_drv.so
     #%dir %{_mandir}/man4x
     %{_mandir}/man4/ati.4*
     %{_mandir}/man4/r128.4*
    [hugh@redburn x-radeon-tv-out]$ 

- built the rpm (rpmbuild -bb ~/rpmbuilds/SPECS/xorg-x11-drv-ati.spec)

- installed new binary .rpm (and later installed the debuginfo
  .rpm too when I wanted GDB's help)

- I started x, with a resolution of 800x600 (seems to be manditory for
  the TVOut patch).  This worked.

- I added to /etc/X11/xorg.conf section "Device":
        Option "TVOutput" "NTSC"
  Now I startx and X hangs.

What is it doing?  Here's what GDB says:

    Loaded symbols for /usr/lib/xorg/modules/multimedia/theater_out_drv.so
    0x00265aa5 in ert_read (t=Variable "t" is not available.
    ) at theater_out.c:908
    908         *data = INREG(reg);
    (gdb) where
    #0  0x00265aa5 in ert_read (t=Variable "t" is not available.
    ) at theater_out.c:908
    #1  0x00265c6f in readFIFO (t=0x8e2f1d0, addr=Variable "addr" is not available.
    ) at theater_out.c:1219
    #2  0x002664a7 in saveTimingTables (t=0x8e2f1d0, save=0x8e2f1f4) at theater_out.c:1350
    #3  0x00266c21 in theaterOutSave (t=0x8e2f1d0, pScrn=0x8e17590) at theater_out.c:1913
    #4  0x002970e1 in RADEONScreenInit (scrnIndex=0, pScreen=0x8e2e2e0, argc=4, argv=0xbfe6b0c4) at radeon_driver.c:7364
    #5  0x0806f82e in AddScreen ()
    #6  0x080a1bec in InitOutput ()
    #7  0x0806ffc6 in main ()
    (gdb) next
    909     }
    (gdb) next
    readFIFO (t=0x8e2f1d0, addr=Variable "addr" is not available.
    ) at theater_out.c:1221
    1221          while ((tmp & VIP_HOST_RD_WT_CNTL_RD_ACK) == 0);
    (gdb) next
    1219              ert_read(t , TV_HOST_RD_WT_CNTL , &tmp);
    (gdb) print t
    $1 = 0x8e2f1d0
    (gdb) next
    1221          while ((tmp & VIP_HOST_RD_WT_CNTL_RD_ACK) == 0);
    (gdb) print tmp
    $2 = 4607
    (gdb) print/o tmp
    $3 = 010777
    (gdb) print *t
    $6 = {VIP = 0x8e1b318, MMIO = 0xb7e85000 <Address 0xb7e85000 out of bounds>, theatre_num = -1, standard = TV_STD_NTSC, compatibleMode = 0, currentMode = 0x0, hPos = 0, vPos = 0, hSize = 0, savedState = {clkout_cntl = 0, 
	clock_sel_cntl = 0, crc_cntl = 0, crt_pll_cntl = 0, dfrestart = 0, dhrestart = 662, dvrestart = 578, frame_lock_cntl = 0, gain_limit_settings = 25101823, hdisp = 639, hstart = 651, htotal = 815, hw_debug = 0, 
	linear_gain_settings = 16777472, master_cntl = 1074398803, modulator_cntl1 = 1753219086, modulator_cntl2 = 0, pll_cntl0 = 0, pll_test_cntl = 0, pre_dac_mux_cntl = 8, rgb_cntl = 8060944, sync_cntl = 44, sync_lock_cntl = 0, 
	sync_size = 0, timing_cntl = 1913257984, tvo_data_delay_a = 0, tvo_data_delay_b = 0, tvo_sync_pat_expect = 0, tvo_sync_threshold = 0, tv_dac_cntl = 2621955, tv_pll_cntl = 50395449, tv_pll_fine_cntl = 0, 
	upsamp_and_gain_cntl = 5, upsamp_coeffs = {0 <repeats 15 times>}, uv_adr = 160, vdisp = 479, vftotal = 1, vscaler_cntl1 = 687865899, vscaler_cntl2 = 268435456, vtotal = 589, y_fall_cntl = 65552, y_rise_cntl = 1048592, 
	y_saw_tooth_cntl = 1048592, disp_merge_cntl = 4294901760, h_code_timing = {0 <repeats 32 times>}, v_code_timing = {0 <repeats 32 times>}}, modeState = {clkout_cntl = 0, clock_sel_cntl = 0, crc_cntl = 0, crt_pll_cntl = 0, 
	dfrestart = 0, dhrestart = 0, dvrestart = 0, frame_lock_cntl = 0, gain_limit_settings = 0, hdisp = 0, hstart = 0, htotal = 0, hw_debug = 0, linear_gain_settings = 0, master_cntl = 0, modulator_cntl1 = 0, 
	modulator_cntl2 = 0, pll_cntl0 = 0, pll_test_cntl = 0, pre_dac_mux_cntl = 0, rgb_cntl = 0, sync_cntl = 0, sync_lock_cntl = 0, sync_size = 0, timing_cntl = 0, tvo_data_delay_a = 0, tvo_data_delay_b = 0, 
	tvo_sync_pat_expect = 0, tvo_sync_threshold = 0, tv_dac_cntl = 0, tv_pll_cntl = 0, tv_pll_fine_cntl = 0, upsamp_and_gain_cntl = 0, upsamp_coeffs = {0 <repeats 15 times>}, uv_adr = 0, vdisp = 0, vftotal = 0, 
	vscaler_cntl1 = 0, vscaler_cntl2 = 0, vtotal = 0, y_fall_cntl = 0, y_rise_cntl = 0, y_saw_tooth_cntl = 0, disp_merge_cntl = 0, h_code_timing = {0 <repeats 32 times>}, v_code_timing = {0 <repeats 32 times>}}}
    (gdb) 

So it looks as if the routine readFIFO in theater_out.c is waiting for
a hardware status bit (VIP_HOST_RD_WT_CNTL_RD_ACK) to come up.  But it
is not coming up.

Here's what the end of Xlog.0.log says:
    (**) RADEON(0): RADEONScreenInit d8000000 0
    (**) RADEON(0): Map: 0xd8000000, 0x04000000
    (**) RADEON(0): Allocating VIP interface(**) RADEON(0): TVOutput opt = NTSC
    (II) Loading sub module "theater_out"
    (II) LoadModule: "theater_out"
    (II) Loading /usr/lib/xorg/modules/multimedia/theater_out_drv.so
    (II) Module theater_out: vendor="X.Org Foundation"
	    compiled for 7.0.0, module version = 1.0.0
	    ABI class: X.Org Video Driver, version 0.8
    (**) RADEON(0): Found theater_out module
    (II) RADEON(0): Embedded Rage Theater detected
    (**) RADEON(0): Entering initTheaterOut, s = NTSC
    (**) RADEON(0): RADEONSave
    (**) RADEON(0): RADEONSaveMode(0x8e19008)
    (**) RADEON(0): Read: 0x0000000c 0x00030065 0x00000000
    (**) RADEON(0): Read: rd=12, fd=101, pd=3
    (**) RADEON(0): Read VCLK_ECP_CNTL = 00000003
    (**) RADEON(0): RADEONSaveMode returns 0x8e19008
    (**) RADEON(0): Entering theaterOutSave
    (**) RADEON(0): Entering RT_Save
    (**) RADEON(0): saveTimingTables: reading timing tables

Anybody know what is going wrong?

Would more information be useful?

Thanks.

Hi

I have a AIW 9000pro on Fedora Core 4 Linux.

Which software would help my TV tuner to at least perform a bit?

Thank you