[Debian-eeepc-devel] Wireless abrubtly stopped working on 1000

[Robert J. Macomber]

On Tue, Jan 12, 2010 at 10:14:28AM +0100, Christoph Dibak wrote:
> 
> I had such trouble yesterday.  I got alway a "Unknown Error 132" when i
> tried to "ifconfig wlan0 up" on my 1005 HA.  The point was, that I've
> accidental pressed the function key for enabling/disabling wireless
> (Fn + F2).
> Sometimes it's that easy ;)

Sometimes it's not, though.  The wireless is enabled, the wlan0
interface is up, and "iwlist scan" reports back correctly.  It just
doesn't want to actually make the association with the access point.
Just to see if it'd change anything, I toggled the wireless off and
then back on just now, but no change.


> On Mon, Jan 11, 2010 at 12:39:56PM -0800, Robert J. Macomber wrote:
> > This morning the wireless on my Eee abruptly stopped being able to
> > connect to my access point.  It can still see the local set of access
> > points, but when I try to connect with it, the connection fails and
> > kern.log receives a periodic "RTMPCancelTimer failed, Timer hasn't
> > been initialize!" message.
> > 
> > This literally happened "abruptly"; it had connected perfectly fine as
> > usual, but in the middle of an apt-get download it disconnected and
> > hasn't been able to reconnect since.  I've tried down- and upgrading
> > the kernel (its default version is the standard Debian 2.6.30-2) based
> > on half-hopes from googling for the error message, and also tried the
> > firmware-ralink package from Sid, but nothing changes.
> > 
> > Does anyone have any idea what could cause this, or ideas about ways
> > to investigate further?
> > -- 
> > Robert Macomber
-- 
Robert Macomber