PDA

View Full Version : downgrading the firmware



Laurent Perez
2004-07-14, 08:22
Hi

My squeezebox has been updated with firmware 2.9 when I tried to use
cvs builds instead of 5.1.x or 5.2.x stable versions because of 100%
cpu usage problems. Around twenty cvs builds I tried still had the cpu
problem, so I'm currently using the 5.1.5 non-cvs version which is
able to index my library (600+ albums) fine without eating the cpu,
and I'm trying not to use the shoutcast plugin (randomly crashes the
server) not too often, I suggest people with 100% cpu freeze troubles
use this 5.1.5 version, which seems ok.

Since the firmware updates, my squeezebox is now randomly rebooting
itself while playing songs, sometimes 10 minutes after starting,
sometimes hours. This has been reported on the list (see archives, i.e
downgrading the firmware should fix it) but sadly I don't manage to
downgrade the firmware back to the 5.1.5 slimserver bundled one.

My C:\Program Files\SlimServer\server\Firmware directory contains these files:

21/04/2004 17:36 385 squeezebox.version
21/04/2004 17:36 88 889 squeezebox_10.bin
21/04/2004 17:36 118 340 squeezebox_20.bin
21/04/2004 17:36 119 246 squeezebox_21.bin
21/04/2004 17:36 89 289 squeezebox_8.bin

the squeezebox.version contains :

# Squeezebox firmware revisions 1..8 all used the "old" update mechanism.
# The newest version is always required to talk to the current server
# version, so we force them all to go to v.10
#
# from to

1 10
2 10
3 10
4 10
5 10
6 10
7 10
8 10
#10 8
# version 10 is the same as version 8, except that it has additional
# support to be updated to version 20 and above.

since the squeezebox is using the 29 firmware, I tried to add the line
"29 10" which I assume means "version 2.9 is version 1.0" (?),
restarted server, restarted the squeezebox holding brightness, but it
didn't downgrade the firmware :(

what's the correct procedure to revert the firmware back to older versions ?
thanks :)

laurent

kdf
2004-07-14, 10:32
Quoting Laurent Perez <hakimm (AT) gmail (DOT) com>:

> Hi
>
> My squeezebox has been updated with firmware 2.9 when I tried to use
> cvs builds instead of 5.1.x or 5.2.x stable versions because of 100%
> cpu usage problems. Around twenty cvs builds I tried still had the cpu
> problem, so I'm currently using the 5.1.5 non-cvs version which is
> able to index my library (600+ albums) fine without eating the cpu,
> and I'm trying not to use the shoutcast plugin (randomly crashes the
> server) not too often, I suggest people with 100% cpu freeze troubles
> use this 5.1.5 version, which seems ok.
>
> Since the firmware updates, my squeezebox is now randomly rebooting
> itself while playing songs, sometimes 10 minutes after starting,
> sometimes hours. This has been reported on the list (see archives, i.e
> downgrading the firmware should fix it) but sadly I don't manage to
> downgrade the firmware back to the 5.1.5 slimserver bundled one.
>
> My C:\Program Files\SlimServer\server\Firmware directory contains these
> files:
>
> 21/04/2004 17:36 385 squeezebox.version
> 21/04/2004 17:36 88 889 squeezebox_10.bin
> 21/04/2004 17:36 118 340 squeezebox_20.bin
> 21/04/2004 17:36 119 246 squeezebox_21.bin
> 21/04/2004 17:36 89 289 squeezebox_8.bin
>
> the squeezebox.version contains :
>
> # Squeezebox firmware revisions 1..8 all used the "old" update mechanism.
> # The newest version is always required to talk to the current server
> # version, so we force them all to go to v.10
> #
> # from to
>
> 1 10
> 2 10
> 3 10
> 4 10
> 5 10
> 6 10
> 7 10
> 8 10
> #10 8
> # version 10 is the same as version 8, except that it has additional
> # support to be updated to version 20 and above.
>
> since the squeezebox is using the 29 firmware, I tried to add the line
> "29 10" which I assume means "version 2.9 is version 1.0" (?),
> restarted server, restarted the squeezebox holding brightness, but it
> didn't downgrade the firmware :(
>
> what's the correct procedure to revert the firmware back to older versions ?
> thanks :)

that's the right idea, but I think 10 10 to 20 was a one way change. Try making
the line "29 20" and see if you have better results.
-kdf

Laurent Perez
2004-07-14, 12:32
> that's the right idea, but I think 10 10 to 20 was a one way change. Try making
> the line "29 20" and see if you have better results.

yeah, the firmware was downgraded back to 2.0, I hope this will indeed
solve the device reboot problems ;)

thanks