I ended up extracting the bin files from pvr48wdm_1.8.22037.exe. While it is fairly old it did allow me to get mythtv running. Currently I am tuning fuzz, but I'm a lot further along than I was. I am going to look into extracting the bin files from the latest driver, pvr48wdm_2.0.22280.exe.
On Sat, 05 Mar 2005 08:19:43 +0000, stephen parkinson <[EMAIL PROTECTED]> wrote: > Isaiah Frantz wrote: > > >Also is this message ok in dmesg: > >ivtv: Unknown card: vendor/device: 4444/0016, subsystem vendor/device: > >0070/e817 > >ivtv: Defaulting to WinTV PVR 150 card > > > >Or do I need to add a definition for the PVR 500? > > > > > >On Fri, 4 Mar 2005 23:39:56 -0800, Isaiah Frantz > ><[EMAIL PROTECTED]> wrote: > > > > > >>Thanks a lot for all of your help. That almost worked for me. > >>I got the following error: > >>Unable to open '/lib/modules/ivtv-fw-enc.bin'. > >>ivtv: failed loading encoder firmware > >>ivtv: Error loading firmware -3! > >>ivtv: Error -3 initializing firmware. > >>ivtv: Error -12 on initialization > >>ivtv-iTVC15_16_mpg2_encoder_card: probe of 0000:02:09.0 failed with error > >>-12 > >>ivtv: ==================== END INIT IVTV ==================== > >> > >>I went looking in the source and found this in ivtv-driver.h: > >>/*Used for locating the firmware mailboxes*/ > >>#if defined(LINUX26) && defined(CONFIG_FW_LOADER) && defined(IVTV_FW_LOADER) > >>#define IVTV_FIRM_ENC_FILENAME "ivtv-fw-enc.bin" > >>#define IVTV_FIRM_DEC_FILENAME "ivtv-fw-dec.bin" > >>#else > >>#define IVTV_FIRM_ENC_FILENAME "/lib/modules/ivtv-fw-enc.bin" > >>#define IVTV_FIRM_DEC_FILENAME "/lib/modules/ivtv-fw-dec.bin" > >>#endif > >> > >>Can I substitute the ROM file you mentioned for the enc and dec bin > >>files, or do I need to extract the bins from the ROM? > >> > >> > >>On Fri, 4 Mar 2005 22:32:53 -0800 (PST), Jason Knisley > >><[EMAIL PROTECTED]> wrote: > >> > >> > >>>A couple of things you need to remember: > >>> > >>>1. The kernel tuner module is behind the times. > >>>Because of this, you need to rename or remove the > >>>kernel tuner module so that the ivtv one will load. > >>>It's in /lib/KVER/kernel/drivers/media/video > >>> > >>>2. The kernel needs to be compiled WITHOUT 4kstacks. > >>>For the moment, pending a new patch, ivtv is dependent > >>>on 8k stacks. > >>> > >>>As for the firmware, it's actually right out in plain > >>>sight on the PVR500 CD. It's a file called HcwMkoA.ROM > >>>(and yes, the copy is case-sensitive) and it needs to > >>>be placed in the /lib/modules directory. > >>> > >>>0.3.2f will get things working nicely, although > >>>there's a slight modification to tuner.c (you change > >>>the FQ1236A MK4's VHFHI->UHF threshold to 16*442.00), > >>>but it should mainly work after that. We're hoping to > >>>get rid of the ivtv tuner and move it into the new > >>>v4l2, which will require using the addr parameter for > >>>the tuner module. Don't worry about that for now and > >>>just use the tuner included with ivtv. > >>> > >>>There are still some issues with scaling and VBI > >>>slicing. You need to use the 720*480 mode when trying > >>>to record or you'll crop the right half of the > >>>picture. Additionally, the VBI data isn't sliced off > >>>and is in a fine line at the top of the recording. > >>> > >>>modprobe cx25840 i2c_enable=1 no_black_magic=1 // > >>>audiofmt=1 cardfmt=1 > >>> > >>>(where that double slash indicated you're supposed to > >>>keep it on the same line) > >>> > >>>then "modprobe ivtv tuner=54,54" > >>> > >>>It's type 54 for me, but I think I added mine in at > >>>the end. If that doesn't say "FQ1236A MK4" when you > >>>load it up (check your log dir/messages) then look in > >>>tuner.c and find said tuner. TCL2002N is type 50, so > >>>count down however many it is to that one. There's > >>>your tuner. > >>> > >>>That should do it. > >>>Jason > >>> > >>>--- Isaiah Frantz <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>>>Hey there, > >>>>I have been watching this mail list and keep seeing > >>>>people say that > >>>>they have their PRV500 working. What nobody has > >>>>bothered to do is > >>>>concisely tell what ivtv codebase (as there appears > >>>>to be two forks) > >>>>and what patches (as there seem to be many floating > >>>>around) they are > >>>>using when they get it to "work". > >>>> > >>>>I have tried to get 0.3.2f to work on a 2.6.10-r7 > >>>>gentoo-dev kernel, > >>>>but every time I modprobe ivtv I get a kernel panic. > >>>> > >>>>Would it be possible for one of you folks to write a > >>>>short guide to > >>>>getting this working, including where one obtains > >>>>the firmware. I > >>>>tried to use the firmware extractor in the util dir > >>>>but it looks like > >>>>it is expecting the pvr250-350 file which is totaly > >>>>different from the > >>>>pvr500 file: > >>>> > >>>> > >>>> > >>>http://hauppauge.lightpath.net/software/pvr150/pvr150_2028_23053_whql.zip > >>> > >>> > >>>>Thanks. > >>>> > >>>> > >>>> > >>>> > >>>> > >>>------------------------------------------------------- > >>> > >>> > >>>>SF email is sponsored by - The IT Product Guide > >>>>Read honest & candid reviews on hundreds of IT > >>>>Products from real users. > >>>>Discover which products truly live up to the hype. > >>>>Start reading now. > >>>> > >>>> > >>>> > >>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> > >>> > >>>>_______________________________________________ > >>>>ivtv-devel mailing list > >>>>[email protected] > >>>> > >>>> > >>>> > >>>https://lists.sourceforge.net/lists/listinfo/ivtv-devel > >>> > >>> > >>>------------------------------------------------------- > >>>SF email is sponsored by - The IT Product Guide > >>>Read honest & candid reviews on hundreds of IT Products from real users. > >>>Discover which products truly live up to the hype. Start reading now. > >>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>>_______________________________________________ > >>>ivtv-devel mailing list > >>>[email protected] > >>>https://lists.sourceforge.net/lists/listinfo/ivtv-devel > >>> > >>> > >>> > > > > > >------------------------------------------------------- > >SF email is sponsored by - The IT Product Guide > >Read honest & candid reviews on hundreds of IT Products from real users. > >Discover which products truly live up to the hype. Start reading now. > >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >_______________________________________________ > >ivtv-devel mailing list > >[email protected] > >https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > > googling on linux & 4444:0016 > > gives as first result > > Hacking_GPIO_of_CX23416/FCX23415 > > stephen > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
