Bugzilla – Bug 12357
Squeezebox 3 firmware downgrade from r26820 to r26660 fails
Last modified: 2009-10-23 12:32:15 UTC
After upgrading to non-working version of squeezecenter (r26820) I downgraded to a former working revision: r26660. Squeezcenter starts and is working. The SqueezeBox 3 tells me that a "newer" Firmware is available. After holding the Brightness Button on the remote, one of the following events occur: 1) The display turns black. I can't turn the SB on with the remote. Using the Web interface, I can at least turn on the SB and control it via remote but not via Web Interface, which still says i have to update the firmware. 3) Same as above with the difference, that though turning on and off through Web Interface works, SB can't be used with the remote. 3) The SB states: 'update begin: bad state', and returns to the "Update Firmware" display. I am using Ubuntu Hardy Server, the packages are retrieved from the unstable apt repository.
Ross, please try this with fw 126 -> 125, then follow up with 130 -> 125. These are the SB3 firmware versions associated with the SC builds the OP mentions.
I tried upgrading and downgrading 125 - 126 and 125 - 130, they upgrade and downgrade fine for me. Christian is SqueezeCenter running properly now? Is your SB3 still in one of these 3 funny states? Have you tried holding the brightness button once more to force another update?
No, after waiting a few days, I was able to upgrade to another revision. This went fine. As for me, I am happy. If you still want to investigate further, I'm glad to help.
Christian have you ever noticed that bad state message in the past? It usually means some kind of networking problem that occurred at that time, but since you saw more than one problem it could be something else.
I could observe this behavior only in this case. Though I didn't do any firmware downgrades apart from this one. Also I never had any networking problems. Since I was too lazy to make an upgrade to some later revision, this issue persisted for about a week. Then I could reliably reproduce it. Sorry, that I can't provide any logs, they don't reach that far back.
I understand, thanks Christian. I'll need to keep my ear to the ground for this one going forward.
I'm marking this bug as closed, as we have not experienced any more issues around this bug