PDA

View Full Version : Can't update 6.5b1 SVN6798 to firmware 36



Philip Meyer
2006-04-02, 16:57
My SB3 connects to slimserver and prompts me to press and hold the brightness key to update the firmware. However, as soon as I do this, slimserver crashes with the following:

2006-04-03 00:51:47.0474 Client not found for slimproto msg op: IR
Can't call method "prefGet" on an undefined value at P:/Music/SlimServer/trunk/server/Slim/Player/Client.pm line 850.
2006-04-03 00:51:47.2500 closing dbh with active statement handles

Phil

Philip Meyer
2006-04-04, 12:23
>My SB3 connects to slimserver and prompts me to press and hold the brightness key to update the firmware. However, as soon as I do this, slimserver crashes with the following:
>
>2006-04-03 00:51:47.0474 Client not found for slimproto msg op: IR
>Can't call method "prefGet" on an undefined value at P:/Music/SlimServer/trunk/server/Slim/Player/Client.pm line 850.
>2006-04-03 00:51:47.2500 closing dbh with active statement handles
>
I have one SB using firmware 36, and one on firmware 28. I have tried to upgrade 28->36, but get the above problem. I have tried to downgrade 36->28 by modifying the version file, but get the same problem.

I have tried moving my slimserver.pref file sideways so that slimserver creates a fresh one, in case there was some corruption in the preferences. The effect is strange though, in that the SB doesn't request to update the firmware. I found that if I press and hold the brightness key anyway, the SB locks up (no message, just becomes unresponsive). I have to hard-power down the device to recover. I have tried doing a factory reset (press and hold Add whilst powering up the unit) - the unit does then prompt to do an update, but the same crash occurrs.

I appear to be stuck. Any clues as to what is going on?

Phil

kdf
2006-04-04, 12:28
Quoting Phil Meyer <slim (AT) hergest (DOT) demon.co.uk>:

>> My SB3 connects to slimserver and prompts me to press and hold the
>> brightness key to update the firmware. However, as soon as I do
>> this, slimserver crashes with the following:
>>
>> 2006-04-03 00:51:47.0474 Client not found for slimproto msg op: IR
>> Can't call method "prefGet" on an undefined value at
>> P:/Music/SlimServer/trunk/server/Slim/Player/Client.pm line 850.
>> 2006-04-03 00:51:47.2500 closing dbh with active statement handles
>>
> I have one SB using firmware 36, and one on firmware 28. I have
> tried to upgrade 28->36, but get the above problem. I have tried to
> downgrade 36->28 by modifying the version file, but get the same
> problem.

disable trackstat or the execute plugin. Both of these are reacting
to "stop" a callback
and check a client that has just gone away for firmware update.
-k

Philip Meyer
2006-04-04, 14:44
>disable trackstat or the execute plugin. Both of these are reacting
>to "stop" a callback
>and check a client that has just gone away for firmware update.
>
Thankyou.

I disabled the execute plugin first, and still got the problem. Then disabled the trackstat plugin too, at which point I could do updates to firmware again.

Is this a problem with the plugins, or a problem with the slimserver code? I'm wondering who I should inform.

I've discovered that firmware 36 is still completely unuseable on my SB3, so I have now reverted back to 28, which works better.

Phil

kdf
2006-04-04, 14:55
On 4-Apr-06, at 2:44 PM, Phil Meyer wrote:

>
> I disabled the execute plugin first, and still got the problem. Then
> disabled the trackstat plugin too, at which point I could do updates
> to firmware again.
>
yup, both have to be off since both subscribe to the 'stop' command.

> Is this a problem with the plugins, or a problem with the slimserver
> code? I'm wondering who I should inform.
I updated Execute so that it shouldn't cause the problem, since I was
already in the middle of another fix. the callback routines should do a
safety check to make sure a client is present. I got sidetracked
before I got a chance to pass this on to erland.

> I've discovered that firmware 36 is still completely unuseable on my
> SB3, so I have now reverted back to 28, which works better.

odd. I've had no trouble with any of them myself.

-k