Crash/Reboot when setting WEP keys in new Boom

[kolding]

I had a weird problem when I got mine. I was trying to connect to my wireless network, which is enabled with WEP instead of WPA (old laptop and Squeezebox 1 holding me back). When I got to the WEP key entrance page, I'd see the row of asterisks (I think), but I couldn't dial in any numbers. After a few seconds of staring at me, the Boom would reboot and start the setup dialogs again. Went through this several times, never being able to enter any WEP key characters.

I was able to fix this by plugging it into a wired connection, and letting it upgrade it's firmware, but I'm not sure that would occur to the less technical. After the firmware upgrade, I was able to easily enter the WEP key. However, at this point, the blank characters were different (not asterisks, or maybe they were asterisks at this point, and something different before). I don't know what version of the firmware was on the box when manufactured, as it's been overwritten now.

Now, I had done something a bit "weird". I'd actually received the box at work, and unpacked it (I love opening presents), plugged it in and turned it on. It connected to a open WiFi net here, but never got to the point of actually connection to a server or SN. Don't know if that somehow impacted it's behavior when I got it home later.

Eric

[ccrome2]

Should we start a troubleshooting page on the wiki, in parallel with the
FAQ?

That way real people that experience the problems can assist in making the
troubleshooting guide.

BTW, the other way to fix that is to do a factory reset.

-Caleb


On Thu, Sep 4, 2008 at 3:06 PM, kolding <
kolding.3f8han1220566203 (AT) no-mx (DOT) forums.slimdevices.com> wrote:

>
> I had a weird problem when I got mine. I was trying to connect to my
> wireless network, which is enabled with WEP instead of WPA (old laptop
> and Squeezebox 1 holding me back). When I got to the WEP key entrance
> page, I'd see the row of asterisks (I think), but I couldn't dial in
> any numbers. After a few seconds of staring at me, the Boom would
> reboot and start the setup dialogs again. Went through this several
> times, never being able to enter any WEP key characters.
>
> I was able to fix this by plugging it into a wired connection, and
> letting it upgrade it's firmware, but I'm not sure that would occur to
> the less technical. After the firmware upgrade, I was able to easily
> enter the WEP key. However, at this point, the blank characters were
> different (not asterisks, or maybe they were asterisks at this point,
> and something different before). I don't know what version of the
> firmware was on the box when manufactured, as it's been overwritten
> now.
>
> Now, I had done something a bit "weird". I'd actually received the box
> at work, and unpacked it (I love opening presents), plugged it in and
> turned it on. It connected to a open WiFi net here, but never got to
> the point of actually connection to a server or SN. Don't know if that
> somehow impacted it's behavior when I got it home later.
>
> Eric
>
>
> --
> kolding
>
> SqueezeBox 2 -> Rotel RSX-1056 -> Totem Acoustic Dreamcatchers
> SqueezeBox 3 -> Rotel RX-1052 -> Vandersteen 1B's
> SqueezeBox Boom
> SliMP3 and Squeezebox 1 -> Retired
> ------------------------------------------------------------------------
> kolding's Profile: http://forums.slimdevices.com/member.php?userid=31
> View this thread: http://forums.slimdevices.com/showthread.php?t=52000
>
>

[JJZolx]

BTW, the other way to fix that is to do a factory reset.

Erm, what about the crasher? Should he file a bug? If a firmware bug requires a factory reset to overcome, wouldn't that be considered a fairly serious problem?

[ccrome2]

The bug has already need filed, fixed, and closed. This is only a
problem for factory firmware, and will be fixed in future builds.

On 9/4/08, JJZolx <JJZolx.3f8opb1220575802 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
> ccrome2;336737 Wrote:
>> BTW, the other way to fix that is to do a factory reset.
>
> Erm, what about the crasher? Should he file a bug? If a firmware bug
> requires a factory reset to overcome, wouldn't that be considered a
> fairly serious problem?
>
>
> --
> JJZolx
>
> Jim
> ------------------------------------------------------------------------
> JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10
> View this thread: http://forums.slimdevices.com/showthread.php?t=52000
>
>

[kolding]

The bug has already need filed, fixed, and closed. This is only a
problem for factory firmware, and will be fixed in future builds.



Great, just wanted to make sure it was known before I filed a bug or whatnot. Probably a good thing to note in a FAQ.

Eric

[oreillymj]

So the easiest fix is just to disable WEP during initial setup. Let the Boom connect to your network via DHCP and update itself.

Then once it's updated, you can set up the wireless security.