[mythtvnz] HVR 2200 replacement?

Mon Jan 5 22:30:49 GMT 2015

So from what I understand, the issue that I’m having is caused by having both tuners up at once. Most likely firmware related by my googles, but haven’t had a chance to confirm or deny this at this stage. On the list to do hopefully this week.

Given the age of mine I doubt it is hardware, and since noticing the issue i’ve moved it to a test box (new mobo, new PSU, new everything - but same distro and kernel) to try and resolve the issue as the TV tuner was sitting in a box that has a few KVM’s so rebooting to resolve didn’t always fly. When i’ve seen these errors I was streaming direct from the tuners with DVBlast and then trying to get Myth to take these UDP streams as input - Didn’t quite get it working on the Myth side but the multicast side was perfectly working.

My first question to Robin - Has this started happening recently because you’ve been recording/streaming from both tuners at once? Does a reboot resolve the errors?

Cheers,

Fraser

> On 6/01/2015, at 11:01 am, Curtis Walker <sultanoswing at gmail.com> wrote:
> 
> On 6 January 2015 at 00:35, Fraser McGlinn <fraser at frizianz.com <mailto:fraser at frizianz.com>> wrote:
>> 
>> Hi Guys,
>> 
>> May or may not be useful to say that i’ve been having issues with my 6 month old HVR2200 on Ubuntu 14.04 (doubtful that mine is hardware) - Kernel 3.13.0-39. Similar errors, but not quite the same. So take this with a ain of salt as it might not be related.
>> 
>> [68399.023383] saa7164_api_i2c_write() error, ret(1) = 0xc
>> [68399.178019] saa7164_cmd_send() No free sequences
>> [68399.181181] saa7164_api_i2c_read() error, ret(1) = 0xc
>> [68399.187800] saa7164_cmd_send() No free sequences
>> [68399.191026] saa7164_api_i2c_read() error, ret(1) = 0xc
>> [68399.197696] saa7164_cmd_send() No free sequences
>> [68399.200161] saa7164_api_i2c_write() error, ret(1) = 0xc
>> [68399.202626] saa7164_cmd_send() No free sequences
>> [68399.205071] saa7164_api_i2c_write() error, ret(1) = 0xc
>> [68399.217513] saa7164_cmd_send() No free sequences
>> [68399.219887] saa7164_api_i2c_read() error, ret(1) = 0xc
>> [68399.224600] saa7164_cmd_send() No free sequences
>> [68399.226958] saa7164_api_i2c_write() error, ret(1) = 0xc
>> [68399.229317] saa7164_cmd_send() No free sequences
>> [68399.231629] saa7164_api_i2c_write() error, ret(1) = 0xc
>> [68399.233992] saa7164_cmd_send() No free sequences
>> [68399.236338] saa7164_api_i2c_write() error, ret(1) = 0xc
>> 
>> Cheers,
>> 
>> Fraser
>> 
>> On 5/01/2015, at 11:11 pm, Robin Gilks <g8ecj at gilks.org> wrote:
>> 
>> 
>> On 5 January 2015 at 21:54, Robin Gilks <g8ecj at gilks.org> wrote:
>> 
>> Greetings all
>> 
>> My HVR2200 has started to go flakey. The log fills up with
>> Jan  5 21:39:41 jupiter kernel: [ 8338.648333] saa7164_cmd_send() No
>> free
>> sequences
>> Jan  5 21:39:41 jupiter kernel: [ 8338.648343] saa7164_api_i2c_read()
>> error, ret(1) = 0xc
>> Jan  5 21:39:41 jupiter kernel: [ 8338.648349] tda10048_readreg: readreg
>> error (ret == -5)
>> Jan  5 21:39:43 jupiter kernel: [ 8340.648332] saa7164_cmd_send() No
>> free
>> sequences
>> Jan  5 21:39:43 jupiter kernel: [ 8340.648343] saa7164_api_i2c_read()
>> error, ret(1) = 0xc
>> Jan  5 21:39:43 jupiter kernel: [ 8340.648348] tda10048_readreg: readreg
>> error (ret == -5)
>> every 2 seconds all the time the backend is running.
>> 
>> So I'm looking at ways I can continue getting Sky into my system, either
>> an analog input as the HVR2200 provides, an HD PVR (can I use the gaming
>> edition?) or a DVB-S2 capture card with an extra card to take my fully
>> paid up sky subscription card.
>> 
>> If I use anything other than a replacement for the 2200 then I'll also
>> need a DVB-T card as well, but it looks the the 2200 is a bit like
>> rocking
>> horse manure :(
>> 
>> Thoughts?
>> 
>> 
>> 
>> You sure it wasn't some recent kernel/firmware update problem? Might be
>> worth popping an older, known good configuration in to test it, or a
>> slightly older mythbuntu install onto a spare drive. Of course it *could*
>> be flaky hardware, but flaky software is far more common!
>> 
>> 
>> Good thought but I haven't updated the kernel on this Gentoo system for
>> over 2 years !!
>> 
>> It failed originally just over 2 weeks ago. I turned the box off, removed
>> the card, put it back and fired up again and it has run until mid
>> afternoon today. I've tried a power cycle and it did resurrect it for
>> about 10 minutes but I think it may now be terminal.
>> 
>> I'll take it out and check for bulging caps in the morning and see what
>> bits I can get at SI Components (I'm heading that way tomorrow anyway!!).
>> 
>> 
>> --
>> Robin Gilks
>> 
>> 
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz at lists.linuxnut.co.nz
>> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> 
>> 
>> 
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz at lists.linuxnut.co.nz <mailto:mythtvnz at lists.linuxnut.co.nz>
>> http://lists.ourshack.com/mailman/listinfo/mythtvnz <http://lists.ourshack.com/mailman/listinfo/mythtvnz>
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/ <http://www.gossamer-threads.com/lists/mythtv/mythtvnz/>
>> 
> 
> ...and I presume you have also tried a different PCI(e) slot? Could be
> motherboard, power supply - anything else really - as well as the card
> itself. Of course if you've got access to a known good card, that'd
> help diagnose/confirm the problem is with the card itself.
> 
> _______________________________________________
> mythtvnz mailing list
> mythtvnz at lists.linuxnut.co.nz <mailto:mythtvnz at lists.linuxnut.co.nz>
> http://lists.ourshack.com/mailman/listinfo/mythtvnz <http://lists.ourshack.com/mailman/listinfo/mythtvnz>
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/ <http://www.gossamer-threads.com/lists/mythtv/mythtvnz/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ourshack.com/pipermail/mythtvnz/attachments/20150106/4fe6e0d7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.ourshack.com/pipermail/mythtvnz/attachments/20150106/4fe6e0d7/attachment-0001.pgp>