[ath9k-devel] Can't associate with a particular AP

[Julien Valroff <julien@kirya.net>]

Le dimanche 23 oct. 2011 ? 18:52:07 (+0200 CEST), Peter Stuge a ?crit?:
> Julien Valroff wrote:
> > > I think it is important to iwconfig eth1 mode monitor before you run
> > > ip link set dev eth1 up, and once you have done that it does not
> > > matter what settings wireshark does or does not do, the mode can't be
> > > changed when the interface is up, so just starting the capture should
> > > work.
> > 
> > I couldn't capture anything this way from the other laptops.
> 
> How does it fail?

No error, simply no packet being capture.

> > > > Cell 01 - Address: BA:F4:8A:C6:C8:44
> > > ..
> > > > Cell 04 - Address: C6:6E:27:A6:BE:A4
> > > 
> > > Which is the actual correct address of your AP? I would expect
> > > c6-6e-27, but the IEEE OUI listing does not have a match for it!
> > 
> > I would also say that, given what I can see from the other laptops.
> 
> I would check the sticker on the AP.

The only MAC being stated on the sticker is the one for the ethernet
interface (as explained, it is the router of my internet provider).

[...]

> > as I have no problem with the same AP with other
> > laptops/smartphones.
> 
> The other laptops likely have different hardware and software. If you
> want you can gather more data by comparing results while you
> eliminate those differences one at a time.

I'll do this.

> > > I would try FreeBSD on that machine. I believe the driver there is
> > > more reliable, and using it can allow you to get more concrete help
> > > from Adrian in case the problem is seen also there.
> > 
> > I will try something like a livecd,
> 
> Might work, but by doing that you are only adding more parameters,
> which is absolutely counter-productive for debugging.

That's just a more convenient way to start.
 
> > I do not want to install FreeBSD.
> 
> This is stupid. Either you want to resolve the problem or you do not.
> If you do not then you would not have posted to the list. If
> installing FreeBSD can help identify the problem then that is
> obviously what you should do.

I can do that, but this will have to wait - as I'd like to supply as many
details as possible, I'd thought that 

> > Or it could be a good opportunity to test Debian GNU/kFreeBSD ;)
> 
> Again a really bad idea. The purpose of using FreeBSD would be to
> get another data point, and to take advantage of Adrian's expertise.

See the smiley at the end of my sentence

> The only way of doing that which makes sense is to use exactly the
> same code that Adrian has; which means you should build the very
> latest fbsd world and kernel, and see what happens. This should be
> really easy given that you have experience from distribution
> development already. Also, this should be absolutely obvious to you
> already. I'm surprised I have to explain it.
> 
> It's simple: Either you want to try to identify the problem, or you
> don't care so much. If you don't care then you can't expect anyone
> else to, and the problem will stay unresolved. You have an
> opportunity to improve ath9k for the benefit of all, and you do not
> want to do it because you would have to install FreeBSD? lolwut?

I have absolutely *no* experience with FreeBSD, and we are talking about my
main laptop, the data of which I need everyday. Before installing FreeBSD, I
need to move 500Gb to another computer which I do not have on hand, this
explains why I am reluctant to install FreeBSD /now/.

Sorry if I haven't understood your initial request, I had considered it as a
"give it a try and see if it works"?

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ <julien@kirya.net> ~ <julien@debian.org>    
 : :'  :  Debian Developer & Free software contributor
 `. `'`   http://www.kirya.net/
   `-     4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1