From: "Alina Friedrichsen" <x-alina@gmx.net>
To: Hin-Tak Leung <hintak.leung@gmail.com>, Larry.Finger@lwfinger.net
Cc: linux-wireless@vger.kernel.org, maximlevitsky@gmail.com,
kalle.valo@iki.fi, samuel@sortiz.org, linville@tuxdriver.com
Subject: Re: Regression caused by commit e32b1b9a33759e8a83ac566c4c43f23ed5d6343b
Date: Fri, 23 Jan 2009 06:40:53 +0100 [thread overview]
Message-ID: <20090123054053.270710@gmx.net> (raw)
In-Reply-To: <3ace41890901222117q55040043lfcab89fc928422ed@mail.gmail.com>
Hello!
> I don't want to do a "me too", but my rtl8187B broke yesterday after
> upgrading to wireless-testing/compat-wireless head,
> and it worked again today. There are only two patches between
> yesterday and today and one of them is John's revert, so it is
> possible that the rtl8187B is also affected.
>=20
> The symptom is as you said, I can associate and authenticate, but dhc=
p
> won't finish and wpa_suplicant ifdown the device.
> I tried that a few times and restarting NM, modprobe -r/-v, etc. In
> the end it was easier just to blow away the compat-wireless update
> redirectory and revert back to the vendor-shipped kernel modules - an=
d
> hope that it is just a transient problem and the problem would go awa=
y
> when I git fetch next time :-).
I unfortunately can't reproduce the problem with my b43 und my other ca=
rds work fine, too. But I think the problem is that the NetworkManager =
does the following: (And causes with it some low level drivers and wifi=
cards into trouble.)
[99554.112921] wlan0: Set SSID
[99554.113853] wlan0: Set BSSID
[99554.113861] wlan0: Set SSID
[99554.115084] wlan0: Set BSSID
[99554.115091] wlan0: Set SSID
Have you test it manual with the NetworkManager disabled?
Regards
Alina
--=20
Psssst! Schon vom neuen GMX MultiMessenger geh=F6rt? Der kann`s mit all=
en: http://www.gmx.net/de/go/multimessenger
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-23 5:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 2:08 Regression caused by commit e32b1b9a33759e8a83ac566c4c43f23ed5d6343b Larry Finger
2009-01-23 2:14 ` John W. Linville
2009-01-23 2:21 ` Alina Friedrichsen
2009-01-23 5:32 ` Larry Finger
2009-01-23 7:13 ` Alina Friedrichsen
2009-01-23 9:56 ` Sedat Dilek
2009-01-23 12:29 ` Samuel Ortiz
2009-01-23 23:16 ` Alina Friedrichsen
2009-01-23 16:33 ` Larry Finger
2009-01-23 20:18 ` Sedat Dilek
2009-01-23 5:17 ` Hin-Tak Leung
2009-01-23 5:40 ` Alina Friedrichsen [this message]
2009-01-23 15:47 ` Michael Buesch
2009-01-23 15:49 ` John W. Linville
2009-01-23 16:03 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090123054053.270710@gmx.net \
--to=x-alina@gmx.net \
--cc=Larry.Finger@lwfinger.net \
--cc=hintak.leung@gmail.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maximlevitsky@gmail.com \
--cc=samuel@sortiz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.