Bug 17133 - Player unresponsive and screen blank instead of showing prompt to upgrade firmware
: Player unresponsive and screen blank instead of showing prompt to upgrade fir...
Status: NEW
Product: MySqueezebox.com
Classification: Unclassified
Component: Player UI
: Prod
: PC Other
: P1 critical (vote)
: Hotfix
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-06 13:19 UTC by Ryan
Modified: 2012-03-05 06:39 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan 2011-04-06 13:19:22 UTC
I have the latest SBS server 7.5.3 r31792 
this version of SBS includes FW version 132 for Classic

If I connect the player to MSB.com It get a fw update to version 133

It seems the versions are out of sync

also when I connect the device to MSB.com at first it just goes blank. until I make a change from the MSB.com web interface when I can then perform the FW update.

When I switch back to SBS of course there is another update back to ver 132
Comment 1 Mickey Gee 2011-04-08 15:01:10 UTC
Logitech employee brought one over to Ryan and me to review. I thought it was bricked, and so did Ryan. Nothing happens with any remote keys.

We were able to get it to update firmware to 133, and it worked normally again.

Ryan saw this with another unit and documents this in above.
Comment 2 Ryan 2011-04-11 16:53:43 UTC
I have verified this connected to SBS 7.6 and testMSB.com. When first connected  the player goes blank.
 
I connected to SBS 7.5.3 got to FW 132 then connected to Test MSB.com unit went Blank until some action from my PC at TestMSB.com

version 136 down grade to 132 SBS 7.5.3 ok
version 132 upgrade to 136 testMSB.com screen goes blank until some TestMSB.com action then requests FW update often get a message "update_begin bad state"

version 132 upgrade to 133 via MSB.com is the same
Comment 3 Michael Herger 2012-03-05 06:39:45 UTC
Are you able to reproduce this issue? There's a similar issue I've seen myself, but it only happened to me (and most commenters) once: 
https://bugs-archive.lyrion.org/show_bug.cgi?id=17497