[mythtv-users] depmod and modprobe errors with pvr-250
James Boike
jboike at nyc.rr.com
Sun Aug 3 18:43:10 EDT 2003
Folks,
Thanks for all your hard work with this project -- ivtv paired with
MythTV made me a very recent Linux convert. Though I've searched through
FAQs, docs, and various mail lists, I find myself stuck. I use Mandrake
9.1, kernel 2.4.21, a PVR-250 rev2, and Myth 0.10 installed from Thac's
RPMs. I posted a similar note to IVTV, but since I followed MythTV docs
this list is probably more familiar with the situation.
I've followed Myth's mini-HowTo
(http://mythtv.org/docs/mythtv-HOWTO-19.html#ss19.10) and successfully
finished each step up to the depmod -a command from within
~/ivtv/ivtv/driver. Doing this renders:
[root at ____ driver]# depmod -a
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
And the results of the next step: modprobe ivtv
[root at ____ driver]# modprobe ivtv
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_smbus_write_byte_data_R086140c4
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_probe_R383d2454
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_add_driver_Raa1c123c
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_transfer_R33c36c56
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_smbus_read_byte_data_R4e67a885
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_attach_client_R0c95dc6e
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_detach_client_Rc6b463c3
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_del_driver_Raddfe9b5
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o:
unresolved symbol i2c_check_functionality_R1a3f6656
modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7115.o failed
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol i2c_probe_R383d2454
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol i2c_master_send_R188f3446
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol i2c_add_driver_Raa1c123c
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol
i2c_transfer_R33c36c56/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol i2c_attach_client_R0c95dc6e
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol i2c_detach_client_Rc6b463c3
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o:
unresolved symbol i2c_del_driver_Raddfe9b5
modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/msp3400.o failed
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o:
unresolved symbol i2c_bit_add_bus_Rd69f43f9
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o:
unresolved symbol video_register_device_R43c2ffa4
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o:
unresolved symbol video_unregister_device_R0ae0f10e
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o:
unresolved symbol i2c_master_send_R188f3446
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o:
unresolved symbol i2c_bit_del_bus_R38650d11
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o:
unresolved symbol __pollwait_R73a0d137
modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/ivtv.o failed
modprobe: insmod ivtv failed
IVTV list told me depmod just checks module dependencies, and that it's
"only really a problem if the unresolved symbols happen on module load."
This seems to be the case given the second output, so I assume I have a
problem. I don't seem to have a /dev/v4l directory, though lspci -v
successfully displays my Hauppauge card.
One note that I'm not sure is related: Myth 19.10 docs say I do not need
to recompile my kernel, but IVTV readme says I have to get my kernel
"patched and compiled with the v4l2 stuff." I don't seem to have v4l2 on
my system, as there is no v4l or v4l2 directory in dev. Are these two
instructions contradictory?
I apologize for the length, but I want to be as thorough as possible.
I'm very new, trying to grasp all this and taking copious notes so I can
publish a newbie's HowTo when complete. I appreciate any recommendations
to get past depmod and modprobe -- the simpler and more basic, the better.
Thanks again for all your efforts,
Jamey
More information about the mythtv-users
mailing list