Er, no. I am just confused. Less so now, thanks.
Thanks,
Russell.
Richie wrote:
On 17/12/05, Russell Mulcahy [EMAIL PROTECTED] wrote:
This may (not) be relevant - my firmware version is reported as 40 for the
same 5.2.1 build! Am I *that* far ahead ;-)
No you're not
This may (not) be relevant - my firmware version is reported as 40 for
the same 5.2.1 build! Am I *that* far ahead ;-)
I also have a problem where my SB2 "can't find slimserver" after a
power on or restart. Pressing "left" and resetting up the connection
works every time. This is with a
On 17/12/05, Russell Mulcahy [EMAIL PROTECTED] wrote:
This may (not) be relevant - my firmware version is reported as 40 for the
same 5.2.1 build! Am I *that* far ahead ;-)
No you're not ahead, you have a SB1 if the firmware is version 40.
I hope no one sold it to you pretending it was a SB2.
dean Wrote:
Also, what version of firmware are you running?
I'm still looking at this.
I'm running what ever version of firmware ships with 6.2.1 - 5194 -
Linux - EN - utf8. I'm not sure how to check, but I think this
answers your question.
I rearranged my network infrastructure to put my
There is a version of Ethereal for Windows.
http://www.ethereal.com/
My guess is that it's related to something in the switch that for
Mysterious Reasons doesn't like seeing a DHCP packet too soon after
reboot... but why it would be so upset that it would ignore further
ones is curious.
It
Jeff Wrote:
I'm running what ever version of firmware ships with 6.2.1 - 5194 -
Linux - EN - utf8. I'm not sure how to check, but I think this
answers your question.
No, that's the slimserver software version and locale. Instead, look
just above that info for Player Firmware Version in
MrC Wrote:
No, that's the slimserver software version and locale. Instead, look
just above that info for Player Firmware Version in the web or look at
Settings-Information-Player Information on the SB.
What's the point? Firmware versions and software versions are sync'ed;
that will answer
Jeff Wrote:
What's the point? Firmware versions and software versions are sync'ed;
that will answer Dean's question.
Just to satisfy others out there (since Dean should know), the firmware
version shipping with SlimServer 6.2.1 is 28.
I was simply offering a How To in response to your
dean Wrote:
On Dec 12, 2005, at 8:28 AM, Jeff wrote:[color=blue]
It absolutely should and as far as I can tell, does.
Can you reproduce the problem in a way that we can do it here too?
Can you also provide details about your network setup (devices,
configuration?)
Thanks,
Hi Jeff,
On Dec 12, 2005, at 12:58 PM, Jeff wrote:
1) Disconnect SlimServer machine from the network. Wait 5-10 seconds.
Squeezebox display goes dark.
2) Disconnect Squeezebox from the network. Screen remains dark.
3) Wait 60 seconds or so.
4) Connect Squeezebox to the network. Wait 30
Hi Dean,
dean Wrote:
Alas, those steps don't do it for me here. Is there some other trick
I missed?
.
Some questions...
Are your devices using DHCP or static addresses? Are the addresses
changing? Do you have the ability to do a packet capture?
I don't get it. This
On Dec 12, 2005, at 1:20 PM, Jeff wrote:
I don't get it. This reproduces so easily for me!
Frustrating... grrr...
UNIX box has a static address. Squeezeboxes have dynamic addresses
via
DHCP. It's possible that the router isn't coming back immediately
with
a DHCP address, perhaps
dean Wrote:
The thing is that it doesn't give up. It just keeps trying.
What would be useful would be to get a packet dump from the server when
it's in the state of not being able to connect.
Also, without rebooting the player, what happens if you go back to the
main menu and try to
On Dec 12, 2005, at 1:45 PM, Jeff wrote:
dean Wrote:
The thing is that it doesn't give up. It just keeps trying.
What would be useful would be to get a packet dump from the server
when
it's in the state of not being able to connect.
Also, without rebooting the player, what happens if you
14 matches
Mail list logo