<br><br><div class="gmail_quote">2008/5/10 Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 05/10/2008 12:05 PM, Mike Dent wrote:<br>
> 2008/5/10 Michael T. Dean:<br>
<div class="Ih2E3d">>> On 05/10/2008 08:27 AM, Mike Dent wrote:<br>
</div><div class="Ih2E3d">>>> 2008-05-10 07:30:03.348 DVBSH(0): Failed to open DVR device<br>
>>> /dev/dvb/adapter0/dvr0 : Device or resource busy<br>
>>><br>
>> It appears that something that's not Myth is using one of your capture<br>
>> cards--one of the capture cards you've promised for Myth's exclusive use<br>
>> (as Myth expects all capture cards to be for its exclusive use). Or,<br>
>> could be issues with loss of communication with the card (i.e. due to<br>
>> bad drivers). Perhaps it's just one of the known problematic capture<br>
>> cards.<br>
</div><div class="Ih2E3d">> Well they are both Hauppauge Nova-T DVB-T cards. Nothing else *should* be<br>
> using them as far as know, nothing other than Myth running on the box.<br>
><br>
<br>
</div>Nova-T 500? If so, that's the specific one I was thinking of when I<br>
said, "known problematic capture cards." It can be made to work (at<br>
least relatively reliably), but I think you have to make sure you have a<br>
specific kernel and/or driver. Probably more information in the<br>
archives. Or, you might want to start a thread whose subject contains<br>
"Nova-T 500" to get more info.<br>
<div><div></div><div class="Wj3C7c"><br>
Mike<br></div></div></blockquote></div><br><br>It's a straight Nova-T PCI card:-<br><br><a href="http://www.hauppauge.co.uk/pages/products/data_novatpci.html">http://www.hauppauge.co.uk/pages/products/data_novatpci.html</a><br>
<br>I think these are ok? Not sure if there is some firmware I should upgrade to though?<br><br>Mike<br><br>