I know this question probably belongs on the ivtv list but I figured I start here first since I am using this distro. I have searched and cannot find a satisfactory answer:

No matter how many times I reboot, I keep getting the following error from ivtv (in syslog and the console):

ivtv: 100ms time out waiting for firmware

I looked through syslog and it seems to be identifiing my card (AverMedia M179) but eventually I see the timeout. If I try and watch live tv I get a blank screen and eventually return to MythTV. If I try the cat /dev/video > test.mpg method I get a zero length file.

Anyone have any suggestions? Solutions? What information can I provide that will help?

Thanks for reading!

Jason

... running R4V2 ... BTW

I'm having the same problem. Occasionally things seem to work. odd... any updates on this? r4v2 here

Actually, my update on this is that it turns out the card (M179) is simply not compatible with my system. AverMedia's tech support was helpful up to the point where the determined that it simply would not work (not even under Windows with AverTV) so they pretty much bailed on me. Anyone want to buy a gently used AverTV M179?

Another update: I purchased a PVR-350 ... never turning back! This thing is great and I got a good deal on it (under $170 shipped) brand new from an online store.

Please share what about your system it was incompatible with. I have the following hardware, and I'm having the same problem you are:

ASUS A7N8X Deluxe
AMD Mobile 2400
1gig PC3200 RAM
GeForce TI-200
(3) M179's
Vanilla "Auto-Install" of KnoppMyth


The problem occurs with 1, 2, or 3 cards in. Doesn't matter the PCI slot, doesn't matter the IRQ assignment.

one boot out of 20 I MIGHT be able to cat /dev/video and not get a ZERO sized file, but Myth hangs when trying to watch TV, and EVENTUALLY comes back as well. Same EXACT behavior as the other poster described.

The log is full of this:


Jul 26 15:36:50 backend1 kernel: ivtv: api call 0x000000a1
Jul 26 15:36:50 backend1 kernel: ivtv: init error 16. Code -16
Jul 26 15:36:50 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:50 backend1 kernel: ivtv: api call 0x0000009f
Jul 26 15:36:50 backend1 kernel: ivtv: init error 15. Code -16
Jul 26 15:36:51 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:51 backend1 kernel: ivtv: api call 0x000000d0
Jul 26 15:36:51 backend1 kernel: ivtv: init error 17. Code -16
Jul 26 15:36:51 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:51 backend1 kernel: ivtv: api call 0x000000a1
Jul 26 15:36:51 backend1 kernel: ivtv: init error 16. Code -16
Jul 26 15:36:52 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:52 backend1 kernel: ivtv: api call 0x000000d8
Jul 26 15:36:52 backend1 kernel: ivtv: init error 18. Code -16
Jul 26 15:36:52 backend1 kernel:
Jul 26 15:36:52 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:52 backend1 kernel: ivtv: api call 0x000000d0
Jul 26 15:36:52 backend1 kernel: ivtv: init error 17. Code -16
Jul 26 15:36:53 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:53 backend1 kernel: ivtv: api call 0x000000d6
Jul 26 15:36:53 backend1 kernel: ivtv: init error 20. Code -16
Jul 26 15:36:53 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:53 backend1 kernel: ivtv: api call 0x000000d8
Jul 26 15:36:53 backend1 kernel: ivtv: init error 18. Code -16
Jul 26 15:36:53 backend1 kernel:
Jul 26 15:36:54 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:54 backend1 kernel: ivtv: api call 0x000000cd
Jul 26 15:36:54 backend1 kernel: ivtv: init error 19. Code -16
Jul 26 15:36:54 backend1 kernel:
Jul 26 15:36:55 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:55 backend1 kernel: ivtv: api call 0x000000d6
Jul 26 15:36:55 backend1 kernel: ivtv: init error 20. Code -16
Jul 26 15:36:55 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:55 backend1 kernel: ivtv: api call 0x00000081
Jul 26 15:36:55 backend1 kernel: ivtv: startcap error 1. Code -16
Jul 26 15:36:56 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:56 backend1 kernel: ivtv: api call 0x000000cd
Jul 26 15:36:56 backend1 kernel: ivtv: init error 19. Code -16
Jul 26 15:36:56 backend1 kernel:
Jul 26 15:36:57 backend1 kernel: ivtv: 100 ms time out waiting for firmware
Jul 26 15:36:57 backend1 kernel: ivtv: api call 0x00000081
Jul 26 15:36:57 backend1 kernel: ivtv: startcap error 1. Code -16
Jul 26 15:36:57 backend1 kernel: ivtv: ivtv-api.c: unknown ioctl 0x803c7601
Jul 26 15:36:57 backend1 kernel: ivtv: ivtv-api.c: unknown ioctl 0x803c7601
Jul 26 15:36:58 backend1 kernel: ivtv: Timeout waiting for data!
Jul 26 15:37:00 backend1 kernel: ivtv: Timeout waiting for data!
Jul 26 15:37:08 backend1 kernel: ivtv: 1000 ms time out waiting for firmware
Jul 26 15:37:08 backend1 kernel: ivtv: api call 0x00000082
Jul 26 15:37:08 backend1 kernel: ivtv: stopcap error 2. Code -16
Jul 26 15:37:10 backend1 kernel: ivtv: 1000 ms time out waiting for firmware
Jul 26 15:37:10 backend1 kernel: ivtv: api call 0x00000082
Jul 26 15:37:10 backend1 kernel: ivtv: stopcap error 2. Code -16
Jul 26 15:58:07 backend1 -- MARK --

Anyway, PLEASE share the other hardware details. Let me know what I need to try to change.

AND, anyone else who wants to take a shot at helping fix this, we'd all appreciate it.

Turns out that the card just would not work in my MoBo at all. Not under Linux; Not under Windows. However, you may want to check out the ivtv-dev mailing list as I have seen some recent buzz about people working on the m179.

Try a new ivtv driver. I had no success until I tried -ck. Ive included it in /usr/local/lib...

_________________
cesman

When the source is open, the possibilities are endless!

Tried every rev I could get my hands on, and in the end, returned the (3) cards for (2) PVR-250's, and I haven't looked back.

To be fair, the M179's were "discounted, returned merchandise" when I got them from Fry's. I took them back, told them they didn't work PERIOD under any OS, any chipset, etc, that I tried, so they RMA"d them to the vendor.