Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Ahmed Ammar <b33fc0d3@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>, linux-wireless@vger.kernel.org
Subject: Re: B43 will not associate
Date: Wed, 05 Mar 2008 13:16:40 -0500	[thread overview]
Message-ID: <1204741000.9378.6.camel@localhost.localdomain> (raw)
In-Reply-To: <84ac67910803050734t1386a8edx39eb7133c909d9bb@mail.gmail.com>

On Wed, 2008-03-05 at 15:34 +0000, Ahmed Ammar wrote:
> >  It's impossible to debug something, if you don't fscking
> >  tell me your testbed setup and what's going on/wrong.
> 
> Well you don't get what you don't ask for.
> 
> I assume testbed means my hardware.
> 
> x86_64 proc., runnig 2.6.24-rt3 (in 64bit) with gentoo userland
> (64bit). The card in question is a pci card.
> 
> I have tried on 2.6.24 vanilla and the association problem is exactly
> the same. The card can see the AP fine but simply won't associate, as
> you can see in the previous dmesg (wlan1). The capture is was to see
> what packets the b43 driver is sending. I was asked to do this by
> Johannes Berg.

I think Michael was also looking for stuff like your wireless cards.
Kind of pointless to post about your hardware when you exclude the
wireless hardware you're using and the problem you're having is
wireless-related.

1) What's your wlan0?  What driver is it using?
2) What's your wlan1?  What driver is it using?
3) Which interface are you having problems on?

Personally, I was somewhat confused because you (I think) said you were
having problems with _wlan1_, but you referenced wlan0 in other mails.

Dan



  reply	other threads:[~2008-03-05 18:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 19:43 B43 will not associate Ahmed Ammar
2008-03-04 19:47 ` Michael Buesch
2008-03-04 22:13   ` Ahmed Ammar
2008-03-05 14:17     ` Michael Buesch
2008-03-05 15:26       ` Ahmed Ammar
2008-03-05 15:34       ` Ahmed Ammar
2008-03-05 18:16         ` Dan Williams [this message]
2008-03-05 20:53           ` Ahmed Ammar
2008-03-05 21:23             ` Dan Williams
2008-03-06  0:12               ` Ahmed Ammar
2008-03-05 15:49       ` Ahmed Ammar

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=1204741000.9378.6.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=b33fc0d3@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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