From: "Claudio Roberto França Pereira" <spideybr@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Problems with ath9k: can't authenticate
Date: Fri, 13 Apr 2012 09:44:25 -0300 [thread overview]
Message-ID: <CAGo3Weqrx-K5h__0KbtHLQMaKof7yf0ZntP1HBYsm9kJPXwVBA@mail.gmail.com> (raw)
Hi guys. I'm having problems with my wireless nic, on a notebook. The
card is an ath9k 802.11n wireless adapter. The driver is loaded,
wpa_supplicant and wicd get to recognize them, I can see the
association working correctly, but I can't get the card to
authenticate, it ALWAYS times out. I tried looking at the kernel
documentation for the ath9k driver, but without success. I'll look for
it using the work internet.
Anyway, does anyone with a similar setup had any problems with atheros
nics? And how did you solve it?
Thinking further, I had to enable wireless extensions (wext) to make
wicd handle ath9k. Should I disable it and stick to wpa_supplicant?
Also, I'm using a non-modular kernel, compiling everything in it.
Yesterday I left the notebook making a new modular kernel, with sound
and wireless drivers modular. I'm almost going all the way to
genkernel. Any clues?
I'm running ~amd64, kernel 3.3.0. 3.1.X worked somewhat ok, but I
can't shake the feeling that under Windows this laptop of mine would
work flawlessly. I'm not whining, just wanna find a comparable
configuration, and solve my usability issues.
Thanks
--
Claudio Roberto França Pereira
next reply other threads:[~2012-04-13 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 12:44 Claudio Roberto França Pereira [this message]
2012-04-13 13:43 ` [gentoo-user] Problems with ath9k: can't authenticate Robert David
2012-04-13 20:42 ` Claudio Roberto França Pereira
2012-04-14 2:11 ` Zhu Sha Zang
2012-04-16 14:23 ` Willie WY Wong
2012-04-16 16:57 ` Claudio Roberto França Pereira
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=CAGo3Weqrx-K5h__0KbtHLQMaKof7yf0ZntP1HBYsm9kJPXwVBA@mail.gmail.com \
--to=spideybr@gmail.com \
--cc=gentoo-user@lists.gentoo.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