gatos-devel Mailing List for GATOS

On April 30, 2002 02:57 am, you wrote:
> I too have had similar experiences to RC, but my experiences (as yet) under
> linux are frighteningly poor.
>
> My system is a single 500Mhz AMD K6-2, AIW 128 w/32Mb ram
>
> As soon as I hit the record button, I get a huge amount in my FIFO buffer,
> which rapidly fills up.
>
> The FIFO buffer increases at a much faster rate than the Frames encoded.
>
> The most I have been able to record is 1 minute with a FIFO buffer of 196
> Mb.
>
> Other than avView, no other program will touch recording from km, although
> they will display TV (I assume in overlay mode).
>
> Is there a likelihood of actual V4L compliance or V4L2 ? (So I can see if
> anything else will record better)
>
> Can I do anything other than hdparm and run off my fastest disk to improve
> the performance.
>
> When my machine was locking up, I disabled DRI/DRM in the kernel and in X,
> can I just disable it in one, or will this not help my encoding woes?
>
> I would love to get some of these videos (A whole collection will come to
> me if I can encode them to VCD) in a digital format, so I can move the
> actual tapes into storage.
>
> Any suggestions greatly appreciated, and thanks for your efforts thus far.
>

Well, km CVS and ffmpeg CVS work fine, Ive been able to encode to MPEG4 (not 
DivX) realtime. (on my Tbird 900) and I bet If it wasn't for the 30 feet of 
cable connecting my computer to the main line, Id have better quality too ;)

I also haven't been able to capture reliably with avview. But ffmpeg works 
fine.

-- 
Thomas Fjellstrom
tfj...@sh...
http://strangesoft.net

On Tue, 30 Apr 2002, Don Smith wrote:

> I would be interested in the patch to stop trashing the consoles, could
> you send it to me?
>
> also, i seem to recall that in windows i was able to change the location
> of the display through software, is there any way i can help provide
> information to get this worked on. The machine is still a dual boot
> linux/winme is there any information i can provide?

You can do this for a regular monitor by using xvidtune. For TV-out this
is not supported.

                      Vladimir Dergachev

>
> many thanks
>
> don smith
>
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

I would be interested in the patch to stop trashing the consoles, could 
you send it to me?

also, i seem to recall that in windows i was able to change the location 
of the display through software, is there any way i can help provide 
information to get this worked on. The machine is still a dual boot 
linux/winme is there any information i can provide?

many thanks

don smith

On 29-Apr-02 at 22:45, Don Smith (dcs...@ho...) wrote:
> Many thanks for the fine work in that i've been able to get TVout to work
> with my card after disabling pnpos in the motherboard bios.   Having said
> that i guess i have a few mandatory questions. 
> 
> 1. It seems to trash all my consoles is this normal?

Yes. I supplied a fix for this, but it wasn't accepted.

> 2. The screen is slightly off center, more to the right than it should be
> 3. the grey background in X has some sort of tiling on it but once i load
> ximian, everything looks fine 
> 
> Again Many thanks for the great work
> Don Smith

On Tue, Apr 30, 2002 at 12:06:00AM -0400, Vladimir Dergachev wrote:
> > 3. the grey background in X has some sort of tiling on it but once i load ximian, everything looks fine
> Most likely this is caused by scaling. Not a problem.
IMHO it is because the RGB grid is so large on TV, so depending on color the
line seems to be shorter or wider.

>                        best
>                          Vladimir Dergachev
Bye,

Peter Surda (Shurdeek) <shu...@pa...>, ICQ 10236103, +436505122023

--
                   It's not a bug, it's tradition!

On Tue, 30 Apr 2002, Russell Davies wrote:

> Can someone (preferably vlad and eanholt) provide a summary as to
> the current state of affairs with FreeBSD, the DRI kernel stuff and
> the GATOS drivers and which we should be using with what? I'm
> starting to get very confused!

Well, ati.2 should work with FreeBSD as is. But there is no version of
drm-kernel for FreeBSD so it won't work. Also, km is linux-only.

                         Vladimir Dergachev

>
> Last night, I attempted to get the following to work with
> FreeBSD-4.5-STABLE and XFree-4.2.0 and an ATI Radeon QD (AGP) (ChipID =
> 0x5144) (radeon aiw 32mb agp);
>
> 	1. dri via the new sysdrm-tcldrm material located at
> 	http://gladstone.uoregon.edu/~eanholt/dri/files.html
>
> 	2. The gatos radeon drivers in ATI-4.2.0-11.i386.tar.gz
>
> Now, the drivers that came with XFree-4.2.0 seemed to work fairly
> well (there are some known clipping issues with the Radeon however)
> and dri all worked, with pretty substantial benchmarks.
>
> However, after installing the ATI-4.2.0-11.i386.tar.gz binaries,
> X>x.log actually worked, but the screen was very distored, a
> subsequent 'startx' wedged the machine solid.
>
> I compiled the latest cvs checkout of ati.2 myself and installed
> those with similar results. The machine just locks. I'm trying to
> find out if what I'm trying to accomplish is possible at this stage.
> Namely;
>
> FreeBSD-4.5-STABLE, XFree86-4.2.0, the in-kernel dri driver from
> http://gladstone.uoregon.edu/~eanholt/dri/index.html and the GATOS
> radeon drivers.
>
> I could simply use the radeon drivers that XFree provides, but then
> I have no access to the TV Tuner/Composite Video on my card.
>
> cheers,
> 	Russell.
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

On Mon, 29 Apr 2002, Don Smith wrote:

> Many thanks for the fine work in that i've been able to get TVout to work with my card after disabling pnpos in the motherboard bios.
> Having said that i guess i have a few mandatory questions.
>
> 1. It seems to trash all my consoles is this normal?

yes.

> 2. The screen is slightly off center, more to the right than it should be

yes, we do not know how to correct this yet.

> 3. the grey background in X has some sort of tiling on it but once i load ximian, everything looks fine

Most likely this is caused by scaling. Not a problem.

                       best

                         Vladimir Dergachev

>
> Again Many thanks for the great work
> Don Smith
>

Many thanks for the fine work in that i've been able to get TVout to =
work with my card after disabling pnpos in the motherboard bios. =20
Having said that i guess i have a few mandatory questions.

1. It seems to trash all my consoles is this normal?
2. The screen is slightly off center, more to the right than it should =
be
3. the grey background in X has some sort of tiling on it but once i =
load ximian, everything looks fine

Again Many thanks for the great work
Don Smith

Can someone (preferably vlad and eanholt) provide a summary as to
the current state of affairs with FreeBSD, the DRI kernel stuff and
the GATOS drivers and which we should be using with what? I'm
starting to get very confused!

Last night, I attempted to get the following to work with
FreeBSD-4.5-STABLE and XFree-4.2.0 and an ATI Radeon QD (AGP) (ChipID =
0x5144) (radeon aiw 32mb agp);

	1. dri via the new sysdrm-tcldrm material located at
	http://gladstone.uoregon.edu/~eanholt/dri/files.html

	2. The gatos radeon drivers in ATI-4.2.0-11.i386.tar.gz

Now, the drivers that came with XFree-4.2.0 seemed to work fairly
well (there are some known clipping issues with the Radeon however)
and dri all worked, with pretty substantial benchmarks. 

However, after installing the ATI-4.2.0-11.i386.tar.gz binaries, 
X>x.log actually worked, but the screen was very distored, a
subsequent 'startx' wedged the machine solid.

I compiled the latest cvs checkout of ati.2 myself and installed
those with similar results. The machine just locks. I'm trying to
find out if what I'm trying to accomplish is possible at this stage.
Namely;

FreeBSD-4.5-STABLE, XFree86-4.2.0, the in-kernel dri driver from
http://gladstone.uoregon.edu/~eanholt/dri/index.html and the GATOS
radeon drivers.

I could simply use the radeon drivers that XFree provides, but then
I have no access to the TV Tuner/Composite Video on my card.

cheers,
	Russell.

On Monday 29 April 2002 12:23 pm, Vladimir Dergachev wrote:
> On Mon, 29 Apr 2002, Jesse Gough wrote:
> > Sorry if this has been answered elsewhere, I've looked around bothsites
> > with no luck finding an answer
> >
> > Basically I have the following
> > Radeon 7500 AIW
> > amd k6-2 500mhz
> > 256mb ram
> >
> > I would like to archive some videos using "composite" (my VCR) as my
> > input source, eventually in mpeg or mpeg2 format, as that has a good
> > compression+compatiblity tradeoff In windows I tried many things, and on
> > the fly mpeg encoding was hopeless, and avi recording was dropping alot
> > of frames, and the software was rather buggy If needed, recording as avi
> > then later converting to mpeg or mpeg2 is fine...on the fly would be ni=
ce
> > though In the current state of the gatos project, am I going to be able
> > to accomplish this goal with my system under linux?
>
> I do not think this would work at the moment. Two reasons:
>
>    1) VCR usually output Macrovision protected signal and you get a
>       corrupted picture when trying to capture that. (or some VCRs
>       just output a bad signal).

=46WIW - I've almost always used a VCR (cheapo analog, mono RCA outputs) as=
 a=20
video source on my AIW 128 Pro PCI captures... and it has worked reasonably=
=20
well... the best quality being avi/opendivx - although I could care less=20
about 'sharing' with MS users or encoding to another format (xine does a ve=
ry=20
nice job on playing most formats)

Of course you're machine needs to be outfitted with the appropriate=20
dll's/codec's, avifile, etc... to get everything to handle the various=20
encoding/decoding choices.

I haven't tried anything with my stereo/hi-fi VCR (macrovision?) or tapes w=
ith=20
any sort of implied copy protection.

>    2) To write raw data you need too much bandwidth. So AVview only
>       supports capturing compressed video and your CPU is not very fast.
>       Even with compression you need hard drive controller that supports
>       DMA to reduce CPU usage.

I agree on the bandwidth and CPU limitations - the last time I spent time w=
ith=20
avview and/or ffmpeg, my ATI card was in a p3 1GHz machine with 7200rpm IDE=
,=20
xfs filesystem, 2.4.17 kernel, etc... and I wouldn't try to do anything els=
e=20
on the machine during a capture.

(Things may have improved quite a bit since my last experiments... WRT=20
bandwidth, overhead, overruns, etc... but I haven't checked out the latest=
=20
'km' and friends lately)

=2D Jason

>                      Vladimir Dergachev
>
> > _______________________________________________
> > Gatos-devel mailing list
> > Gat...@li...
> > https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

Jesse Gough scribbled:

> Sorry if this has been answered elsewhere, I've looked around bothsites with no luck finding an answer
> 
> Basically I have the following
> Radeon 7500 AIW
> amd k6-2 500mhz
> 256mb ram
> 
> I would like to archive some videos using "composite" (my VCR) as my input source, eventually in mpeg or mpeg2 format, as that has a good compression+compatiblity tradeoff
> In windows I tried many things, and on the fly mpeg encoding was hopeless, and avi recording was dropping alot of frames, and the software was rather buggy
> If needed, recording as avi then later converting to mpeg or mpeg2 is fine...on the fly would be nice though
> In the current state of the gatos project, am I going to be able to accomplish this goal with my system under linux?
> 


With a 500Mhz chip, regardless of the video card, you are going to need 
to do some experimentation to determine a happy medium between quality
and performance. Especially, unfortunately, with the K6-2 family chips.

Your expected quality will not be much more than
video:
320x240x300000vbr (maybe half vbr 150000)
audio:
2400x9600 ( some experimentation here is required )

On another note...
IIRC there have been certain derogatory issues with the 7500
board WRT capture ( feel free to correct this, anybody )

note: your mileage will vary WRT patience




-- 
  Issued as is without warranty of any kind; without even the
  implied warranty of merchantability or fitness for a
  particular purpose - GNU General Public License

  the unofficial official GATOS irc at:
  irc.openprojects.net #gatos-ati
	# Ross Coleman
-----

> 
> I would like to archive some videos using "composite" (my VCR) as my input source, eventually in mpeg or mpeg2 format, as that has a good compression+compatiblity tradeoff

Didn't even get proper results in Windoze with ATI drivers...

On Mon, 29 Apr 2002, Jesse Gough wrote:

> Sorry if this has been answered elsewhere, I've looked around bothsites with no luck finding an answer
>
> Basically I have the following
> Radeon 7500 AIW
> amd k6-2 500mhz
> 256mb ram
>
> I would like to archive some videos using "composite" (my VCR) as my input source, eventually in mpeg or mpeg2 format, as that has a good compression+compatiblity tradeoff
> In windows I tried many things, and on the fly mpeg encoding was hopeless, and avi recording was dropping alot of frames, and the software was rather buggy
> If needed, recording as avi then later converting to mpeg or mpeg2 is fine...on the fly would be nice though
> In the current state of the gatos project, am I going to be able to accomplish this goal with my system under linux?
>

I do not think this would work at the moment. Two reasons:

   1) VCR usually output Macrovision protected signal and you get a
      corrupted picture when trying to capture that. (or some VCRs
      just output a bad signal).

   2) To write raw data you need too much bandwidth. So AVview only
      supports capturing compressed video and your CPU is not very fast.
      Even with compression you need hard drive controller that supports
      DMA to reduce CPU usage.

                     Vladimir Dergachev

>
>
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

On Mon, 29 Apr 2002, Bert Vermeulen wrote:
> On Mon, 29 Apr 2002, Russell Davies wrote:
> > I should probably also mention I'm unable to get sound working
> > either on this card with the latest ati.2 code and 4.2.0
> I've tried all the usual tricks I've seen people mention on this mailing
> list, but I'm not entirely convinced it's not a sound driver problem
> though... I have an SB live! 5.1, the driver of which apparently sucks;
> mixers don't work, for example. It may just be muted in the mixer, with no
> way for me to change that.

Try: connect the audio out of the card to line in. Connect headphones (or
analog speakers) to the Front out. Unmute&increase the level of line-in...

If you want another test, connect a male-male lead to the sound card line
in, and the other end to a CD-player/cassette player/radio (line out
preferable, use headphone if it doesn't have line-out). Don't turn the
volume up to anything that would be unpleasently loud with headphones; you
may damage the line-in circuit (portable devices powered via 2 cells
should be safest).

If you have the card connected internally, connect a CD-ROM drive
analog-out to that port, and play a CD. If you hear it, then the sound
card & driver are working fine (triv, disconnect any speakers attached to 
the front-out, and any digital-audio cable you may have).

-- 
Regards, ia...@bi...
My website: http://www.iain.thomas.dial.pipex.com/

Sorry if this has been answered elsewhere, I've looked around bothsites with no luck finding an answer

Basically I have the following
Radeon 7500 AIW
amd k6-2 500mhz
256mb ram

I would like to archive some videos using "composite" (my VCR) as my input source, eventually in mpeg or mpeg2 format, as that has a good compression+compatiblity tradeoff
In windows I tried many things, and on the fly mpeg encoding was hopeless, and avi recording was dropping alot of frames, and the software was rather buggy
If needed, recording as avi then later converting to mpeg or mpeg2 is fine...on the fly would be nice though
In the current state of the gatos project, am I going to be able to accomplish this goal with my system under linux?

TV-out is not supported by ati.2 drivers.

                              Vladimir Dergachev

On Mon, 29 Apr 2002, Ralf Oelschlaegel wrote:

> Hello,
>
> I'm testing a lot of X11-Modes to setup a XServer for Radeon VE on a PAL-TV
> via Composite, but all default modelines and all modelines I found, that should
> work, didn't.
> I use kernel 2.4.18, XFree 4.2.0 and the ati.2 + drm-kernel driver from CVS.
> No error messages but only flicker on the TV (the vesafb is running correct but
> to slow for video, dvd ...)
> Is there a modeline or special options to run this configuration with the
> ati/radeon
> driver?
>
> Thanks, Ralf
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

On Mon, 29 Apr 2002, Russell Davies wrote:

> I should probably also mention I'm unable to get sound working
> either on this card with the latest ati.2 code and 4.2.0

I've tried all the usual tricks I've seen people mention on this mailing
list, but I'm not entirely convinced it's not a sound driver problem
though... I have an SB live! 5.1, the driver of which apparently sucks;
mixers don't work, for example. It may just be muted in the mixer, with no
way for me to change that.


Bert Vermeulen
be...@bi...
--
Profanity is the inevitable linguistic crutch of the inarticulate motherfucker.

Hello,

I'm testing a lot of X11-Modes to setup a XServer for Radeon VE on a PAL-TV
via Composite, but all default modelines and all modelines I found, that should
work, didn't.
I use kernel 2.4.18, XFree 4.2.0 and the ati.2 + drm-kernel driver from CVS.
No error messages but only flicker on the TV (the vesafb is running correct but
to slow for video, dvd ...)
Is there a modeline or special options to run this configuration with the
ati/radeon
driver?

Thanks, Ralf

I should probably also mention I'm unable to get sound working
either on this card with the latest ati.2 code and 4.2.0

r.

On Mon, 29 Apr 2002, Bert Vermeulen wrote:

> On Sun, 28 Apr 2002, Vladimir Dergachev wrote:
>
> > The entire log of both cases would be helpful.
>
> I'll mail them to you off-list.
>
> > What happens is that somehow it cannot access BIOS on the second
> > attempt, I am unsure why. As a workaround try using GATOS specific
> > options that are mentioned at the end of http://gatos.sf.net/ati.2.php
> > (you can get the info of what to specify there from the successful log).
>
> That's the funny thing, X won't accept those options in the the Device
> section of that card. I've verified that the compiled modules have been
> installed properly etc, but it refuses any of those options.

What do you mean "wont' accept" ? Does it give you an error message ?
What happens if you only try to use one card ?

                        Vladimir Dergachev

>
>
> Bert Vermeulen
> be...@bi...
> --
> Profanity is the inevitable linguistic crutch of the inarticulate motherfucker.
>
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

On Sun, 28 Apr 2002, Vladimir Dergachev wrote:

> The entire log of both cases would be helpful.

I'll mail them to you off-list.

> What happens is that somehow it cannot access BIOS on the second
> attempt, I am unsure why. As a workaround try using GATOS specific
> options that are mentioned at the end of http://gatos.sf.net/ati.2.php
> (you can get the info of what to specify there from the successful log).

That's the funny thing, X won't accept those options in the the Device
section of that card. I've verified that the compiled modules have been
installed properly etc, but it refuses any of those options.


Bert Vermeulen
be...@bi...
--
Profanity is the inevitable linguistic crutch of the inarticulate motherfucker.

On Sun, Apr 28, 2002 at 03:38:47PM -0400, Alan Murrell wrote:
> So basically I should just grab the latest code from
> the CVS, compile it, and cross my fingers?  I can do
> that :-)
You forgot the most important phrase:
devel branch

> Alan
Bye,

Peter Surda (Shurdeek) <shu...@pa...>, ICQ 10236103, +436505=
122023

--
  funny thats the third time since ive been on IRC today that i seen the wo=
rd=20
                 "slave" and "microsoft" in the same sentence

The entire log of both cases would be helpful. What happens is that
somehow it cannot access BIOS on the second attempt, I am unsure why.
As a workaround try using GATOS specific options that are mentioned at the
end of http://gatos.sf.net/ati.2.php (you can get the info of what to
specify there from the successful log).

                            Vladimir Dergachev

On Sun, 28 Apr 2002, Bert Vermeulen wrote:

> Hi all,
>
> I'm having some problems using my ATI AIW radeon. I've compiled the latest
> XFree86 out of CVS, with the latest DRM and ati.2 modules out of the gatos
> CVS. Here's what I'm seeing:
>
> - the first time I run X with this driver (i.e. after boot), it all pretty
>   much works. I haven't tried tv-out (though that's what I eventually hope
>   to get out of it), but tv-in works somewhat, albeit without sound.
>
> - after quitting X and restarting it, the radeon won't initialize properly.
>   I think the problem may be related to I2C bus communication, not that I
>   know what that is.
>
> This comes up at first start:
>
> (II) RADEON(1): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6.
> (II) RADEON(1): Detected FQ1216ME/P device at 0xc6
> [...]
> (II) RADEON(1): I2C device "Radeon multimedia bus:MSP34xx" registered at address 0x80.
> (II) RADEON(1): Found MSP3410D, rom version 0x25, chip_id=0x040a
> (II) RADEON(1): Detected MSP3430 at 0x80
> [...]
> (II) RADEON(1): Device 1 on VIP bus ids as 4d541002
> (II) RADEON(1): Detected Rage Theatre revision 00000003
> (II) RADEON(1): 0x55 0xaa
> (II) RADEON(1): video decoder type is 0x40d8 versus 0x40d8
> (II) RADEON(1): Tuner is on port 0
> (II) RADEON(1): Composite connector is port 2
> (II) RADEON(1): SVideo connector is port 6
> (II) RADEON(1): Connectors (detected): tuner=0, composite=2, svideo=6
> (II) RADEON(1): Connectors (using): tuner=0, composite=2, svideo=6
> (II) RADEON(1): video decoder type used: 0x0006
> (II) RADEON(1): Rage Theatre setting standard 0x0000
> (II) RADEON(1): Rage Theatre setting standard 0x0000
> (II) RADEON(1): Rage Theatre Checkpoint 1
> (II) RADEON(1): Rage Theatre Checkpoint 2, counter=386
> (II) RADEON(1): Rage Theatre Checkpoint 3
> (II) RADEON(1): checkpoint 3a i=10
> (II) RADEON(1): checkpoint 3a i=9
> (II) RADEON(1): Rage Theatre Checkpoint 4
> (II) RADEON(1): Rage Theatre Checkpoint 5
> (II) RADEON(1): Rage Theatre setting standard 0x0000
> (II) RADEON(1): Direct rendering disabled
>
> Second and subsequent restarts:
>
> (II) RADEON(1): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6.
> (II) RADEON(1): Detected NO TUNNER device at 0xc6
> [...]
> (II) RADEON(1): I2C device "Radeon multimedia bus:MSP34xx" registered at address 0x80.
> (II) RADEON(1): Found MSP3410D, rom version 0x25, chip_id=0x040a
> (II) RADEON(1): Detected MSP3430 at 0x80
> [...]
> (II) RADEON(1): Device 0 on VIP bus ids as 3
> (II) RADEON(1): Device 1 on VIP bus ids as 4d541002
> (II) RADEON(1): Detected Rage Theatre revision 00000003
> (II) RADEON(1): 0x55 0xaa
> (II) RADEON(1): video decoder type is 0x4ce9 versus 0x4ce9
> (II) RADEON(1): Tuner is on port 0
> (II) RADEON(1): Tuner is on port 1
> (II) RADEON(1): Tuner is on port 2
> (II) RADEON(1): Tuner is on port 3
> (II) RADEON(1): Tuner is on port 4
> (II) RADEON(1): Rage Theatre: Connectors (detected): tuner=4, composite=0, svideo=0
> (II) RADEON(1): RageTheatre: Connectors (using): tuner=4, composite=0, svideo=0
> (II) RADEON(1): Unsupported reference clock frequency, Rage Theatre disabled
> (EE) RADEON(1): Failed to initialize Rage Theatre, chip disabled
> (II) RADEON(1): Direct rendering disabled
>
> I get a blank screen at that point.
>
> lspci identifies the card like as:
>
> 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon QD (prog-if 00 [VGA])
>         Subsystem: ATI Technologies Inc Radeon AIW
>
> The system also has a geforce2 in a PCI slot, which works fine on another
> monitor.
>
> Does anybody know what could cause this? Not knowing anything about how the
> whole thing fits together, I can't even begin to fix this. Is this card even
> supported? Is it possibly something like that I2C bus not getting
> initialized properly, or something or other not being reset when X exits?
>
> Incidentally, in the ati.2 driver, I've had to do this to get it to compile:
>
> --cut-here-----------------------------------------
> --- radeon_dri.c.orig   Sun Apr 28 19:20:45 2002
> +++ radeon_dri.c        Sun Apr 28 19:20:54 2002
> @@ -536,7 +536,7 @@
>         pSAREAPriv->nbox = 1;
>
>         ret = drmRadeonClear(info->drmFD,
> -                            DRM_RADEON_BACK | DRM_RADEON_DEPTH,
> +                            RADEON_BACK | RADEON_DEPTH,
>                              color, depth, color_mask, depth_mask,
>                              pSAREAPriv->boxes, pSAREAPriv->nbox);
>         if (ret) {
> --cut-here-----------------------------------------
>
>
> Any help is much appreciated.
>
>
> Bert Vermeulen
> be...@bi...
> --
> Profanity is the inevitable linguistic crutch of the inarticulate motherfucker.
>
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

On Sun, 28 Apr 2002, Alan Murrell wrote:

> > Yes it works. I haven't tested the model you have
> > personally (I have a AIW 128
> > 16M non-theatre), but we had positive reports from
> > owners of that card.
>
> I'll assume that by "owners of that card" you are
> referring to the model that I "have"? :-)
>
> So basically I should just grab the latest code from
> the CVS, compile it, and cross my fingers?  I can do
> that :-)

No. You should go and read http://gatos.sf.net/watching_tv.php

                     Vladimir Dergachev

>
> Thanx to all who have responded; you've helped clear
> things up for me, and given me a little more
> confidence andfaith that I didn;t waste my money (tho
> it would have been my fault for not researching more
> thoroughly! lol)
>
> Alan
>
>
> ______________________________________________________________________
> Post your ad for FREE! http://personals.yahoo.ca
>
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Hi all,

I'm having some problems using my ATI AIW radeon. I've compiled the latest
XFree86 out of CVS, with the latest DRM and ati.2 modules out of the gatos
CVS. Here's what I'm seeing:

- the first time I run X with this driver (i.e. after boot), it all pretty
  much works. I haven't tried tv-out (though that's what I eventually hope
  to get out of it), but tv-in works somewhat, albeit without sound.

- after quitting X and restarting it, the radeon won't initialize properly.
  I think the problem may be related to I2C bus communication, not that I
  know what that is.

This comes up at first start:

(II) RADEON(1): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6.
(II) RADEON(1): Detected FQ1216ME/P device at 0xc6
[...]
(II) RADEON(1): I2C device "Radeon multimedia bus:MSP34xx" registered at address 0x80.
(II) RADEON(1): Found MSP3410D, rom version 0x25, chip_id=0x040a
(II) RADEON(1): Detected MSP3430 at 0x80
[...]
(II) RADEON(1): Device 1 on VIP bus ids as 4d541002
(II) RADEON(1): Detected Rage Theatre revision 00000003
(II) RADEON(1): 0x55 0xaa
(II) RADEON(1): video decoder type is 0x40d8 versus 0x40d8
(II) RADEON(1): Tuner is on port 0
(II) RADEON(1): Composite connector is port 2
(II) RADEON(1): SVideo connector is port 6
(II) RADEON(1): Connectors (detected): tuner=0, composite=2, svideo=6
(II) RADEON(1): Connectors (using): tuner=0, composite=2, svideo=6
(II) RADEON(1): video decoder type used: 0x0006
(II) RADEON(1): Rage Theatre setting standard 0x0000
(II) RADEON(1): Rage Theatre setting standard 0x0000
(II) RADEON(1): Rage Theatre Checkpoint 1
(II) RADEON(1): Rage Theatre Checkpoint 2, counter=386
(II) RADEON(1): Rage Theatre Checkpoint 3
(II) RADEON(1): checkpoint 3a i=10
(II) RADEON(1): checkpoint 3a i=9
(II) RADEON(1): Rage Theatre Checkpoint 4
(II) RADEON(1): Rage Theatre Checkpoint 5
(II) RADEON(1): Rage Theatre setting standard 0x0000
(II) RADEON(1): Direct rendering disabled

Second and subsequent restarts:

(II) RADEON(1): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6.
(II) RADEON(1): Detected NO TUNNER device at 0xc6
[...]
(II) RADEON(1): I2C device "Radeon multimedia bus:MSP34xx" registered at address 0x80.
(II) RADEON(1): Found MSP3410D, rom version 0x25, chip_id=0x040a
(II) RADEON(1): Detected MSP3430 at 0x80
[...]
(II) RADEON(1): Device 0 on VIP bus ids as 3
(II) RADEON(1): Device 1 on VIP bus ids as 4d541002
(II) RADEON(1): Detected Rage Theatre revision 00000003
(II) RADEON(1): 0x55 0xaa
(II) RADEON(1): video decoder type is 0x4ce9 versus 0x4ce9
(II) RADEON(1): Tuner is on port 0
(II) RADEON(1): Tuner is on port 1
(II) RADEON(1): Tuner is on port 2
(II) RADEON(1): Tuner is on port 3
(II) RADEON(1): Tuner is on port 4
(II) RADEON(1): Rage Theatre: Connectors (detected): tuner=4, composite=0, svideo=0
(II) RADEON(1): RageTheatre: Connectors (using): tuner=4, composite=0, svideo=0
(II) RADEON(1): Unsupported reference clock frequency, Rage Theatre disabled
(EE) RADEON(1): Failed to initialize Rage Theatre, chip disabled
(II) RADEON(1): Direct rendering disabled

I get a blank screen at that point.

lspci identifies the card like as:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon QD (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Radeon AIW

The system also has a geforce2 in a PCI slot, which works fine on another
monitor.

Does anybody know what could cause this? Not knowing anything about how the
whole thing fits together, I can't even begin to fix this. Is this card even
supported? Is it possibly something like that I2C bus not getting
initialized properly, or something or other not being reset when X exits?

Incidentally, in the ati.2 driver, I've had to do this to get it to compile:

--cut-here-----------------------------------------
--- radeon_dri.c.orig   Sun Apr 28 19:20:45 2002
+++ radeon_dri.c        Sun Apr 28 19:20:54 2002
@@ -536,7 +536,7 @@
        pSAREAPriv->nbox = 1;

        ret = drmRadeonClear(info->drmFD,
-                            DRM_RADEON_BACK | DRM_RADEON_DEPTH,
+                            RADEON_BACK | RADEON_DEPTH,
                             color, depth, color_mask, depth_mask,
                             pSAREAPriv->boxes, pSAREAPriv->nbox);
        if (ret) {
--cut-here-----------------------------------------


Any help is much appreciated.


Bert Vermeulen
be...@bi...
--
Profanity is the inevitable linguistic crutch of the inarticulate motherfucker.