Discussion:
some trouble with slimproto in cvs
Jason Holtzapple
2004-10-20 20:32:31 UTC
Permalink
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?

2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
2004-10-20 13:27:24.8228 Slimproto accepted connection from: 192.168.1.24
2004-10-20 13:27:24.8303 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10, IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
2004-10-20 13:27:26.9244 Slimproto client readable: 192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at /home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
2004-10-20 13:27:27.5033 Slimproto accepted connection from: 192.168.1.23
2004-10-20 13:27:27.5059 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10, IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:27.5180 hello from existing client: 00:04:20:05:00:96 on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.5376 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
2004-10-20 13:27:28.6330 Slimproto accepted connection from: 192.168.1.25
2004-10-20 13:27:28.6348 Slimproto client readable: 192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10, IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:28.6473 hello from existing client: 00:04:20:05:6a:c0 on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
2004-10-20 13:27:28.9107 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at /home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at /home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
2004-10-20 13:27:28.9358 Slimproto accepted connection from: 192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.9431 Slimproto client readable: 192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10, IO::Socket::INET=GLOB(0x99a4158)
dean blackketter
2004-10-20 21:11:44 UTC
Permalink
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.


-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
2004-10-20 13:27:24.8303 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
2004-10-20 13:27:26.9244 Slimproto client readable: 192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
2004-10-20 13:27:27.5059 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:27.5180 hello from existing client: 00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.5376 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
2004-10-20 13:27:28.6348 Slimproto client readable: 192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:28.6473 hello from existing client: 00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
2004-10-20 13:27:28.9107 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.9431 Slimproto client readable: 192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
kdf
2004-10-20 21:22:34 UTC
Permalink
should be ok if you just delete squeezebox_40.bin and run cvs update again, then
reload firmware. I belive the firmware update routine does allow reloading
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
2004-10-20 13:27:24.8303 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
2004-10-20 13:27:26.9244 Slimproto client readable: 192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
2004-10-20 13:27:27.5059 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:27.5180 hello from existing client: 00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.5376 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
2004-10-20 13:27:28.6348 Slimproto client readable: 192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:28.6473 hello from existing client: 00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
2004-10-20 13:27:28.9107 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.9431 Slimproto client readable: 192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
Richard Titmuss
2004-10-20 21:38:36 UTC
Permalink
This will usually work, but if you have the broken firmware 40 the
squeezebox does not respond to the remote control so its not possible to
start the firmware update.

Regards,
Richard
Post by kdf
should be ok if you just delete squeezebox_40.bin and run cvs update again, then
reload firmware. I belive the firmware update routine does allow reloading
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
2004-10-20 13:27:24.8303 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
2004-10-20 13:27:26.9244 Slimproto client readable: 192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
2004-10-20 13:27:27.5059 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:27.5180 hello from existing client: 00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.5376 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
2004-10-20 13:27:28.6348 Slimproto client readable: 192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:28.6473 hello from existing client: 00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
2004-10-20 13:27:28.9107 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.9431 Slimproto client readable: 192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
kdf
2004-10-20 21:39:29 UTC
Permalink
ah...THAT kind of broken :)
Post by Richard Titmuss
This will usually work, but if you have the broken firmware 40 the
squeezebox does not respond to the remote control so its not possible to
start the firmware update.
Regards,
Richard
Post by kdf
should be ok if you just delete squeezebox_40.bin and run cvs update again,
then
Post by kdf
reload firmware. I belive the firmware update routine does allow reloading
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
2004-10-20 13:27:24.8228 Slimproto accepted connection from: 192.168.1.24
2004-10-20 13:27:24.8303 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
2004-10-20 13:27:26.9244 Slimproto client readable: 192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
2004-10-20 13:27:27.5033 Slimproto accepted connection from: 192.168.1.23
2004-10-20 13:27:27.5059 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:27.5180 hello from existing client: 00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.5376 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
2004-10-20 13:27:28.6330 Slimproto accepted connection from: 192.168.1.25
2004-10-20 13:27:28.6348 Slimproto client readable: 192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:28.6473 hello from existing client: 00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
2004-10-20 13:27:28.9107 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
2004-10-20 13:27:28.9358 Slimproto accepted connection from: 192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.9431 Slimproto client readable: 192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
Jeff Coffler
2004-10-20 21:48:09 UTC
Permalink
I've been thinking about this, as I'm working with someone else to write an
AMX automation module based on an extended command.pm CLI module (in
progress; we'll submit to this list when done).

If I don't use an I/R remote control because I use an automation system, how
would one update the firmware? If I send a "brightness" command via the CLI
command "button brightness" (docs not handy, but I think that's it), would
that work? The process says to press AND HOLD the brightness button, and I
can't really do THAT via the CLI.

Is there a way to trigger firmware updates via the web interface as well?

Thanks,

-- Jeff


----- Original Message -----
From: "Richard Titmuss" <richard_titmuss-/E1597aS9LT10XsdtD+***@public.gmane.org>
To: "Slim Devices Developers" <developers-***@public.gmane.org>
Sent: Wednesday, October 20, 2004 2:38 PM
Subject: Re: [Developers] some trouble with slimproto in cvs
Post by Richard Titmuss
This will usually work, but if you have the broken firmware 40 the
squeezebox does not respond to the remote control so its not possible to
start the firmware update.
Regards,
Richard
Post by kdf
should be ok if you just delete squeezebox_40.bin and run cvs update again, then
reload firmware. I belive the firmware update routine does allow reloading
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
2004-10-20 13:27:24.8303 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
2004-10-20 13:27:26.9244 Slimproto client readable: 192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
2004-10-20 13:27:27.5059 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:27.5180 hello from existing client: 00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.5376 Slimproto client readable: 192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
2004-10-20 13:27:28.6348 Slimproto client readable: 192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:28.6473 hello from existing client: 00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
2004-10-20 13:27:28.9107 Slimproto client readable: 192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.9431 Slimproto client readable: 192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
Jeff Coffler
2004-10-20 21:51:45 UTC
Permalink
I encountered a problem with SlimServer v5.3.1 and playlists using the
default HTML skin on Windows 2003 Server:

If, via my browser, I try to save a playlist, I get an error that the
playlist already exists. Yet, it doesn't! If I select "overwrite", I get
the same error.

I know that the SlimServer can write in the playlists directory because it
writes player playlists to a file named after the player MAC address.
Indeed, if I rename that file to my playlist file manually (not via the
SlimServer), then I can actually select that playlist to play.

Known problem? Update to the CVS archives? Or is this something new?

-- Jeff
dean blackketter
2004-10-20 21:59:54 UTC
Permalink
You HAVE to send IR brightness codes to the player physically to
trigger an upgrade. This is a security measure to prevent accidental
upgrading due to network traffic.
Post by Jeff Coffler
I've been thinking about this, as I'm working with someone else to write an
AMX automation module based on an extended command.pm CLI module (in
progress; we'll submit to this list when done).
If I don't use an I/R remote control because I use an automation system, how
would one update the firmware? If I send a "brightness" command via the CLI
command "button brightness" (docs not handy, but I think that's it), would
that work? The process says to press AND HOLD the brightness button, and I
can't really do THAT via the CLI.
Is there a way to trigger firmware updates via the web interface as well?
Thanks,
-- Jeff
----- Original Message -----
Sent: Wednesday, October 20, 2004 2:38 PM
Subject: Re: [Developers] some trouble with slimproto in cvs
Post by Richard Titmuss
This will usually work, but if you have the broken firmware 40 the
squeezebox does not respond to the remote control so its not possible to
start the firmware update.
Regards,
Richard
Post by kdf
should be ok if you just delete squeezebox_40.bin and run cvs update
again, then
Post by Richard Titmuss
Post by kdf
reload firmware. I belive the firmware update routine does allow
reloading
Post by Richard Titmuss
Post by kdf
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
Jeff Coffler
2004-10-20 22:12:00 UTC
Permalink
Okay, I'll just keep a remote control handy for these cases, I guess. Might
have been nice to at least allow the WWW server to update the firmware, but
if you guys wanted to restrict that, so be it.

So (out of curiousity): what happens if something "goes wrong" with firmware
(like what's being discussed here), and you can't send a brightness I/R
signal? Is there some back door mechanism? Or is it time to send a
SqueezeBox back to Slim Devices to be reprogrammed?

-- Jeff


----- Original Message -----
From: "dean blackketter" <dean-SBQ2+***@public.gmane.org>
To: "Slim Devices Developers" <developers-***@public.gmane.org>
Sent: Wednesday, October 20, 2004 2:59 PM
Subject: Re: [Developers] some trouble with slimproto in cvs
Post by dean blackketter
You HAVE to send IR brightness codes to the player physically to
trigger an upgrade. This is a security measure to prevent accidental
upgrading due to network traffic.
Post by Jeff Coffler
I've been thinking about this, as I'm working with someone else to write an
AMX automation module based on an extended command.pm CLI module (in
progress; we'll submit to this list when done).
If I don't use an I/R remote control because I use an automation system, how
would one update the firmware? If I send a "brightness" command via the CLI
command "button brightness" (docs not handy, but I think that's it), would
that work? The process says to press AND HOLD the brightness button, and I
can't really do THAT via the CLI.
Is there a way to trigger firmware updates via the web interface as well?
Thanks,
-- Jeff
----- Original Message -----
Sent: Wednesday, October 20, 2004 2:38 PM
Subject: Re: [Developers] some trouble with slimproto in cvs
Post by Richard Titmuss
This will usually work, but if you have the broken firmware 40 the
squeezebox does not respond to the remote control so its not possible to
start the firmware update.
Regards,
Richard
Post by kdf
should be ok if you just delete squeezebox_40.bin and run cvs update
again, then
Post by Richard Titmuss
Post by kdf
reload firmware. I belive the firmware update routine does allow
reloading
Post by Richard Titmuss
Post by kdf
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client, id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
dean blackketter
2004-10-20 22:28:28 UTC
Permalink
Post by Jeff Coffler
Okay, I'll just keep a remote control handy for these cases, I guess.
Might
have been nice to at least allow the WWW server to update the
firmware, but
if you guys wanted to restrict that, so be it.
Ok. It's certainly possible for us to change the firmware to not have
this requirement, but unless it's a real show-stopper for you, we'd
feel better leaving it this way.
Post by Jeff Coffler
So (out of curiousity): what happens if something "goes wrong" with firmware
(like what's being discussed here), and you can't send a brightness I/R
signal? Is there some back door mechanism? Or is it time to send a
SqueezeBox back to Slim Devices to be reprogrammed?
In this case, the problem isn't that there's a fatal bug in the
firmware, rather that there's a mismatch in the protocol between the
player and server. Another way to solve the problem that Jason's
having is to change the server software to not send the confusing data
to the player.

The real root of the problem is that there were, for a couple of hours,
two different firmware 40 versions, one that worked and one that didn't
with the latest software. If you grabbed and installed the first one,
then installed the updated server software, the server assumed you had
the newer firmware and made the player puke. I figured it wouldn't be
a problem, but it turned out to bite somebody. Lesson learned.

-dean
Post by Jeff Coffler
----- Original Message -----
Sent: Wednesday, October 20, 2004 2:59 PM
Subject: Re: [Developers] some trouble with slimproto in cvs
Post by dean blackketter
You HAVE to send IR brightness codes to the player physically to
trigger an upgrade. This is a security measure to prevent accidental
upgrading due to network traffic.
Post by Jeff Coffler
I've been thinking about this, as I'm working with someone else to write an
AMX automation module based on an extended command.pm CLI module (in
progress; we'll submit to this list when done).
If I don't use an I/R remote control because I use an automation system, how
would one update the firmware? If I send a "brightness" command via the CLI
command "button brightness" (docs not handy, but I think that's it), would
that work? The process says to press AND HOLD the brightness button, and I
can't really do THAT via the CLI.
Is there a way to trigger firmware updates via the web interface as well?
Thanks,
-- Jeff
----- Original Message -----
Sent: Wednesday, October 20, 2004 2:38 PM
Subject: Re: [Developers] some trouble with slimproto in cvs
Post by Richard Titmuss
This will usually work, but if you have the broken firmware 40 the
squeezebox does not respond to the remote control so its not
possible
to
start the firmware update.
Regards,
Richard
Post by kdf
should be ok if you just delete squeezebox_40.bin and run cvs update
again, then
Post by Richard Titmuss
Post by kdf
reload firmware. I belive the firmware update routine does allow
reloading
Post by Richard Titmuss
Post by kdf
current firmware on top of itself, does it not?
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll
need
to
roll back to a nightly from a couple of days ago, install 39 again,
then use the latest CVS. This is due to the fact that for a couple
hours there was a slightly broken firmware 40, and you might have
grabbed it in that window.
-dean
Post by Jason Holtzapple
I updated from cvs a short while ago and restarted the server after a
firmware upgrade. Now the squeezeboxen won't connect. They seem stuck
in a connection loop. I went from firmware 39 to 40. Any ideas?
2004-10-20 13:27:24.5241 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.5271 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.5313 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.5349 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8024 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8063 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:24.8076 new state: OP
2004-10-20 13:27:24.8185 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8194 attempting to read 4 bytes
2004-10-20 13:27:24.8201 no more to read.
192.168.1.24
192.168.1.24:27133
2004-10-20 13:27:24.8315 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8323 attempting to read 4 bytes
2004-10-20 13:27:24.8330 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8338 new state: LENGTH
2004-10-20 13:27:24.8345 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:24.8352 attempting to read 4 bytes
2004-10-20 13:27:24.8360 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:24.8368 new state: DATA
2004-10-20 13:27:24.8375 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:24.8383 attempting to read 10 bytes
2004-10-20 13:27:24.8390 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:24.8401 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xab78a0c)
2004-10-20 13:27:24.8411 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:60:8a
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
2004-10-20 13:27:24.8430 creating new client,
id:00:04:20:05:60:8a
ipport: 192.168.1.24:27133
2004-10-20 13:27:24.8471 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:24.8501 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:24.8545 sending squeezebox frame: grfb, length: 2
2004-10-20 13:27:24.8581 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8936 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:26.8975 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:26.8988 new state: OP
2004-10-20 13:27:26.8997 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:26.9005 attempting to read 4 bytes
2004-10-20 13:27:26.9012 no more to read.
192.168.1.25:29466
2004-10-20 13:27:26.9253 Slimproto connection closed by peer in readable.
2004-10-20 13:27:26.9260 Slimproto connection closed
getpeername() on closed socket GEN16 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.23
192.168.1.23:21333
2004-10-20 13:27:27.5070 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5078 attempting to read 4 bytes
2004-10-20 13:27:27.5086 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5094 new state: LENGTH
2004-10-20 13:27:27.5101 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5109 attempting to read 4 bytes
2004-10-20 13:27:27.5117 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:27.5125 new state: DATA
2004-10-20 13:27:27.5133 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:27.5141 attempting to read 10 bytes
2004-10-20 13:27:27.5149 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:27.5158 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x8fd5844)
2004-10-20 13:27:27.5167 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:00:96
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
00:04:20:05:00:96
on ipport: 192.168.1.23:21333
2004-10-20 13:27:27.5193 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:27.5230 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.5267 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:27.5281 new state: OP
2004-10-20 13:27:27.5290 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:27.5298 attempting to read 4 bytes
2004-10-20 13:27:27.5306 no more to read.
2004-10-20 13:27:27.9052 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:27.9227 sending squeezebox frame: grfd, length: 562
192.168.1.23:21333
2004-10-20 13:27:28.5386 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.5394 Slimproto connection closed
192.168.1.25
192.168.1.25:29470
2004-10-20 13:27:28.6359 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6367 attempting to read 4 bytes
2004-10-20 13:27:28.6375 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6383 new state: LENGTH
2004-10-20 13:27:28.6392 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6400 attempting to read 4 bytes
2004-10-20 13:27:28.6408 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.6417 new state: DATA
2004-10-20 13:27:28.6425 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.6434 attempting to read 10 bytes
2004-10-20 13:27:28.6442 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.6451 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0xaa3ee38)
2004-10-20 13:27:28.6461 Squeezebox says hello.
Deviceid: 2
revision: 40
mac: 00:04:20:05:6a:c0
bitmapped: 32768
reconnect: 16384
wlan_channellist: 07ff
00:04:20:05:6a:c0
on ipport: 192.168.1.25:29470
2004-10-20 13:27:28.6487 sending squeezebox frame: vers, length: 5
2004-10-20 13:27:28.6524 sending squeezebox frame: grfd, length: 562
2004-10-20 13:27:28.6563 sending squeezebox frame: i2cc, length: 60
2004-10-20 13:27:28.6577 new state: OP
2004-10-20 13:27:28.6587 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.6595 attempting to read 4 bytes
2004-10-20 13:27:28.6603 no more to read.
192.168.1.24:27133
2004-10-20 13:27:28.9119 Slimproto connection closed by peer in readable.
2004-10-20 13:27:28.9127 Slimproto connection closed
getpeername() on closed socket GEN20 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
getpeername() on closed socket GEN23 at
/home/slim/perl/lib/5.8.5/i386-netbsd/IO/Socket.pm line 206.
192.168.1.24
2004-10-20 13:27:28.9408 sending squeezebox frame: grfd, length: 562
192.168.1.24:27137
2004-10-20 13:27:28.9443 state: OP, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9451 attempting to read 4 bytes
2004-10-20 13:27:28.9459 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9468 new state: LENGTH
2004-10-20 13:27:28.9477 state: LENGTH, framelen: 0, inbuflen: 0
2004-10-20 13:27:28.9486 attempting to read 4 bytes
2004-10-20 13:27:28.9495 Got 4 bytes from client, 0 remaining
2004-10-20 13:27:28.9503 new state: DATA
2004-10-20 13:27:28.9512 state: DATA, framelen: 10, inbuflen: 0
2004-10-20 13:27:28.9521 attempting to read 10 bytes
2004-10-20 13:27:28.9529 Got 10 bytes from client, 0 remaining
2004-10-20 13:27:28.9541 Got Slimproto frame, op HELO, length 10,
IO::Socket::INET=GLOB(0x99a4158)
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
Jeff Coffler
2004-10-20 22:38:08 UTC
Permalink
Hi Dean,
Post by dean blackketter
Post by Jeff Coffler
Okay, I'll just keep a remote control handy for these cases, I guess.
Might
have been nice to at least allow the WWW server to update the
firmware, but
if you guys wanted to restrict that, so be it.
Ok. It's certainly possible for us to change the firmware to not have
this requirement, but unless it's a real show-stopper for you, we'd
feel better leaving it this way.
It's not a showstopper, most certainly. More an oddity.

My goal here is to have my automation system (AMX NetLinx) fully control the
SqueezeBox (like it did with my old Audiotron). I've paired off with
someone else; Thomas is working on the SlimServer command.pm file, I'm
working on the NetLinx side. He has already extended the CLI (command.pm)
to support extended status (returning all status information in one CLI
command), and I'm using that in my NetLinx module. Browsing extensions are
in progress while I put more time/work into the NetLinx module.

So, in these cases, even though my AMX control panel controls everything in
the house, I'll need to pull out an I/R remote control to update the
firmware.

As I said: Not a showstopper, just an oddity. Particularly since I'll never
touch the remote control otherwise.

-- Jeff
Kevin Hawkins
2004-10-25 12:01:34 UTC
Permalink
Post by Jeff Coffler
Hi Dean,
Post by dean blackketter
Post by Jeff Coffler
Okay, I'll just keep a remote control handy for these cases, I guess.
Might
have been nice to at least allow the WWW server to update the
firmware, but
if you guys wanted to restrict that, so be it.
Ok. It's certainly possible for us to change the firmware to not have
this requirement, but unless it's a real show-stopper for you, we'd
feel better leaving it this way.
It's not a showstopper, most certainly. More an oddity.
My goal here is to have my automation system (AMX NetLinx) fully control the
SqueezeBox (like it did with my old Audiotron). I've paired off with
someone else; Thomas is working on the SlimServer command.pm file, I'm
working on the NetLinx side. He has already extended the CLI (command.pm)
to support extended status (returning all status information in one CLI
command), and I'm using that in my NetLinx module. Browsing extensions are
in progress while I put more time/work into the NetLinx module.
So, in these cases, even though my AMX control panel controls everything in
the house, I'll need to pull out an I/R remote control to update the
firmware.
Hi Jeff - most interested in this - We have a xAP connector available
for SlimServer that connects via the CLI and presents control and events
from the server as an 'audio control' schema (via UDP) allowing control
and remote display on 'whatever' devices. It also translates IR
keypresses to our network IR schema and handles our OSD (on screen
display) messages. I have xAP working with my Crestron system here but
via a PC helper application (TCP linked) as the UDP implementation
within SIMPL on Crestron currently has a lacking feature we need. xAP
is a great system in that it abstracts the hardware to a 'role' and
therefore supports many different hardware players transparently. Also
all xAP devices become network shareable resources. So I currently have
full control and display of the SlimServer via Crestron and xAP. I was
waiting for the Crestron UDP issue to be resolved before posting the
module as then no PC helper application wil be required.

I have recently been talking with AMX too about supporting xAP natively
and now have a Netlinx 3000 / MVP 8400 / CV7 system here that I'm
playing with to look at the practicality, but although I am familiar
with Crestron I am early on the learning curve with AMX however I think
I can support xAP natively here on teh Netlinx. Adding xAP support
would allow many many devices to just drop in and be useable from your
AMX system - eg lighting control, internet news/weather feeds, CallerID
, TV listings info , mp3 players, PVR TV recorders etc etc.

One of the things we needed was better control and event reporting via
the CLI and I note you have someone addressing this. A few requests have
peppered this list on the subject but we realise it is low prority and
far more exciting features continue to appear daily which keep us all
content. The author of the xAP conduit had some ideas & 'wishes' here
(re the CLI) and it may be worth pooling some thoughts between us.
Certainly there were some problems in the current efficiency and in the
completeness/frequency of the event reporting. Also the new features
of SlimServer are not accessible yet via the CLI for example the fuller
IR code reporting from a Squeezebox - and the text writing to the
displays. The latter needs particular attention now with regard to the
graphic display, we have more font information and are no longer within
a fixed 2x40 format, plus of course the ability to send bitmaps.

Are you an AMX reseller or a user ?? Please feel free to contact me
offlist if any of this is of interest..

Kevin
Jeff Coffler
2004-10-25 16:27:32 UTC
Permalink
Hi Kevin,

Feel free to E-Mail me separately if you want to take this off the list.
Post by Kevin Hawkins
One of the things we needed was better control and event reporting via
the CLI and I note you have someone addressing this. A few requests have
peppered this list on the subject but we realise it is low prority and
far more exciting features continue to appear daily which keep us all
content. The author of the xAP conduit had some ideas & 'wishes' here
(re the CLI) and it may be worth pooling some thoughts between us.
Certainly there were some problems in the current efficiency and in the
completeness/frequency of the event reporting. Also the new features
of SlimServer are not accessible yet via the CLI for example the fuller
IR code reporting from a Squeezebox - and the text writing to the
displays. The latter needs particular attention now with regard to the
graphic display, we have more font information and are no longer within
a fixed 2x40 format, plus of course the ability to send bitmaps.
Our CLI enhancements weren't "general enhancements that might be
interesting". Our CLI enhancements were quite targeted: How would one
efficiently write an automation system module to tie in with the SlimServer
software? The existing CLI interface was lacking in many key areas,
including:

1) No way to get "full status" on a player. You can get bits and pieces,
but it wasn't easy to get everything you needed in one shot (thereby
necessitating "multiple trips" to get the data). Most of this WAS available
via the HTTP interface, but at high cost for an automation system,

2) Absolutely no way at all to do browsing via the CLI interface.

Having already done a module to tie in with Audiotrons, I had some knowledge
of what was needed. I wanted to keep things generic (so other
people/software could use the CLI extensions), but still allow it to be
fairly easy on the NetLinx side. Things are progressing nicely.

I've included a message here that contains more detail (and was orginally
sent to this list). If you want more details of that thread, I suspect you
check the archives.
Post by Kevin Hawkins
Are you an AMX reseller or a user ?? Please feel free to contact me
offlist if any of this is of interest.
I am an end-user that is a programmer by profession. I knew way more about
programming in general (and after a short period of time, programming under
NetLinx) than my dealer knew.

-- Jeff

Jason Holtzapple
2004-10-20 21:51:01 UTC
Permalink
I'm not sure how I got the bad version, as I just upgraded firmware today.

I tried older cvs with v39, but the Squeezeboxes won't connect. I just tried
2004-10-28 18:00, which is just after the broken v40 and before the fixed
v40, and that wouldn't connect either. Is there another time I could try?

thanks
--Jason
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need to
roll back to a nightly from a couple of days ago, install 39 again, then
use the latest CVS. This is due to the fact that for a couple hours
there was a slightly broken firmware 40, and you might have grabbed it
in that window.
-dean
dean blackketter
2004-10-20 22:07:56 UTC
Permalink
Post by Jason Holtzapple
I'm not sure how I got the bad version, as I just upgraded firmware today.
When did you last update CVS? If you have firmware v40 from a few hours
on monday, then you might see this problem...
Post by Jason Holtzapple
I tried older cvs with v39, but the Squeezeboxes won't connect. I just tried
2004-10-28 18:00, which is just after the broken v40 and before the fixed
v40, and that wouldn't connect either. Is there another time I could try?
Try yesterday's nightly. Downgrade your player to version 39. Then
update to the latest CVS and upgrade again to 40.

-dean
Post by Jason Holtzapple
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need
to roll back to a nightly from a couple of days ago, install 39
again, then use the latest CVS. This is due to the fact that for a
couple hours there was a slightly broken firmware 40, and you might
have grabbed it in that window.
-dean
_______________________________________________
Developers mailing list
http://lists.slimdevices.com/lists/listinfo/developers
Jason Holtzapple
2004-10-20 22:47:02 UTC
Permalink
Post by dean blackketter
Post by Jason Holtzapple
I'm not sure how I got the bad version, as I just upgraded firmware today.
When did you last update CVS? If you have firmware v40 from a few hours
on monday, then you might see this problem...
Just this afternoon at about 2 PM (MST).
Post by dean blackketter
Post by Jason Holtzapple
I tried older cvs with v39, but the Squeezeboxes won't connect. I just tried
2004-10-28 18:00, which is just after the broken v40 and before the fixed
v40, and that wouldn't connect either. Is there another time I could try?
Try yesterday's nightly. Downgrade your player to version 39. Then
update to the latest CVS and upgrade again to 40.
I tried 2009-10-19 - and it doesn't work. I can't even connect to the
server - the boxes display Slimproto error, length nnn.
Post by dean blackketter
-dean
Post by Jason Holtzapple
Post by dean blackketter
What are you seeing on the display?
If you are seeing SlimProto errors on the display, then you'll need
to roll back to a nightly from a couple of days ago, install 39
again, then use the latest CVS. This is due to the fact that for a
couple hours there was a slightly broken firmware 40, and you might
have grabbed it in that window.
-dean
dean blackketter
2004-10-20 22:59:31 UTC
Permalink
Post by Jason Holtzapple
Post by dean blackketter
Post by Jason Holtzapple
I'm not sure how I got the bad version, as I just upgraded firmware today.
When did you last update CVS? If you have firmware v40 from a few
hours on monday, then you might see this problem...
Just this afternoon at about 2 PM (MST).
Right but if you have the older v40 already on your squeezebox then it
will get confused.
Post by Jason Holtzapple
Post by dean blackketter
Post by Jason Holtzapple
I tried older cvs with v39, but the Squeezeboxes won't connect. I just tried
2004-10-28 18:00, which is just after the broken v40 and before the fixed
v40, and that wouldn't connect either. Is there another time I could try?
Try yesterday's nightly. Downgrade your player to version 39. Then
update to the latest CVS and upgrade again to 40.
I tried 2009-10-19 - and it doesn't work. I can't even connect to the
server - the boxes display Slimproto error, length nnn.
My bad, sorry. Yesterday's still sends the confusing data to the
player. You'll need the one from the 18th or earlier.

(alternatively, you can comment out these lines in
Slim::Player::Squeezebox.pm in the latest CVS

# tell the client the server version
if ($revision == 0 || $revision > 39) {
$client->sendFrame('vers', \$::VERSION);
}

That should resolve the incompatibility, allowing you to press and hold
brightness and force upgrade to the latest.
Jason Holtzapple
2004-10-20 23:12:07 UTC
Permalink
Post by dean blackketter
Post by Jason Holtzapple
Post by dean blackketter
Try yesterday's nightly. Downgrade your player to version 39. Then
update to the latest CVS and upgrade again to 40.
I tried 2009-10-19 - and it doesn't work. I can't even connect to the
server - the boxes display Slimproto error, length nnn.
My bad, sorry. Yesterday's still sends the confusing data to the
player. You'll need the one from the 18th or earlier.
(alternatively, you can comment out these lines in
Slim::Player::Squeezebox.pm in the latest CVS
# tell the client the server version
if ($revision == 0 || $revision > 39) {
$client->sendFrame('vers', \$::VERSION);
}
That should resolve the incompatibility, allowing you to press and hold
brightness and force upgrade to the latest.
Thanks for this tip, but I did find a spot where I could get the players
to connect - if someone else gets caught by this.

1. pull cvs from 2004-10-18 12:00 UTC
2. copy squeezebox_39.bin onto squeezebox_40.bin
3. change squeezebox.version to allow "downgrade"

# from to
# from1..from2 to

1..8 10

# version 10 is the same as version 8, except that it has additional
# support to be updated to version 20 and above.

10..40 40

# future versions may be downgraded to this one
* 40

4. force downgrade to v39.
5. kill server
6. start latest server and upgrade to good v40.

*phew* (your way seems easier now, though)

--Jason
Loading...