Morten Feldthaus wrote:
> On 2/8/07, Sander Sweers <[EMAIL PROTECTED]> wrote:
>   
>> Roger Depreeuw wrote:
>>     
>>> On Thu, 2007-02-08 at 17:18 +0100, Morten Feldthaus wrote:
>>>       
>>>> Hi
>>>>
>>>> I'm trying to get my PVR-350 to work in Linux. First I tried installing it 
>>>> on a
>>>> VIA EPIA computer using Ubuntu Edgy. I followed the guide at
>>>> https://help.ubuntu.com/community/Install_IVTV_Edgy
>>>>
>>>> I get the following errors in dmesg:
>>>> ivtv0: Autodetected Hauppauge WinTV PVR-350
>>>> ivtv0 warning: Encoder mailbox not found
>>>> ivtv0 warning: invalid api mailbox
>>>> ivtv0 warning: Encoder firmware dead!
>>>> ivtv0: Error initializing firmware
>>>> ivtv0: Error -19 on initialization
>>>>
>>>> Now i've installed the newest Mythdora on my AMD 1700+ and I'm getting the 
>>>> same
>>>> error. I've tried compiling the newest 0.7.x driver from ivtvdriver.org 
>>>> without
>>>> any luck.
>>>>
>>>> Do you guys have any suggestions? Is the card dead?
>>>>
>>>>         
>>> There is an issue about new firmware files that need to have a fixed
>>> length.
>>> Download the new released ivtv package and you'll find a new encoder
>>> firmware file. Hope this helps
>>> Good luck
>>>       
>> Always include the whole INIT IVTV and any module options you have in
>> /etc/modprobe.conf.This is essential informations.
>>     
>
> I don't have any modprobe.conf and I don't use any module options.
> Here's the complete dmesg output:
>
> [17179769.268000] ivtv:  ==================== START INIT IVTV
> ====================
> [17179769.268000] ivtv:  version 0.7.3 (tagged release) loading
> [17179769.268000] ivtv:  Linux version: 2.6.17-10-386 mod_unload 486
> REGPARM gcc-4.1
> [17179769.268000] ivtv:  In case of problems please include the debug
> info between
> [17179769.268000] ivtv:  the START INIT IVTV and END INIT IVTV lines, along 
> with
> [17179769.268000] ivtv:  any module options, when mailing the
> ivtv-users mailinglist.
> [17179769.268000] ivtv0: Autodetected Hauppauge WinTV PVR-350 card
> (cx23415 based)
> [17179769.272000] ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKB]
> -> GSI 11 (level, low) -> IRQ 11
> [17179769.348000] tveeprom 1-0050: Hauppauge model 48139, rev K2B7,
> serial# 8660755
> [17179769.348000] tveeprom 1-0050: tuner model is Philips FM1216ME MK5
> (idx 117, type 4)
> [17179769.348000] tveeprom 1-0050: TV standards PAL(B/G) PAL(I)
> SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
> [17179769.348000] tveeprom 1-0050: audio processor is MSP4418 (idx 25)
> [17179769.348000] tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
> [17179769.348000] tveeprom 1-0050: has radio, has IR remote
> [17179769.436000] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> [17179769.636000] tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
> [17179769.728000] saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> [17179769.940000] saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
> [17179769.996000] msp3400 1-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver 
> #0)
> [17179769.996000] msp3400 1-0040: MSP4418G-B3 supports nicam and
> radio, mode is autodetect and autoselect
> [17179770.704000] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> [17179770.796000] ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> [17179771.028000] ivtv0 warning: Encoder mailbox not found
> [17179771.028000] ivtv0 warning: invalid api mailbox
> [17179771.028000] ivtv0 warning: Encoder firmware dead!
> [17179771.036000] ivtv0: Error initializing firmware
> [17179771.048000] ivtv0: Error -19 on initialization
> [17179771.048000] ivtv:  ====================  END INIT IVTV
> ====================
>
>   
>> On top of Roger's suggestion, does it work in windows?
>>     
>
> I've just installed the board on Windows, but all I get is a black
> area where the picture was supposed to be.
>
>   
In case you haven't already found this thread, here it is 
(http://www.gossamer-threads.com/lists/ivtv/devel/22826). It's old, but 
it might just be weird enough to be your problem. In the end, this 
person tried a different PCI slot and it worked.

Dustin

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to