Of course I am using kernel 2.6.18, I wouldn't have come so far if i didn't :) I also recompiled ivtv, I don't use lirc.
modinfo cx25840 says: filename: /lib/modules/2.6.18-ck1/kernel/drivers/media/video/cx25840/cx25840.ko description: Conexant CX25840 audio/video decoder driver author: Ulf Eklund, Chris Kennedy, Hans Verkuil, Tyler Trafford license: GPL vermagic: 2.6.18-ck1 SMP mod_unload gcc-4.1 depends: v4l2-common parm: firmware:Firmware image [default: v4l-cx25840.fw] (charp) parm: ignore:List of adapter,address pairs not to scan (array of short) parm: probe:List of adapter,address pairs to scan additionally (array of short) parm: force:List of adapter,address pairs to boldly assume to be present (array of short) parm: debug:Debugging messages [0=Off (default) 1=On] (int) modprobe cx25840 -v says: insmod /lib/modules/2.6.18-ck1/kernel/drivers/media/video/cx25840/cx25840.ko Another problem I have is that he can't load the firmware when I reload the module. He does find it when he loads it on startup. Does someone has the solution to these 2 problems? Thanks in advance. > For your case, I've no clue. But I think ivtv 0.8 goes with kernel > 2.6.18. Do you have the latest kernel? Even if you upgraded to your > latest kernel, make sure you re-compile ivtv and lirc after your > recent kernel upgrade. > > If this doesn' help, check 'modinfo cx26840' if there are any debug > options enable it during modprobe (or in modprobe.conf). That should > give you more info. > > Cheers, > -Jana > > On 10/1/06, Michael Adriaansen <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I've think I might have the same problem. I can't find any errors when >> searching for ivtv in dmesg and when I cat /dev/video0 > my.mpg, I get >> an >> empty file of 0B. When I do dmesg |grep cx25840, i get a lot of errors >> like this: >> cx25840 3-0044: 1x1 is not a valid size! >> Do you get that text as well? I'm using ivtv 0.8 btw and i don't get >> that >> i2c error. >> >> >> > Nope. Didn't help. Same exact problem. Any other suggestion? >> > >> > It's hard to imagine there aren't others in the same boat as mine. >> > >> > Thanks, >> > -Jana >> > >> > >> > On 9/30/06, Sander Sweers <[EMAIL PROTECTED]> wrote: >> >> Janardhanan Radhakrishnan wrote: >> >> > On further investigation it looks like the tuner is not tuning to >> any >> >> > frequency because of the following messages in dmesg dump: >> >> > >> >> > ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >> >> > ivtv0: i2c hardware 0x00000008 not found for command 0x4008646d! >> >> > ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >> >> > ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >> >> > ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >> >> >> >> Try newi2c=0 as a module option to ivtv and see if this helps. >> >> >> >> Everything else looks ok to me. >> >> >> >> Greets >> >> Sander >> >> >> >> _______________________________________________ >> >> ivtv-users mailing list >> >> [email protected] >> >> http://ivtvdriver.org/mailman/listinfo/ivtv-users >> >> >> > >> > _______________________________________________ >> > ivtv-users mailing list >> > [email protected] >> > http://ivtvdriver.org/mailman/listinfo/ivtv-users >> > >> >> >> >> _______________________________________________ >> ivtv-users mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-users >> > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
