gatos-devel Mailing List for GATOS

On Thu, 30 Nov 2006, huygens wrote:

>> Could you try adding
>>
>> #include <linux/poll.h>
>>
>> in the km_api_data.h file after the first #define line?
>
> Thank you for your reply!
> I have tried that, but get the following error now:
>
> make -C /lib/modules/2.6.18-1.2849.fc6/build M=3D/home/huygens/tarballs=
/km modules
> make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
>  CC [M]  /home/huygens/tarballs/km/km_api.o
> In Datei, eingef=C3=BCgt von /home/huygens/tarballs/km/km_api.c:31:
> /home/huygens/tarballs/km/km_api_data.h:11:9: Fehler: #include erwartet=
 "DATEINAME" oder <DATEINAME>
>
> --> That means: Error: #include expects "FILENAME" or <FILENAME>

This looks like a copy-paste error. Please make sure that the new line is=
=20
exactly as above. Especially make sure that there is < and > characters=20
around the file name and that there is nothing extra on the line.

--=20
Antti Ajanki

> Could you try adding
> 
> #include <linux/poll.h>
> 
> in the km_api_data.h file after the first #define line?

Thank you for your reply!
I have tried that, but get the following error now:

make -C /lib/modules/2.6.18-1.2849.fc6/build M=/home/huygens/tarballs/km modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
  CC [M]  /home/huygens/tarballs/km/km_api.o
In Datei, eingefügt von /home/huygens/tarballs/km/km_api.c:31:
/home/huygens/tarballs/km/km_api_data.h:11:9: Fehler: #include erwartet "DATEINAME" oder <DATEINAME>

--> That means: Error: #include expects "FILENAME" or <FILENAME>

make[2]: *** [/home/huygens/tarballs/km/km_api.o] Fehler 1
make[1]: *** [_module_/home/huygens/tarballs/km] Fehler 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
make: *** [all] Fehler 2




----------
Sent via SPRACI - http://www.spraci.com/ - Parties,Raves,Clubs,Festivals

On Tue, 28 Nov 2006, huygens wrote:

>I have got the same error when compiling km-0.6.1, but using Fedora Core=
 6 with kernel-2.6.18-1.2849.fc6.i686. I have also made the symbolic link=
 config.h > autoconf.h.
>
>Here is what I get as output from make:
>
>make -C /lib/modules/2.6.18-1.2849.fc6/build M=3D/home/huygens/tarballs/=
km modules
>make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
>  CC [M]  /home/huygens/tarballs/km/km_api.o
>  CC [M]  /home/huygens/tarballs/km/km_api_data.o
>  CC [M]  /home/huygens/tarballs/km/km_memory.o
>  CC [M]  /home/huygens/tarballs/km/km.o
>In file included from /home/huygens/tarballs/km/km.h:16,
>                 from /home/huygens/tarballs/km/km.c:39:
>/home/huygens/tarballs/km/km_api_data.h:92: Fehler: expected declaration=
 specifiers or =C2=BB...=C2=BC before =C2=BBpoll_table=C2=BC

Could you try adding

#include <linux/poll.h>

in the km_api_data.h file after the first #define line?

--=20
Antti Ajanki

On Sun, 26 Nov 2006, William M. Quarles wrote:

>Antti Ajanki wrote:
>> Is lircd running and does it recognize your remote? In Debian lircd is 
>> started by typing
>> 
>> /etc/init.d/lirc restart
>> 
>
>[root@localhost ~]# /etc/init.d/lirc restart
>Stopping infrared remote control daemon (lircd):           [  OK  ]
>Starting infrared remote control daemon (lircd):           [  OK  ]
>[root@localhost ~]#
>
>It doesn't say anything about whether or not my remote is recognized.

At least it doesn't report any errors. Maybe it prints some more 
information is syslog or some other log file?

>[root@localhost ~]# xmode2
>xmode2: No such file or directory
>xmode2: error opening /dev/lirc
>
>Also, from the man page on xmode2:
>
>"Of course this program won't work with hardware that decodes the 
>signals itself like e.g. TV cards or the Irman."

So, is your remote one of those?  Though, it shouldn't matter after you 
get lirc to recognize it.

>> Also, does avview print out any LIRC related error messages when you start 
>> it from the command line?
>> 
>
>[root@localhost ~]# libzvbi available export modules:
>         HTML:keyword "html" mimetype "text/html" extension "html,htm"
>         PNG:keyword "png" mimetype "image/png" extension "png"
>         PPM:keyword "ppm" mimetype "image/x-portable-pixmap" extension 
>"ppm"
>         Text:keyword "text" mimetype "text/plain" extension "txt"
>         VTX:keyword "vtx" mimetype "application/videotext" extension "vtx"
>NUM_ADAPTORS=1
>Adaptor 0: ATI Radeon Video Overlay
>                 type input video image
>                 ports 73
>73 ATI Radeon Video Overlay
>master=.controlwin row=1 column=0
>Looking for km device that corresponds to PCI:01:00.0
>master=.controlwin row=1 column=0

Which version is this? It should at least say:

Initializing LIRC.

and then give some warnings if it can't connect to lirc daemon.

-- 
Antti Ajanki

I have got the same error when compiling km-0.6.1, but using Fedora Core 6 with kernel-2.6.18-1.2849.fc6.i686. I have also made the symbolic link config.h > autoconf.h.

Here is what I get as output from make:

make -C /lib/modules/2.6.18-1.2849.fc6/build M=/home/huygens/tarballs/km modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
  CC [M]  /home/huygens/tarballs/km/km_api.o
  CC [M]  /home/huygens/tarballs/km/km_api_data.o
  CC [M]  /home/huygens/tarballs/km/km_memory.o
  CC [M]  /home/huygens/tarballs/km/km.o
In file included from /home/huygens/tarballs/km/km.h:16,
                 from /home/huygens/tarballs/km/km.c:39:
/home/huygens/tarballs/km/km_api_data.h:92: Fehler: expected declaration specifiers or »...¼ before »poll_table¼
/home/huygens/tarballs/km/km.c:51: Fehler: expected »)¼ before string constant
/home/huygens/tarballs/km/km.c:52: Fehler: expected »)¼ before string constant
/home/huygens/tarballs/km/km.c:53: Fehler: expected »)¼ before string constant
/home/huygens/tarballs/km/km.c: In Funktion »km_probe¼:
/home/huygens/tarballs/km/km.c:635: Warnung: format »%08lx¼ erwartet Typ »long unsigned int¼, aber Argument 2 hat Typ »resource_size_t¼
/home/huygens/tarballs/km/km.c:635: Warnung: format »%08lx¼ erwartet Typ »long unsigned int¼, aber Argument 3 hat Typ »resource_size_t¼
/home/huygens/tarballs/km/km.c:747: Fehler: Dereferenzierung eines Zeigers auf unvollstándigen Typen
/home/huygens/tarballs/km/km.c:759: Fehler: Dereferenzierung eines Zeigers auf unvollstándigen Typen
/home/huygens/tarballs/km/km.c:778: Fehler: Dereferenzierung eines Zeigers auf unvollstándigen Typen
/home/huygens/tarballs/km/km.c: In Funktion »km_remove¼:
/home/huygens/tarballs/km/km.c:800: Fehler: Dereferenzierung eines Zeigers auf unvollstándigen Typen
/home/huygens/tarballs/km/km.c: Auf höchster Ebene:
/home/huygens/tarballs/km/km.c:1026: Fehler: »PCI_DEVICE_ID_ATI_RADEON_LE¼ ist hier nicht deklariert (nicht in einer Funktion)
/home/huygens/tarballs/km/km.c:1028: Fehler: »PCI_DEVICE_ID_ATI_RADEON_LF¼ ist hier nicht deklariert (nicht in einer Funktion)
make[2]: *** [/home/huygens/tarballs/km/km.o] Fehler 1
make[1]: *** [_module_/home/huygens/tarballs/km] Fehler 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
make: *** [all] Fehler 2

Please help!




----------
Sent via SPRACI - http://www.spraci.com/ - Parties,Raves,Clubs,Festivals

Antti Ajanki wrote:
> On Fri, 17 Nov 2006, William M. Quarles wrote:
> 
> 
>>I downloaded the appropriate file, and copied and pasted the correct
>>remote values for my model into the /etc/lircd.conf file.  I changed the
>>button names to match what you wrote in the example file.  I still can't
>>get the remote to work properly.
> 
> 
> Is lircd running and does it recognize your remote? In Debian lircd is 
> started by typing
> 
> /etc/init.d/lirc restart
> 

[root@localhost ~]# /etc/init.d/lirc restart
Stopping infrared remote control daemon (lircd):           [  OK  ]
Starting infrared remote control daemon (lircd):           [  OK  ]
[root@localhost ~]#

It doesn't say anything about whether or not my remote is recognized.

> There is a utility program called xmode2 included in the LIRC package (at 
> least in the Debian). It should show visually IR pulses from the remote on 
> the screen if LIRC is correctly configured.

[root@localhost ~]# xmode2
xmode2: No such file or directory
xmode2: error opening /dev/lirc

Also, from the man page on xmode2:

"Of course this program won’t work with hardware that decodes the 
signals itself like e.g. TV cards or the Irman."

> Also, does avview print out any LIRC related error messages when you start 
> it from the command line?
> 

[root@localhost ~]# libzvbi available export modules:
         HTML:keyword "html" mimetype "text/html" extension "html,htm"
         PNG:keyword "png" mimetype "image/png" extension "png"
         PPM:keyword "ppm" mimetype "image/x-portable-pixmap" extension 
"ppm"
         Text:keyword "text" mimetype "text/plain" extension "txt"
         VTX:keyword "vtx" mimetype "application/videotext" extension "vtx"
NUM_ADAPTORS=1
Adaptor 0: ATI Radeon Video Overlay
                 type input video image
                 ports 73
73 ATI Radeon Video Overlay
master=.controlwin row=1 column=0
Looking for km device that corresponds to PCI:01:00.0
master=.controlwin row=1 column=0

> 
>>Any thoughts?  I would prefer to generate my own file, but I have tried
>>and I can't figure out how to do it, nor can I find instructions on it
>>on the LiRC website.
> 
> 
> A program called irrecord will do this. It too comes with LIRC.
> 

As I said, I tried and I can't get it to work.  Although I could have 
been more explicit.

[root@localhost ~]# irrecord --driver=atilibusb ati_remote.txt

irrecord -  application for recording IR-codes for usage with lirc

Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...)

irrecord: could not init hardware (lircd running ? --> close it, check 
permissions)
[root@localhost ~]# /etc/init.d/lirc stop
Stopping infrared remote control daemon (lircd):           [  OK  ]
[root@localhost ~]# irrecord --driver=atilibusb ati_remote.txt

irrecord -  application for recording IR-codes for usage with lirc

Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...)

irrecord: could not init hardware (lircd running ? --> close it, check 
permissions)

Meh.

Peace,
William

I am trying to compile km (cvs 2006-11-21) on my Fedore Core 6, x86_64
system.

Got as far as creating link:

config.h -> autoconf.h

in the kernel sources.

Now, make fails with:

make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-x86_64'
  CC [M]  /tmp/build/km/km_api.o
  CC [M]  /tmp/build/km/km_api_data.o
  CC [M]  /tmp/build/km/km_memory.o
  CC [M]  /tmp/build/km/km.o
In file included from /tmp/build/km/km.h:16,
                 from /tmp/build/km/km.c:40:
/tmp/build/km/km_api_data.h:92: error: expected declaration specifiers
or ‘...’ before ‘poll_table’


...

any help would be greatly appreciated.


Marc

> On Sun, 19 Nov 2006 18:04:19 +0100 (CET), "Michael Fritscher"
> <mi...@fr...> wrote :
>> >> > I was a previous happy user of the GATOS driver for my ATI
>> >> > All-In-wonder 128 16 Mb but I have some problems to set it up
>> >> > correctly with Xorg.
>> >> >
>> >> > I'm running Debian Testing which got Xorg 7.1.0-6 and I can't
>> >> > start xawtv anymore. It seems that no device has been detected :
>> >
>> > [snip]
>> >
>> >> > Can someone be so kind as to send me an appropriate or similar
>> >> > Xorg configuration file xorg.conf ?
>> >> >
>> >> > And what could possibly has gone wrong ?
>> >
>> >> Which driver did you use? if you used the ati.2 driver, you need
>> >> new drivers...
>> >> I've created a patch against xorg 7.1-cvs, which can be found here:
>> >> http://mifritscher.de/ati2.patch.gz
>> >> But it has the old xvideo vs. dri problem...
>> >> More infos can be found here:
>> >> https://bugs.freedesktop.org/show_bug.cgi?id=3D8811
>> >>
>> >
>> > Hello,
>> >
>> > I haven't used any ati.2 driver : I thought that everything was
>> > merged with Xorg...
>> >
>> > What do I have to do ? Can I wait for the changes to be reflected
>> > in my Debian release of Xorg or will I have to manually compile the
>> > patch each and everytime ?
>> >
>> > I'm a little lost in what I should do in order to have everything
>> > work with my AIW 128. From the GATOS website it seems that I don't
>> > have to use the ati.2 drivers but I still have to get the km or
>> > v4l2 driver (which one ?) to have videocapture.
>> >
>> > For debugging purpose how can I test if I got 3D acceleration, 2D
>> > acceleration and Xvimage (DVD hardware acceleration), capture,
>> > etc... I've only tried glxgears but it almost freeze my system
>> > (with CPU usage skyrocketting).
>> >
>> > I'm not sure that I've loaded every necessary module (haven't heard
>> > before of i2c and detec_theatre), could it be the problem ?
>> >
>> > Thanks again,
>> >
>> > P.S. : could you send me your xorg.conf to give me some ideas ?
>> I'm not at home atm, but I used a standard xorg.conf extended the
>> modules i2c and detect_threatre. I hope the that patch gets official
>> when the dri+ Xv problem get fixed.
>> I think I used km/v4l2 long time ago with x.org 6.7, but the picture
>> interfered extremly with the desktop, with AccleratedX I got a good
>> picture, but no audio *g*
>
> Ok so I'll have to wait until the patch get official.
> Did you manage to get the DVD playback acceleration working ?
> It's mentionned as 'Xvimage' on the GATOS web site, I don't know if
> that's what you intend to say with 'Xv'.
>
> Regards,
>
I'll try to fix the dri-bug this weekend, but I have to repair the
dri-files , I've a mixture from Xorg 7.1 from ubuntu and 7.1-git/cvs...
drivers are working fine between this versions, but the dri-subsystem
don't.
I didn't try DVD-playback yet, Xv is the video-subsystem from X.

I also want to add that I can play dvd using vlc at 800X600
wxvlc shows 11% of my  AMD Athlon(tm) XP 3200+
at full screen

Can't I get 640X480?

Niv wrote:
> I can confirm getting 800x600 in tv out on a PAL tv.
> looks good so far.
> it didnt look so good , so I tried choosing 640x480 in xfce4, and got a 
> bad blue screen. its a xfce4 thing. will try it again soon, and report back
> 
> thanks,
> 
> niv
> Rune Petersen wrote:
>> David R. Litwin wrote:
>>> On 27/10/06, *Niv* <ni...@cs... <mailto:ni...@cs...>> wrote:
>>>
>>>     According to the gentoo wiki (I use gentoo)
>>>     http://gentoo-wiki.com/HOWTO_TV-Out, the gatos project is less up to
>>>     date then the tv out implantations in the radeon/ati driver that merged
>>>     to xorg x11 7.
>>>
>>>
>>> 1: I read that it was only the input in which was merged; not tv-output. 2: I have xorg 7.1. 3, the gatos driver (or patch) is only for xorg 7.0 and ati
>>> driver 6.6.3. however, the patch from 
>>> http://www.ece.auckland.ac.nz/~wsun013/tvout/index.html may be for this driver. 4: I have debian, not gentoo.
>>>
>>>
>>>     I will give it a go later and share my expirince.
>> I have made a patch for 6.6.3:
>> http://megahurts.dk/rune/stuff/xorg7.1-6.6.3-tv_output.patch.gz
>>
>> If you could report back if it works, I'll add it on the page.
>>
>>
>> Rune Petersen
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

On Sun, 19 Nov 2006 18:04:19 +0100 (CET), "Michael Fritscher"
<mi...@fr...> wrote :
> >> > I was a previous happy user of the GATOS driver for my ATI
> >> > All-In-wonder 128 16 Mb but I have some problems to set it up
> >> > correctly with Xorg.
> >> >
> >> > I'm running Debian Testing which got Xorg 7.1.0-6 and I can't
> >> > start xawtv anymore. It seems that no device has been detected :
> >
> > [snip]
> >
> >> > Can someone be so kind as to send me an appropriate or similar
> >> > Xorg configuration file xorg.conf ?
> >> >
> >> > And what could possibly has gone wrong ?
> >
> >> Which driver did you use? if you used the ati.2 driver, you need
> >> new drivers...
> >> I've created a patch against xorg 7.1-cvs, which can be found here:
> >> http://mifritscher.de/ati2.patch.gz
> >> But it has the old xvideo vs. dri problem...
> >> More infos can be found here:
> >> https://bugs.freedesktop.org/show_bug.cgi?id=8811
> >>
> >
> > Hello,
> >
> > I haven't used any ati.2 driver : I thought that everything was
> > merged with Xorg...
> >
> > What do I have to do ? Can I wait for the changes to be reflected
> > in my Debian release of Xorg or will I have to manually compile the
> > patch each and everytime ?
> >
> > I'm a little lost in what I should do in order to have everything
> > work with my AIW 128. From the GATOS website it seems that I don't
> > have to use the ati.2 drivers but I still have to get the km or
> > v4l2 driver (which one ?) to have videocapture.
> >
> > For debugging purpose how can I test if I got 3D acceleration, 2D
> > acceleration and Xvimage (DVD hardware acceleration), capture,
> > etc... I've only tried glxgears but it almost freeze my system
> > (with CPU usage skyrocketting).
> >
> > I'm not sure that I've loaded every necessary module (haven't heard
> > before of i2c and detec_theatre), could it be the problem ?
> >
> > Thanks again,
> >
> > P.S. : could you send me your xorg.conf to give me some ideas ?
> I'm not at home atm, but I used a standard xorg.conf extended the
> modules i2c and detect_threatre. I hope the that patch gets official
> when the dri+ Xv problem get fixed.
> I think I used km/v4l2 long time ago with x.org 6.7, but the picture
> interfered extremly with the desktop, with AccleratedX I got a good
> picture, but no audio *g*

Ok so I'll have to wait until the patch get official.
Did you manage to get the DVD playback acceleration working ?
It's mentionned as 'Xvimage' on the GATOS web site, I don't know if
that's what you intend to say with 'Xv'.

Regards,

> On Sun, 19 Nov 2006 15:10:39 +0100 (CET), "Michael Fritscher"
> <mi...@fr...> wrote :
>
>> > Hello,
>> >
>> > I was a previous happy user of the GATOS driver for my ATI
>> > All-In-wonder 128 16 Mb but I have some problems to set it up
>> > correctly with Xorg.
>> >
>> > I'm running Debian Testing which got Xorg 7.1.0-6 and I can't start
>> > xawtv anymore. It seems that no device has been detected :
>
> [snip]
>
>> > Can someone be so kind as to send me an appropriate or similar
>> > Xorg configuration file xorg.conf ?
>> >
>> > And what could possibly has gone wrong ?
>
>> Which driver did you use? if you used the ati.2 driver, you need new
>> drivers...
>> I've created a patch against xorg 7.1-cvs, which can be found here:
>> http://mifritscher.de/ati2.patch.gz
>> But it has the old xvideo vs. dri problem...
>> More infos can be found here:
>> https://bugs.freedesktop.org/show_bug.cgi?id=3D8811
>>
>
> Hello,
>
> I haven't used any ati.2 driver : I thought that everything was merged
> with Xorg...
>
> What do I have to do ? Can I wait for the changes to be reflected in my
> Debian release of Xorg or will I have to manually compile the patch
> each and everytime ?
>
> I'm a little lost in what I should do in order to have everything work
> with my AIW 128. From the GATOS website it seems that I don't have to
> use the ati.2 drivers but I still have to get the km or v4l2 driver
> (which one ?) to have videocapture.
>
> For debugging purpose how can I test if I got 3D acceleration, 2D
> acceleration and Xvimage (DVD hardware acceleration), capture, etc...
> I've only tried glxgears but it almost freeze my system (with CPU usage
> skyrocketting).
>
> I'm not sure that I've loaded every necessary module (haven't heard
> before of i2c and detec_theatre), could it be the problem ?
>
> Thanks again,
>
> P.S. : could you send me your xorg.conf to give me some ideas ?
I'm not at home atm, but I used a standard xorg.conf extended the modules
i2c and detect_threatre. I hope the that patch gets official when the dri=
+
Xv problem get fixed.
I think I used km/v4l2 long time ago with x.org 6.7, but the picture
interfered extremly with the desktop, with AccleratedX I got a good
picture, but no audio *g*

On Sun, 19 Nov 2006 15:10:39 +0100 (CET), "Michael Fritscher"
<mi...@fr...> wrote :

> > Hello,
> >
> > I was a previous happy user of the GATOS driver for my ATI
> > All-In-wonder 128 16 Mb but I have some problems to set it up
> > correctly with Xorg.
> >
> > I'm running Debian Testing which got Xorg 7.1.0-6 and I can't start
> > xawtv anymore. It seems that no device has been detected :

[snip]

> > Can someone be so kind as to send me an appropriate or similar
> > Xorg configuration file xorg.conf ?
> >
> > And what could possibly has gone wrong ?

> Which driver did you use? if you used the ati.2 driver, you need new
> drivers...
> I've created a patch against xorg 7.1-cvs, which can be found here:
> http://mifritscher.de/ati2.patch.gz
> But it has the old xvideo vs. dri problem...
> More infos can be found here:
> https://bugs.freedesktop.org/show_bug.cgi?id=8811
> 

Hello,

I haven't used any ati.2 driver : I thought that everything was merged
with Xorg...

What do I have to do ? Can I wait for the changes to be reflected in my
Debian release of Xorg or will I have to manually compile the patch
each and everytime ?

I'm a little lost in what I should do in order to have everything work
with my AIW 128. From the GATOS website it seems that I don't have to
use the ati.2 drivers but I still have to get the km or v4l2 driver
(which one ?) to have videocapture.

For debugging purpose how can I test if I got 3D acceleration, 2D
acceleration and Xvimage (DVD hardware acceleration), capture, etc...
I've only tried glxgears but it almost freeze my system (with CPU usage
skyrocketting).

I'm not sure that I've loaded every necessary module (haven't heard
before of i2c and detec_theatre), could it be the problem ?

Thanks again,

P.S. : could you send me your xorg.conf to give me some ideas ?

> Hello,
>
> I was a previous happy user of the GATOS driver for my ATI
> All-In-wonder 128 16 Mb but I have some problems to set it up correctly
> with Xorg.
>
> I'm running Debian Testing which got Xorg 7.1.0-6 and I can't start
> xawtv anymore. It seems that no device has been detected :
> linux@linux:~$ xawtv
> This is xawtv-3.95, running on Linux/i686 (2.6.17.11)
> can't open /dev/video0: No such device
> v4l-conf had some trouble, trying to continue anyway
> v4l2: open /dev/video0: No such device
> v4l2: open /dev/video0: No such device
> v4l: open /dev/video0: No such device
> no video grabber device available
>
> And if trying to run v4l-conf:
> linux@linux:~$ v4l-conf
> v4l-conf: using X11 display :0.0
> dga: version 2.0
> mode: 1024x768, depth=3D16, bpp=3D16, bpl=3D2048, base=3D0xe0000000
> can't open /dev/video0: No such device
>
> Or xawtv -hwscan:
> linux@linux:~$ xawtv -hwscan
> This is xawtv-3.95, running on Linux/i686 (2.6.17.11)
> looking for available devices
> port 73-73
>     type : Xvideo, image scaler
>     name : ATI Rage128 Video Overlay
>
> Can someone be so kind as to send me an appropriate or similar
> Xorg configuration file xorg.conf ?
>
> And what could possibly has gone wrong ?
>
> Thanks in advance,
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
Which driver did you use? if you used the ati.2 driver, you need new
drivers...
I've created a patch against xorg 7.1-cvs, which can be found here:
http://mifritscher.de/ati2.patch.gz
But it has the old xvideo vs. dri problem...
More infos can be found here:
https://bugs.freedesktop.org/show_bug.cgi?id=3D8811

I can confirm getting 800x600 in tv out on a PAL tv.
looks good so far.
it didnt look so good , so I tried choosing 640x480 in xfce4, and got a 
bad blue screen. its a xfce4 thing. will try it again soon, and report back

thanks,

niv
Rune Petersen wrote:
> David R. Litwin wrote:
>>
>> On 27/10/06, *Niv* <ni...@cs... <mailto:ni...@cs...>> wrote:
>>
>>     According to the gentoo wiki (I use gentoo)
>>     http://gentoo-wiki.com/HOWTO_TV-Out, the gatos project is less up to
>>     date then the tv out implantations in the radeon/ati driver that merged
>>     to xorg x11 7.
>>
>>
>> 1: I read that it was only the input in which was merged; not tv-output. 2: I have xorg 7.1. 3, the gatos driver (or patch) is only for xorg 7.0 and ati
>> driver 6.6.3. however, the patch from 
>> http://www.ece.auckland.ac.nz/~wsun013/tvout/index.html may be for this driver. 4: I have debian, not gentoo.
>>
>>
>>     I will give it a go later and share my expirince.
> 
> I have made a patch for 6.6.3:
> http://megahurts.dk/rune/stuff/xorg7.1-6.6.3-tv_output.patch.gz
> 
> If you could report back if it works, I'll add it on the page.
> 
> 
> Rune Petersen

Hello,

I was a previous happy user of the GATOS driver for my ATI
All-In-wonder 128 16 Mb but I have some problems to set it up correctly
with Xorg.

I'm running Debian Testing which got Xorg 7.1.0-6 and I can't start
xawtv anymore. It seems that no device has been detected :
linux@linux:~$ xawtv
This is xawtv-3.95, running on Linux/i686 (2.6.17.11)
can't open /dev/video0: No such device
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: No such device
v4l2: open /dev/video0: No such device
v4l: open /dev/video0: No such device
no video grabber device available

And if trying to run v4l-conf:
linux@linux:~$ v4l-conf
v4l-conf: using X11 display :0.0
dga: version 2.0
mode: 1024x768, depth=16, bpp=16, bpl=2048, base=0xe0000000
can't open /dev/video0: No such device

Or xawtv -hwscan:
linux@linux:~$ xawtv -hwscan
This is xawtv-3.95, running on Linux/i686 (2.6.17.11)
looking for available devices
port 73-73
    type : Xvideo, image scaler
    name : ATI Rage128 Video Overlay

Can someone be so kind as to send me an appropriate or similar
Xorg configuration file xorg.conf ?

And what could possibly has gone wrong ?

Thanks in advance,

On Fri, 17 Nov 2006, William M. Quarles wrote:

> I downloaded the appropriate file, and copied and pasted the correct
> remote values for my model into the /etc/lircd.conf file.  I changed the
> button names to match what you wrote in the example file.  I still can't
> get the remote to work properly.

Is lircd running and does it recognize your remote? In Debian lircd is 
started by typing

/etc/init.d/lirc restart

There is a utility program called xmode2 included in the LIRC package (at 
least in the Debian). It should show visually IR pulses from the remote on 
the screen if LIRC is correctly configured.

Also, does avview print out any LIRC related error messages when you start 
it from the command line?

> Any thoughts?  I would prefer to generate my own file, but I have tried
> and I can't figure out how to do it, nor can I find instructions on it
> on the LiRC website.

A program called irrecord will do this. It too comes with LIRC.

-- 
Antti Ajanki

Antti Ajanki wrote:
> On Wed, 15 Nov 2006, William M. Quarles wrote:
> 
> 
>>Antti Ajanki wrote:
>>
>>>The button names depend on your LIRC configuration. They can be found from
>>>/etc/lirc/lircd.conf.
>>>
>>
>>Um, I don't even have a /etc/lirc/lircd.conf file.  Aren't they device
>>dependent?
> 
> 
> Yes they indeed are, but they also specify the names that LIRC uses for 
> the remote control buttons. LIRC won't work without the file, there is 
> information about downloading/generating the file on the LIRC 
> documentation. Some distros may call it /etc/lircd.conf.
> 
> 

I downloaded the appropriate file, and copied and pasted the correct 
remote values for my model into the /etc/lircd.conf file.  I changed the 
button names to match what you wrote in the example file.  I still can't 
get the remote to work properly.

begin remote

   name  ATIUSB_5000023600
   bits           16
   eps            30
   aeps          100

   one             0     0
   zero            0     0
   pre_data_bits   8
   pre_data       0x14
   post_data_bits  16
   post_data      0x0
   gap          227972
   min_repeat      4
   toggle_bit      0


       begin codes
           1                        0x000000000000920D
           2                        0x000000000000930E
           3                        0x000000000000940F
           4                        0x0000000000009510
           5                        0x0000000000009611
           6                        0x0000000000009712
           7                        0x0000000000009813
           8                        0x0000000000009914
           9                        0x0000000000009A15
           A                        0x0000000000008500
           B                        0x0000000000008601
           POWER                    0x0000000000008702
           TV                       0x0000000000008803
           DVD                      0x0000000000008904
           WEB                      0x0000000000008A05
           MEDIA_LIBRARY            0x0000000000008B06
           drag                     0x0000000000008C07
           0                        0x0000000000009C17
           C                        0x0000000000009E19
           D                        0x000000000000A01B
           MUTE                     0x0000000000008F0A
           TV_ON_DEMAND             0x000000000000A11C
           MAX_WINDOW               0x000000000000A520
           E                        0x000000000000A621
           F                        0x000000000000A823
           OK                       0x000000000000A31E
           LEFT                     0x000000000000A21D
           RIGHT                    0x000000000000A41F
           UP                       0x0000000000009F1A
           DOWN                     0x000000000000A722
           REWIND                   0x000000000000A924
           PLAY                     0x000000000000AA25
           FORWARD                  0x000000000000AB26
           RECORD                   0x000000000000AC27
           STOP                     0x000000000000AD28
           PAUSE                    0x000000000000AE29
           MOUSE_BUTTON_LEFT        0x000000000000FD78
           MOUSE_BUTTON_RIGHT       0x000000000000017C
           VOL-                     0x0000000000008E09
           VOL+                     0x0000000000008D08
           CH-                      0x000000000000910C
           CH+                      0x000000000000900B
           MOUSE-UP                 0x000000000000F772
           MOUSE-DOWN               0x000000000000F873
           MOUSE-LEFT               0x000000000000F570
           MOUSE-RIGHT              0x000000000000F671
           MOUSE-LEFT_UP            0x000000000000F974
           MOUSE-LEFT_DOWN          0x000000000000FC77
           MOUSE-RIGHT_UP           0x000000000000FA75
           MOUSE-RIGHT_DOWN         0x000000000000FB76
           DVD-ROOT_MENU            0x0000000000009B16
           LAUNCH_SETUP             0x0000000000009D18
       end codes

end remote

Any thoughts?  I would prefer to generate my own file, but I have tried 
and I can't figure out how to do it, nor can I find instructions on it 
on the LiRC website.


>>>>3. Why doesn't GATOS provide premade configuration files for the remotes
>>>>that users can go ahead and use, or edit to make it work as they please?
>>>
>>>
>>>Good idea! I now added a sample configuration file lircrc.example.
> 
> 
> This is in CVS. For instructions on accessing CVS see
> <http://sourceforge.net/cvs/?group_id=12629>.
> 

On Wed, 15 Nov 2006, William M. Quarles wrote:

> Antti Ajanki wrote:
>> The button names depend on your LIRC configuration. They can be found from
>> /etc/lirc/lircd.conf.
>>
>
> Um, I don't even have a /etc/lirc/lircd.conf file.  Aren't they device
> dependent?

Yes they indeed are, but they also specify the names that LIRC uses for 
the remote control buttons. LIRC won't work without the file, there is 
information about downloading/generating the file on the LIRC 
documentation. Some distros may call it /etc/lircd.conf.

>>> 3. Why doesn't GATOS provide premade configuration files for the remotes
>>> that users can go ahead and use, or edit to make it work as they please?
>>
>>
>> Good idea! I now added a sample configuration file lircrc.example.

This is in CVS. For instructions on accessing CVS see
<http://sourceforge.net/cvs/?group_id=12629>.

-- 
Antti Ajanki

Antti Ajanki wrote:
> Sorry for the late reply, I've been out of town for whole week.
> 
> On Fri, 3 Nov 2006, William M. Quarles wrote:
<snip>
>>But thirdly,
>>
>>3. Why doesn't GATOS provide premade configuration files for the remotes
>>that users can go ahead and use, or edit to make it work as they please?
> 
> 
> Good idea! I now added a sample configuration file lircrc.example.
> 

Sorry, where can I find this file?

Thanks,
William

Antti Ajanki wrote:
> Sorry for the late reply, I've been out of town for whole week.
> 
> On Fri, 3 Nov 2006, William M. Quarles wrote:
> 
> 
>>2.  I don't know how to make a configuration file!  I have read the
>>README file for AVview, and I understand "The following commands are
>>recogniced [sic] as config field values," but what about the other
>>fields? I'm not sure what to put in the "button" field at all for
>>example, especially the CH +/- and VOL +/- buttons.
> 
> 
> The button names depend on your LIRC configuration. They can be found from 
> /etc/lirc/lircd.conf.
> 

Um, I don't even have a /etc/lirc/lircd.conf file.  Aren't they device 
dependent?

> 
>>But thirdly,
>>
>>3. Why doesn't GATOS provide premade configuration files for the remotes
>>that users can go ahead and use, or edit to make it work as they please?
> 
> 
> Good idea! I now added a sample configuration file lircrc.example.
> 

Cool, thanks.  I'll check that out.

On Sun, 12 Nov 2006, Francisco L. Fernandez wrote:

> My setup is as follows:
>
> - Slackware 10.2
> - Kernel 2.4.15/2.4.18
> - Xorg 6.9 compiled from sources.

Have you tried Xorg 7.1? The GATOS driver has been merged into it, so you 
only need to compile km.

-- 
Antti Ajanki

Sorry for the late reply, I've been out of town for whole week.

On Fri, 3 Nov 2006, William M. Quarles wrote:

> 2.  I don't know how to make a configuration file!  I have read the
> README file for AVview, and I understand "The following commands are
> recogniced [sic] as config field values," but what about the other
> fields? I'm not sure what to put in the "button" field at all for
> example, especially the CH +/- and VOL +/- buttons.

The button names depend on your LIRC configuration. They can be found from 
/etc/lirc/lircd.conf.

>
> But thirdly,
>
> 3. Why doesn't GATOS provide premade configuration files for the remotes
> that users can go ahead and use, or edit to make it work as they please?

Good idea! I now added a sample configuration file lircrc.example.

-- 
Antti Ajanki

Hello,

After all my frustrating experiences with gatos capture for mach64 and
rage128 cards,I have purchased a well known supportd card: AIW Radeon
7500 AGP PAL (Rage Theatre 100).
But for my pain, It works even worse that my badly supported AIW 128
pro.

Problems:

1. If I load km after the drm radeon driver (tested with a bunch of drm
versions from 2005 to tha very last, using libdrm from 1.0, 2.0 and
2.3). It is unable to recognize the card and setup /dev/video0. It stops
the output of kernel messages with this line:

Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=732

like if km_probe is not 
2. Even disabling dri and radeon.ko loading, capture doesn't work.
2.1 It stalls when using ffmpeg 0.4.8 directly  without a single frame
captured.
dmesg output follows:

00ffff0000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131068
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 126972 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 ASUS                                  ) @ 0x000f5a60
ACPI: RSDT (v001 ASUS   P3V_4X   0x30303031 MSFT 0x31313031) @
0x1fffc000
ACPI: FADT (v001 ASUS   P3V_4X   0x30303031 MSFT 0x31313031) @
0x1fffc080
ACPI: BOOT (v001 ASUS   P3V_4X   0x30303031 MSFT 0x31313031) @
0x1fffc040
ACPI: DSDT (v001   ASUS P3V_4X   0x00001000 MSFT 0x0100000b) @
0x00000000
ACPI: PM-Timer IO Port: 0xe408
Allocating PCI resources starting at 30000000 (gap: 20000000:dfff0000)
Detected 666.729 MHz processor.
Built 1 zonelists.  Total pages: 131068
Kernel command line: BOOT_IMAGE=linux ro root=1601 apm=off acpi=on
pci=routeirq ide=reverse ide3=noprobe hdg=noprobe hdh=noprobe nohotplug
ide_setup: ide=reverse : Enabled support for IDE inverse scan order.
ide_setup: ide3=noprobe
ide_setup: hdg=noprobe
ide_setup: hdh=noprobe
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 515872k/524272k available (2116k kernel code, 7864k reserved,
828k data, 156k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Calibrating delay using timer specific routine.. 1334.44 BogoMIPS
(lpj=6672206)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: Intel Pentium III (Coppermine) stepping 03
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
 tbxface-0107 [01] load_tables           : ACPI Tables successfully
acquired
Parsing all Control Methods:
Table [DSDT](id 0005) - 259 Objects with 35 Devices 78 Methods 16
Regions
ACPI Namespace successfully loaded at root c041c250
ACPI: setting ELCR to 0200 (from 8c20)
evxfevnt-0089 [02] enable                : Transition to ACPI mode
successful
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf0890, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
evgpeblk-0951 [04] ev_create_gpe_block   : GPE 00 to 0F [_GPE] 2 regs on
int 0x9
evgpeblk-1048 [03] ev_initialize_gpe_bloc: Found 3 Wake, Enabled 0
Runtime GPEs in this block
Completing Region/Field/Buffer/Package
initialization:................................................
Initialized 15/16 Regions 5/5 Fields 19/19 Buffers 9/11 Packages (268
nodes)
Initializing Device/Processor/Thermal objects by executing _INI methods:
Executed 0 _INI methods requiring 0 _STA executions (examined 38
objects)
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
PnPBIOS: Disabled by ACPI PNP
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: Routing PCI interrupts for all devices because "pci=routeirq"
specified
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:04.2[D] -> Link [LNKD] -> GSI 10 (level,
low) -> IRQ 10
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 15
PCI: setting IRQ 15 as level-triggered
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKB] -> GSI 15 (level,
low) -> IRQ 15
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKA] -> GSI 5 (level, low)
-> IRQ 5
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 10 (level,
low) -> IRQ 10
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 5 (level, low)
-> IRQ 5
pnp: 00:03: ioport range 0xe400-0xe47f could not be reserved
pnp: 00:03: ioport range 0xe800-0xe80f has been reserved
PCI: Bridge: 0000:00:01.0
  IO window: d000-dfff
  MEM window: d7000000-d7dfffff
  PREFETCH window: d7f00000-e3ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Simple Boot Flag at 0x3a set to 0x1
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Activating ISA DMA hang workarounds.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
HPT370A: IDE controller at PCI slot 0000:00:0e.0
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
HPT370A: chipset revision 4
HPT370A: 100% native mode on irq 11
HPT37X: using 33MHz PCI clock
    ide0: BM-DMA at 0x8400-0x8407, BIOS settings: hda:DMA, hdb:pio
HPT37X: using 33MHz PCI clock
    ide1: BM-DMA at 0x8408-0x840f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ST3120022A, ATA DISK drive
ide0 at 0x9800-0x9807,0x9402 on irq 11
Probing IDE interface ide1...
hdc: ST3120026A, ATA DISK drive
ide1 at 0x9000-0x9007,0x8802 on irq 11
VP_IDE: IDE controller at PCI slot 0000:00:04.1
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci0000:00:04.1
    ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:DMA, hdf:pio
Probing IDE interface ide2...
hde: SONY DVD-ROM DDU1612, ATAPI CD/DVD-ROM drive
ide2 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 512KiB
hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=16383/255/63,
UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3
hdc: max request size: 512KiB
hdc: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
hdc: cache flushes supported
 hdc: hdc1 hdc2
hde: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI: (supports S0 S1 S4 S5)
md: Autodetecting RAID arrays.
Time: tsc clocksource has been installed.
input: AT Translated Set 2 keyboard as /class/input/input0
md: autorun ...
md: considering hdc2 ...
md:  adding hdc2 ...
md:  adding hda3 ...
md: created md0
md: bind<hda3>
md: bind<hdc2>
md: running: <hdc2><hda3>
md0: setting max_sectors to 2048, segment boundary to 524287
raid0: looking at hdc2
raid0:   comparing hdc2(97682432) with hdc2(97682432)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at hda3
raid0:   comparing hda3(97682432) with hdc2(97682432)
raid0:   EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 195364864 blocks.
raid0 : conf->hash_spacing is 195364864 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 4 bytes for hash.
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 156k freed
input: ImPS/2 Generic Wheel Mouse as /class/input/input1
EXT3 FS on hdc1, internal journal
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA Apollo Pro 133 chipset
agpgart: AGP aperture is 64M @ 0xe4000000
Linux video capture interface: v2.00
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKB] -> GSI 15 (level,
low) -> IRQ 15
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0b.0: 3Com PCI 3c905C Tornado at e0818000.
st: Version 20050830, fixed bufsize 32768, s/g segs 256
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05,
2004/03/08
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 10 (level,
low) -> IRQ 10
dc395x: Used settings: AdapterID=07, Speed=0(20.0MHz), dev_mode=0x57
dc395x:                AdaptMode=0x0f, Tags=4(16), DelayReset=1s
dc395x: Connectors:  Termination: Auto Low High 
dc395x: Performing initial SCSI bus reset
scsi0 : Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05,
2004/03/08
PCI: Enabling device 0000:00:0c.0 (0084 -> 0085)
ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKA] -> GSI 5 (level, low)
-> IRQ 5
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
eth0:  setting full-duplex.
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 ok...@mo...).
eth0: no IPv6 routers present
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Kmultimedia API module version alpha-6.0 loaded
Kmultimedia module version alpha-6.0 loaded
Page size is 4096 sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=732
km: probing 0000:01:00.0
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 5 (level, low)
-> IRQ 5
km: using irq 5
Register aperture is 0xd7000000 0x00010000
kms variables: reg_aperture=0xe0900000
km: DMA_GUI_STATUS=0x00000002 entries=2
sizeof(kmfl_template)=780 sizeof(KM_FIELD)=52
Device 0000:01:00.0 (0x1002:0x5157) corresponds to /dev/video0
kms variables: reg_aperture=e0900000
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
Stopping GUIDMA queue
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
Stopping GUIDMA queue
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
radeon_get_window_parameters: width=720 height=288
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 2 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
radeon_get_window_parameters: width=720 height=288
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
radeon_get_window_parameters: width=720 height=288
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
radeon_get_window_parameters: width=720 height=288
radeon_get_window_parameters: width=720 height=288
km: /dev/video0 uses frame format 720x288
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue
Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
Purging transfer queue
radeon_get_window_parameters: width=720 height=288
Capture buf size=414720
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue

2.2 It segfaults using avview last version.
Dmesg output follows (this time with km_debug=1):

000
dma_table[5][7].to_addr=0x0d97f000
dma_table[5][8].to_addr=0x0c267000
dma_table[5][9].to_addr=0x0ece3000
dma_table[5][10].to_addr=0x090aa000
dma_table[5][11].to_addr=0x097ee000
dma_table[5][12].to_addr=0x08497000
dma_table[5][13].to_addr=0x08fa2000
dma_table[5][14].to_addr=0x11228000
dma_table[5][15].to_addr=0x0e474000
dma_table[5][16].to_addr=0x09095000
dma_table[5][17].to_addr=0x071f6000
dma_table[5][18].to_addr=0x07abd000
dma_table[5][19].to_addr=0x0787e000
dma_table[5][20].to_addr=0x0ea4c000
dma_table[5][21].to_addr=0x10697000
dma_table[5][22].to_addr=0x08573000
dma_table[5][23].to_addr=0x14ed4000
dma_table[5][24].to_addr=0x0820f000
dma_table[5][25].to_addr=0x11236000
dma_table[5][26].to_addr=0x0c75f000
dma_table[5][27].to_addr=0x139a9000
dma_table[5][28].to_addr=0x0f7e3000
dma_table[5][29].to_addr=0x08237000
dma_table[5][30].to_addr=0x135dd000
dma_table[5][31].to_addr=0x09d40000
dma_table[5][32].to_addr=0x11152000
dma_table[5][33].to_addr=0x0e408000
dma_table[5][34].to_addr=0x0cf96000
dma_table[5][35].to_addr=0x1406e000
dma_table[5][36].to_addr=0x111f2000
dma_table[5][37].to_addr=0x0da7d000
dma_table[5][38].to_addr=0x13e26000
dma_table[5][39].to_addr=0x1f4a5000
dma_table[5][40].to_addr=0x07dee000
dma_table[5][41].to_addr=0x07f81000
dma_table[5][42].to_addr=0x071f5000
dma_table[5][43].to_addr=0x084fd000
dma_table[5][44].to_addr=0x1f5fe000
dma_table[5][45].to_addr=0x07026000
dma_table[5][46].to_addr=0x0d37a000
dma_table[5][47].to_addr=0x111db000
dma_table[5][48].to_addr=0x079a3000
dma_table[5][49].to_addr=0x1fade000
dma_table[5][50].to_addr=0x08193000
dma_table[5][51].to_addr=0x08855000
dma_table[5][52].to_addr=0x09332000
dma_table[5][53].to_addr=0x0c5f3000
dma_table[5][54].to_addr=0x0eff4000
dma_table[5][55].to_addr=0x111ec000
dma_table[5][56].to_addr=0x08c78000
dma_table[5][57].to_addr=0x01661000
dma_table[5][58].to_addr=0x0925e000
dma_table[5][59].to_addr=0x072e4000
dma_table[5][60].to_addr=0x08b3c000
dma_table[5][61].to_addr=0x07c69000
dma_table[5][62].to_addr=0x0ab8d000
dma_table[5][63].to_addr=0x09759000
dma_table[5][64].to_addr=0x084af000
dma_table[5][65].to_addr=0x1feb5000
dma_table[5][66].to_addr=0x087d8000
dma_table[5][67].to_addr=0x08f17000
dma_table[5][68].to_addr=0x08ba5000
dma_table[5][69].to_addr=0x15fae000
dma_table[5][70].to_addr=0x0909b000
dma_table[5][71].to_addr=0x13c20000
dma_table[5][72].to_addr=0x070e1000
dma_table[5][73].to_addr=0x14cd2000
dma_table[5][74].to_addr=0x08d8a000
dma_table[5][75].to_addr=0x0ca8c000
dma_table[5][76].to_addr=0x0c188000
dma_table[5][77].to_addr=0x0935d000
dma_table[5][78].to_addr=0x09244000
dma_table[5][79].to_addr=0x070ea000
dma_table[5][80].to_addr=0x017ec000
dma_table[5][81].to_addr=0x0e1cd000
dma_table[5][82].to_addr=0x1688c000
dma_table[5][83].to_addr=0x1f25b000
dma_table[5][84].to_addr=0x084a2000
dma_table[5][85].to_addr=0x074d4000
dma_table[5][86].to_addr=0x071dd000
dma_table[5][87].to_addr=0x0912c000
dma_table[5][88].to_addr=0x1210a000
dma_table[5][89].to_addr=0x1f4b5000
dma_table[5][90].to_addr=0x091b4000
dma_table[5][91].to_addr=0x1fa08000
dma_table[5][92].to_addr=0x1fb50000
dma_table[5][93].to_addr=0x0d54a000
dma_table[5][94].to_addr=0x0c9e1000
dma_table[5][95].to_addr=0x13f72000
dma_table[5][96].to_addr=0x0920e000
dma_table[5][97].to_addr=0x08bc8000
dma_table[5][98].to_addr=0x0974d000
dma_table[5][99].to_addr=0x0fc5a000
dma_table[5][100].to_addr=0x0e418000
dma_table[5][101].to_addr=0x0f38e000
dma_table[6]=e08fe000
dma_table[6][0].to_addr=0x14da7000
dma_table[6][1].to_addr=0x1286d000
dma_table[6][2].to_addr=0x0ea86000
dma_table[6][3].to_addr=0x0cfb9000
dma_table[6][4].to_addr=0x0c5bf000
dma_table[6][5].to_addr=0x0c274000
dma_table[6][6].to_addr=0x0c272000
dma_table[6][7].to_addr=0x0e6a1000
dma_table[6][8].to_addr=0x13cbc000
dma_table[6][9].to_addr=0x0f430000
dma_table[6][10].to_addr=0x1111f000
dma_table[6][11].to_addr=0x0e451000
dma_table[6][12].to_addr=0x109f2000
dma_table[6][13].to_addr=0x0df33000
dma_table[6][14].to_addr=0x0d05e000
dma_table[6][15].to_addr=0x0c18e000
dma_table[6][16].to_addr=0x0f91c000
dma_table[6][17].to_addr=0x093db000
dma_table[6][18].to_addr=0x11f46000
dma_table[6][19].to_addr=0x090a2000
dma_table[6][20].to_addr=0x16532000
dma_table[6][21].to_addr=0x0f074000
dma_table[6][22].to_addr=0x0f016000
dma_table[6][23].to_addr=0x0cef5000
dma_table[6][24].to_addr=0x1f55d000
dma_table[6][25].to_addr=0x0f6b8000
dma_table[6][26].to_addr=0x14024000
dma_table[6][27].to_addr=0x14c8c000
dma_table[6][28].to_addr=0x0e4e4000
dma_table[6][29].to_addr=0x0c7cc000
dma_table[6][30].to_addr=0x0d896000
dma_table[6][31].to_addr=0x0f3d5000
dma_table[6][32].to_addr=0x0d8ab000
dma_table[6][33].to_addr=0x11288000
dma_table[6][34].to_addr=0x0e1cb000
dma_table[6][35].to_addr=0x13f66000
dma_table[6][36].to_addr=0x0ec35000
dma_table[6][37].to_addr=0x0fc73000
dma_table[6][38].to_addr=0x146f2000
dma_table[6][39].to_addr=0x09848000
dma_table[6][40].to_addr=0x1125e000
dma_table[6][41].to_addr=0x146f6000
dma_table[6][42].to_addr=0x0eca4000
dma_table[6][43].to_addr=0x0c67f000
dma_table[6][44].to_addr=0x0e49c000
dma_table[6][45].to_addr=0x0c69f000
dma_table[6][46].to_addr=0x0c7c3000
dma_table[6][47].to_addr=0x0d35d000
dma_table[6][48].to_addr=0x0abcd000
dma_table[6][49].to_addr=0x113ee000
dma_table[6][50].to_addr=0x111a8000
dma_table[6][51].to_addr=0x090c9000
dma_table[6][52].to_addr=0x0921a000
dma_table[6][53].to_addr=0x0c964000
dma_table[6][54].to_addr=0x174d4000
dma_table[6][55].to_addr=0x0f117000
dma_table[6][56].to_addr=0x0ef9f000
dma_table[6][57].to_addr=0x13d02000
dma_table[6][58].to_addr=0x097f2000
dma_table[6][59].to_addr=0x0c6a3000
dma_table[6][60].to_addr=0x0f359000
dma_table[6][61].to_addr=0x1244b000
dma_table[6][62].to_addr=0x0d048000
dma_table[6][63].to_addr=0x11454000
dma_table[6][64].to_addr=0x0cfbb000
dma_table[6][65].to_addr=0x0e586000
dma_table[6][66].to_addr=0x0f356000
dma_table[6][67].to_addr=0x113e8000
dma_table[6][68].to_addr=0x15989000
dma_table[6][69].to_addr=0x14bcb000
dma_table[6][70].to_addr=0x0f0d3000
dma_table[6][71].to_addr=0x0f031000
dma_table[6][72].to_addr=0x0c6c4000
dma_table[6][73].to_addr=0x109ff000
dma_table[6][74].to_addr=0x1f0d7000
dma_table[6][75].to_addr=0x11b9e000
dma_table[6][76].to_addr=0x0c276000
dma_table[6][77].to_addr=0x0c5e6000
dma_table[6][78].to_addr=0x0ee28000
dma_table[6][79].to_addr=0x0ef0e000
dma_table[6][80].to_addr=0x0c9c2000
dma_table[6][81].to_addr=0x12f14000
dma_table[6][82].to_addr=0x0cf0a000
dma_table[6][83].to_addr=0x0d1c7000
dma_table[6][84].to_addr=0x0c900000
dma_table[6][85].to_addr=0x12b0c000
dma_table[6][86].to_addr=0x091c7000
dma_table[6][87].to_addr=0x174e9000
dma_table[6][88].to_addr=0x13d0f000
dma_table[6][89].to_addr=0x1395f000
dma_table[6][90].to_addr=0x0ec2c000
dma_table[6][91].to_addr=0x0c3d6000
dma_table[6][92].to_addr=0x1057a000
dma_table[6][93].to_addr=0x098e5000
dma_table[6][94].to_addr=0x0ecff000
dma_table[6][95].to_addr=0x12343000
dma_table[6][96].to_addr=0x1104f000
dma_table[6][97].to_addr=0x13115000
dma_table[6][98].to_addr=0x0c5da000
dma_table[6][99].to_addr=0x0da74000
dma_table[6][100].to_addr=0x14ed3000
dma_table[6][101].to_addr=0x0cfdc000
dma_table[7]=e0cee000
dma_table[7][0].to_addr=0x0e464000
dma_table[7][1].to_addr=0x0e88a000
dma_table[7][2].to_addr=0x0e868000
dma_table[7][3].to_addr=0x0f39e000
dma_table[7][4].to_addr=0x0e9d1000
dma_table[7][5].to_addr=0x0c96a000
dma_table[7][6].to_addr=0x11879000
dma_table[7][7].to_addr=0x0f16a000
dma_table[7][8].to_addr=0x13d7e000
dma_table[7][9].to_addr=0x13f6c000
dma_table[7][10].to_addr=0x0df2c000
dma_table[7][11].to_addr=0x0c252000
dma_table[7][12].to_addr=0x1095e000
dma_table[7][13].to_addr=0x0c777000
dma_table[7][14].to_addr=0x0f0f0000
dma_table[7][15].to_addr=0x07715000
dma_table[7][16].to_addr=0x1fdb1000
dma_table[7][17].to_addr=0x0efad000
dma_table[7][18].to_addr=0x1106c000
dma_table[7][19].to_addr=0x0e4b7000
dma_table[7][20].to_addr=0x0f7dc000
dma_table[7][21].to_addr=0x0c1c9000
dma_table[7][22].to_addr=0x0ef81000
dma_table[7][23].to_addr=0x13d12000
dma_table[7][24].to_addr=0x08baf000
dma_table[7][25].to_addr=0x110b9000
dma_table[7][26].to_addr=0x1098b000
dma_table[7][27].to_addr=0x0d983000
dma_table[7][28].to_addr=0x1494b000
dma_table[7][29].to_addr=0x0c5d5000
dma_table[7][30].to_addr=0x0cfcb000
dma_table[7][31].to_addr=0x0eda7000
dma_table[7][32].to_addr=0x09970000
dma_table[7][33].to_addr=0x07010000
dma_table[7][34].to_addr=0x0e01e000
dma_table[7][35].to_addr=0x0cf90000
dma_table[7][36].to_addr=0x0df3c000
dma_table[7][37].to_addr=0x0e8be000
dma_table[7][38].to_addr=0x0d36f000
dma_table[7][39].to_addr=0x113a5000
dma_table[7][40].to_addr=0x11349000
dma_table[7][41].to_addr=0x0c6af000
dma_table[7][42].to_addr=0x13cc6000
dma_table[7][43].to_addr=0x0f0dd000
dma_table[7][44].to_addr=0x0c9dc000
dma_table[7][45].to_addr=0x11db3000
dma_table[7][46].to_addr=0x0c935000
dma_table[7][47].to_addr=0x091bf000
dma_table[7][48].to_addr=0x0eecf000
dma_table[7][49].to_addr=0x151bf000
dma_table[7][50].to_addr=0x084e9000
dma_table[7][51].to_addr=0x09034000
dma_table[7][52].to_addr=0x151e5000
dma_table[7][53].to_addr=0x0e1b5000
dma_table[7][54].to_addr=0x123fd000
dma_table[7][55].to_addr=0x0e85e000
dma_table[7][56].to_addr=0x12313000
dma_table[7][57].to_addr=0x0e870000
dma_table[7][58].to_addr=0x0c1f6000
dma_table[7][59].to_addr=0x1442e000
dma_table[7][60].to_addr=0x14edc000
dma_table[7][61].to_addr=0x0e824000
dma_table[7][62].to_addr=0x14214000
dma_table[7][63].to_addr=0x13ef8000
dma_table[7][64].to_addr=0x1f328000
dma_table[7][65].to_addr=0x112c0000
dma_table[7][66].to_addr=0x09cc6000
dma_table[7][67].to_addr=0x0da83000
dma_table[7][68].to_addr=0x14bdd000
dma_table[7][69].to_addr=0x10625000
dma_table[7][70].to_addr=0x0ea13000
dma_table[7][71].to_addr=0x132bf000
dma_table[7][72].to_addr=0x0c298000
dma_table[7][73].to_addr=0x13d63000
dma_table[7][74].to_addr=0x07d74000
dma_table[7][75].to_addr=0x0c76c000
dma_table[7][76].to_addr=0x13063000
dma_table[7][77].to_addr=0x0c672000
dma_table[7][78].to_addr=0x0dd3d000
dma_table[7][79].to_addr=0x0f911000
dma_table[7][80].to_addr=0x0c747000
dma_table[7][81].to_addr=0x0c198000
dma_table[7][82].to_addr=0x11128000
dma_table[7][83].to_addr=0x11855000
dma_table[7][84].to_addr=0x0f234000
dma_table[7][85].to_addr=0x0df3e000
dma_table[7][86].to_addr=0x0e476000
dma_table[7][87].to_addr=0x1634b000
dma_table[7][88].to_addr=0x0c9db000
dma_table[7][89].to_addr=0x0e442000
dma_table[7][90].to_addr=0x0ec0a000
dma_table[7][91].to_addr=0x0eea6000
dma_table[7][92].to_addr=0x0d98c000
dma_table[7][93].to_addr=0x0ec00000
dma_table[7][94].to_addr=0x0f7b1000
dma_table[7][95].to_addr=0x1317e000
dma_table[7][96].to_addr=0x1317f000
dma_table[7][97].to_addr=0x0918a000
dma_table[7][98].to_addr=0x0918b000
dma_table[7][99].to_addr=0x087c4000
dma_table[7][100].to_addr=0x087c5000
dma_table[7][101].to_addr=0x09314000
dma_table[8]=e0cf0000
dma_table[8][0].to_addr=0x09315000
dma_table[8][1].to_addr=0x09058000
dma_table[8][2].to_addr=0x09059000
dma_table[8][3].to_addr=0x09d46000
dma_table[8][4].to_addr=0x09d47000
dma_table[8][5].to_addr=0x05fe6000
dma_table[8][6].to_addr=0x05fe7000
dma_table[8][7].to_addr=0x08bc6000
dma_table[8][8].to_addr=0x08bc7000
dma_table[8][9].to_addr=0x1f83a000
dma_table[8][10].to_addr=0x1f83b000
dma_table[8][11].to_addr=0x1fd4e000
dma_table[8][12].to_addr=0x1fd4f000
dma_table[8][13].to_addr=0x05adc000
dma_table[8][14].to_addr=0x05add000
dma_table[8][15].to_addr=0x0608c000
dma_table[8][16].to_addr=0x0608d000
dma_table[8][17].to_addr=0x146f4000
dma_table[8][18].to_addr=0x146f5000
dma_table[8][19].to_addr=0x05fe2000
dma_table[8][20].to_addr=0x05fe3000
dma_table[8][21].to_addr=0x0c95e000
dma_table[8][22].to_addr=0x0c95f000
dma_table[8][23].to_addr=0x09988000
dma_table[8][24].to_addr=0x09989000
dma_table[8][25].to_addr=0x0823c000
dma_table[8][26].to_addr=0x0823d000
dma_table[8][27].to_addr=0x06088000
dma_table[8][28].to_addr=0x06089000
dma_table[8][29].to_addr=0x02db6000
dma_table[8][30].to_addr=0x02db7000
dma_table[8][31].to_addr=0x1e066000
dma_table[8][32].to_addr=0x1e067000
dma_table[8][33].to_addr=0x01892000
dma_table[8][34].to_addr=0x01893000
dma_table[8][35].to_addr=0x05fd6000
dma_table[8][36].to_addr=0x05fd7000
dma_table[8][37].to_addr=0x05fea000
dma_table[8][38].to_addr=0x05feb000
dma_table[8][39].to_addr=0x055ba000
dma_table[8][40].to_addr=0x055bb000
dma_table[8][41].to_addr=0x05502000
dma_table[8][42].to_addr=0x05503000
dma_table[8][43].to_addr=0x0605c000
dma_table[8][44].to_addr=0x0605d000
dma_table[8][45].to_addr=0x05a40000
dma_table[8][46].to_addr=0x05a41000
dma_table[8][47].to_addr=0x055c0000
dma_table[8][48].to_addr=0x055c1000
dma_table[8][49].to_addr=0x055be000
dma_table[8][50].to_addr=0x055bf000
dma_table[8][51].to_addr=0x09f0e000
dma_table[8][52].to_addr=0x09f0f000
dma_table[8][53].to_addr=0x0c7de000
dma_table[8][54].to_addr=0x0c7df000
dma_table[8][55].to_addr=0x05400000
dma_table[8][56].to_addr=0x05401000
dma_table[8][57].to_addr=0x09136000
dma_table[8][58].to_addr=0x09137000
dma_table[8][59].to_addr=0x054e8000
dma_table[8][60].to_addr=0x054e9000
dma_table[8][61].to_addr=0x0176e000
dma_table[8][62].to_addr=0x0176f000
dma_table[8][63].to_addr=0x1f8f6000
dma_table[8][64].to_addr=0x1f8f7000
dma_table[8][65].to_addr=0x1f2b6000
dma_table[8][66].to_addr=0x1f2b7000
dma_table[8][67].to_addr=0x146e6000
dma_table[8][68].to_addr=0x146e7000
dma_table[8][69].to_addr=0x0903e000
dma_table[8][70].to_addr=0x0903f000
dma_table[8][71].to_addr=0x1fdde000
dma_table[8][72].to_addr=0x1fddf000
dma_table[8][73].to_addr=0x057e6000
dma_table[8][74].to_addr=0x057e7000
dma_table[8][75].to_addr=0x097e4000
dma_table[8][76].to_addr=0x097e5000
dma_table[8][77].to_addr=0x0985c000
dma_table[8][78].to_addr=0x0985d000
dma_table[8][79].to_addr=0x1f0d2000
dma_table[8][80].to_addr=0x1f0d3000
dma_table[8][81].to_addr=0x09214000
dma_table[8][82].to_addr=0x09215000
dma_table[8][83].to_addr=0x1f98a000
dma_table[8][84].to_addr=0x1f98b000
dma_table[8][85].to_addr=0x087d2000
dma_table[8][86].to_addr=0x087d3000
dma_table[8][87].to_addr=0x07c54000
dma_table[8][88].to_addr=0x07c55000
dma_table[8][89].to_addr=0x081d0000
dma_table[8][90].to_addr=0x081d1000
dma_table[8][91].to_addr=0x084d8000
dma_table[8][92].to_addr=0x084d9000
dma_table[8][93].to_addr=0x09046000
dma_table[8][94].to_addr=0x09047000
dma_table[8][95].to_addr=0x09242000
dma_table[8][96].to_addr=0x09243000
dma_table[8][97].to_addr=0x09966000
dma_table[8][98].to_addr=0x09967000
dma_table[8][99].to_addr=0x06ce4000
dma_table[8][100].to_addr=0x06ce5000
dma_table[8][101].to_addr=0x07c6c000
RADEON_RBBM_STATUS=0x00000140
RADEON_BUS_CNTL=0x5133a3b0
Starting GUIDMA queue
km: DMA_GUI_QUEUE stalled after abort
RADEON_RBBM_STATUS=0x00000140
radeon_get_window_parameters: width=720 height=288
RADEON_RBBM_STATUS=0x00000140
radeon_get_window_parameters: width=720 height=288
RADEON_RBBM_STATUS=0x00000140
radeon_get_window_parameters: width=720 height=288
RADEON_RBBM_STATUS=0x00000140
radeon_get_window_parameters: width=720 height=288
RADEON_RBBM_STATUS=0x00000140
radeon_get_window_parameters: width=720 height=288
Stopping GUIDMA queue
km: GUI_DMA_QUEUE abort stalled
km: closed stream, 0 buffers captured
Purging transfer queue

--------------------------

My setup is as follows:

- Slackware 10.2
- Kernel 2.4.15/2.4.18
- Xorg 6.9 compiled from sources.
- PIII copermine 666/133 - Slot1
- Asus P3V4X
- 512 MB RAM
- Highpoint HPT370A IDE controller
- Radeon AIW 7500 PAL 64MB
- Other info in dmesg output.

Of course, I am displaying overlay when I start capturing and it looks
well.

Regards,

Vadimir,

If the situation is as you describe, (I think that the DMA issue is also
affecting the putvideo support merge for mach64 based cards) then I
wonder what is the future for gatos on rage 128:
1. Mantain a parallel patch that could work disabling DRI. There are
still some issues to solve though, because doing a bit more testing, I
have discoverd that old flaws from XFree86 times are still present,
namely:

- There are reported lockups of rage 128 engine while capturing. As I
have said I don't have drm/dri loaded. Probably becasue that, some
frames are partially captured and then you notice a vertical
displacement in the captured frames.

Normal frame -> Displaced frame

----------        ----------
1111111111        3333333333
2222222222  --->  4444444444
3333333333        1111111111
4444444444        2222222222
----------        ----------

- Sometimes (I haven't done extensive testing yet) after using overlay
to play video (i.e. with mplayer),it is not possible to display overlay
video in (you only get a black screen with xawtv) again, until you reset
the X server.
2. Trying to rewrite video capture support from scratch to adapt it to
the dma usage by the drm or ddx components. It could even work without X
like Eric Sellers driver. It is sad tho say that until now, only Eric's 
driver has worked for me (I only had AIW mach 64 and 128 --showing the
displacement problem in capture and also AIW Radeon 9000 -- not
supported then, I plan to test it soon with Xorg 6.9+).
3. Suspend the development and make clear that those cards are never
going to work.

I have now my AIW 128 pro retired to another computer, but ready to help
in testing work.

Regards


On Wed, 1 Nov 2006 02:58:39 -0500 (EST)
Vladimir Dergachev <vo...@mi...> wrote:

> 
> Hi Francisco,
> 
>     Sorry for the delayed response, comments below:
> 
> 
> 
> > Hello,
> >
> > I have adapted the patch posted by Vladimir as long ago as Thu, 23
> > Dec 2004, to make it work with Xorg 6.9.0 final release.
> >
> > Video capture works. I must say that with XFree 4.3 (from which the
> > codebase is adapted) I never was able to get video capture working
> > properly.
> >
> > The problem is that it doesn't work with DRI enabled.
> >
> > Regarding the line:
> >
> >            info->accel->Sync(pScrn);
> >
> > in r128_video.c
> >
> > (1) if I left the line uncommented (as is in the patch), Xorg enters
> > in a deadlock, posting the following lines again and again:
> >
> > (EE) R128(0): R128CCEWaitForIdle: CCE stop -1007
> > (EE) R128(0): R128CCEWaitForIdle: CCE reset -1007
> > (EE) R128(0): R128CCEWaitForIdle: CCE start -1007
> > (EE) R128(0): R128CCEWaitForIdle: CCE idle -1007
> > (EE) R128(0): Idle timed out, resetting engine...
> >
> >
> > (2) if I uncomment the line, X locks hard the computer.
> >
> > Vladimir, I am willing to help sorting out this last obstacle to get
> > gatos working at last with
> > AIW Rage 128 pro.
> 
> The reason why this happens is that both GATOS capture module and DRI
> use  the same DMA queue (there is only one on Rage128). That was why 
> the patch never made it into Xorg CVS - the changes needed to get both
> 
> working smoothly would be too extensive and I was not even sure that
> it  would be possible.
> 
> One could try to cut out the capture support, but, if I remember 
> correctly, there was some separate cause for lockups with DRI enabled
> and  Xv running.
> 
>                     best
> 
>                         Vladimir Dergachev
> 
> >
> > Regards
> >
> > On Mon, 10 Jan 2005 06:18:20 -0500 (EST)
> > Rick Scott <rw...@al...> wrote:
> >
> >> The "green dots" problem was fixed with the addition of
> >>
> >> OUTREG(R128_OV0_VID_BUF0_BASE_ADRS, offset1 & 0xfffffff0);
> >>
> >> in r128_video.c:R128DisplayVideo422.
> >> It should go just before
> >>
> >> OUTREG(R128_OV0_VID_BUF1_BASE_ADRS, offset1 & 0xfffffff0);
> >>
> >> Should be around line 1093.
> >>
> >>
> >> On 10-Jan-05 at 05:17, SABA Simone Consultant
> >> (Sim...@co...) wrote: > hi, I managed
> >to > figure that out that already (after the II try) :)
> >>> but thank you very much anyway
> >>>   in the meantime I found a few problems (unseen the first time),
> >>> i will try and describe 'em:
> >>>
> >>> - surely there is a bug in avview, after you aknoledge km
> >>>   is not loaded it loops to death, strace-ing the process
> >>>   you get lots of xv parameters readings, like this
> >>>
> >>>   read(3, "XV_BRIGHTNESS\0Y\0", 16)       = 16
> >>> read(3, "\3\0\0\0\30\374\377\377\350\3\0\0\f\0\0\0", 16) = 16
> >>> read(3, "XV_CONTRAST\0", 12)            = 12
> >>> read(3, "\3\0\0\0\30\374\377\377\350\3\0\0\20\0\0\0", 16) = 16
> >>> read(3, "XV_SATURATION\0T\0", 16)       = 16
> >>> read(3, "\3\0\0\0\30\374\377\377\350\3\0\0\f\0\0\0", 16) = 16
> >>> read(3, "XV_COLOR\0TIO", 12)            = 12
> >>> read(3, "\3\0\0\0\30\374\377\377\350\3\0\0\10\0\0\0", 16) = 16
> >>> read(3, "XV_HUE\0C", 8)                 = 8
> >>> read(3, "\3\0\0\0\0\0\0\0\1\0\0\0\24\0\0\0", 16) = 16
> >>> read(3, "XV_DOUBLE_BUFFER\0\0\0\0", 20) = 20
> >>> read(3, "\3\0\0\0\0\0\0\0\f\0\0\0\f\0\0\0", 16) = 16
> >>> read(3, "XV_ENCODING\0", 12)            = 12
> >>> read(3, "\3\0\0\0\0\0\0\0\377\377\377\377\10\0\0\0", 16) = 16
> >>>
> >>>      so most likely it is some unhandled condition,
> >>> tonight i'm going to check if it is really the last revision,
> >>>
> >>> - xawtv works, meaning that tuner tunes, audio is ok input is
> >>>   switched from sources, BUT the picture is randomly garbled,
> >>>   i can still see the picture, but it is dotted with green fixed
> >>>   pixels, they won't go away and they won't move, if i reboot, the
> >>>   pattern changes but the problem remains, once i had a pattern
> >>>   that matched the shape of my gkrellm window quite closely
> >>>
> >>> - didn't try capture cause avview is unusable
> >>>
> >>> - loaded the km but i could not get an accesible /dev/video,
> >>>   well, honestly i didn't try very hard, i will try again
> >>>
> >>> - xv is still working flawlessly
> >>>
> >>>   xorg.log wasn't a very interesting reading, lots of PutVideo
> >logs >> and a few frequency changes, no errors, nothing strange
> >>>   of course i've not tried to fiddle with the function Rick
> >>> suggested
> >>>
> >>> if you need me to drill out any info from the logs just tell me
> >>>
> >>> regards
> >>> Simone
> >>>
> >>>> -----Messaggio originale-----
> >>>> Da: Vladimir Dergachev [mailto:vo...@mi...]
> >>>> Inviato: mercoled_ 5 gennaio 2005 21.51
> >>>> A: SABA Simone Consultant
> >>>> Cc: Rick Scott
> >>>> Oggetto: Re: R: R: [GATOS][2] Rage 128 testing
> >>>>
> >>>>
> >>>>
> >>>> Hi Simone,
> >>>>
> >>>>    Once you compiled the Xserver there is no need to
> >>>> recompile the entire
> >>>> thing to apply the driver patch, just do this:
> >>>>
> >>>> cd programs/Xserver/hw/xfree86/drivers/ati
> >>>> make
> >>>> make install
> >>>>
> >>>>                      best
> >>>>
> >>>>                         Vladimir Dergachev
> >>>>
> >>>> On Wed, 5 Jan 2005, SABA Simone Consultant wrote:
> >>>>
> >>>>> hi, i did not have time to make extensive testing
> >>>>> cause compiling took almost forever, and at first i
> >>>>> forgot to modify the code as you mentioned :((
> >>>>> anyway it is working :) i tried xv, tv tuner, glxgears
> >>>>> (dri remains disabled, any hope to get it working?)
> >>>>> without problems, only thing missing a test is video
> >>>>> capture
> >>>>>  in the next few days i think i will try out if km is
> >>>>> also working
> >>>>>
> >>>>> meanwhile thank you for the great patch,
> >>>>> i hope it will make it to the official release
> >>>>> go gatos :D
> >>>>>
> >>>>>> -----Messaggio originale-----
> >>>>>> Da: Vladimir Dergachev [mailto:vo...@mi...]
> >>>>>> Inviato: marted_ 4 gennaio 2005 5.25
> >>>>>> A: Rick Scott
> >>>>>> Cc: SABA Simone Consultant
> >>>>>> Oggetto: Re: R: [GATOS][2] Rage 128 testing
> >>>>>>
> >>>>>>
> >>>>>>>>
> >>>>>>>>       Could you check the following:
> >>>>>>>>
> >>>>>>>>       1. Instead of your fix, could you replace the code
> >>>>>> around line 434
> >>>>>>>>          in r128_mm_i2c.c with the following and check
> >>>>>> whether it does
> >>>>>>>>          the same thing:
> >>>>>>>>
> >>>>>>>>         /* You can't attach addon card to a notebook */
> >>>>>>>>      if(!info->MM_TABLE_valid &&
> >>>>>>>>                   (((info->Chipset != PCI_CHIP_RAGE128LE) &&
> >>>>>>>>             (info->Chipset != PCI_CHIP_RAGE128LF) &&
> >>>>>>>>             (info->Chipset != PCI_CHIP_RAGE128MF) &&
> >>>>>>>>             (info->Chipset != PCI_CHIP_RAGE128ML)) ||
> >>>>>>>>             info->forceI2CProbing))R128DetectAddon(pPriv);
> >>>>>>>>             else {
> >>>>>>>>         pPriv->addon_board = FALSE;
> >>>>>>>>         pPriv->board_info = info->MM_TABLE.tuner_type;
> >>>>>>>>         }
> >>>>>>>
> >>>>>>> This works fine, and also clears up the vertical jumping.
> >>>>>> It seems that
> >>>>>>> board_info is used in other key locations, go figure :)
> >>>>>>
> >>>>>> Excellent - thank you !
> >>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>>       2. Is the deadlock with DRI enabled solved by
> >>>>>> removing the line
> >>>>>>>>             info->accel->Sync(pScrn);
> >>>>>>>>          someplace around line 452 in r128_video.c ?
> >>>>>>>
> >>>>>>> This seems to have worked, but I have to go back and check
> >>>>>> my config, and the
> >>>>>>> logs to make sure. Okay, dri and drm loaded. Direct
> >>>>>> rendering got disabled,
> >>>>>>> probably due to some of the unresolved symbols, looks like
> >>>>>> I'm not loading gl
> >>>>>>> :( I'll have to look into that more tomorrow, the holiday
> >>>> is over :)
> >>>>>>
> >>>>>> Cool, thank you ! This would be the last problem I am aware
> >>>>>> of, if it is
> >>>>>> fixed, I can go commit code to X.org and see whether there
> >>>>>> any new bug
> >>>>>> reports.
> >>>>>>
> >>>>>>                       best
> >>>>>>
> >>>>>>                          Vladimir Dergachev
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> The SF.Net email is sponsored by: Beat the post-holiday blues
> >> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> >> It's fun and FREE -- well,
> >almost....http://www.thinkgeek.com/sfshirt >
> >_______________________________________________ > Gatos-devel mailing
> >list > Gat...@li...
> >> https://lists.sourceforge.net/lists/listinfo/gatos-devel
> >>
> >

Hi there,

I am interested in getting the ball rolling on the Theater 550 chip.  I
am not sure if this is used in there AIW stuff, but I would like to
develop the driver for their TV Wonder card.  Looks like Jeremy Fergason
made a comment on Technical Documentation for this card back in January
but it hasn't been discussed since.  Just wondering if someone could
help get a contact at ATI so that I can try to get my paws on this
documentation!

Thanks, Jason