PDA

View Full Version : player freeze?



Chris Kantarjiev
2005-08-11, 09:53
I have a Squeezebox (1st version) that suffers from random music
dropouts of many seconds. It's over WiFi, and I've always blamed
the access point. It's not at all reproducable, I'm afraid - there
are times when the buffer display just goes to empty and the music
stops.

I recently tried running the slimserver with a nice of -4, which
seems to help a lot. I didn't notice the buffer going to empty.
But I still got dropouts ... and when I looked, the display was
frozen, not responding to the IR remote at all.

I suppose it could still be the WiFi freezing - are the remote
commands handled by the box or the server? - but I also witnessed
a fair number of player reboots when it got bad. It would reboot,
try to get to the access point, make it to 10 in the countdown
and reboot again...

Sigh.

kdf
2005-08-11, 10:10
This does sound a lot like wireless troubles. The Squeezebox is essentially a
dumb terminal. The IR codes are sent to the server, and the server generates
all of the responses, text, etc. The player itself does very little, outside
of character generation, mixer control and minimal data handling.

If you have other wifi devices in the neighbourhood, try switching yours to a
different channel.

-kdf

Yannzola
2005-08-11, 10:17
I have a Squeezebox (1st version) that suffers from random music
dropouts of many seconds. It's over WiFi, and I've always blamed
the access point. It's not at all reproducable, I'm afraid - there
are times when the buffer display just goes to empty and the music
stops.

I recently tried running the slimserver with a nice of -4, which
seems to help a lot. I didn't notice the buffer going to empty.
But I still got dropouts ... and when I looked, the display was
frozen, not responding to the IR remote at all.

I suppose it could still be the WiFi freezing - are the remote
commands handled by the box or the server? - but I also witnessed
a fair number of player reboots when it got bad. It would reboot,
try to get to the access point, make it to 10 in the countdown
and reboot again...

Sigh.

I've had similiar problems lately (SB2 wireless)It's been freezing at least once almost every day. Any suggestions on troubleshooting?

BTW: I've been checking the debugging boxes (_musicmagic, _info, etc.)... hoping to get some diagnostics info, but have as of yet never been able to locate the log.txt file anywhere. It doesn't seem to be getting created anywhere in the Slimserver directory abd the link points to a blank page from the debug page. Also, the debug setting are always re-set to default (non-checked) after a crash (feature?).

y.

kdf
2005-08-11, 10:35
Quoting Yannzola <Yannzola.1tm17b (AT) no-mx (DOT) forums.slimdevices.com>:
> BTW: I've been checking the debugging boxes (_musicmagic, _info,
> etc.)... hoping to get some diagnostics info, but have as of yet never
> been able to locate the log.txt file anywhere. It doesn't seem to be
> getting created anywhere in the Slimserver directory abd the link
> points to a blank page from the debug page. Also, the debug setting are
> always re-set to default (non-checked) after a crash (feature?).

feature. they are command-line switches. you can set them after starting, but
you can also set them in teh command line. Windows users can do this by
editing the command startup parameters.

log:
http://serverIP:9000/log.txt

linux, its in /tmp/slimserver.log

you can also use the --logfile xxxxx.log to specify the log filename if you run
from command line.

-kdf

Chris Kantarjiev
2005-08-11, 12:31
> This does sound a lot like wireless troubles. The Squeezebox is essentially a
> dumb terminal. The IR codes are sent to the server, and the server generates
> all of the responses, text, etc. The player itself does very little, outside
> of character generation, mixer control and minimal data handling.

OK, that's what I needed to know.

> If you have other wifi devices in the neighbourhood, try switching yours to a
> different channel.

It was on channel 1. The only other device I find in a scan (right now)
is on channel 6; I switched to channel 4 and turned on "microwave
resiliency", which I'd ignored because *we* don't have a microwave.

Now for more testing.

I notice, though, that while trying to find the network, the Squeezebox
counted down to 10 and crashed/rebooted ... still something fishy there.
I ended up going through setup again to make sure it found the new channel.

Greg Klanderman
2005-08-11, 13:25
what does it report the wireless signal strength to be?

Renyao
2005-08-11, 20:15
Hi SB2 wireless users,

Please Try using 11M 802.11b mode instead of 54M 802.11g mode when you have dropout or similar problems .

when using 54M 802.11g wireless mode,the receiving error rate in my computer's network card reaches(5%~30%),and SB2 will refuse to work in about every 50 minutes.

After changeing to 11M 802.11b wireless mode,the error rate is normal (0.3% in average),and SB2 woks errorlessly.

Renyao He



Chris Kantarjiev Wrote:
> I have a Squeezebox (1st version) that suffers from random music
> dropouts of many seconds. It's over WiFi, and I've always blamed
> the access point. It's not at all reproducable, I'm afraid - there
> are times when the buffer display just goes to empty and the music
> stops.
>
> I recently tried running the slimserver with a nice of -4, which
> seems to help a lot. I didn't notice the buffer going to empty.
> But I still got dropouts ... and when I looked, the display was
> frozen, not responding to the IR remote at all.
>
> I suppose it could still be the WiFi freezing - are the remote
> commands handled by the box or the server? - but I also witnessed
> a fair number of player reboots when it got bad. It would reboot,
> try to get to the access point, make it to 10 in the countdown
> and reboot again...
>
> Sigh.

I've had similiar problems lately (SB2 wireless)It's been freezing at
least once almost every day. Any suggestions on troubleshooting?

BTW: I've been checking the debugging boxes (_musicmagic, _info,
etc.)... hoping to get some diagnostics info, but have as of yet never
been able to locate the log.txt file anywhere. It doesn't seem to be
getting created anywhere in the Slimserver directory abd the link
points to a blank page from the debug page. Also, the debug setting are
always re-set to default (non-checked) after a crash (feature?).

y.


--
Yannzola

dean
2005-08-11, 21:04
Renyao,

On Aug 11, 2005, at 8:15 PM, Renyao wrote:
> Please Try using 11M 802.11b mode instead of 54M 802.11g mode when
> you have dropout or similar problems .
>
> when using 54M 802.11g wireless mode,the receiving error rate in my
> computer's network card reaches(5%~30%),and SB2 will refuse to
> work in about every 50 minutes.
>
> After changeing to 11M 802.11b wireless mode,the error rate is
> normal (0.3% in average),and SB2 woks errorlessly.
Which router are you using when you see these performance problems?

Chris Kantarjiev
2005-08-11, 21:45
kdf, you must have nailed it. As I wrote, I changed from channel 1 to
channel 4, and it's been playing flawlessly for about 12 hours now...

FWIW, I'm running 802.11b though a second gen airport.

The crash-on-countdown is still there, and I, too, can never get
anything meaningful in my logfile, even though I specify it with
--logfile ... maybe I need to turn on more command
line debug settings.

Thanks!

Best,
chris

MrC
2005-08-11, 22:06
Remeber too folks, those 2.4Ghz cordless phones wreak havoc on some wireless b connections, as they're in the same band. The manuals or tech support for these phones usually tell you the channel(s) being used by the device. Configuring your AP to avoid those channels will help.

Renyao
2005-08-12, 04:38
Hi dean blackketter,

The wireless network card in my computer is TP-LINK TL-WN350G.

The router I use is TP-LINK TL-WR340G.

They are both made in China.I see these data in the advanced section of data statistics in the client of
TP-LINK TL-WN350G.

See http://www.tp-link.com.cn for more information.

Renyao


-----原始邮件-----
?件人: dean blackketter [mailto:dean (AT) slimdevices (DOT) com]
??时间: 2005 08 12 12:04
收件人: Slim Devices Discussion
主题: Re: [slim] Re: player freeze?

Renyao,

On Aug 11, 2005, at 8:15 PM, Renyao wrote:
> Please Try using 11M 802.11b mode instead of 54M 802.11g mode when
> you have dropout or similar problems .
>
> when using 54M 802.11g wireless mode,the receiving error rate in my
> computer's network card reaches(5%~30%),and SB2 will refuse to
> work in about every 50 minutes.
>
> After changeing to 11M 802.11b wireless mode,the error rate is
> normal (0.3% in average),and SB2 woks errorlessly.
Which router are you using when you see these performance problems?

dean
2005-08-12, 07:52
On Aug 12, 2005, at 4:38 AM, Renyao wrote:
> The wireless network card in my computer is TP-LINK TL-WN350G.
>
> The router I use is TP-LINK TL-WR340G.
>
> They are both made in China.I see these data in the advanced
> section of data statistics in the client of
> TP-LINK TL-WN350G.
Thanks, Renyao. I don't think these devices are available here for
testing.

I can say that we haven't seen this kind of difference between
802.11g and 802.11b in the other routers we've tested.

I'm glad that you found a work-around...