[mythtv-users] IVTV Problem

[Sean]

Good, I thought I was going crazy!!!!!

I noticed yesterday that you (Jarod) mentioned that the 0.12 releases was
available via apt as long as your set the at-bleeding section and that that
release included support for ALSA, Lirc and IVTV. Does this mean that we can
skip scertain sections of your very, very well loved installed guide?

-Sean
...who is perpectually sorry for being a noob...someone ask a Mac question!


> On Thursday, Oct 23, 2003, at 16:52 US/Pacific, Jake wrote:
> 
>> I have been setting up my Myth-Tv Box according to Jarod's
>> Instructions.
>> All has gone well but i have hit a serious snag.
>> 
>> I issue the command:
>> [root at localhost root]# /sbin/modprobe ivtv
>> 
>> And I get this:
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/ivtv.o:
>> init_module: No suc h device
>> Hint: insmod errors can be caused by incorrect module parameters,
>> including inva lid IO or IRQ parameters.
>> You may find more information in syslog or the output from dmesg
>> /lib/modules/2.4.20-20_29.rh9.at/drivers/media/video/ivtv.o: insmod
>> /lib/modules /2.4.20-20_29.rh9.at/drivers/media/video/ivtv.o failed
>> Segmentation fault
>> 
>> I have seen similar problems on the list, but thier solutions don't
>> seem
>> to work. Actually they don't really seem to be the same problem.
>> [snip]
>> My modules.conf has exactly what is on Jarod's instructions.
>> 
>> The crazy thing is that installed ivtv once before and it worked fine.
>> I
>> was even able to capture video with mplayer. Mind this was just 2 days
>> ago. I have tried strating over froma fresh install, but that didn't
>> work either.
> 
> It was just Wednesday or Thursday that Axel updated the ivtv rpms. Due
> to a lack of clarity on licensing issues, for legal reasons, he removed
> the firmware from them.
> 
> Try this on for size:
> 
> # wget 
> http://hauppauge.lightpath.net/software/pvr250/pvr250_17_21226.exe
> # /usr/lib/ivtv/ivtvfwextract.pl pvr250_17_21226.exe
> 
> That'll drop the latest firmware in place for you, then try the
> modprobe again. I'm in the midst of updating the docs as I type, new
> version should be up later tonight.
> 
> --Jarod