<div class="gmail_quote">On Fri, Feb 4, 2011 at 9:22 AM, Christopher Meredith <span dir="ltr"><<a href="mailto:chmeredith@gmail.com">chmeredith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I have been using firewire as an alternate tuner for clear QAM<br>
stations accessible via my cablebox, and as a channel changer for the<br>
same cable box and an HD-PVR. It worked fine until I updated Ubuntu to<br>
Maverick (10.10). Now, the firewire system seems to be really<br>
unstable. It keeps "collapsing" during recordings. When that happens,<br>
I get the following in dmesg:<br>
<br>
[280735.091273] firewire_ohci: failed to read phy reg<br>
<br>
And after that plugreport shows this:<br>
<br>
<br>
Host Adapter 0<br>
==============<br>
<br>
Node 0 GUID 0x0000000000000000<br>
------------------------------<br>
libiec61883 error: error reading oMPR<br>
libiec61883 error: error reading iMPR<br>
<br>
Node 1 GUID 0x0400000004000000<br>
------------------------------<br>
libiec61883 error: error reading oMPR<br>
libiec61883 error: error reading iMPR<br>
<br>
The only way I've been able to find to get it back is rebooting. This<br>
is pretty frustrating. Does anyone have any suggestions for how to<br>
address this?<br></blockquote></div><br>What distribution and kernel were you running before when things worked? Which kernel are you running on Ubuntu 10.10 now? Could you give the 'uname -a' output?<br>Do you know offhand which firewire controller you have? (Should be able to find this out by poking around the dmesg from bootup, or using 'lspci' <br>
Do you happen to know if you were previously running the "old" firewire stack as opposed to the new "juju" stack? Generally, the new stack seems to behave better with most firewire devices, but there are always possible exceptions. I would hope that Ubuntu 10.10 is using the new stack.<br>
Good luck with the debugging.<br><br>-Greg<br>