Hello,
It seems, there I have some timing problems with ivtv driver. My box: Abit 
AV-8 Third-Eye/Athlon64 3200+/1 GB RAM/Matrox-G450/Hauppauge PVR-350, Gentoo 
linux, 64-bit mode.
And what goes on:
        kernel 2.6.16-gentoo-r9/ ivtv-0.6.2: initialization of PVR-350 mostly 
ok (I 
will explain later). Success in ~90% cases.
        kernel 2.6.16-gentoo-r13/ ivtv-0.6.2: initialization of PVR-350 mostly 
ok.
        kernel 2.6.16-gentoo-r13-SMP/ ivtv-0.6.2 (yeah, I think about upgrade 
to 
Athlon64X2): initialization of PVR-350 mostly ok. As previous, ~90% success.
        kernel 2.6.16-gentoo-r13-SMP/ivtv-0.6.3: initialization of PVR-350 ok 
in ~50% 
cases
        kernel 2.6.17-gentoo-r3-SMP/ivtv-0.7.0: initialization of OVR-350 
mostly 
fails (failure probability is cca 10:1).
        The most illustrative is the situation for 2.6.16-gentoo-r13-SMP kernel 
and 
ivtv-0.6.3 (see the included log) - testing 'loop':
-----
modprobe ivtv
rmmod tda9887 ivtv saa7127 tuner saa7115 msp3400 v4l2_common i2c_algo_bit 
v4l1_compat tveeprom videodev
----
PVR-350 is (randomly?) properly initialized and (randomly?) the initialization 
fails, without any other hw or sw change.
The situation is even worse with kernel 2.6.17 and ivtv-0.7.0; if the 
initialization fails, then system is hard-locked afterwards, it produces the 
at the end the message:

ivtv0: loaded v4l-cx2341-enc.fw firmware (262144 bytes)
ivtv0: loaded v4l-cx2341-dec.fw firmware (262144 bytes)
ivtv0 warning: 1000 ms time out waiting for firmware
ivtv0 warning: failed api call 0x00000080 with result 0xfffffff0
ivtv0 warning: Encoder firmware dead!
ivtv0 warning: 1000 ms time out waiting for firmware
ivtv0 warning: failed api call 0x00000000 with result 0xfffffff0
ivtv0 warning: Decoder firmware dead!
ivtv0: Error initializing firmware!

and the whole system is frozen, no keyboard, no mouse, no network, even 
watchdog and hangcheck-timer are dead, only reset-button can help.
But, if it is happening the PVR-350 is initialized properly, it works without 
any troubles for all combinations of kernel/driver, mentioned above.
So, it seems, I have some timing problem, which is going worse and worse with 
every new version of ivtv-driver. I do not think I have some hw problem 
(among the ivtv driver all other things work properly, looks rather as like 
as my PVR-350 card is too lazy at the start.
What should I try?
Thanks for every help,
-- 
Jan Taimr
---------------------------------------
The worst computer virus is an end-user
---------------------------------------

Attachment: ivtv-0.6.3.bz2
Description: BZip2 compressed data

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

Reply via email to