[mythtvnz] HVR 2200 replacement?

[Curtis Walker]

On 6 January 2015 at 00:35, Fraser McGlinn <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
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives 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.