From: Christian Lamparter <chunkeey@googlemail.com>
To: Duarte Nuno Gomes <dnunogomes@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: p54pci does not work
Date: Tue, 20 Apr 2010 11:32:31 +0200 [thread overview]
Message-ID: <201004201132.31766.chunkeey@googlemail.com> (raw)
In-Reply-To: <i2u719bd8781004192319ge1e40479oa17f0f5036a6cee@mail.gmail.com>
On Tuesday 20 April 2010 08:19:11 Duarte Nuno Gomes wrote:
> On Tue, Apr 13, 2010 at 6:48 PM, Christian Lamparter
> <chunkeey@googlemail.com> wrote:
> > On Tuesday 13 April 2010 07:47:42 Duarte Nuno Gomes wrote:
> >> it works all ok ... when i visit some websites ( www.rcmadeira.pt.vu is one
> >> of them ), my connection just disconnects and i cannot resume it . i need to
> >> shutdown and re lauch kernel in order to work with wireless again.
> >
> > hrmf, works here no matter how much i try.
> > But let's not get carry away, I guess the problem you are describing
> > has more to do with the amount of data which is transfered.
> > Ideally, you should be able to reproduce this _hang_ with any network
> > benchmarking tools (like iperf / nttcp / netperf (or whatever you prefer)).
> i would if u had a way of having a demon running on some shell and
> know what to check for
> >
> >> here is what dmesg outputs
> >>
> >> No probe response from AP 00:24:17:6c:a5:0e after 500ms, disconnecting.
> >> Phy0 : cannot boot firmware !
> >
> > are you getting these messages in this order? (some timestamps,
> > and maybe p54pci dmesg output while initializing would be jolly nice)
[...]
> >
> > * Wireless setup (Which band (2.4 or 5GHz) ? Do you use WPA/WPA2 with CCMP/TKIP,
> > (you can turn off the hw crypto accelerator by loading p54common with the module
> > parameter nohwcrypt=1 )
>
> 2.4 Ghz with WPA / TKIP
> IT WORKS WITH THAT NOHWCRYPT PARAMETER! ill test a little more !
> just need to figure out now , how to load it with parameter on boot !
> easy task !
echo "options p54common nohwcrypt=1" > /etc/modprobe/p54common.conf,
if you compiled p54common as a module (which I hope you did).
if p54common is built-in, then you'll have to add a p54common.nohwcrypt=1
kernel cmdline parameter.
The (most likely) reason why your AP drops you and does not allow you
to reconnect, is probably due to the "TKIP countermeasures".
What's your Accesspoint/Router and which firmware are you currently using?
Regards,
Chr
prev parent reply other threads:[~2010-04-20 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 5:47 p54pci does not work Duarte Nuno Gomes
2010-04-13 17:48 ` Christian Lamparter
[not found] ` <i2u719bd8781004192319ge1e40479oa17f0f5036a6cee@mail.gmail.com>
2010-04-20 9:32 ` Christian Lamparter [this message]
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=201004201132.31766.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=dnunogomes@gmail.com \
--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).