Bug 3368 - Holding brightness for firmware upgrade causes "update_begin: bad state"
: Holding brightness for firmware upgrade causes "update_begin: bad state"
Status: CLOSED FIXED
Product: SB 2/3
Classification: Unclassified
Component: SB Server
: 48
: PC Windows XP
: P2 trivial with 1 vote (vote)
: Future
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-01 16:26 UTC by Chris Owens
Modified: 2008-12-18 10:04 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Owens 2006-05-01 16:26:29 UTC
If I hold down the �brightness� button as though trying to upgrade the firmware, the remote control stops working.  The player must be rebooted to fix!
Comment 1 Andy Grundman 2006-05-03 12:49:45 UTC
Did some testing, this bug can be reproduced by:

Start SlimServer (6.3 or trunk).
Connect a player with firmware 48.
Hold brightness key.
Player reports "update_begin: bad state" and reboots.
After reboot, holding brightness does a correct upgrade to the same version 48.

Also related to this is: Player will lock up if firmware 48 file is missing.  This is probably only an issue if there is a player with a newer version than 48 on a SlimServer (or SqueezeNetwork) and the person tries holding brightness.  The server will try to send the same version the user currently has, but won't find the file and cause the player to lock up.  Player must be power cycled or the server restarted to fix.
Comment 2 Richard Titmuss 2006-05-23 14:23:43 UTC
The player will lockup if the firmware image is missing, but after some discussion it was decided that the slimserver/squeezenetwork should be configured to always have a new firmware image to send to the player. To fix the player not to lock up will allow possible unsolicited firmware upgrades to be sent to the player.

Comment 3 Matt Smith 2006-08-02 14:47:14 UTC
I run server: SlimServer Version: 6.5b1 - 8764 - Windows XP - EN - cp1252 and I cannot get this problem to go away.  Rebooting the device does not fix the problem.  Right now I cannot use my Squeezebox 3!!!

If I should create a new bug instead of this, let me know.

Comment 4 KDF 2006-08-02 15:11:28 UTC
You should be contacting support@slimdevices.com for this one.