On 9/16/05, Torsten Mohr <[EMAIL PROTECTED]> wrote:
> 
> I load the driver with this part in:
> ivtv-0.3.9/driver/Makefile2.6
> 
> reload:
>   -sudo rmmod ivtv-fb ivtv msp3400 saa7115 saa7127 tuner
>   sync
>   -sudo modprobe i2c-core
>   -sudo modprobe i2c-algo-bit
>   -sudo insmod saa7115.ko
>   -sudo insmod msp3400.ko once=1 simple=1 standard=0x03
>   -sudo modprobe tuner type=29
>   -sudo modprobe videodev
>   -sudo insmod ivtv.ko ivtv_debug=0 ivtv_std=2 tuner=52
> 
> In /etc/modprobe.conf i have:
> 
> options tuner   type=2

Please don't cross post, choose either the devel list or the users
list, not both. For the archives sake, this is my reply (also sent to
ivtv-users).

Firstly, you've specifying *three* conflicting tuner types, but you
shouldn't need to manually specify them anyway. Remove all your
modules options, do a cold boot, then simply do a 'modprobe ivtv' (the
other modules will get loaded automatically). If you're still having
problems, post your dmesg output.

Side note: that stuff in the makefile seems out of place, and should
really be removed (or replaced with a plain old 'modprobe ivtv'). Does
anyone actually use the make reload target, and should it even be
there?

Cheers,

Ross


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to