[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ivtv driver in Wheezy 3.2.0-4-amd64



Thanks for your answer, Sven!

On Sat, 05 Jan 2013 18:02:33 +0100, Sven Joachim wrote:

> The obvious difference to the dmesg with the old kernel is that there
> are no messages from the ivtv module.  Is that module loaded?  If not,
> what happens if you modprobe it manually?

The module isn't loaded.

With the older kernel I get:

$ lsmod | grep ivtv
ivtv                  128970  0 
cx2341x                21461  1 ivtv
v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
videodev               70889  6 
cx2341x,v4l2_common,ivtv,cx25840,tuner,wm8775
tveeprom               20593  1 ivtv
i2c_algo_bit           12841  2 ivtv,radeon
i2c_core               23876  17 
i2c_i801,ddbridge,i2c_algo_bit,tveeprom,drm,drm_kms_helper,videodev,
v4l2_common,ivtv,radeon,tea5767,cx25840,tuner,tda8290,tda9887,wm8775,
tuner_simple

But with the newer the same command returns nothing.

When I try to load it I get

# modprobe ivtv
libkmod: ERROR ../libkmod/libkmod-module.c:174 kmod_module_parse_depline: 
ctx=0x7fc95a92e010 path=/lib/modules/3.2.0-4-amd64/kernel/drivers/media/
i2c/tveeprom.ko error=No such file or directory
libkmod: ERROR ../libkmod/libkmod-module.c:174 kmod_module_parse_depline: 
ctx=0x7fc95a92e010 path=/lib/modules/3.2.0-4-amd64/kernel/drivers/media/
i2c/tveeprom.ko error=No such file or directory
ERROR: could not insert 'ivtv': Unknown symbol in module, or unknown 
parameter (see dmesg)

dmesg contains:
http://pastebin.com/raw.php?i=T6CCMV7z


>> Is this a known problem and should I just wait for 3.2.0-5 or can I do
>> something?
> 
> I don't think it is known, consider filing a bug (use reportbug for
> that).  BTW, the -3 and -4 are _not_ package versions, they rather
> indicate the ABI of the kernel (version would be 3.2.35-2 for the -4
> kernel, the -3 kernel did not include that information in the uname
> output).

Thanks for the explanations about the kernel versions.

I used reportbug to file the bug. But I haven't received an ack until now 
(sent it about 5 mins ago).
I will post the link and number here when I got it...


Cheers
Ramon


Reply to: