> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Sam
> Varshavchik
> Sent: Sunday, November 19, 2006 4:49 PM
> To: User discussion about IVTV
> Subject: Re: [ivtv-users] lirc_i2c: no version for
> "lirc_unregister_plugin" found
>
> David Fishburn writes:
>
> >
> >
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On Behalf Of Sam
> >> Varshavchik
> >> Sent: Sunday, November 19, 2006 2:08 PM
> >> To: User discussion about IVTV
> >> Subject: Re: [ivtv-users] lirc_i2c: no version for
> >> "lirc_unregister_plugin" found
> >>
> >> David Fishburn writes:
> >>
> >> > sudo modprobe lirc_i2c
> >> > dmesg | tail
> >> >
> >> > I get this output:
> >> > [ 44.670400] lirc_dev: IR Remote Control driver
> >> registered, at major 61
> >> > [ 44.681445] lirc_i2c: no version for
> >> "lirc_unregister_plugin" found:
> >> > kernel tainted.
> >>
> >> This is a known issue, but does not have anything to do with
> >> your other problems.
> >>
> >> Earlier this year I sent a quick fix to the makefile to stop
> >> it from tainting the kernel. It was so long ago that I
> >> forgot if it was lirc's makefile or ivtv's makefile that
> >> needed to be fixed. It was a no-brainer fix, but nobody cared.
> >
> >
> > Hmm, will that address the no version for
> "lirc_unregister_plugin" found
> > error?
>
> Yup.
>
> > I did a search on your username and did not find any
> references to this.
> >
> > I also check the lirc open source page:
> > http://sourceforge.net/forum/forum.php?forum_id=16771
> >
> >
> > Any suggestions on where I might find the fix you posted?
>
> Sourceforge's search is crap. I found my original message.
> It was an lirc
> makefile fix:
>
> ==============================================================
> =============
>
> From: Sam Varshavchik <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Sat, 08 Jul 2006 18:12:13 -0400
>
> Searching the list archives, I find occasional messages going
> back to 2005
> about people wondering why they get their kernel tainted
> after loading
> various lirc modules.
>
> I'll skip the excrutiating details. To make a long story
> short, it looks
> like there's a very easy way to finally bury this bug,
> starting with kernel
> 2.6.17, due to some enhancements in the module build system.
>
> I'll make this short. My lirc packaging script does this:
>
> ==============================================================
> ============
>
> [ unpack, configure, et al ]
>
> # Fix kernel taint due to missing symvers
>
> make -C drivers/lirc_dev
>
> for f in drivers/*/.
> do
> test -f drivers/lirc_dev/Modules.symvers || continue
> test -f $f/Modules.symvers || cp
> drivers/lirc_dev/Modules.symvers $f/Modules.symvers
> done
>
> make
>
> ==============================================================
> ============
>
> Rather than running make right off the bat, first, I manually
> run make in
> drivers/lirc_dev. Under 2.6.17 -- and under 2.6.17 only --
> modpost creates
> Modules.symvers in drivers/lirc_dev (this is why I test if
> Modules.symvers
> was created, so the whole thing gets ignored when building
> modules for older
> kernels). I take it, and copy it to all the other driver directories.
>
> Presto. No more tainted kernels.
>
> It would be nice if lirc's Makefile gets fixed to take
> advantage of 2.6.17's
> modpost, before the 0.8.1 release.
I tried these steps, but ended with the same results.
Here is exactly what I did, logged in as root.
Now download and install the driver. As of this writing, the latest
version
is lirc-0.8.1pre2. See the LIRC homepage or the project's Sourceforge
download page
wget
http://lirc.sourceforge.net/software/snapshots/lirc-0.8.1pre2.tar.bz2
cd /usr/src
tar -xjvf /opt/download/lirc/lirc-0.8.1pre2.tar.bz2 -C /usr/src
cd /usr/src/lirc-0.8.1pre2
Compile driver module
Before we can compile, we'll need to tell LIRC which type of IR
receiver/blaster we have. Do a
./configure
and select
1: Driver Configuration -> 5: TV Card -> g: Hauppauge TV card.
Scroll down to 3: Save configuration & run configure
Wait for configure to finish building the makefiles.
Fix the "kernel tainted" messages thanks to Sam Varshavchik with:
make -C drivers/lirc_dev
for f in drivers/*/.
do
test -f drivers/lirc_dev/Modules.symvers || continue
test -f $f/Modules.symvers || cp
drivers/lirc_dev/Modules.symvers $f/Modules.symvers
done
Once that's done, do
make
make install
Assuming there were no errors, do a
depmod -a
then look for the following files:
ls /lib/modules/`uname -r`/misc
lirc_dev.ko lirc_i2c.ko
If either file is missing, read through the make output and look for
any errors that might explain the problem.
I rebooted here:
Testing LIRC
Load the driver module into the kernel and make sure it sees your IR
hardware.
modprobe lirc_i2c
dmesg | tail
[ 45.457825] lirc_dev: IR Remote Control driver registered, at major 61
[ 45.462504] lirc_i2c: no version for "lirc_unregister_plugin" found:
kernel tainted.
[EMAIL PROTECTED]:/usr/src/lirc-0.8.1pre2/drivers/lirc_dev# ll
total 184
drwxrwxrwx 4 fishburn users 4096 2006-11-19 19:47 .
drwxrwxrwx 18 fishburn users 4096 2006-11-19 19:36 ..
drwxr-xr-x 2 root root 4096 2006-11-14 21:17 .deps
-rw-r--r-- 1 fishburn users 21222 2006-09-21 23:18 lirc_dev.c
-rw-r--r-- 1 fishburn users 6872 2006-09-21 23:18 lirc_dev.h
-rw-r--r-- 1 root root 29149 2006-11-19 19:47 lirc_dev.ko
-rw-r--r-- 1 root root 244 2006-11-19 19:47 .lirc_dev.ko.cmd
-rw-r--r-- 1 root root 1888 2006-11-19 19:47 lirc_dev.mod.c
-rw-r--r-- 1 root root 5896 2006-11-19 19:47 lirc_dev.mod.o
-rw-r--r-- 1 root root 10353 2006-11-19 19:47 .lirc_dev.mod.o.cmd
-rw-r--r-- 1 root root 24309 2006-11-19 19:47 lirc_dev.o
-rw-r--r-- 1 root root 13754 2006-11-19 19:47 .lirc_dev.o.cmd
-rw-r--r-- 1 root root 11273 2006-11-19 19:36 Makefile
-rw-r--r-- 1 fishburn users 448 2004-04-25 12:29 Makefile.am
-rw-r--r-- 1 fishburn users 11561 2006-10-14 02:24 Makefile.in
-rw-r--r-- 1 root root 242 2006-11-14 21:18 Modules.symvers
-rw-r--r-- 1 root root 284 2006-11-19 11:43 Module.symvers
drwxr-xr-x 2 root root 4096 2006-11-19 19:47 .tmp_versions
Not sure why I have 2 of these:
-rw-r--r-- 1 root root 242 2006-11-14 21:18 Modules.symvers
-rw-r--r-- 1 root root 284 2006-11-19 11:43 Module.symvers
Do you see anything I missed?
Dave
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
