>>>>> On Wed, 11 Jun 2008 10:42:25 -0400 (EDT), Junk Mail <[EMAIL PROTECTED]> >>>>> said:
JM> Simply doing this: JM> cat /dev/video0 > test.mpg JM> produces a 0 byte file and causes the log messages, so mythtv is not JM> likely to be responsible. You'll almost certainly need to reboot to get to a stable state. Once it gets into the DMA TIMEOUT mode you're stuck and I've found no combination of unloading/reloading etc that fixes the issue until a fresh reboot. The bad news is that for my system, I've never fixed it. If you search back through the older list logs you'll find a script that I run all the time to capture debugging output from syslog as a "hack" which tends to delay the inevitable crash for a few days. I've been sort of convinced I need a better motherboard, but I'm not positive. Any chance your motherboard is based on the VIA chipset? -- "In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
