PDA

View Full Version : Plz help with these FW21 Squeezebox problems



Jason
2004-05-01, 17:38
I have been trying to work with Sean Adams on this, but it is very slow
getting responses from him (I know he's a busy guy), so I wanted to post
this here in case anyone has any additional insight on helping me get my
problems resolved.

I updated my Squeezebox to FW21 with the 5.1.5 release. I was the original
beta tester for the native Audi interface on the Phatbox, I like helping
beta test new stuff so I figured what the heck and loaded up FW21.

That was a mistake. After loading the new firmware I immediately started
having problems with my squeezebox, which had been fine before. I now get
numerous audio glitches (the sound you get from a scratched CD when playing
it on an older CD player) and occassional moments of silence when playing my
MP3 collection. Sometimes a song will play fine for a minute or two and then
you will hear a small glitch in the output, other times the song becomes so
garbled that I am worried it will damage my speakers. I sent one of the
files to Sean and he said it plays without any problems on FW21. My old
SliMP3, btw, has had absolutely no problems through any of this.

I have tried hard wiring my squeezebox to the LAN (it was hooked up via 128
bit WEP encrypted wireless) and tried all of the audio outputs. The
slimserver never shows any distress and the buffer shows plenty of capacity
on the Squeezebox.

Since Sean indicated he couldn't duplicate the problem I figured I would try
another route. I downloaded the latest nightly of slimserver for Windows
and loaded it onto my Windows XP laptop (a P4 2.2 with 512MB of RAM). I
direct connected the laptop and squeezebox together via a small ethernet
switch and the squeezebox immediately discovered the new slimserver and said
it needed to update FW.

The FW update is a mess. When I try to update the firmware I see all kinds
of garbled characters on the screen, followed by a message that the FW
update has failed. This also results in the slimserver locking up on the
laptop for about 5 minutes, then restarting.

Here are some photos of what the squeezebox is doing during the firmware
update process (taken with a high speed camera).

http://home.comcast.net/~audi-fan/squeeze1.jpg

http://home.comcast.net/~audi-fan/squeeze2.jpg

http://home.comcast.net/~audi-fan/squeeze3.jpg

http://home.comcast.net/~audi-fan/squeeze4.jpg

Obviously I am finding all of this rather distressing. I realize that FW21
is in beta, but I am trying to figure out what is going on here so that I
can get my unit operational again. If you guys don't have a good idea of
what is happening here, I would think that Slim Devices would want to get
ahold of my unit so that they can figure out what went wrong with the FW21
update that appears to have corrupted it, or maybe someone has other ideas
of what could be going on here.

I just want to go back to enjoying the tunes again guys!

-Jason.

kdf
2004-05-01, 17:49
Do you have any access to a linux machine anywhere? Even if only for long
enough to install the server, and do an upgrade. All the problems with FW2x
seem to be whilst using WinXP (at least to my memory). I've running v22 right
now and have had not a single firmware upgrade problem since ...well, since
prolly v2 or 3.

-kdf

Quoting Jason <jason (AT) pagefamily (DOT) net>:

> I have been trying to work with Sean Adams on this, but it is very slow
> getting responses from him (I know he's a busy guy), so I wanted to post
> this here in case anyone has any additional insight on helping me get my
> problems resolved.
>

seanadams
2004-05-03, 10:25
Jason,

Those photos are really interesting. In addition to the email I sent
you, I have some more thoughts for the benefit of others who may be
interested:

Between firmware version 1x and 2x, we upgraded to a newer version of
the underlying OS that runs Squeezebox. What came along with this were
some big changes in the way the hardware drivers for the display,
pcmcia, and sram/flash are supposed to interact. Although the new way
is better for a number of performance reasons, it did necessitate a
major rework of all of our low-level drivers. I'm trying not to get too
buried in the details here, but basically we are implementing all of
these different interfaces in software using a shared bus, and getting
all the timing right is tricky. What you're probably seeing there is
some kind of contention between the display and memory drivers - it may
also explain the audio glitches you're getting.

At any rate, it looks like somewhere we're driving the bus incorrectly
or too fast... but this is the first time I've seen the behavior in
your pictures, so what I'd really like to do is swap out your
squeezebox for another so that I can do some experiments with it.

Thanks,
Sean


On May 1, 2004, at 5:38 PM, Jason wrote:

> I have been trying to work with Sean Adams on this, but it is very
> slow getting responses from him (I know he's a busy guy), so I wanted
> to post this here in case anyone has any additional insight on helping
> me get my problems resolved.
>
> I updated my Squeezebox to FW21 with the 5.1.5 release. I was the
> original beta tester for the native Audi interface on the Phatbox, I
> like helping beta test new stuff so I figured what the heck and loaded
> up FW21.
>
> That was a mistake. After loading the new firmware I immediately
> started having problems with my squeezebox, which had been fine
> before. I now get numerous audio glitches (the sound you get from a
> scratched CD when playing it on an older CD player) and occassional
> moments of silence when playing my MP3 collection. Sometimes a song
> will play fine for a minute or two and then you will hear a small
> glitch in the output, other times the song becomes so garbled that I
> am worried it will damage my speakers. I sent one of the files to Sean
> and he said it plays without any problems on FW21. My old SliMP3,
> btw, has had absolutely no problems through any of this.
>
> I have tried hard wiring my squeezebox to the LAN (it was hooked up
> via 128 bit WEP encrypted wireless) and tried all of the audio
> outputs. The slimserver never shows any distress and the buffer shows
> plenty of capacity on the Squeezebox.
>
> Since Sean indicated he couldn't duplicate the problem I figured I
> would try another route. I downloaded the latest nightly of
> slimserver for Windows and loaded it onto my Windows XP laptop (a P4
> 2.2 with 512MB of RAM). I direct connected the laptop and squeezebox
> together via a small ethernet switch and the squeezebox immediately
> discovered the new slimserver and said it needed to update FW.
>
> The FW update is a mess. When I try to update the firmware I see all
> kinds of garbled characters on the screen, followed by a message that
> the FW update has failed. This also results in the slimserver locking
> up on the laptop for about 5 minutes, then restarting.
>
> Here are some photos of what the squeezebox is doing during the
> firmware update process (taken with a high speed camera).
>
> http://home.comcast.net/~audi-fan/squeeze1.jpg
>
> http://home.comcast.net/~audi-fan/squeeze2.jpg
>
> http://home.comcast.net/~audi-fan/squeeze3.jpg
>
> http://home.comcast.net/~audi-fan/squeeze4.jpg
>
> Obviously I am finding all of this rather distressing. I realize that
> FW21 is in beta, but I am trying to figure out what is going on here
> so that I can get my unit operational again. If you guys don't have a
> good idea of what is happening here, I would think that Slim Devices
> would want to get ahold of my unit so that they can figure out what
> went wrong with the FW21 update that appears to have corrupted it, or
> maybe someone has other ideas of what could be going on here.
>
> I just want to go back to enjoying the tunes again guys!
>
> -Jason.
>

Graham Scott
2004-05-03, 10:37
If it's of any use Sean, I've seen this happen - just once - when
selecting the Search for Artist menu...flicking back and going into the
option again cured it.

Running v5.1.5

Sean Adams wrote:

>
> Jason,
>
> Those photos are really interesting. In addition to the email I sent
> you, I have some more thoughts for the benefit of others who may be
> interested:
>