PDA

View Full Version : SB3 failing to connect to Slim



chris.mason
2007-05-02, 03:09
Hi all,

I've been running SlimServer 6.5.2 from a while ago - think it had firmware 72 with it.
I've had some problems with stuttering on my sb3 recently - the display stutters, as does the audio.

My SB3 is connected wireless by the way.

Before you say to check my wireless connectivity, I have, there are no problems there...

Anyway, I decided to upgrade to the latest nightly three days ago, that came with a firmware upgrade - 81 I think.

Since then, my SB3 won't connect to SLimserver anymore. Tries to , but then fails, and switches itself off. I've tried this wirelessly, and wired, no joy.
I've also tried a completely vanilla 6.5.2 install with no plugins, no joy.
I've tried going back to my last working installation - doesn't work.
I've tried a fresh 6.5.1 installation, that doesn't work either.

I can only guess that the latest firmware has screwed up something in my SB3.

Does anyone know how to down-rev the firmware? I've switched on auto-update on the SB3, but it makes no difference. I've also tried various resets - press 1 while powering up, press Add while powering up.

I'm open to any suggestions....I need my Squeezebox!!

Edit : forgot to say that I've run Slim with just every debug I can think of. I can see the SB3 and Slim communicating, but it doesn't go anywhere, thus:

2007-05-02 10:52:07.5159 It's a Squeezebox
2007-05-02 10:52:07.5161 calculated <mypcname> length: 17
2007-05-02 10:52:07.5164 gotDiscoveryRequest: Sent discovery response.
2007-05-02 10:52:07.9657 gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC= 00:04:20:06:9d:99

This message is repeated many times.

I also see this:

2007-05-02 10:47:27.4666 gotDiscoveryRequest: Sent discovery response.
2007-05-02 10:47:28.1185 Slimproto client readable: 192.168.0.4:16896
2007-05-02 10:47:28.1189 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:47:28.1192 attempting to read 4 bytes
2007-05-02 10:47:38.1346 Slimproto client readable: 192.168.0.4:16897
2007-05-02 10:47:38.1349 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:47:38.1351 attempting to read 4 bytes
2007-05-02 10:47:48.1354 Slimproto client readable: 192.168.0.4:16898
2007-05-02 10:47:48.1357 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:47:48.1359 attempting to read 4 bytes
2007-05-02 10:47:58.1365 Slimproto client readable: 192.168.0.4:16899
2007-05-02 10:47:58.1368 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:47:58.1370 attempting to read 4 bytes
2007-05-02 10:48:08.1497 Slimproto client readable: 192.168.0.4:16900
2007-05-02 10:48:08.1508 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:48:08.1511 attempting to read 4 bytes
2007-05-02 10:48:18.1254 Slimproto client readable: 192.168.0.4:16901
2007-05-02 10:48:18.1257 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:48:18.1259 attempting to read 4 bytes
2007-05-02 10:48:28.1254 Slimproto client readable: 192.168.0.4:16902
2007-05-02 10:48:28.1257 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:48:28.1259 attempting to read 4 bytes
2007-05-02 10:48:38.1254 Slimproto client readable: 192.168.0.4:16903
2007-05-02 10:48:38.1270 state: OP, framelen: 0, inbuflen: 0
2007-05-02 10:48:38.1273 attempting to read 4 bytes
2007-05-02 10:48:59.0798 Slimproto client readable: 192.168.0.4:16904
2007-05-02 10:48:59.0802 state: OP, framelen: 0, inbuflen: 0

Any help GREATLY appreciated!

Chris.

chris.mason
2007-05-02, 11:17
Anybody got any ideas? Am I the only one with this issue?

If someone could tell me how to revert firmware, that would be a good start!

Thanks,
Chris.

kdf
2007-05-02, 11:26
Quoting "chris.mason"
<chris.mason.2pyxbb1178130001 (AT) no-mx (DOT) forums.slimdevices.com>:

> If someone could tell me how to revert firmware, that would be a good
> start!

older server version will take care of it automatically, and then if
you need the more recent server you can modify the Firmware/*.version
files to block the firmware update. They are text files and you
simply need to change the numbers to match the firmware you have,
instead of the number matching the firmware included with the newer
server version. This is an unsupported configuration, however.

-kdf

Skunk
2007-05-02, 11:32
I've tried going back to my last working installation - doesn't work.
I've tried a fresh 6.5.1 installation, that doesn't work either.


Does that mean you didn't uninstall the previous version and delete the slimserver folder before upgrading? Not sure if it's necessary anymore, but at one time seemed to be a problem for people. Is it possible one of the processes was still running while you were installing over, even after 'stopping slimserver' or 'exiting' using the tray icon?

Can you connect to squeezenetwork? Maybe try disabling firewalls and anti-virus(?). These are random guesses, if you didn't notice :-)

If a problem w/ SB was impeding my music fix, I'd probably contact support directly.

chris.mason
2007-05-02, 11:43
I just realised the firmware reversion is moot point right now, while my SB3 refuses to connect to SlimServer.

Do the debug messages I listed give any indication to the issue?

kdf
2007-05-02, 12:00
Ok, how about a factory reset? Press and hold ADD while powering on.

You might also try going through the setup again and setting teh slimserver IP manually.

-kdf

chris.mason
2007-05-03, 06:05
Hmmm...(blushes)...one reboot of my router later and all is OK (well, how OK remains to be seen, but my SB3 and Slim are now talking to each other).

I started getting suspicious of curious behaviour on my PC (where SlimServer is), I couldn't get to various devices on my LAN, which led me to the rather obvious (in hindsight) conclusion that there was a routing issue. I rebooted the router, and bingo...

Chris.