Darren Hart wrote:

we are many having problems with the tuner. We are not yet sure where
the problem comes from. Check the mythtv user, ivtv-user and
ivtv-devel lists archives in the past days. They are already threads
on that matter.

There are currently 2 main ideas: DMA problems and power supply.
I currently disabled DMA on my hard disk, and I have 5 hours uptime,
which is one of the best I had in the past week. But I can't see Live
TV correctly because of that... :(

Just to add to the mix, I run the frontend and backend on the same system with a pvr-250 and a pvr-350, using ivtv-fb for X. All my drives, including root, recordings, and live-tv cache, are all nfs mounted. With Myth 0.16 and ivtv-0.1.9a I had very few lockups, with Myth 0.17 and ivtv-0.2.0-rc3g I get a lockup at least once a show. I can ssh in and kill the frontend and restart it. The UI is responsive but all the text and the selection area are filled with a portion of the last frame played before the crash. If I try and play a recording, the machine locks hard.

Checking lspci show that the pvr-250 and the nvidia card (used only for viewing boot messages and the tty) share IRQ 11, and the pvr-350 is on IRQ 9.

Since I am not sharing IRQ's with the 350 and I don't have any local disks spun up, I thought this might be an interesting data point. The box is a PII 400 with 320 MB of RAM.

thoughts? comments?

Just did some testing, when playback locks up, the following starts repeating in syslog:


Mar 11 19:06:53 leeloo kernel: ivtv: 1000 ms time out waiting for firmware
Mar 11 19:06:53 leeloo kernel: ivtv: Failed api call 0x00000015 with result 0xfffffff0
Mar 11 19:06:53 leeloo kernel: ivtv: DEC: couldnt read clock




--Darren _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to