PDA

View Full Version : Updating



coffeetime
2008-12-07, 14:30
Hello!

If somebody can help or have an idea? Each time when I switch music source, it's saying "Updating Squeezebox firmware ?? Excuse me, but WTF?
My firmware:
Squeezebox Controller 7.2 r3191
Squeezebox Receiver 55

SqueezeCenter Version: 7.2.1 - 23630 @ Mon Oct 20 19:52:55 PDT 2008 - Red Hat - EN - utf8
Server IP address: 192.168.1.100
Perl Version: 5.10.0 i386-linux-thread-multi
MySQL Version: 5.0.45

Platform Architecture: i686-linux

Hostname: localhost

Server Port Number: 9000

Total Players Recognized: 1

MeSue
2008-12-07, 15:09
There are several mentions of this in the forum. From what I have gathered, tt is a result of the recent SqueezeNetwork upgrade. It will stop when 7.3 comes out, or you can install a 7.3 beta now. Or avoid switching music sources until they get the firmware aligned.

mvalera
2008-12-08, 10:42
Why are you switching music source to SqueezeNetwork?

Unless you are turning off your computer, you should just access all your SqueezeNetwork services through SqueezeCenter.

Mike

coffeetime
2008-12-08, 12:42
Well, when I switch music source on contoller to my localhost or back to squeezenetwork or vice versa, this happens each and every time. Am I missing something?

coffeetime
2008-12-08, 15:42
I don't want to open a new thread, so I'll post here. I'm experiencing a situation, which didn't happen before.

SB has a solid white light (music is playing from Shoutcast and I can hear it). On Squeeze Network account I see controller and reciver connected, I also see them both connected in my router. Now, the controller was in a cradle for about 3 hours and it was not shut down. I grabbed it and now it's connecting to a SB for more than 15min? What's wrong with this gadget?

EDIT: reseting controller helped, but this is....

RichNY
2008-12-09, 12:25
Why are you switching music source to SqueezeNetwork?

Unless you are turning off your computer, you should just access all your SqueezeNetwork services through SqueezeCenter.

Mike

So when I try to access Pandora or any service that requires Squeezenetwork credentials I cant get them to work if I'm not logged on through Squeezenetwork.
So this is why I switch back and forth from Squeezenetwork to Squeezeserver a couple times a day.

propup
2008-12-11, 10:36
"Why are you switching music source to SqueezeNetwork? Unless you are turning off your computer, you should just access all your SqueezeNetwork services through SqueezeCenter."

I don't get this... please school me. I have always had to "switch" in and out of my SqueezeCenter host to SqueezeNetwork just as the OP indicates...
This has been true for as long as I can remember.

Current configuration:Duet remote controller and an (2) SB3 classics. Running SqueezeCenter Version: 7.3 - 24179 @ Tue Dec 2 11:03:01 PST 2008 on a Windows 2003 server. (this is the first time that I am using a nightly version as opposed to the official release)

When I woke up the controller just now I was still connected to Squeeze Network from yesterday. Before doing anything, I checked firmware and there was an update available. I ran the update and the controller restarted.

I then "switched" over to my SqueezeCenter server. I got the following message: Updated software is available for this remote. It may take a few minutes to update to version 7.3r3476. So I applied THAT update and the controller restarted.

Now I can access my local library and basic internet streams as expected but there is no option for SqueezeNetwork. Never has been either.

Worse, I now had no SETTINGS option! The screen was blank... so I could not even change music sources if I wanted to! I was able to go to Choose Player and I selected my other SB3 classic. FWIW, the graphic on the remote shows the 2nd SB3 Classic as a Transporter! At least once I selected one or the other players... I was able to "see" settings again.

Then, because I CANNOT see / find SqueezeNetwork, I went to settings / Music Source / and selected SqueezeNetwork. When I checked Settings / Advanced / Software Updaste I get the message: Updated software is available for this remote. It may take a few minutes to update to version 7.3r3191 which I guess is older than my nightly from December 2nd?

If 7.3 were officially released then I guess I could test this with a bit less confusion (any updated release info?)

So Updating to 7.3x nightly does not seem like a good idea, but neither does the problems I had with 7.2

coffeetime
2008-12-11, 11:54
Well, again some problems. Controller was in the cradle the whole day and I just picked it up and it crashed.
It lost wifi connection, restarted itself. After that all my settings were gone. Alerted me about an update, I confirmed it. Update was not successful . It restared itself again.
On SN I see that controller is not connected, while my router shows me it is? Music from SC is playing? I can't connect to SN or my localhost.
I'm still running FW 7.2 r3191 and by the way, for the past 2 days everything was working great.

coffeetime
2008-12-26, 12:39
So, with no reason I have again the same problems like with SC 7.2. When I switch to localhost, it needs 20s and again it's saying on the controller-updating firmware? I'm running the latest, stable one, 7.3.
Does anyone have the same problem?

Mark Miksis
2008-12-26, 12:56
I'm not really sure which firmware version SN requires right now, but FYI the latest stable SC is 7.3.1, not 7.3.

funkstar
2008-12-26, 12:56
Have you tried 7.3.1?

It was release quickly after 7.3 as there were a couple of nasty bugs that were only discovered on releasing 7.3.0

Mnyb
2008-12-26, 13:18
Hmm afaik

7.3 and 7.3.1 should run with SBC firmware 3476

http://update.slimdevices.com/update/firmware/7.3.1/

7.3.2 has version 3587

http://update.slimdevices.com/update/firmware/7.3.2/

So having 3196 when your SC is 7.3 is weird ?

Has the FW gone wrong somewhere ? theres a couple of methods to manually update the FW of your SBC, search the forum.
Or wiki here: http://wiki.slimdevices.com/index.php/SqueezeOS_Upgrades
I use the SD card method it's the simplest to use.

coffeetime
2008-12-26, 13:50
Thank you for info. guys. Well, I'm running 7.3.1

coffeetime
2008-12-26, 15:05
It looks like I have the same problem which I had with 7.2. I've tried copying again the fw update, I've tried reseting both reciver and controller, but no success.
My specs:
-Controller Player Firmware Version: 7.3 r3476
-Reciver Player Firmware Version: 56
-SC 7.3.1

Any ideas?

I must say that after 7.3.1 everything was working like a charm. Until today.

OppfinnarJocke
2008-12-26, 18:34
Why are you switching music source to SqueezeNetwork?

Unless you are turning off your computer, you should just access all your SqueezeNetwork services through SqueezeCenter.

Mike

Well, to quote the OP, "WTF"... Do you Logitechies really expect people *not* to switch music sources? I do it all the time. Whan I get home, I turn to SqueezeNetwork for internet radio. At some time later I may turn on my comp and switch to that music source...

Did you really develop teh SqueexeBox from a use-case where the user stayed with one and only one source? If so I think you erred, not us users...

dvbnick
2008-12-27, 03:10
Do you Logitechies really expect people *not* to switch music sources? I do it all the time.

Same thing here. Don't want to keep my Server running while listening to Internet radio. So I'm switching between SC and SN almost every day. This caues annoyance, sorry. WAF going down to zero...
dvbnick

coffeetime
2008-12-27, 10:21
Well, to quote the OP, "WTF"... Do you Logitechies really expect people *not* to switch music sources? I do it all the time. Whan I get home, I turn to SqueezeNetwork for internet radio. At some time later I may turn on my comp and switch to that music source...

Did you really develop teh SqueexeBox from a use-case where the user stayed with one and only one source? If so I think you erred, not us users...


I agree. This is exactly what I meant.

But if I go back to my problem; I just saw that SC reports:
Squeezebox
Player Model: receiver
Firmware: 55

while when I look in SN, it reports:
Player Firmware Version: 56

So, something went wrong. Why and when, I have no idea. But I think this is my problem? So, switching between sources triggers "updating fw" each and every time, but it's a little bit funny, since it seems that this update never actually update the unit.