>
> Hi,
>
> The weird thing is the following set of messages:
>
> kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> kernel: ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> firmware_helper[13004]: Loading of /lib/firmware/v4l-cx2341x-enc.fw for
> ivtv driver failed: No such file or directory
> firmware_helper[13007]: Loading of /lib/firmware/v4l-cx2341x-dec.fw for
> ivtv driver failed: No such file or directory
> kernel: ivtv0: Encoder revision: 0x02050032
> kernel: ivtv0: Decoder revision: 0x02020023
>
> First is says it loaded the firmware, then it says the firmware_helper
> could not find the file and then it prints the versions of firmware that's
> loaded.
>
> Is there perhaps anything special that ivtv needs to do an a udev based
> system (or on a system with udev implemented in the way Fedora5 does
> it???)
>
> Looks like udev is trying to do something ivtv is already doing by itself,
> or am I misinterpreting stuff here?
>
> Regards,
> Stanley.
>
>
Well, it took some time, but I think I nailed it...
The problem was indeed the firmware_helper. FC5 has a udev rule in
/etc/udev/rules.d/05-udev-early.rules to define an action for loading
firmware:
ACTION=="add", SUBSYSTEM=="firmware", ENV{FIRMWARE}=="*",
RUN="/sbin/firmware_helper", OPTIONS="last_rule"
I commented this out, now all is working fine again. Tried multiple
reboots, everyone of them went fine, no more hangs in udev while booting
and ivtv (both cards) works great every time.
I also added a small set of rules to set the permissions so I can run
MythTV as user mythtv:
/etc/udev/rules.d/99-ivtv.rules:
KERNEL=="fb[0-9]*", GROUP="video", MODE="660"
KERNEL=="*", SUBSYSTEM=="sound", GROUP="audio", MODE="660",
OPTIONS+="last_rule"
KERNEL=="*", SUBSYSTEM=="video4linux", GROUP="video", MODE="660",
OPTIONS+="last_rule"
Perhaps there is a better way to do this, but it works for me...
>
>> Interestingly, my system is also dual-core, although AMD based: Asus
>> M2N32-SLI, nforce-590/Athlon X2 4600+. Following in your footsteps, I
>> moved the PVR-150 over to my old system (single-core nforce2-based
>> motherboard) and the card is now recognized and can capture from the
>> svideo port, although I still get the firmware "no such file or
>> directory" error during initialization. I still have a problem tuning
>> channels, but I'll post that separately after a bit more
>> experimentation.
>>
>> Daniel
>>
>>
>> kernel: ivtv: ==================== START INIT IVTV ====================
>> kernel: ivtv: version 0.7.0 (tagged release) loading
>> kernel: ivtv: Linux version: 2.6.17.6-c1 mod_unload 686 REGPARM
>> 4KSTACKS gcc-4.1
>> kernel: ivtv: In case of problems please include the debug info between
>> kernel: ivtv: the START INIT IVTV and END INIT IVTV lines, along with
>> kernel: ivtv: any module options, when mailing the ivtv-users
>> mailinglist.
>> kernel: ivtv0: Autodetected Hauppauge WinTV PVR-250 card (cx23415 based)
>> kernel: ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC2] -> GSI 17
>> (level, high) -> IRQ 21
>> kernel: tuner 5-0061: chip found @ 0xc2 (ivtv i2c driver #0)
>> kernel: saa7115 5-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
>> kernel: msp3400 5-0040: MSP3435G-B6 found @ 0x80 (ivtv i2c driver #0)
>> kernel: msp3400 5-0040: MSP3435G-B6 supports radio, mode is autodetect
>> and autoselect
>> kernel: tveeprom 5-0050: Hauppauge model 48011, rev F310, serial#
>> 5193118
>> kernel: tveeprom 5-0050: tuner model is Philips FI1236 MK2 (idx 10, type
>> 2)
>> kernel: tveeprom 5-0050: TV standards NTSC(M) (eeprom 0x08)
>> kernel: tveeprom 5-0050: audio processor is MSP3435 (idx 10)
>> kernel: tveeprom 5-0050: has radio
>> kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
>> kernel: ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
>> firmware_helper[13004]: Loading of /lib/firmware/v4l-cx2341x-enc.fw for
>> ivtv driver failed: No such file or directory
>> firmware_helper[13007]: Loading of /lib/firmware/v4l-cx2341x-dec.fw for
>> ivtv driver failed: No such file or directory
>> kernel: ivtv0: Encoder revision: 0x02050032
>> kernel: ivtv0: Decoder revision: 0x02020023
>> kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers
>> (4096KB total)
>> kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers
>> (2048KB total)
>> kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers
>> (2048KB total)
>> kernel: ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers
>> (2048KB total)
>> kernel: ivtv0: Create encoder radio stream
>> kernel: tuner 5-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and
>> compatibles))
>> kernel: ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
>> kernel: ivtv: ==================== END INIT IVTV ====================
>>
>>
>>
>>
>> On Thu, 2006-09-07 at 13:49 +0200, Stanley Merkx wrote:
>>> Hi,
>>>
>>> I have the same problem with 2 PVR-350s.
>>>
>>> I recently built a new server with an Intel D805 (dual core) and an MSI
>>> mainboard with an Intel845 chipset. Installed it with FC5,
>>> 2.6.17-1.2174smp and the ivtv bundles from atrpms.
>>>
>>> The PVRs just don't want to play nice in this system; they've been
>>> working
>>> fine for years in my old debian based system.
>>>
>>> To me it looks like a timing issue, possibly with the interaction
>>> between
>>> udev and ivtv: 4 out of 5 times the system just hangs when starting
>>> udev.
>>> The one time it does start, I get exactly the same errors as shown in
>>> the
>>> thread: firmware file not found. The weird thing is: often the first
>>> PVR
>>> loads fine, but the second one gives the error message (on a file that
>>> was
>>> succesfully used just a split second earlier).
>>>
>>> the 1 in 20 reboots that do manage to initialise the PVRs, they work
>>> fine,
>>> until I get a DMA error which requires a reboot to fix, so while story
>>> starts again...
>>>
>>> Yesterday I took an old Pentium-II box and installed it with exactly
>>> the
>>> same stuff as my new box and placed both PVRs in it.
>>>
>>> And guess what: it all works perfectly... Haven't had time to do any
>>> real
>>> testing, but I have done several reboots and each time the PVRs
>>> initialised without a glitch...
>>>
>>> Suggestions anyone???
>>>
>>> Regards,
>>> Stanley.
>>>
>>>
>>>
>>> > I've also been having problems with the 2.6.17-1.2174 kernel (though
>>> I'm
>>> > using the standard version, not the smp version). I've tried it with
>>> both
>>> > the latest version from the 0.7 branch in subversion and with the
>>> > ivtv-kmdl
>>> > kernel module from atrpms, neither work.
>>> >
>>> > Regards
>>> > David
>>> >
>>
>> <...snip...>
>>
>> --
>> Daniel Parish <[EMAIL PROTECTED]>
>>
>>
>> _______________________________________________
>> ivtv-users mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
