Bug 3360 - SB3 became SB2 after flashing FW48
: SB3 became SB2 after flashing FW48
Status: CLOSED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Hardware
: 48
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-01 12:00 UTC by Louis
Modified: 2008-12-18 11:38 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Louis 2006-05-01 12:00:57 UTC
After installing SlimServer 6.2.2 my SB3 required a new firmware load/install.

Installed firmware 48, but now in the player-info it says: Squeezebox2.

shouldn't this be Squeezebox3 and/or Squeezebox2 v3 ?

regards,

Louis
Comment 1 KDF 2006-05-01 21:31:02 UTC
This is nothing. They are exactly the same as far as the server is concerned.  Already well mentioned in forums ans shoudl alreayd be fixed.  Please report your MAC address so that we can look into this.
Comment 2 KDF 2006-05-02 16:08:44 UTC
Louis, could you please report the MAC address from your player info and/or the bottom of the device?

I have confirmed that the fix does work, and SB3 is reported as Squeezebox v3.  This works only by player MAC address, so that is relevant.

thanks.
Comment 3 Louis 2006-05-03 06:01:55 UTC
(In reply to comment #2)
> Louis, could you please report the MAC address from your player info and/or the
> bottom of the device?
> I have confirmed that the fix does work, and SB3 is reported as Squeezebox v3. 
> This works only by player MAC address, so that is relevant.
> thanks.

The MAC address is:

00:04:20:06:17:A0

Comment 4 KDF 2006-05-03 10:00:07 UTC
I see the problem.  working on a fix.
Comment 5 KDF 2006-05-03 18:50:42 UTC
fixes committed to trunk at change 7283 and 6.3.0 at change 7284.
May 4 builds of 6.5 and 6.3 should now correctly show Squeezebox v3 for any player using MAC address above 00:04:20:06:00:00

please reopen if any issues remain.
Comment 6 Chris Owens 2006-06-27 14:21:54 UTC
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.