Pipe Dream schreef:
>
> # modprobe ivtv
>
>/FATAL: Error inserting ivtv
>/>>/ (/lib/modules/2.6.16.13-4-smp/kernel/drivers/media/video/ivtv.ko):
>/>>/ Unknown symbol in module, or unknown parameter (see dmesg).
>/>>/
>/>>/ dmesg gives
>/>>/
>/>>/ ivtv: module not supported by Novell, setting U taint flag.
>/>>/ ivtv: Unknown symbol tveeprom_read
>/>>/ ivtv: Unknown symbol tveeprom_hauppauge_analog
>
>Found this read out in another post and this is exactly the same error message
>I receive as well.
>
>/
>
>
> ------------------------------------------------------------------------
> How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call
> rates.
> <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
>
>
>
>
> <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
>------------------------------------------------------------------------
>
>_______________________________________________
>ivtv-users mailing list
>[email protected]
>http://ivtvdriver.org/mailman/listinfo/ivtv-users
><http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
>
I had the same problem, also on a Suse 10.1 SMP kernel. This is how I
solved it:
The HowTo states that some modules should be replaced by those of ivtv.
It says to
cd /lib/modules/`uname -r`/kernel/drivers/media/video/
mv msp3400.ko msp3400.ko.old
mv tveeprom.ko tveeprom.ko.old
mv tuner.ko tuner.ko.old
mv tda9887.ko tda9887.ko.old
and replace them by the ivtv-variantsBut for ivtv 6.3 that seems to be
incorrect; in 6.3, there are no ivtv-variants of those modules.
Furthermore, the firmware howto has a small flaw (a typo I suppose) it
states
SuSE users may need to look in the file /sbin/udev.firmware.sh for
the FIRMWARE_DIRS variable
This should be /sbin/udev/firmware.sh; a slash between udev and
firmware, in stead of a dot.
After moving the .ko.old modules to their original names, run
depmod -a
again, and move the firmware to the location found (in my case,
/lib/firmware).
Now, do
modprobe ivtv
It loads succesfully, and
cat /dev/video0 > test.mpg
gives a result.
I hope this helps for you, too.
Now I have to find out how to tune it - ptune-ui.pl compaints that it
can't find Tk.pm. But probably someone has tackled that too...
regards, Jogchum
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
