gatos-devel Mailing List for GATOS

Done. Thank you !

                      Vladimir Dergachev

On Fri, 25 Jun 2004, Maurizio Avogadro wrote:

> Vladimir,
>
> I noticed that the latest CVS version of km still doesn't include an 
> identifier for the Rage128 TF chip: since with that addition the CVS version 
> compiles correctly and the km modules load without problems, I think you 
> should consider the opportunity to add that identifier.
>
> Thank you
>
> Maurizio
>
> Maurizio Avogadro wrote:
>> Vladimir,
>> 
>> thank you, I was able to compile and insert the km modules successfully in 
>> my kernel 2.6.3-9mdk (mandrake 10.0): I made a quick test with avview and 
>> it seems that I can happily capture video from my card.
>> 
>> I don't remember how my card was detected by kernel 2.4.22 (the previous 
>> kernel I was using, mandrake 9.2), but with 2.4.x I could use km 0.5.0 
>> unpatched. I don't know if my include/linux/pci_ids.h was modified by 
>> Mandrake; I attach it in case you need it to help mandrake 10.0 users...
>> 
>> Thank you again
>> 
>> Maurizio
>> 
>> $ diff -U 2 km.c.orig km.c
>> 
>> --- km.c.orig    2004-03-15 01:20:16.000000000 +0100
>> +++ km.c    2004-05-07 00:42:14.000000000 +0200
>> @@ -933,4 +933,6 @@
>>          {PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RAGE128_PX,
>>           PCI_ANY_ID, PCI_ANY_ID, 0, 0, HARDWARE_RAGE128},   + 
>> {PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RAGE128_TF,
>> +         PCI_ANY_ID, PCI_ANY_ID, 0, 0, HARDWARE_RAGE128}, 
>> {PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RAGE128_TR,
>>           PCI_ANY_ID, PCI_ANY_ID, 0, 0, HARDWARE_RAGE128}, 
>> [...]
>

Vladimir,

I noticed that the latest CVS version of km still doesn't include an 
identifier for the Rage128 TF chip: since with that addition the CVS 
version compiles correctly and the km modules load without problems, I 
think you should consider the opportunity to add that identifier.

Thank you

Maurizio

Maurizio Avogadro wrote:
> Vladimir,
> 
> thank you, I was able to compile and insert the km modules successfully 
> in my kernel 2.6.3-9mdk (mandrake 10.0): I made a quick test with avview 
> and it seems that I can happily capture video from my card.
> 
> I don't remember how my card was detected by kernel 2.4.22 (the previous 
> kernel I was using, mandrake 9.2), but with 2.4.x I could use km 0.5.0 
> unpatched. I don't know if my include/linux/pci_ids.h was modified by 
> Mandrake; I attach it in case you need it to help mandrake 10.0 users...
> 
> Thank you again
> 
> Maurizio
> 
> $ diff -U 2 km.c.orig km.c
> 
> --- km.c.orig    2004-03-15 01:20:16.000000000 +0100
> +++ km.c    2004-05-07 00:42:14.000000000 +0200
> @@ -933,4 +933,6 @@
>          {PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RAGE128_PX,
>           PCI_ANY_ID, PCI_ANY_ID, 0, 0, HARDWARE_RAGE128},   
> +        {PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RAGE128_TF,
> +         PCI_ANY_ID, PCI_ANY_ID, 0, 0, HARDWARE_RAGE128},   
>          {PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RAGE128_TR,
>           PCI_ANY_ID, PCI_ANY_ID, 0, 0, HARDWARE_RAGE128},   
> 
> [...]

> is
>>> needed for capture, or do I have to somehow get the GATOS version to
>>> compile and load?
>> AFAIK that's what would be needed: to incorporate the changes in the
>> gatos radeon driver into the stock driver so that the dri initialization
>> does not interfere with km.
>
> So, the KM driver has been updated for 2.6, but DRM has not?  What's the
> point then?  Something doesn't make sense here.

You don't need DRM driver for capture - if you don't load it all will be 
well.

The reason for not porting DRM driver is that the new DRM driver contains 
an ioctl that allows to reconfigure MC controller - so they old hack is 
not necessary, but this requires changes in ati.4.4.0 drivers to support 
it..

                         best

                           Vladimir Dergachev

>
> Andy Johnson
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

On Thursday 24 June 2004 10:57 pm, Luis A. Montes wrote:
<snip>
> > > Have you tried removing the radeon dri module? I think that at this
> > > point the two are incompatible. They were not compatible with XFree86
> > > and there is no reason to believe that they got to be compatible in
> > > X.org without anybody really trying. Disregard the warning about sysfs
> > > for now, they will be fixed later.
> > 
> > ?
> > 
> > DRI works.  The tuner works using avview.  Capture does not, even though
> > it compiles and loads under 2.6.  The ati.4.4.0 modules in CVS compile and
> > load with X.org 6.7.  However, drm-kernel from CVS does not compile under
> > 2.6.  The real question is:  Does the 2.6 radeon kernel module have what 
is
> > needed for capture, or do I have to somehow get the GATOS version to
> > compile and load?
> AFAIK that's what would be needed: to incorporate the changes in the
> gatos radeon driver into the stock driver so that the dri initialization
> does not interfere with km.

So, the KM driver has been updated for 2.6, but DRM has not?  What's the
point then?  Something doesn't make sense here.

Andy Johnson

On Jun 24, 2004, at 11:00 PM, david goldfarb wrote:
>
>
> I just finished fighting that battle...The short answer is that the 
> "radeon" driver doesn't
> recognize the RV280 chipID (0x5964) given by the 9200SE.  Hence the 
> driver doesn't claim the
> device and the XFree86 ultimately can't find any Device section 
> willing to claim it.
>
> A quick check to see if this is the case, is to include a line "ChipID 
> 0x5157" in the Device
> section to force the system into thinking you have an 8500 (which is 
> supported by XFree86 4.3.0).
>
> After lots of poking around the XFree86 code I found a file:
>
> xc/programs/Xserver/hw/xfree86/scanpci/xf86PciIds.h
>
> which lists a lot of device IDs that are supported.  I am still a bit 
> confused as 0x5964 doesn't
> appear in XFree86 4.4.0 file either, but the stock 4.4.0 "radeon" 
> driver version does drive my
> 9200SE (without TV).
>
> I had been using the "fglrx" driver from ATI's WWW site which works 
> with TV_output as well, but
> that driver crashed and burned when I got a second 9200SE and tried to 
> setup Xinerama.  Now I am
> trying to get Xinerama working with TV_output.
>
> I recently started trying to integrate the TV_Output branch of the 
> ati.2 module into the ati.4.4.0
> module.  So far I haven't broken anything, but no TV-out yet.   I am 
> going to play with it a
> little more and then post the patch (working or not...) and see if 
> anybody else can help.
>
> David.

I was actually able to get things working by installing the ati-drivers 
from portage.  Fired right up with no issues.  The tv out screen  is 
slightly off center.. that's the only issue I'm having at this point.

>
> 	
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

> Haven"t found definitive documentation describing how I"m supposed to 
> make this all work, so here"s what I"ve done so far:  System is Gentoo 
> 2004.1, 2.6.7-gentoo-r5, XFree86 4.3.0.1, gatos 4.3.0.ebuild.
> 
> I"m trying to get X running, but I"m also trying to get TV-out working 
> as well.  My TV is connected to the composite output on the ATI card.
> 
> After everything was said and done, the ebuild put everything in 
> /usr/X11R6/lib/modules-extra/gatos.  I added the appropriate modules 
> line into XF86Config and renamed the default modules in 
> /usr/X11R6/lib/modules so X wouldn"t load them on startup.  I modified 
> XF86Config as follows:
> 
> Section "Device"
>      Identifier  "radeon"
>      Driver      "radeon"
> #       BusID   "PCI:1:0:0"
>          BusID   "PCI:1:0:1"
>      #VideoRam    131072
>      Option      "TVOutput" "NTSC"
>      # Insert Clocks lines here if appropriate
> EndSection


I just finished fighting that battle...The short answer is that the "radeon" driver doesn't
recognize the RV280 chipID (0x5964) given by the 9200SE.  Hence the driver doesn't claim the
device and the XFree86 ultimately can't find any Device section willing to claim it.

A quick check to see if this is the case, is to include a line "ChipID 0x5157" in the Device
section to force the system into thinking you have an 8500 (which is supported by XFree86 4.3.0).

After lots of poking around the XFree86 code I found a file:

xc/programs/Xserver/hw/xfree86/scanpci/xf86PciIds.h

which lists a lot of device IDs that are supported.  I am still a bit confused as 0x5964 doesn't
appear in XFree86 4.4.0 file either, but the stock 4.4.0 "radeon" driver version does drive my
9200SE (without TV).

I had been using the "fglrx" driver from ATI's WWW site which works with TV_output as well, but
that driver crashed and burned when I got a second 9200SE and tried to setup Xinerama.  Now I am
trying to get Xinerama working with TV_output.

I recently started trying to integrate the TV_Output branch of the ati.2 module into the ati.4.4.0
module.  So far I haven't broken anything, but no TV-out yet.   I am going to play with it a
little more and then post the patch (working or not...) and see if anybody else can help.

David.


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

On Thursday 24 June 2004 9:34 am, Luis A. Montes wrote:
> On Mon, 2004-06-21 at 22:45, Andrew S. Johnson wrote:
> > Avview from CVS works under Slackware 10.0 RC1 using the stock 2.6.7 kernel in 
> > testing/ and ati.4.4.0 from CVS.  Slackware now uses X.org, BTW.   Drm-kernel 
> > from CVS didn't compile (is it for 2.4.x only?), but the stock radeon kernel 
> > module seems to work for tuner support.  The km modules build and load, but I 
> > get this in dmesg when they are loaded:
> > 
> > Linux video capture interface: v1.00
> > Kmultimedia module version alpha-3.0 loaded
> > Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=1212
> > km: using irq 12
> > Register aperture is 0xed000000 0x00080000
> > kms variables: reg_aperture=0xe0e5e000
> > km: DMA_GUI_STATUS=0x00000002 entries=2
> > videodev: "Km" has no release callback. Please fix your driver for proper 
> > sysfs support, see http://lwn.net/Articles/36850/
> > videodev: "Km" has no release callback. Please fix your driver for proper 
> > sysfs support, see http://lwn.net/Articles/36850/
> > sizeof(kmfl_template)=780 sizeof(KM_FIELD)=52
> > Device ATI Technologies Inc Radeon R100 QD [Radeon 7200] 0000:01:00.0 
> > (0x1002:0x5144) corresponds to /dev/video0
> > kms variables: reg_aperture=0xe0e5e000
> > 
> > And this when I scan for the capture device:
> > 
> > Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
> > Purging transfer queue
> > WARNING !   Radeon memory controller is misconfigured, disabling capture
> > WARNING !   upgrade your Xserver and DRM driver
> > km: no data is available until AVview or xawtv is started
> > 
> > It doesn't crash or lockup, which is a pleasant surprise.  It looks like it's 
> > close.  Does anyone know how to make this work, or is it a non-working thing 
> > right now?
> Have you tried removing the radeon dri module? I think that at this
> point the two are incompatible. They were not compatible with XFree86
> and there is no reason to believe that they got to be compatible in
> X.org without anybody really trying. Disregard the warning about sysfs
> for now, they will be fixed later.

?

DRI works.  The tuner works using avview.  Capture does not, even though
it compiles and loads under 2.6.  The ati.4.4.0 modules in CVS compile and
load with X.org 6.7.  However, drm-kernel from CVS does not compile under
2.6.  The real question is:  Does the 2.6 radeon kernel module have what is
needed for capture, or do I have to somehow get the GATOS version to
compile and load?

Thanks,

Andy Johnson

> > 
> > Also, is the tuner output supposed to show on every KDE desktop as an alpha 
> > overlay, or is something wrong?  Is the alpha of the tuner display 
> > adjustable?  I did see a slider for changing the alpha of the background 
> > which works well enough, but I'm not sure why I'd want to do that.
> > 
> > Thanks,
> > 
> > Andy Johnson

Hi all,

I have a Rage Mobility P/M based notebook on which I'm
trying to get the TV-Out working. I have checked out
the cvs ati.2 tree and patched it with retinalburns
tvout patch. The patch applied cleanly and I'm stuck
there as I have xorg-x11 on my laptop.

Is there a way to compile ati.2 using xorg-x11? please
outline what sources I need and how to go about this.

I use gentoo and any specific tips would be really
appreciated.

The binaries both ati.2 & retinalburn's doesn't work
for me. The screen goes garbage when startng X.

Thanks for your time.

Venkat.


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

On Wed, 16 Jun 2004, Mark Brown wrote:

> [ Since the mailing list Admin refused to allow the large file bug reports to issue onto the list I have transcribed the salient points of the Bug Reports in text mode. ]
>
> Your request for details on the crashes. I have crashes of ATIMMC.EXE and Windows XP SP1 reboots.
> These crashes have occurred with 2 system:
> a) P4-2.0 GHz and P4-2.8 GHz // AsusP4S800 // 256MBytes PC2700
>
> b) P4 2.8 GHz // ECS 648FX-A // 512 MBytes PC3200
>
> 1) Every time a crash occurs, it crashes at the identical location, with the identical stack trace. I have sent the Microsoft Visual Studio Debugger details  paste from the most recent crash details to ATI around 10 times over the past 6 months. It has happened maybe 60 times.  I have never received any information back from them describing anything about what the program is doing at this location.  That is not behavior one would expect from a company determined to release bug-free product. These crashes are still occuring.
> The following Bug Reports will allow anyone intent on constructive discussion to muse on what could be causing these crashes.
>
> --------------------------------------------------------------------------
>
> Unhandled exception at Ox73ddl351 in ATIMMC.exe: OxCOOOOOO5: Access
> violation reading location Ox00000004.
>
> Address 73dd1351
> 73DD1340 ret 4
> 73DD1343 mov eax,dword ptr [eax+38h]
> 73DD1346 test eax,eax
> 73DD1348 jne 73E2E490
> 73DD134E jmp 73DD133F
> 73DD1350 push esi
> =>  73DD1351 mov esi,dword ptr [ecx+4]
> 73DD1354 test esi,esi
> 73DD1356 push edi
> 73DD1357 je 73DD137F
> 73DD1359 mov edi,dword ptr [esp+0Ch]
> 73DD135D xor edx,edx
> 73DD135F mov eax,edi
>
>
> Registers
> EAX = 00000000
> EBX = 73EA0008
> ECX = 00000000
> EDX = 00000003
> ESI = OOAF8400
> EDI = 00155074
> EIP = 73DD1351
> ESP = 06C9FCOC
> EBP = 06C9FC40
> EFL = 00000246
>
>
> Call Stack
> mfC42.dll!73ddl351()
> mfC42.dll!73dd5cl6()
> mfC42.dll!73e47754()
> mfC42.dll!73dd64dO()
> mfC42.dll!73dd64b9()
> mfC42.dll!73dd63fe()
> mfC42.dll!73de77ef()
> mfC42.dll!73dd62c4()
> ntdll.dll!77f7e45c()
> ntdll.dll!77f5f7ee()
> ntdll.dll!77f944cb()
> ntdll.dll!77f58bod()
> ntdll.dll!77f59037()
> ntdll.dll!77f59037()
> ntdll.dll!77f69456()
> ntdll.dll!77f69471()
> ntdll.dll!77f69464()
> kernel32.dll!77e73aal()
> ntdll.dll!77f6f5c7()
> mfC42.dll!73dd5d6e()
> ntdll.dll!77f5b42c()
> ntdll.dll!77f62864()
> brnel32.dll!77e798CC()
> ntdll.dll!77f95769()
> ntdll.dll!77f95769()
> kernel32.dll!77e7a65f()
> kernel32.dll!77e7a652()
> kernel32.dll!77e7990f()
> atidvcr.dll!06977578()
> atidvcr.dll!0697754e()
> ntdll.dll!77f57f98()
> atidvcr.dll!06977459()
> kernel32.dll!77e7d33b()
> ntdll.dll!77f57f98()


Well, this is the problem with debugging Windows - no symbols or code to 
pick through.. The only thing I know about this is that it went through ntdll
so this is likely equivalent to Linux "Oops" inside a driver - this often 
segfaults the application.

                             best

                                 Vladimir Dergachev

Haven't found definitive documentation describing how I'm supposed to 
make this all work, so here's what I've done so far:  System is Gentoo 
2004.1, 2.6.7-gentoo-r5, XFree86 4.3.0.1, gatos 4.3.0.ebuild.

I'm trying to get X running, but I'm also trying to get TV-out working 
as well.  My TV is connected to the composite output on the ATI card.

After everything was said and done, the ebuild put everything in 
/usr/X11R6/lib/modules-extra/gatos.  I added the appropriate modules 
line into XF86Config and renamed the default modules in 
/usr/X11R6/lib/modules so X wouldn't load them on startup.  I modified 
XF86Config as follows:

Section "Device"
     Identifier  "radeon"
     Driver      "radeon"
#       BusID   "PCI:1:0:0"
         BusID   "PCI:1:0:1"
     #VideoRam    131072
     Option      "TVOutput" "NTSC"
     # Insert Clocks lines here if appropriate
EndSection



I got the option lines above from a previous post in this list so I'm 
assuming they are correct.

When I start X with this configuration, it fails.  Here are snippets 
from my logs:

...
...
(II) LoadModule: "radeon"
(II) Loading /usr/X11R6/lib/modules-extra/gatos/drivers/radeon_drv.o
(II) Module radeon: vendor="The XFree86 Project"
         compiled for 4.3.0.1, module version = 4.0.1
         Module class: XFree86 Video Driver
         ABI class: XFree86 Video Driver, version 0.6
(II) LoadModule: "ati"
(II) Loading /usr/X11R6/lib/modules-extra/gatos/drivers/ati_drv.o
(II) Module ati: vendor="The XFree86 Project"
         compiled for 4.3.0.1, module version = 6.4.18
         Module class: XFree86 Video Driver
         ABI class: XFree86 Video Driver, version 0.6
...
...
(II) ATI: ATI driver (version 6.4.18) for chipsets: ati, ativga
(II) R128: Driver for ATI Rage 128 chipsets:
         ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF 
(AGP),
         ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML 
(AGP),
         ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB 
(PCI/AGP),
         ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI),
         ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP),
         ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH 
(PCI/AGP),
         ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ 
(PCI/AGP),
         ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL 
(PCI/AGP),
         ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN 
(PCI/AGP),
         ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI),
         ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI),
         ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT 
(PCI/AGP),
         ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV 
(PCI/AGP),
         ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX 
(PCI/AGP),
         ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
         ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
         ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP),
         ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP),
         ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP),
         ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP),
         ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP),
         ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR 
(AGP),
         ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT 
(AGP?),
         ATI Rage 128 Pro ULTRA TU (AGP?)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
         ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
         ATI Radeon VE/7000 QY (AGP), ATI Radeon VE/7000 QZ (AGP),
         ATI Radeon Mobility M7 LW (AGP),
         ATI Mobility FireGL 7800 M7 LX (AGP),
         ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ 
(AGP),
         ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QI (AGP),
         ATI Radeon 8500 QJ (AGP), ATI Radeon 8500 QK (AGP),
         ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP),
         ATI Radeon 8500 QN (AGP), ATI Radeon 8500 QO (AGP),
         ATI Radeon 8500 Qh (AGP), ATI Radeon 8500 Qi (AGP),
         ATI Radeon 8500 Qj (AGP), ATI Radeon 8500 Qk (AGP),
         ATI Radeon 8500 Ql (AGP), ATI Radeon 8500 BB (AGP),
         ATI Radeon 7500 QW (AGP), ATI Radeon 7500 QX (AGP),
         ATI Radeon 9000 Id (AGP), ATI Radeon 9000 Ie (AGP),
         ATI Radeon 9000 If (AGP), ATI Radeon 9000 Ig (AGP),
         ATI Radeon Mobility M9 Ld (AGP), ATI Radeon Mobility M9 Le 
(AGP),
         ATI Radeon Mobility M9 Lf (AGP), ATI Radeon Mobility M9 Lg 
(AGP),
         ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP),
         ATI Radeon 9500 AF (AGP), ATI FireGL Z1/X1 AG (AGP),
         ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
         ATI Radeon 9700 NF (AGP), ATI FireGL X1 NG (AGP)
(II) Primary Device is: PCI 01:00:0
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:0) 
found
(EE) No devices detected.

Fatal server error:
no screens found

I muddled around with it a bit and added BusID lines to the Driver in 
the Device section, but that did nothing.  I tried each of these but 
neither worked.

        BusID   "PCI:1:0:0"
        BusID   "PCI:1:0:1"

lspci -v and lspci -n:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400] Chipset 
Host Bridge
         Subsystem: Asustek Computer, Inc.: Unknown device 8118
         Flags: bus master, 66Mhz, medium devsel, latency 8
         Memory at e0000000 (32-bit, prefetchable)
         Capabilities: <available only to root>

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 
(prog-if 00 [Normal decode])
         Flags: bus master, 66Mhz, medium devsel, latency 0
         Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
         I/O behind bridge: 0000c000-0000cfff
         Memory behind bridge: e4000000-e5ffffff
         Prefetchable memory behind bridge: d0000000-dfffffff
         Expansion ROM at 0000c000 [disabled] [size=4K]
         Capabilities: <available only to root>

0000:00:08.0 Ethernet controller: Atheros Communications, Inc. AR5212 
802.11abg NIC (rev 01)
         Subsystem: D-Link System Inc DWL-G520 Wireless PCI Adapter
         Flags: bus master, medium devsel, latency 168, IRQ 16
         Memory at e6000000 (32-bit, non-prefetchable)
         Capabilities: <available only to root>

0000:00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 
01)
         Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge 
DVB card rev2.1
         Flags: bus master, medium devsel, latency 32, IRQ 17
         Memory at e6010000 (32-bit, non-prefetchable)

0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 
1.1 Controller (rev 80) (prog-if 00 [UHCI])
         Subsystem: Asustek Computer, Inc. A7V8X-X motherboard
         Flags: bus master, medium devsel, latency 32, IRQ 21
         I/O ports at d000 [size=32]
         Capabilities: <available only to root>

0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 
1.1 Controller (rev 80) (prog-if 00 [UHCI])
         Subsystem: Asustek Computer, Inc. A7V8X-X motherboard
         Flags: bus master, medium devsel, latency 32, IRQ 21
         I/O ports at d400 [size=32]
         Capabilities: <available only to root>

0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 
1.1 Controller (rev 80) (prog-if 00 [UHCI])
         Subsystem: Asustek Computer, Inc. A7V8X-X motherboard
         Flags: bus master, medium devsel, latency 32, IRQ 21
         I/O ports at d800 [size=32]
         Capabilities: <available only to root>

0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 
(prog-if 20 [EHCI])
         Subsystem: Asustek Computer, Inc. A7V8X-X motherboard rev 1.01
         Flags: bus master, medium devsel, latency 32, IRQ 21
         Memory at e6011000 (32-bit, non-prefetchable)
         Capabilities: <available only to root>

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
         Subsystem: Asustek Computer, Inc. A7V8X-X motherboard
         Flags: bus master, stepping, medium devsel, latency 0
         Capabilities: <available only to root>

0000:00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 
(prog-if 8a [Master SecP PriP])
         Subsystem: Asustek Computer, Inc. A7V8X-X motherboard rev. 1.01
         Flags: bus master, medium devsel, latency 32, IRQ 20
         I/O ports at dc00 [size=16]
         Capabilities: <available only to root>

0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. 
VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
         Subsystem: Asustek Computer, Inc. A7V600 motherboard (ADI 
AD1980 codec [SoundMAX])
         Flags: medium devsel, IRQ 22
         I/O ports at e000
         Capabilities: <available only to root>

0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 
[Rhine-II] (rev 74)
         Subsystem: Asustek Computer, Inc.: Unknown device 80ff
         Flags: bus master, medium devsel, latency 32, IRQ 23
         I/O ports at e800
         Memory at e6012000 (32-bit, non-prefetchable) [size=256]
         Capabilities: <available only to root>

0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV280 
[Radeon 9200 SE] (rev 01) (prog-if 00 [VGA])
         Subsystem: PC Partner Limited: Unknown device 7c26
         Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 16
         Memory at d0000000 (32-bit, prefetchable)
         I/O ports at c000 [size=256]
         Memory at e5000000 (32-bit, non-prefetchable) [size=64K]
         Capabilities: <available only to root>

0000:01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 
9200 SE] (Secondary) (rev 01)
         Subsystem: PC Partner Limited: Unknown device 7c27
         Flags: 66Mhz, medium devsel
         Memory at d8000000 (32-bit, prefetchable) [disabled]
         Memory at e5010000 (32-bit, non-prefetchable) [disabled] 
[size=64K]
         Capabilities: <available only to root>

...

0000:00:00.0 Class 0600: 1106:3205
0000:00:01.0 Class 0604: 1106:b198
0000:00:08.0 Class 0200: 168c:0013 (rev 01)
0000:00:09.0 Class 0480: 1131:7146 (rev 01)
0000:00:10.0 Class 0c03: 1106:3038 (rev 80)
0000:00:10.1 Class 0c03: 1106:3038 (rev 80)
0000:00:10.2 Class 0c03: 1106:3038 (rev 80)
0000:00:10.3 Class 0c03: 1106:3104 (rev 82)
0000:00:11.0 Class 0601: 1106:3177
0000:00:11.1 Class 0101: 1106:0571 (rev 06)
0000:00:11.5 Class 0401: 1106:3059 (rev 50)
0000:00:12.0 Class 0200: 1106:3065 (rev 74)
0000:01:00.0 Class 0300: 1002:5964 (rev 01)
0000:01:00.1 Class 0380: 1002:5d44 (rev 01)

...

This config worked ok before I used the gatos drivers (albeit, it 
complained about tvout but at least X started), but as soon as I tried 
with the new drivers, no dice!

Anyone have any ideas?

Avview from CVS works under Slackware 10.0 RC1 using the stock 2.6.7 kernel in 
testing/ and ati.4.4.0 from CVS.  Slackware now uses X.org, BTW.   Drm-kernel 
from CVS didn't compile (is it for 2.4.x only?), but the stock radeon kernel 
module seems to work for tuner support.  The km modules build and load, but I 
get this in dmesg when they are loaded:

Linux video capture interface: v1.00
Kmultimedia module version alpha-3.0 loaded
Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=1212
km: using irq 12
Register aperture is 0xed000000 0x00080000
kms variables: reg_aperture=0xe0e5e000
km: DMA_GUI_STATUS=0x00000002 entries=2
videodev: "Km" has no release callback. Please fix your driver for proper 
sysfs support, see http://lwn.net/Articles/36850/
videodev: "Km" has no release callback. Please fix your driver for proper 
sysfs support, see http://lwn.net/Articles/36850/
sizeof(kmfl_template)=780 sizeof(KM_FIELD)=52
Device ATI Technologies Inc Radeon R100 QD [Radeon 7200] 0000:01:00.0 
(0x1002:0x5144) corresponds to /dev/video0
kms variables: reg_aperture=0xe0e5e000

And this when I scan for the capture device:

Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
WARNING !   Radeon memory controller is misconfigured, disabling capture
WARNING !   upgrade your Xserver and DRM driver
km: no data is available until AVview or xawtv is started

It doesn't crash or lockup, which is a pleasant surprise.  It looks like it's 
close.  Does anyone know how to make this work, or is it a non-working thing 
right now?

Also, is the tuner output supposed to show on every KDE desktop as an alpha 
overlay, or is something wrong?  Is the alpha of the tuner display 
adjustable?  I did see a slider for changing the alpha of the background 
which works well enough, but I'm not sure why I'd want to do that.

Thanks,

Andy Johnson

Hello,
I have a Radeon AIW 7500.  Has anyone had any success getting this to
work under Fedora Core2 (X.org)?  If so, how?

Thanks in advance,
Anne =C2=A7:-)

Greg Stark wrote:
> Niklas Peinecke <n.p...@we...> writes:
> 
> 
>>I have a Rage Pro (Mach64 GT based) with TV-out and it works with retinal burn
>>patches.
> 
> 
> Mine says "ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT]".
> 
> 
>>Also I have modified Lennard Poettering's atitvout to support the Mach64 GT, so
>>you can use TV-out without the retinalburn patches, even for console &
>>framebuffer (as long as you do not switch resolution). I have not yet released
>>the code though.
> 
> 
> I would be interested in seeing this. I couldn't quite figure out how to use
> this program though. I don't use the framebuffer device currently though, does
> it work for normal X? Also, does it work if the ATI card isn't my primary
> graphics card?
> 
I'm a bit busy at work right now, but I'll try to prepare a version of 
the program for release, so you can try it out yourself. Maybe I'll also 
ask Lennard Poettering to include the patch.

I'll post when it's done.

Usage is straight forward:
1) Set your XServer to the desired resolution.
2) Run atitvout
3) Repeat every time you've switched resolution (e.g. if you change from 
graphics to text & vice versa)

It does work with X better than with framebuffer, because X doesn't 
touch the running graphics card, whereas framebuffer sometimes does 
(e.g. when starting mplayer).

I have no idea what happens in a mutiple card setup.

Niklas

Niklas Peinecke <n.p...@we...> writes:

> I have a Rage Pro (Mach64 GT based) with TV-out and it works with retinal burn
> patches.

Mine says "ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT]".

> Also I have modified Lennard Poettering's atitvout to support the Mach64 GT, so
> you can use TV-out without the retinalburn patches, even for console &
> framebuffer (as long as you do not switch resolution). I have not yet released
> the code though.

I would be interested in seeing this. I couldn't quite figure out how to use
this program though. I don't use the framebuffer device currently though, does
it work for normal X? Also, does it work if the ATI card isn't my primary
graphics card?

-- 
greg

At 01:14 18.06.2004, you wrote:

>Both work great with TV-Out, but it is getting a bit tough to hammer all
>the various patches together to make it work properly, unless you want
>to stick with XFree 4.3.0.  Especially on the Rage128 which doesn't have
>a monitor attached, and needs yet another patch.  That one I gave up on,
>and I'm back to just using MPlayer with the DirectFB vo on a vesa
>framebuffer console.

did you know you can build a "dummy monitor" with just a sub-d connector and some resistors? :)
i made one for an old tnt2 card which needed for some reason a monitor attached, worked like a charm.

>--
>Curtis Magyar
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
>Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
>Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
>REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
>_______________________________________________
>Gatos-devel mailing list
>Gat...@li...
>https://lists.sourceforge.net/lists/listinfo/gatos-devel

i'm using xfree86 4.3.0 with "ati-4.3.0-mach64tvout-20030328" from retinalburn (i think, at least i have that package lying around on my hdd). resolution is 800x600 with a depth of 16.  did you add the two option lines in the device section of your config? mine are:
Option   "TVout"
Option   "TVStandard" "PAL"


At 02:03 18.06.2004, you wrote:

>Bastian Farkas <ba...@fa...> writes:
>
>> my mach64 with tvtuner works just fine with retinalburns drivers.
>
>Really? Is this NTSC output or PAL? What bit depth and resolution are you
>running it at? What version of X and which download from retinalburn did you
>use?
>
>In my case it seems to be some kind of disagreement about colour mode. It
>looks like parts of the screen are in reverse video or even stranger. Kind of
>like some low order bits of one colour channel were mistakenly being used as
>high order bits of another colour channel.
>
>I guess I would have to take a photo of the tv and a screen shot of the CRT
>and put them side by side to show anyone what it looks like.
>
>The strange thing is one day it worked perfectly. I didn't do anything
>differently. It just worked. Watched a movie and it looked flawless. Since
>then it's never worked again.
>
>-- 
>greg
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
>Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
>Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
>REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
>_______________________________________________
>Gatos-devel mailing list
>Gat...@li...
>https://lists.sourceforge.net/lists/listinfo/gatos-devel

Greg Stark wrote:
> So what older ATI cards does tv-out support? I have a Mach64 that it doesn't
> support (I would love to get it working but the retinalburn stuff makes the
> colours come up all strangely for me). What about an "All-In-Wonder Pro"? What
> about a Radeon 7xxx?
> 

I have a Rage Pro (Mach64 GT based) with TV-out and it works with 
retinal burn patches.

Also I have modified Lennard Poettering's atitvout to support the Mach64 
GT, so you can use TV-out without the retinalburn patches, even for 
console & framebuffer (as long as you do not switch resolution). I have 
not yet released the code though.

Niklas

Bastian Farkas <ba...@fa...> writes:

> my mach64 with tvtuner works just fine with retinalburns drivers.

Really? Is this NTSC output or PAL? What bit depth and resolution are you
running it at? What version of X and which download from retinalburn did you
use?

In my case it seems to be some kind of disagreement about colour mode. It
looks like parts of the screen are in reverse video or even stranger. Kind of
like some low order bits of one colour channel were mistakenly being used as
high order bits of another colour channel.

I guess I would have to take a photo of the tv and a screen shot of the CRT
and put them side by side to show anyone what it looks like.

The strange thing is one day it worked perfectly. I didn't do anything
differently. It just worked. Watched a movie and it looked flawless. Since
then it's never worked again.

-- 
greg

On Thu, 2004-06-17 at 18:18 -0400, Greg Stark wrote:
> So what older ATI cards does tv-out support? I have a Mach64 that it doesn't
> support (I would love to get it working but the retinalburn stuff makes the
> colours come up all strangely for me). What about an "All-In-Wonder Pro"? What
> about a Radeon 7xxx?


I have two All In Wonder's:
ATI Technologies Inc Radeon R100 QD [Radeon 7200]
and
ATI Technologies Inc Rage 128 RF/SG AGP

Both work great with TV-Out, but it is getting a bit tough to hammer all
the various patches together to make it work properly, unless you want
to stick with XFree 4.3.0.  Especially on the Rage128 which doesn't have
a monitor attached, and needs yet another patch.  That one I gave up on,
and I'm back to just using MPlayer with the DirectFB vo on a vesa
framebuffer console.

--
Curtis Magyar

my mach64 with tvtuner works just fine with retinalburns drivers.

At 00:18 18.06.2004, you wrote:

>So what older ATI cards does tv-out support? I have a Mach64 that it doesn't
>support (I would love to get it working but the retinalburn stuff makes the
>colours come up all strangely for me). What about an "All-In-Wonder Pro"? What
>about a Radeon 7xxx?
>
>-- 
>greg
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
>Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
>Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
>REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
>_______________________________________________
>Gatos-devel mailing list
>Gat...@li...
>https://lists.sourceforge.net/lists/listinfo/gatos-devel

So what older ATI cards does tv-out support? I have a Mach64 that it doesn't
support (I would love to get it working but the retinalburn stuff makes the
colours come up all strangely for me). What about an "All-In-Wonder Pro"? What
about a Radeon 7xxx?

-- 
greg

>               * port km to newer kernels (I see 2.6.7 was just released)
I've been trying to fix km, again given that I'm not experienced with
kernel programing and like everybody else I'm trying to have a life
beyond work ... so it's my excuse for the shoddy work ;-) But it gets km
capturing again under 2.6.6. 

On Wed, 2004-06-16 at 06:59, Adrian Irving-Beer wrote:
> Hi all,
> 
> I'm having no end of issues with km.  I once had it all working pretty
> nicely, but now most everything seems broken in some manner or
> another.  :(
> 
> 
> General configuration:
>         * Debian testing (sarge)
>         * XFree86 4.3.0
>         * ati.2 4.3.0-14
> 
> 
> Problem #1:
>         * Kernel 2.6.6 (Debian 686-1)
cvs code as it is does not work with latests 2.6 kernels (I think
starting with 2.6.4). I'm trying to fix them but I got some issues with
my sourceforge account and I haven't been able to update files in cvs.
The problem is that the modules are not registering properly. This patch
should get the modules registered, although avview will still complain,
because it can't find the /proc entry. Just ignore it and go to select a
V4L device. It should be there. I just makes km capture in 2.6.6
>         * drm-kernel 1.9.0 20020828 (came with kernel)
>         * avview 0.12.0 (deb)
>         * ffmpeg 0.4.8 (deb)
> 
>     I can't get the time of day with km under a 2.6.6 kernel.
>     Attempting to use /dev/video gives me 'device not found'.
> 
> 
> Configuration for #2 and #3:
>         * Kernel 2.4.25 (Debian 686-1)
>         * drm-kernel 1.100.0 20021218 (CVS)
>         * ALSA (Debian modules)
>                 * SB Live, driver emu10k1
> 
> 
> Problem #2:
>         * avview 0.80.3 (CVS)
>                 * also occurs with avview 0.12.0 (deb)
>         * ffmpeg 0.4.8 (CVS)
>                 * also occurs with ffmpeg 0.4.8 (release)
>                 * and ffmpeg 0.4.8 (deb)
> 
>     Attempting to use ffmpeg with any codec seems to record at an
>     average of 5 frames per 40 seconds (0.12 fps).  Plus, each frame
>     is just black and empty anyway.
> 
> 
> Problem #3:
>         * avview 0.80.3 (CVS)
>         * ffmpeg 0.4.8 (release, compiled tree, used for libavcodec)
> 
>     avview records video perfectly.  Any attempt to record using sound
>     immediately segfaults it, though.  (This occurs after the 'don't
>     let your file get over 1 gig' warning.)
> 
> 
> With all that in mind, I suppose a temporary working solution is to
> use avview for video capture, grab the sound separately, and munge
> them back together with mencoder.
> 
> Any ideas?

Vladimir Dergachev wrote:

> 
>    * Matt Mercer has written some code for Rage Theatre 200 based on
>      the documentation, but had problems uploading the microcode to it -
>      it appears that part of documentation is unclear being written with
>      R300 chip in mind (and Matt has RV250 if I remember it right).
> 
>      So this code never got tested. Matt - could you please correct me
>      on this ?


This is pretty accurate.  Unfortunatly I am tied down with work and 
school to actually tinker with programming this chip at the moment.

Matt

>Message: 8
>From: Lourens Veen <lo...@ra...>
>To: "Mark Brown" <mb...@co...>,
>        "Marcus Brinkmann" <mar...@ru...>,
>        "Bryan D. Stine" <bat...@ge...>
>Subject: Re: [GATOS]AIW9000
>Date: Tue, 15 Jun 2004 23:16:31 +0200
>Cc: <ho...@ho...>, <gat...@li...>
>
>
>Why should they invest money into producing drivers for an OS hardly=20
>anyone uses, for a product that is just about the only one in its=20
>category? That's not a nice way to look at it, but it is the=20
>economical reality unfortunately.
>
>Also, putting pressure on them won't help if they can't release=20
>certain information because they would violate contracts with other=20
>companies if they did.=20
>
>I agree that it would be useful if Vladimir could update the=20
>Supported Cards page with a bit more of an explanation of the=20
>situation.
>
>Lourens
>--=20

Why should ATI not port the catalyst (or some subset of it) to Linux?
They support MacOS, and as far as I can tell, there are far more users
of Linux that MacOS.  Sheesh, not only is it a "non-standard" OS, but
it is "non-standard" hardware to boot (maybe a pun intended).  We are
paying customers just as are user's of other OS's, and ATI could easily
recoup their investment.  Why, they could even maybe hire some of the
Gatos team to do the port... In anycase, I don't buy the canard that
we are using an OS which "hardly anyone uses".  But, that's just my
opinion based on my own eyesight.

Sincerely,

William Epperly
cep...@ea...