PDA

View Full Version : still see display corruption and crashes



Jan Vilhuber
2004-08-17, 14:33
I've updated to firmware 33, using yesterday's nightly (08-16 I think),
and I still see display corruption after some time, i.e. the characters
on the display start running into each other. The only way to recover is
a power-cycle, which is annoying.

Also, the squeezeboxen seem to crash at time (go blank, requuire
power-cycle).

Interestingly, the squeezebox that has the display issue is the one
sitting behind the wireless bridge (neither of my squeezeboxen are
wireless). Maybe I'll swap them out to see if the wireless bridge makes
a difference.

Also, I think the squeezebox is the one I upgraded with the new
display...

jan

Michael Brouwer
2004-08-17, 16:35
I've had the same problem with firmware 33 and an upgraded wireless
squeezebox. The other (perhaps related) problem I've seen is that when
you display names containing special characters like Björk, it first
displays as garbage (BjAErk or something like that) for a moment and
then displays correctly.

Michael

On Aug 17, 2004, at 2:33 PM, Jan Vilhuber wrote:

> I've updated to firmware 33, using yesterday's nightly (08-16 I think),
> and I still see display corruption after some time, i.e. the characters
> on the display start running into each other. The only way to recover
> is
> a power-cycle, which is annoying.
>
> Also, the squeezeboxen seem to crash at time (go blank, requuire
> power-cycle).
>
> Interestingly, the squeezebox that has the display issue is the one
> sitting behind the wireless bridge (neither of my squeezeboxen are
> wireless). Maybe I'll swap them out to see if the wireless bridge makes
> a difference.
>
> Also, I think the squeezebox is the one I upgraded with the new
> display...
>
> jan
>
>
>

Jan Vilhuber
2004-08-17, 17:50
OK, I've exchanged the squeezeboxen (the one with the problem that WAS
behind a wireless bridge is now wired, and the one that WAS wired is now
behind the wireless bridge). I'll report when/if anything changes.

jan


On Tue, 2004-08-17 at 16:35, Michael Brouwer wrote:
> I've had the same problem with firmware 33 and an upgraded wireless
> squeezebox. The other (perhaps related) problem I've seen is that when
> you display names containing special characters like Björk, it first
> displays as garbage (BjAErk or something like that) for a moment and
> then displays correctly.
>
> Michael
>
> On Aug 17, 2004, at 2:33 PM, Jan Vilhuber wrote:
>
> > I've updated to firmware 33, using yesterday's nightly (08-16 I think),
> > and I still see display corruption after some time, i.e. the characters
> > on the display start running into each other. The only way to recover
> > is
> > a power-cycle, which is annoying.
> >
> > Also, the squeezeboxen seem to crash at time (go blank, requuire
> > power-cycle).
> >
> > Interestingly, the squeezebox that has the display issue is the one
> > sitting behind the wireless bridge (neither of my squeezeboxen are
> > wireless). Maybe I'll swap them out to see if the wireless bridge makes
> > a difference.
> >
> > Also, I think the squeezebox is the one I upgraded with the new
> > display...
> >
> > jan
> >
> >
> >

Jan Vilhuber
2004-08-18, 10:35
There's good news and bad news: The good news is that it doesn't seem to
have anything to do with upgrading a Squeezebox.

The bad news is that it's still happening, but now it's the squeezebox
that previously was wired, and now sits behind a wireless hub.

I'm wondering of the added latency of the wireless network is somehow
causing a mess with the display somehow.

Thoughts?
jan


On Tue, 2004-08-17 at 16:35, Michael Brouwer wrote:
> I've had the same problem with firmware 33 and an upgraded wireless
> squeezebox. The other (perhaps related) problem I've seen is that when
> you display names containing special characters like Björk, it first
> displays as garbage (BjAErk or something like that) for a moment and
> then displays correctly.
>
> Michael
>
> On Aug 17, 2004, at 2:33 PM, Jan Vilhuber wrote:
>
> > I've updated to firmware 33, using yesterday's nightly (08-16 I think),
> > and I still see display corruption after some time, i.e. the characters
> > on the display start running into each other. The only way to recover
> > is
> > a power-cycle, which is annoying.
> >
> > Also, the squeezeboxen seem to crash at time (go blank, requuire
> > power-cycle).
> >
> > Interestingly, the squeezebox that has the display issue is the one
> > sitting behind the wireless bridge (neither of my squeezeboxen are
> > wireless). Maybe I'll swap them out to see if the wireless bridge makes
> > a difference.
> >
> > Also, I think the squeezebox is the one I upgraded with the new
> > display...
> >
> > jan
> >
> >
> >

dean
2004-08-18, 10:46
Jan,

I'm looking into the Bjork problem now. What OS are you running? If
it's not Mac or Windows, what version of Perl do you have installed?

The display corruption is what Sean's working on now...

-dean


On Aug 18, 2004, at 10:35 AM, Jan Vilhuber wrote:

> There's good news and bad news: The good news is that it doesn't seem
> to
> have anything to do with upgrading a Squeezebox.
>
> The bad news is that it's still happening, but now it's the squeezebox
> that previously was wired, and now sits behind a wireless hub.
>
> I'm wondering of the added latency of the wireless network is somehow
> causing a mess with the display somehow.
>
> Thoughts?
> jan
>
>
> On Tue, 2004-08-17 at 16:35, Michael Brouwer wrote:
>> I've had the same problem with firmware 33 and an upgraded wireless
>> squeezebox. The other (perhaps related) problem I've seen is that
>> when
>> you display names containing special characters like Björk, it first
>> displays as garbage (BjAErk or something like that) for a moment and
>> then displays correctly.
>>
>> Michael
>>
>> On Aug 17, 2004, at 2:33 PM, Jan Vilhuber wrote:
>>
>>> I've updated to firmware 33, using yesterday's nightly (08-16 I
>>> think),
>>> and I still see display corruption after some time, i.e. the
>>> characters
>>> on the display start running into each other. The only way to recover
>>> is
>>> a power-cycle, which is annoying.
>>>
>>> Also, the squeezeboxen seem to crash at time (go blank, requuire
>>> power-cycle).
>>>
>>> Interestingly, the squeezebox that has the display issue is the one
>>> sitting behind the wireless bridge (neither of my squeezeboxen are
>>> wireless). Maybe I'll swap them out to see if the wireless bridge
>>> makes
>>> a difference.
>>>
>>> Also, I think the squeezebox is the one I upgraded with the new
>>> display...
>>>
>>> jan
>>>
>>>
>>>

Jan Vilhuber
2004-08-18, 11:11
On Wed, 2004-08-18 at 10:46, dean blackketter wrote:
> Jan,
>
> I'm looking into the Bjork problem now.

I'm not sure if that's the problem I'm seeing or not. I usually see this
when the bottom line is scrolling. I haven't done any more testing, but
if I listen to the (Ottot's?) Baroque Classical music shoutcast stream,
it's almost guaranteed to happen. Maybe there's umlaut characters in the
stream description at times which could cause this. I don't know for
sure.

> What OS are you running? If
> it's not Mac or Windows, what version of Perl do you have installed?
>

vilhuber@mediapc:~> perl -v

This is perl, v5.8.3 built for i586-linux-thread-multi


vilhuber@mediapc:~> uname -a
Linux mediapc 2.6.5-7.104-default #1 Thu Aug 5 19:14:08 PDT 2004 i686
athlon i386 GNU/Linux
vilhuber@mediapc:~>

> The display corruption is what Sean's working on now...
>

Let me know if I can gather any other info or do any tests (or run test
code).

jan


> -dean
>
>
> On Aug 18, 2004, at 10:35 AM, Jan Vilhuber wrote:
>
> > There's good news and bad news: The good news is that it doesn't seem
> > to
> > have anything to do with upgrading a Squeezebox.
> >
> > The bad news is that it's still happening, but now it's the squeezebox
> > that previously was wired, and now sits behind a wireless hub.
> >
> > I'm wondering of the added latency of the wireless network is somehow
> > causing a mess with the display somehow.
> >
> > Thoughts?
> > jan
> >
> >
> > On Tue, 2004-08-17 at 16:35, Michael Brouwer wrote:
> >> I've had the same problem with firmware 33 and an upgraded wireless
> >> squeezebox. The other (perhaps related) problem I've seen is that
> >> when
> >> you display names containing special characters like Björk, it first
> >> displays as garbage (BjAErk or something like that) for a moment and
> >> then displays correctly.
> >>
> >> Michael
> >>
> >> On Aug 17, 2004, at 2:33 PM, Jan Vilhuber wrote:
> >>
> >>> I've updated to firmware 33, using yesterday's nightly (08-16 I
> >>> think),
> >>> and I still see display corruption after some time, i.e. the
> >>> characters
> >>> on the display start running into each other. The only way to recover
> >>> is
> >>> a power-cycle, which is annoying.
> >>>
> >>> Also, the squeezeboxen seem to crash at time (go blank, requuire
> >>> power-cycle).
> >>>
> >>> Interestingly, the squeezebox that has the display issue is the one
> >>> sitting behind the wireless bridge (neither of my squeezeboxen are
> >>> wireless). Maybe I'll swap them out to see if the wireless bridge
> >>> makes
> >>> a difference.
> >>>
> >>> Also, I think the squeezebox is the one I upgraded with the new
> >>> display...
> >>>
> >>> jan
> >>>
> >>>
> >>>

dean
2004-08-18, 13:07
Hi Jan,

On Aug 18, 2004, at 11:11 AM, Jan Vilhuber wrote:

> On Wed, 2004-08-18 at 10:46, dean blackketter wrote:
>> Jan,
>>
>> I'm looking into the Bjork problem now.
>
> I'm not sure if that's the problem I'm seeing or not. I usually see
> this
> when the bottom line is scrolling. I haven't done any more testing, but
> if I listen to the (Ottot's?) Baroque Classical music shoutcast stream,
> it's almost guaranteed to happen. Maybe there's umlaut characters in
> the
> stream description at times which could cause this. I don't know for
> sure.
I'm only able to reproduce it on my Linux machine as well, I've got a
case, but it's very low level so it's taking me a while to figure it
out.


>> The display corruption is what Sean's working on now...
>>
>
> Let me know if I can gather any other info or do any tests (or run test
> code).
Sean's got a reproduceable case now, so it's just a matter of him being
able to track down the culprit.

-dean