Bug 14889 – Firware-upgrade to 7.4.1 7915 doesn't work due to checksum error

Bug 14889 - Firware-upgrade to 7.4.1 7915 doesn't work due to checksum error

Summary:

Firware-upgrade to 7.4.1 7915 doesn't work due to checksum error

Status:	RESOLVED INVALID

Product:	SqueezePlay
Classification:	Unclassified
Component:	Setup
Version:	7.5.x
Platform:	PC Windows Vista

Importance:	P1 normal (vote)
Target Milestone:	7.5.0
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-10-21 23:39 UTC by Stefan Hansel
Modified:	2009-11-27 02:33 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
/var/log/messages of radio (36.98 KB, text/plain) 2009-10-21 23:39 UTC, Stefan Hansel	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Hansel 2009-10-21 23:39:56 UTC

Created attachment 6188 [details]
/var/log/messages of radio

The radio kindly asks to upgrade the firmware.
I press yes, it says downloading, then says installing then it very shortly
says that the update failed.

Attached is /var/log/messages there is some checksum error in there.

Comment 1 Stefan Hansel 2009-10-21 23:41:16 UTC

I'm using the official debian package from 
http://downloads.slimdevices.com/SqueezeboxServer_v7.4.1/squeezeboxserver_7.4.1_all.deb

by the way.

Comment 2 James Richardson 2009-10-22 17:58:08 UTC

Stefan, is this still failing for you?

Comment 3 Stefan Hansel 2009-10-22 22:31:07 UTC

Yesterday at evening at 23:00 CET I was tired of beeing asked to upgrade again and again (and was afraid of alarm malfunction the next day).

When connected to a local server it still failed then.
I then went to Settings->Advanced->Firmware and could also choose to download from mysqueezebox.com.

This firmware download worked.

Should I download the debian-package again and test again ?

Comment 4 James Richardson 2009-10-26 14:33:47 UTC

This may have been a memory leak error in the previous build of the firmware.

Assigning to QA to monitor for the next firmware release