[mythtv-users] ivtv failure on depmod, unresolved symbols

Matt matt at mmc.net
Mon Oct 6 18:36:41 EDT 2003


If you download the RPMS manually (and make sure they match then you are OK).


By the way, have the AT RPMS for LIRC been fixed yet?  I think last time I
checked, the wrong devices were being created by the LIRC RPMS.

-matt


Jarod C. Wilson said:
> On Sunday, Oct 5, 2003, at 20:10 US/Pacific, A. Barr wrote:
>
>> Thanks to Jarod Wilson for writing the install guide for RH9.  I am
>> following this guide and getting some errors after I install ivtv.
>
> You and lots of other folks right now. I think I've got the problem
> narrowed down to the new version of the ivtv drivers conflicting with
> the recent changes in the v4l2 api, which are patched into the ATrpms
> kernel.
>
>> My Kernel is, 2.4.20-20_29.rh9.
>>
>> I installed ivtv using,
>>
>> apt-get install ivtv-kmdl-$KERNEL
>>
>> Output from rpm -q ivtv is,
>>
>> # rpm -q ivtv
>> ivtv-0.12-cvs20030929_13.rh9.at
>>
>> [root at localhost mythtv]# /sbin/depmod -a
>> depmod: *** Unresolved symbols in
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/ivtv-fb.o
>> depmod: *** Unresolved symbols in
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/ivtv.o
>> depmod: *** Unresolved symbols in
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/msp3400.o
>> depmod: *** Unresolved symbols in
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/saa7115.o
>> depmod: *** Unresolved symbols in
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/saa7127.o
>> depmod: *** Unresolved symbols in
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/tveeprom.o
>
> There are a few things you can do. Wait for an updated package that
> should fix the problem, or uninstall your current ivtv drivers and
> downgrade to the earlier release of the drivers
> (0.12-cvs20030813_12.rh9.at, I believe). I'd suggest either manually
> downloading the older packages from the ATrpms web site, or use
> Synaptic to select them for installation.
>
>> I am also getting this i2c error on startup that I assume is unrelated
>> but thought I should mention.
>>
>> Starting lm_sensors: starting up sensors can't access /proc file
>>
>> /proc/sys/dev/sensors/chips or /proc/bus/i2c unreable
>>
>> It gives me this error when booting.
>
> Yes, it is unrelated. You can either 1) safely ignore it without
> consequence 2) actually set up your sensors or 3) disable it from
> trying to start (w/ "/sbin/chkconfig lm_sensors off")
>
> Sorry for the problems, there ought to be fixed packages coming along
> shortly...
>
> --Jarod
>
> --
> Jarod C. Wilson, RHCE
>
> Got a question? Read this first...
>      http://catb.org/~esr/faqs/smart-questions.html
> MythTV, Red Hat Linux 9 & ATrpms documentation:
>      http://pvrhw.goldfish.org/tiki-page.php?pageName=rh9pvr250
> MythTV Searchable Mailing List Archive
>      http://www.gossamer-threads.com/archive/MythTV_C2/
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>



More information about the mythtv-users mailing list