I have a small problem with my Rev 0.2 Air2Pc card which I can find a easy workaround when I boot my machine. I got 2 of those in my system which works extremely good. The issue is that when the system boot up, the cards gives status of all 0's even if the card is able to receive data (example with dvbsnoop). When MythTV starts, it will deactivate the cards because it assumes they don't work (status is not 1f). It takes about 2-3 minutes for the car to start giving out good status. Is there a way to fix that problem or is this a known problem with these cards? Is this the firmware that takes this long to send to the cards? I don't see any messages in the /var/log/messages or in the "dmesg" that shows that any firmware been sent to the card. Example : [root@SM_MythTV frontends]# azap WTBS using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 509000000 Hz video pid 0x0000, audio pid 0x0000 status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | Related to that, I can see that there is 6 frontends loaded in memory attached to my card, and if I'm not wrong, only the bcm3510 should be attached to it. When the frontend are tried and deemed not the good one, shouldn't they detach? mt352 7172 1 b2c2_flexcop bcm3510 11396 1 b2c2_flexcop stv0299 11784 1 b2c2_flexcop nxt2002 9348 1 b2c2_flexcop stv0297 8960 1 b2c2_flexcop mt312 8324 1 b2c2_flexcop Thanks for the answers... Steve M.
