Mailing List Archive

installing ivtv, pvr-350, mandrake 9.1, unresolved symbols during depmod -a HELLLP!!
MythTV brothers,

I'm trying to install the ivtv drivers for my pvr-350
on a Mandrake 9.1 system. I'll describe step by step
what I did, and hopefully someone can tell me what I
did wrong, and maybe other readers will find this
informative.

I started by following section 19.1 of the MythTV faq:
----------------
In the FAQ:
$ uname -a
Linux pvr 2.4.21-0.16mdk #1 Fri Apr 11 06:51:54 CEST
2003 i686 unknown
unknown GNU/Linux

$ su
# urpmi kernel-source
----------------
So I typed 'uname -a'. The result was pretty much the
same, except my version number is 2.4.21-0.13mdk #1
Fri Mar 14 15:08:06 EST 2003 i686. I'm not sure if
this makes a difference.

Then I entered superuser mode and downloaded the
kernel-source. After like 10-15 minutes of
downloading, this step completed without a hitch.
The downloaded kernel source was a newer version than
the kernel I'm running, but the FAQ says "NOTE: You do
not need to recompile your kernel."

Then I executed:
$ cvs
-d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/ivtv
login
<enter> as password
$ cvs -z3
-d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/ivtv
co ivtv
This part seemed ok.

Then, instead of
$ cd ivtv/ivtv/utils
$ wget
http://hauppauge.lightpath.net/software/pvr250/pvr250_16_21062.exe
$ su
# ./ivtvfwextract.pl pvr250_16_21062.exe
I went to the hauppauge website using a browser and
downloaded the pvr250_16_21062.exe file. I ran
ivtvfwextract on it and this created two files,
lib/modules/ivtv-fw-dec.bin, and
lib/modules/ivtv-fw-enc.bin. Seems fine and dandy.

Then, I did this:
$ cd ~/ivtv/ivtv/driver
$ make
Everything looked good. I now had a bunch of .o files.

I added the required lines to /etc/modules.conf, and
then ran
$ su
# make install
This copied a bunch of .o files into
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/

Next, I did an extra step not covered in the mythTV
FAQ. In the ivtv FAQ found at
http://ivtv.sourceforge.net/FAQ.html#_jump08,
"V4L2 headers are required for ivyTV to compile. You
can either patch your kernel with v4l2 headers or copy
the included videodev2.h from the utils/ directory to
the driver/ directory." So I copied the videodev2.h
file like the FAQ stated.

Then when I did
# depmod -a
I got:
depmod: *** Unresolved symbols in
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7127.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/tveeprom.o
This is where I have the shake my head and say I have
no idea what is going on.
I went ahead and did
# modprobe ivtv
but the driver modules failed to load.

If someone could please please help me with this, I
would be much obliged! I've been stuck on this for a
whole day already.

This mail was probably more verbose than necessary,
but hopefully someone just starting the mythTV project
will find my lengthy descriptions helpful. If you guys
want me to tone it down, just tell me =).



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Re: installing ivtv, pvr-350, mandrake 9.1, unresolved symbols during depmod -a HELLLP!! [ In reply to ]
Well, just for grins (and because I care), I whacked my box and followed
my own instructions. Works For Me:

[root@frontend mythtv]# uname -a
Linux frontend 2.4.21-6mdk #1 Tue Jul 22 14:34:34 EDT 2003 i686 unknown
unknown GNU/Linux
[root@frontend mythtv]# rpm -qa|grep kernel
kernel-2.4.21.6mdk-1-1mdk
kernel-source-2.4.21-6mdk

i2c-algo-bit.o: i2c bit algorithm module version 2.7.0 (20021208)
Linux video capture interface: v1.00
ivtv: Found an iTVC16 based chip
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
tuner: probing ivtv i2c driver #0 i2c adapter [id=0x10005]
tuner: chip found @ 0xc2
tuner(bttv): type forced to 2 (Philips NTSC (FI1236,FM1236 and
compatibles)) [insmod]
saa7114.c: starting probe for adapter ivtv i2c driver #0 (0x10005)
saa7114.c: detecting saa7114 client on address 0x42
saa7115.c: writing init values
status: (1E) 0x50, (1F) 0xc0
msp34xx: init: chip=MSP3435G-B6, has NICAM support
msp3410: daemon started
ivtv: Encoder revision: 0x02040002
ivtv: Registered v4l2 device, minor 0
ivtv: Registered v4l2 device, minor 32
ivtv: Registered v4l2 device, minor 224
ivtv: Found an unknown chip, treating it like an iTVC15
tuner: probing ivtv i2c driver #1 i2c adapter [id=0x10005]
tuner: chip found @ 0xc2

[root@frontend mythtv]# ls -l /dev/vi*
lr-xr-xr-x 1 root root 10 Aug 4 13:42 /dev/video -> v4l/video0
lr-xr-xr-x 1 root root 10 Aug 4 13:42 /dev/video0 -> v4l/video0
lr-xr-xr-x 1 root root 10 Aug 4 13:42 /dev/video1 -> v4l/video1
lr-xr-xr-x 1 root root 11 Aug 4 13:42 /dev/video32 -> v4l/video32
lr-xr-xr-x 1 root root 11 Aug 4 13:42 /dev/video33 -> v4l/video33

I'd suggest that you double check what you did, and if you still can't
figure out what happened that you re-post your question on the ivtv list.