This was talked about in earlier posts. Try 0.3.5k, make sure cx25840
is getting modprobed before ivtv and that it's disabled for the 350 (if
350 is detected first the modprobe command should be modprobe cx25840
i2c_enable -1,1). Make sure you power down after changing settings as
the 150 likes to hold onto bad settings. I'd also suggest putting your
350 closer the AGP slot but that may not be necessary. Here's what
helped me:
This is Fredrik Karlsson from an earlier post:
I have had complete success in this. Like Nick says, the only way to
get the cx25840 to properly load the firmware is to load it before
ivtv is loaded. If it is autoloaded by ivtv, it does not work.
After trying a million setups, I reverted back to a minimalistic
setup, which WORKS!
mythtv root # cat /etc/modules.d/ivtv
#This is the contents of modules.conf
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-81-1 ivtv
alias char-major-61 lirc_i2c
mythtv root # cat /etc/modules.autoload.d/kernel-2.6
#What is loaded at startup
#...
tda9887 pal=B
cx25840 i2c_enable=-1,1
ivtv ivtv_std=2 tda9887=0
ivtv-fb
#For lirc
lirc_dev
lirc_i2c
Simple, yet effective. Mostly IVTV magic :-)
/Fredrik
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
