From: Daniel Mierswa <impulze@impulze.org>
To: linux-wireless@vger.kernel.org
Subject: Re: ath5k: works only occasionaly
Date: Thu, 28 May 2009 18:53:24 +0200 [thread overview]
Message-ID: <4A1EC184.7040406@impulze.org> (raw)
In-Reply-To: <1243528150.20853.7.camel@mj>
On 28.05.2009 18:29, Pavel Roskin wrote:
> The current kernel version is more important than the one you tried
> initially. Also, the chip revision from the kernel log may be useful.
Tried several stable releases from 2.6.24 to 2.6.29, current one is
2.6.30-rc6 tag from wireless-testing.git
> The reason for disconnect should be printed before that line.
I will log and save, once I'm at university again.
> It must be from the driver, not from wpa_supplicant.
Figured as much, otherwise it'd be very surprising if wpa_supplicant was
broken over a decade without anyone but me noticing. :)
> Using -Dwext or -Dnl80211 should have no effect on disconnects.
good to know, one thing less.
> If you can, try connecting to an access point with known good signal to
> see if the problem is caused by low signal.
Problem is that I don't have any "known working" APs in public. :-/
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22
next prev parent reply other threads:[~2009-05-28 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 15:32 ath5k: works only occasionaly Daniel Mierswa
2009-05-28 16:29 ` Pavel Roskin
2009-05-28 16:53 ` Daniel Mierswa [this message]
2009-05-28 17:27 ` Bob Copeland
2009-05-28 17:41 ` Daniel Mierswa
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=4A1EC184.7040406@impulze.org \
--to=impulze@impulze.org \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).