gatos-devel Mailing List for GATOS

Guys,


For those of you who might be interested in a little bit of feedback,
I've performed several tests on FreeBSD 6.1 and Xorg installed via
ports (version 6.9) with the objective to get TV tuner working. I've
used Xawtv (latest from ports) and the following cards (info obtained
from pciconf utility) :

1) drm0@pci1:0:0: class=3D0x030000 card=3D0x4f721002 chip=3D0x4c661002 =
rev=3D0x02 hdr=3D0x00
    vendor   =3D 'ATI Technologies Inc'
    device   =3D 'Mobility Radeon 9000'
    class    =3D display
    subclass =3D VGA

(64MB AGP card, Theater 200)


2) drm1@pci0:7:0: class=3D0x030000 card=3D0x00291002 chip=3D0x50441002 =
rev=3D0x00 hdr=3D0x00
    vendor   =3D 'ATI Technologies Inc'
    device   =3D 'Rage 128 PD/Pro PCI (TMDS)'
    class    =3D display
    subclass =3D VGA

(32MB PCI card, Rage Theater)


3) drm0@pci1:0:0: class=3D0x030000 card=3D0x2f721002 chip=3D0x59611002 =
rev=3D0x01 hdr=3D0x00
    vendor   =3D 'ATI Technologies Inc'
    device   =3D 'Radeon 9200 Series (RV280)'
    class    =3D display
    subclass =3D VGA

none0@pci1:0:1: class=3D0x038000 card=3D0x2f731002 chip=3D0x59411002 =
rev=3D0x01 hdr=3D0x00
    vendor   =3D 'ATI Technologies Inc'
    device   =3D 'RV280 ATI Radeon 9200 - Secondary'
    class    =3D display

(128MB AGP card, Theater 200)

4) drm0@pci1:0:0: class=3D0x030000 card=3D0x02aa1002 chip=3D0x51441002 =
rev=3D0x00 hdr=3D0x00
    vendor   =3D 'ATI Technologies Inc'
    device   =3D 'Radeon 7200 QD SDR/DDR Radeon 7200 QD SDR/DDR'
    class    =3D display
    subclass =3D VGA

(32MB AGP card, Rage Theater)


The results were the following...=20

Card #1 would give me the picture on the video-in, but when tuner is =
used, frequency table is
messed up (maybe Xawtv problem, but it's not like that for other cards =
(!!!)), thus channels
aren't clear and require deep finetuning... NO SOUND on both internal CD =
conector and
external audio output.

Card #2 Is the only Rage card I have, and is the most unstable one. =
Theater doesn't get
detected, and without NoAccel option set to True locks up the machine.

Card #3 I have only managed to run Xawtv a few times with that card, it =
would give me
NO SOUND on both connectors, but in most cases machine would lock up. =
I've tried
different values for AGPFastWrite, without much of a difference.

Card #4 More or less stable card, NO SOUND on both connectors. Btw, I've =
got 2
of them, and both work the same way.

In case anyone gets interested, I can perform some more suggested tests.

Best regards,
Alex Vinogradovs

El Viernes, 29 de Diciembre de 2006 20:33, Rune Petersen escribi=F3:
> > I was just wondering... as x.org-7.2 is nearly out there, do you know if
> > they are working on this? They also say that 7.3 will bring real
> > enhancements. Perhaps they will handle this in some way.
>
> I assume you are mainly referring to Alex's superpatch which is in GIT
> right now. It doesn't include any TV-out support (it initially did, but
> didn't work), though it _is_ improving mode handling, which should make
> it easier for an eventual tv-out module..


Hi.

I wasn't referring to any superpatch, because I don't know anything about i=
t=20
or any other develpment issue. As I said... "just wondering". But more or=20
less, you gave me a good answer. If the support is improving in some way,=20
that's ok. And if at some point an attempt to make tv-out work was there,=20
then well, I guess that sooner or later somebody will succeed.

	Alberto

Alberto Hernando wrote:
> El Jueves, 28 de Diciembre de 2006 20:39, Rune Petersen escribi=F3:
>> Status: non working.
>> reason: ATI changed something, but what?
>> solution: Someone will have to reverse engineer it.
>>
>> It is sad I know. It will hopeful look better a few months from now, b=
ut
>> no promises...
>=20
>=20
> Hi.
>=20
> I was just wondering... as x.org-7.2 is nearly out there, do you know i=
f they=20
> are working on this? They also say that 7.3 will bring real enhancement=
s.=20
> Perhaps they will handle this in some way.
>=20
I assume you are mainly referring to Alex's superpatch which is in GIT
right now. It doesn't include any TV-out support (it initially did, but
didn't work), though it _is_ improving mode handling, which should make
it easier for an eventual tv-out module..


Rune Petersen

El Jueves, 28 de Diciembre de 2006 20:39, Rune Petersen escribi=F3:
> Status: non working.
> reason: ATI changed something, but what?
> solution: Someone will have to reverse engineer it.
>
> It is sad I know. It will hopeful look better a few months from now, but
> no promises...


Hi.

I was just wondering... as x.org-7.2 is nearly out there, do you know if th=
ey=20
are working on this? They also say that 7.3 will bring real enhancements.=20
Perhaps they will handle this in some way.

	Alberto

Bert Haverkamp wrote:
> Hello all,
> 
> I have a shuttle ST62K with a ATI IGP9100 chipset.
> (It is the same chip as the pundit-R)
> lspci: VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP
> 
> Since xorg 7.1 I am at a loss on TV-out. The latest ati drivers
> don't support this chip and the earlier ones don't work with 7.1 Also
> the gatos drivers and patches I tried
> did not work with my board. The only thing I can do is be very careful
> with upgrades and keep x.org <http://x.org> 7.0, but this is a pain.
> 
> Can anyone clarify the status and dificulties with this chipset? Does
> anyone have a working solution?

Status: non working.
reason: ATI changed something, but what?
solution: Someone will have to reverse engineer it.

It is sad I know. It will hopeful look better a few months from now, but
no promises...


Rune Petersen

Ondrej Certik wrote:
> Hi,
> I downloaded this patch
> 
> http://megahurts.dk/rune/stuff/xorg7-6.5.8.0-tv_output.patch.gz
> 
> and applied it to
> 
> xserver-xorg-video-ati-6.6.3
> 
> taken from debian unstable, but basically, its the same as
> 
> http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.6.3.tar.gz
> 
> and I fixed some compilation issues becase the patch was made for
> 6.5.8. I set the resolution in xorg.conf to 800x600 and put
> 
> Option "MonitorLayout"   "AUTO, NONE"
> Option "TVOutput" "PAL"
> 
> to the Device section (I am living in the Czech Republic, so we use
> PAL). I turned off the computer, plugged the svideo cable in, turned
> on the computer and the TV showed the booting process and X, but
> everything in grayscale. I tried 8bpp, 16bpp, 24bpp color depth, but
> it was still grayscale. I also tried putting
> 
> Option "IgnoreEDID" "true"
> 
> to the Device section and
> 
> Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 -hsync -vsync
> 
> to the Monitor section, but I didn't see any difference (still grayscale).
> 
> Does anyone now how to get colors working on 9200SE? Maybe the problem
> is not in the gatos patch, because even the text mode is in grayscale.
> Any hint or suggestion would be appreciated.
> 
gray scale usually means one of three things:
1) Wrong output type is used (PAL vs. NTSC)
2) the AV input on your TV doesn't support svideo/YC (read your manual).
3) some TV needs to be told it is receiving svideo/YC (read your manual).

if you still have trouble, please mail me your log.


Rune Petersen

Hello all,

I have a shuttle ST62K with a ATI IGP9100 chipset.
(It is the same chip as the pundit-R)
lspci: VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP

Since xorg 7.1 I am at a loss on TV-out. The latest ati drivers
don't support this chip and the earlier ones don't work with 7.1 Also the
gatos drivers and patches I tried
did not work with my board. The only thing I can do is be very careful with
upgrades and keep x.org 7.0, but this is a pain.

Can anyone clarify the status and dificulties with this chipset? Does anyone
have a working solution?

Regards,

Bert

--

Hi,
I downloaded this patch

http://megahurts.dk/rune/stuff/xorg7-6.5.8.0-tv_output.patch.gz

and applied it to

xserver-xorg-video-ati-6.6.3

taken from debian unstable, but basically, its the same as

http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.6.3.tar.gz

and I fixed some compilation issues becase the patch was made for
6.5.8. I set the resolution in xorg.conf to 800x600 and put

Option "MonitorLayout"   "AUTO, NONE"
Option "TVOutput" "PAL"

to the Device section (I am living in the Czech Republic, so we use
PAL). I turned off the computer, plugged the svideo cable in, turned
on the computer and the TV showed the booting process and X, but
everything in grayscale. I tried 8bpp, 16bpp, 24bpp color depth, but
it was still grayscale. I also tried putting

Option "IgnoreEDID" "true"

to the Device section and

Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 -hsync -vsync

to the Monitor section, but I didn't see any difference (still grayscale).

Does anyone now how to get colors working on 9200SE? Maybe the problem
is not in the gatos patch, because even the text mode is in grayscale.
Any hint or suggestion would be appreciated.

Thanks,
Ondrej Certik

Hi,

I just installed openSUSE 10.2, which includes Xorg 7.2 RC2.

I have an ATI Mobility M9 and I was trying to get TV-out working with the 
open-source driver, since there is no proprietary driver for this Xorg 
version.

I followed the discussion with subject "TV-Out with current xf86-video-ati 
git", but it didn't help me (I didn't reply to that e-mail because I just 
subscribed to the list now).

I followed the instructions on http://megahurts.dk/rune/tv_output.html, using 
http://megahurts.dk/rune/stuff/xorg7.1-6.6.3-tv_output.patch.gz and 
http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ati-6.6.3.tar.gz .

My /etc/X11/xorg.conf file goes attached.

My TV is pitch black, I cannot see anything on it.

Can someone provide some help? I am willing to test a lot of things if needed.
, although since it is Xmas time, sometimes I can take a little longer to 
answer.

Thanks in advance for any help,

Hugo Costelha

Hi!
Thank you very much for the patch! Everything works fine now!
Regard,
Johannes

Am Mittwoch, den 13.12.2006, 20:34 +0100 schrieb Francisco L. Fernandez:
> On Thu, 7 Dec 2006 11:17:50 +0000 (UTC)
> huygens <joh...@ao...> wrote:
> 
> > Hello!
> > 
> > > Does your motherboard have a SIS chipset (i.e. 735, 745, 746...)?
> > Yes, I have the ECS K7S5A Mainboard with SiS 735 Chipset.
> 
> I had the same problem with a ECS L7S7A2 (SIS 746).
> 
> Apparently a radeon memory controller checking routine fails with this type of motherboard. Perhaps Vladimir should check that. BIOS related?.
> My card was an AIW 9000 pro.
> 
> I had to disable the routine with the attached patch. 
> After that, km worked flawlessly for me. 
> I hope the same happens with you.
> 
> Regards,
> -------------------------------------------------------------------------
> 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 Thu, 7 Dec 2006 11:17:50 +0000 (UTC)
huygens <joh...@ao...> wrote:

> Hello!
> 
> > Does your motherboard have a SIS chipset (i.e. 735, 745, 746...)?
> Yes, I have the ECS K7S5A Mainboard with SiS 735 Chipset.

I had the same problem with a ECS L7S7A2 (SIS 746).

Apparently a radeon memory controller checking routine fails with this type of motherboard. Perhaps Vladimir should check that. BIOS related?.
My card was an AIW 9000 pro.

I had to disable the routine with the attached patch. 
After that, km worked flawlessly for me. 
I hope the same happens with you.

Regards,

Hello.

Did anyone try to get the TV-Out and VGA-Out on G3 iBook working? There
are 2 different cable adaptors available from Apple.

My hardware is like this:
Radeon Mobility M6 LY, G3-600 dual usb iBook of 2001.

With general radeon kernel modul I tried vga out and just got noice on
the screen, or a distorted picture but with laptop screen disabled then.

Regards,
Paolo

Bernhard Rosenkraenzer wrote:
> On Sunday, 10. December 2006 01:03, Rune Petersen wrote:
>> >From the log:
>>
>> (WW) RADEON(0): Invalid Monitor type specified for 1st port
>>
>> STV/CTV still haven't been implemented please use AUTO.
> 
> Tried that too -- exactly the same effect.
> I was checking the "normal" TV-Out yesterday, I've had a look at the SVHS port 
> today, and it actually produces a picture, but it's badly out of sync 
> (nothing recognizable there), tried with both PAL and NTSC outputs.
> 
>> Have you had it working before with an older driver?
> 
> No, didn't try before.
> I've just tried with 6.5.8.0, and it behaves the same as my patch for GIT, so 
> it looks like my patch did the right thing and just isn't compatible with the 
> hardware I'm using (Asus Pundit R350 barebone -- 9100IGP chipset).
> Has anyone had that hardware working? Any hints on what may need tweaking?

great I misread the log, I thought it was a regular 9100 PRO.

The 9100IGP chipset is r300 based, and r300+ based cards doesn't work
with the patch. ATI changed something, and I haven't been able to figure
out what.

> 
>> P.S.
>> I'll have look at getting a patch done for GIT in late January (if
>> someone else doesn't do it first)
> 
> I might have done it, depending on whether or not the patch works on hardware 
> it's supposed to support.

I have the opposite, I can remove ~30% of the code and my card will run
perfectly fine with TV-out, but no other cards will.
> 
>> (hospital again)
> 
> Hope it's nothing serious... Get well soon!

"Just" having plumbing redone which they removed last time.


Rune Petersen

On Sunday, 10. December 2006 01:03, Rune Petersen wrote:
> >From the log:
>
> (WW) RADEON(0): Invalid Monitor type specified for 1st port
>
> STV/CTV still haven't been implemented please use AUTO.

Tried that too -- exactly the same effect.
I was checking the "normal" TV-Out yesterday, I've had a look at the SVHS port 
today, and it actually produces a picture, but it's badly out of sync 
(nothing recognizable there), tried with both PAL and NTSC outputs.

> Have you had it working before with an older driver?

No, didn't try before.
I've just tried with 6.5.8.0, and it behaves the same as my patch for GIT, so 
it looks like my patch did the right thing and just isn't compatible with the 
hardware I'm using (Asus Pundit R350 barebone -- 9100IGP chipset).
Has anyone had that hardware working? Any hints on what may need tweaking?

And can anyone who has an earlier version working check if my patch works?

> Not to stand in the way of progress, bug why the latest version in GIT?
> A better starting point would be 6.6.3 that should be compatible with
> Xorg 7.1 & 7.2.

Several reasons -- first of all because if it has any chances of getting in, 
it'll get in after 6.6.3, so it should work with the stuff being worked on.

Second, post-6.6.3 GIT is the only version that doesn't barf if you throw 
1920x1080 videos at Xv, and I actually need those for a project.

> P.S.
> I'll have look at getting a patch done for GIT in late January (if
> someone else doesn't do it first)

I might have done it, depending on whether or not the patch works on hardware 
it's supposed to support.

> (hospital again)

Hope it's nothing serious... Get well soon!

Regards,
bero

On Thu, 7 Dec 2006, William M. Quarles wrote:
>> Is lircd running (ps ax | grep lircd)?
>
> [William@localhost ~]$ ps ax | grep lircd
>  2201 ?        Ss     0:00 /usr/sbin/lircd
>  3003 pts/1    R+     0:00 grep lircd

There is a helper program called irw in the LIRC. It should read the data 
from lircd and show it on the stdout when you press the remote control 
buttons. If this works the problem is in avview.

>
>> Which lirc modules are loaded (lsmod | grep lirc)?
>
> None!  Just the ati_remote module.

The table at <http://www.lirc.org/html/table.html> probably tells you if 
you need any additional modules (I'm thinking mainly lirc_dev). If you do, 
try to load them manually before starting lircd.

-- 
Antti Ajanki

Bernhard Rosenkraenzer wrote:
> Hi,
> I'm trying to patch the current xf86-video-ati driver with tv-out support.
> 
> The patch I've come up with based on the patch for 6.5.8.0 can be found at
> http://www.arklinux.org/~bero/xorg-ati-20061130-tvout.patch -- it's probably
> a good starting point, but I must be missing something somewhere -- the TV
> goes black when the X server is started.
> 
> Logs look ok and do talk about TVOutput and theater_out (if anyone wants to
> see it, Xorg -verbose 9 output is at
> http://www.arklinux.org/~bero/Xorg.log.atitv ).
> 
> Can someone who is more familiar with the driver/hardware take a look?

I haven't really looked at the git tree since the "big commit" so I wont
comment on the code.

A blank screen usually means the display has been disabled...

>From the log:
(WW) RADEON(0): Invalid Monitor type specified for 1st port

STV/CTV still haven't been implemented please use AUTO.


Have you had it working before with an older driver?

Not to stand in the way of progress, bug why the latest version in GIT?
A better starting point would be 6.6.3 that should be compatible with
Xorg 7.1 & 7.2.


Rune Petersen

P.S.
I'll have look at getting a patch done for GIT in late January (if
someone else doesn't do it first) (hospital again).

Hi,
I'm trying to patch the current xf86-video-ati driver with tv-out support.

The patch I've come up with based on the patch for 6.5.8.0 can be found at
http://www.arklinux.org/~bero/xorg-ati-20061130-tvout.patch -- it's probably
a good starting point, but I must be missing something somewhere -- the TV
goes black when the X server is started.

Logs look ok and do talk about TVOutput and theater_out (if anyone wants to
see it, Xorg -verbose 9 output is at
http://www.arklinux.org/~bero/Xorg.log.atitv ).

Can someone who is more familiar with the driver/hardware take a look?

Thanks,
bero

Antti Ajanki wrote:
> On Sat, 2 Dec 2006, William M. Quarles wrote:
> 
>> Antti Ajanki wrote:
>>> At least it doesn't report any errors. Maybe it prints some more
>>> information is syslog or some other log file?
>> I wouldn't know any other log file to look in, and I don't know where
>> syslog is located (at least not on Fedora Core 5).
> 
> At least on my Debian box dmesg command prints following lines when it 
> recognizes my serial port receiver (I don't known what the print out 
> would be for a USB receiver):
> 
> lirc_dev: IR Remote Control driver registered, at major 61
> lirc_serial: no version for "lirc_unregister_plugin" found: kernel 
> tainted.
> lirc_serial: auto-detected active low receiver
> lirc_dev: lirc_register_plugin: sample_rate: 0
> 
> 
> Is lircd running (ps ax | grep lircd)?

[William@localhost ~]$ ps ax | grep lircd
  2201 ?        Ss     0:00 /usr/sbin/lircd
  3003 pts/1    R+     0:00 grep lircd

> Which lirc modules are loaded (lsmod | grep lirc)?

None!  Just the ati_remote module.

>> Apparently /dev/lirc doesn't exist?  I have a /dev/lircd though.  I
>> tried linking /dev/lirc to /dev/lircd and that definitely wasn't the
>> solution.  Any ideas?
> 
> /dev/lirc should definitely not be a link to /dev/lircd. AFAIK, for a 
> serial port receiver /dev/lirc print the raw infra red signal. I don't 
> known what it does for USB receiver or if it is necessary at all. You 
> would probably get more information on setting up lirc for USB receivers 
> from the lirc mailing list.
> 
>> Which version of what program are you talking about?  I am using AVview
>> 0.80.7 and LIRC 0.8.0.
> 
> I was refering to the version of the avview. 0.80.7 is definitely new 
> enough to support LIRC if lircd was available.
> 

Hello!

> Does your motherboard have a SIS chipset (i.e. 735, 745, 746...)?
Yes, I have the ECS K7S5A Mainboard with SiS 735 Chipset.
 





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

Hello,

Does your motherboard have a SIS chipset (i.e. 735, 745, 746...)?

On Wed, 6 Dec 2006 20:08:58 +0000 (UTC)
huygens <joh...@ao...> wrote:

> Hi again!
> 
> I am using FC6 with Xorg 7.1.1 on an AthlonXP 2400+ and I have an 64MB ATI Radeon AGP Card with "Composite IN", "Composite OUT" and "SVHS OUT". The Chipset is the ATI Rage Theater (Chip: 213RT1ZUA42). There is a label on the Card which says: ATI Radeon R6 DDRF SD64MB
> 
> I have installed km and so "lsmod | grep" km gives:
> km_drv                 46776  0 
> km_api_drv             21680  1 km_drv
> videodev               27073  1 km_drv
> 
> "lsmod | grep radeon" gives:
> radeon                111520  2 
> drm                    75928  3 radeon
> 
> I have NOT installed Gatos ati.2 driver or Gatos drm-kernel, because they aren't needed with Xorg 7.1.1 --> right?
> 
> When starting AVview I see the Video from Composite Input, but I cannot capture!! I get the following error in /var/log/messages:
> 
> --------------------------
> Dec  6 19:43:48 huygens kernel: Processing "VIDEO_STREAM_ACTIVE"="1" int_value=1
> Dec  6 19:43:48 huygens kernel: Purging transfer queue
> Dec  6 19:43:48 huygens kernel: WARNING !   Radeon memory controller is misconfigured, disabling capture
> Dec  6 19:43:48 huygens kernel: WARNING !   upgrade your Xserver and DRM driver
> Dec  6 19:43:48 huygens kernel: km: no data is available until AVview or xawtv is started
> --------------------------
> 
> Any ideas??
> 
> Antti Ajanki wrote:
> 
> > On Mon, 4 Dec 2006, huygens wrote:
> > 
> > I fixed these two in the CVS:
> > 
> > > 1.)symbolic Link config.h -> autoconf.h in Kernel Source
> > > 2.)patch -p1 -i km-kernel-2.6.18-compile.patch
> > 
> > The last two were already taken care of in CVS:
> > 
> > > 3.)changing MODULE_PARM to MODULE_PARM_DESC in km.c
> > > 4.)Adding following lines to km.c at line 874
> 
> 
> 
> 
> ----------
> Sent via SPRACI - http://www.spraci.com/ - Parties,Raves,Clubs,Festivals
> 
> 
> 
> -------------------------------------------------------------------------
> 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
> 

Hi again!

I am using FC6 with Xorg 7.1.1 on an AthlonXP 2400+ and I have an 64MB ATI Radeon AGP Card with "Composite IN", "Composite OUT" and "SVHS OUT". The Chipset is the ATI Rage Theater (Chip: 213RT1ZUA42). There is a label on the Card which says: ATI Radeon R6 DDRF SD64MB

I have installed km and so "lsmod | grep" km gives:
km_drv                 46776  0 
km_api_drv             21680  1 km_drv
videodev               27073  1 km_drv

"lsmod | grep radeon" gives:
radeon                111520  2 
drm                    75928  3 radeon

I have NOT installed Gatos ati.2 driver or Gatos drm-kernel, because they aren't needed with Xorg 7.1.1 --> right?

When starting AVview I see the Video from Composite Input, but I cannot capture!! I get the following error in /var/log/messages:

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

Any ideas??

Antti Ajanki wrote:

> On Mon, 4 Dec 2006, huygens wrote:
> 
> I fixed these two in the CVS:
> 
> > 1.)symbolic Link config.h -> autoconf.h in Kernel Source
> > 2.)patch -p1 -i km-kernel-2.6.18-compile.patch
> 
> The last two were already taken care of in CVS:
> 
> > 3.)changing MODULE_PARM to MODULE_PARM_DESC in km.c
> > 4.)Adding following lines to km.c at line 874




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

On Sat, 2 Dec 2006, William M. Quarles wrote:

> Antti Ajanki wrote:
>> At least it doesn't report any errors. Maybe it prints some more
>> information is syslog or some other log file?
>
> I wouldn't know any other log file to look in, and I don't know where
> syslog is located (at least not on Fedora Core 5).

At least on my Debian box dmesg command prints following lines when it 
recognizes my serial port receiver (I don't known what the print out 
would be for a USB receiver):

lirc_dev: IR Remote Control driver registered, at major 61
lirc_serial: no version for "lirc_unregister_plugin" found: kernel 
tainted.
lirc_serial: auto-detected active low receiver
lirc_dev: lirc_register_plugin: sample_rate: 0


Is lircd running (ps ax | grep lircd)?

Which lirc modules are loaded (lsmod | grep lirc)?

> Apparently /dev/lirc doesn't exist?  I have a /dev/lircd though.  I
> tried linking /dev/lirc to /dev/lircd and that definitely wasn't the
> solution.  Any ideas?

/dev/lirc should definitely not be a link to /dev/lircd. AFAIK, for a 
serial port receiver /dev/lirc print the raw infra red signal. I don't 
known what it does for USB receiver or if it is necessary at all. You 
would probably get more information on setting up lirc for USB receivers 
from the lirc mailing list.

> Which version of what program are you talking about?  I am using AVview
> 0.80.7 and LIRC 0.8.0.

I was refering to the version of the avview. 0.80.7 is definitely new 
enough to support LIRC if lircd was available.

-- 
Antti Ajanki

On Mon, 4 Dec 2006, huygens wrote:

I fixed these two in the CVS:

> 1.)symbolic Link config.h -> autoconf.h in Kernel Source
> 2.)patch -p1 -i km-kernel-2.6.18-compile.patch

The last two were already taken care of in CVS:

> 3.)changing MODULE_PARM to MODULE_PARM_DESC in km.c
> 4.)Adding following lines to km.c at line 874

-- 
Antti Ajanki

Hi again!

I have now compiled km and successfully tested capturing with avview!! I found the following lines in my /var/log/messages file:

km_drv: disagrees about version of symbol video_devdata
Unknown symbol video_devdata

So I deinstalled video4linux from my system and and did a reboot. Then everything was OK. I could compile km and inserted the modules. Then I tried AVView. It didnt work at first. I installed 
drm-kmdl-2.6.18-1.2849.fc6.i686 and capturing worked!!

Thank you All!!




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

Hi again!

I now have successfully compiled km!! YUHU!!
BUT I can't insert the modules :(
First: This is what I have done so far:

1.)symbolic Link config.h -> autoconf.h in Kernel Source
2.)patch -p1 -i km-kernel-2.6.18-compile.patch
3.)changing MODULE_PARM to MODULE_PARM_DESC in km.c
4.)Adding following lines to km.c at line 874

#ifndef PCI_DEVICE_ID_ATI_RADEON_LE
#define PCI_DEVICE_ID_ATI_RADEON_LE 0x4d45
#endif

#ifndef PCI_DEVICE_ID_ATI_RADEON_LF
#define PCI_DEVICE_ID_ATI_RADEON_LF 0x4d46
#endif

If do "make test" I get following:

[root@huygens km]# LC_ALL=C make test
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'
  Building modules, stage 2.
  MODPOST
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
** Syncing disks
sync
** Trying to make sure v4l module is loaded
modprobe videodev || true
** Now loading km modules
insmod ./km_api_drv.ko
insmod: error inserting './km_api_drv.ko': -1 File exists
make: *** [test] Error 1

Every help would be appreciated!




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