HD200 firmware bug? - lockup while playing music

[Brent]

Has anyone experienced a complete lockup of the HD200 (requiring unplugging to reboot) while listening to MP3s? My wife first reported this to me and I've been testing tonight - now have had it happen 3 different times on two different HD200s.

UPDATE: after updating to latest firmware & SageTV beta version this problem goes away.

[PiX64]

Yes, I had this problem as well. I went the route of submitting a bug report to Sage. They were convinced that it was a file issue. I replaced that file with another "good one" and it didn't do the trick.

For me however, The newest sage server beta and beta firmware for the hd200 seem to have gotten rid of my problem.

If yo uhaven't already done so, i would suggest updating your sage backend as well as the hd200 firware.

[Brent]

Originally Posted by PiX64

If yo uhaven't already done so, i would suggest updating your sage backend as well as the hd200 firware.

I think I'm using the latest HD200 firmware, but this morning updated the server to SageTV 6.5.20.216 beta.

I'll test it out & report back. If it happens again I'll submit a but rpt.

UPDATE: Doh! I wasn't using the latest firmware (both HD200s) either. So scratch that.

[cncb]

Brent,

These are the frequent lockups I was referring to in a different thread. I haven't run into it yet with the latest firmware and server software but I will keep testing.

[Brent]

Originally Posted by cncb

Brent,

These are the frequent lockups I was referring to in a different thread. I haven't run into it yet with the latest firmware and server software but I will keep testing.

Well, I haven't listened to music on the HD200's for over a month until this week as I've been that busy. But I never had problems back then with music on the HD200s so this has to be a relatively new problem.

Like you, I'll test it heavily today and report back.

[Brent]

I did a good amount of testing on two HD200s. Zero problems after upgrading SageTV to V6.5.20 RC
and upgrading HD200 firmware to "20090702 0"

So it seems the problem was fixed by one of the two updates above.