From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ath5k and wpa_supplicant
Date: Mon, 1 Jun 2009 15:46:16 +0100 [thread overview]
Message-ID: <358eca8f0906010746j134d4cd3wf1248021cd6ac687@mail.gmail.com> (raw)
Hi All,
Until gentoo-sources-2.6.29-r5 came out I was able to use my ath5 card
with wpa_supplicant. My /etc/conf.d/net contained:
=============================================
modules=( "wpa_supplicant" )
wpa_supplicant_ath0="-Dmadwifi"
=============================================
All went swimmingly well until I tried to re-emerge wpa_supplicant
after I compiled my new kernel - an error message warned that
CONFIG_KMOD was missing ...
=============================================
* Found sources for kernel version:
* 2.6.29-gentoo-r5
* Checking for suitable kernel configuration options...
* requires CONFIG_KMOD to be set to y or m
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
* Once you have satisfied these options, please try merging
* this package again.
=============================================
I searched for KMOD in vane - couldn't find it in the new kernel
.config. So I concluded that it may be curtains for wpa_supplicant.
I enabled ath5k in the kernel as a module, commented out all the
wpa_supplicant entries in my /etc/conf.d/net and rebooted. When I
plugged in my ath5 cardbus it seems that the device is recognised, the
module loaded, but it cannot associate:
=============================================
* Found 00:1D:A2:86:D1:00 (managed, encrypted)
* Found 00:1D:A2:86:D1:80 (managed, encrypted)
* Found 00:1D:A2:86:D4:C0 (managed, encrypted)
* Found "blah-blah" at 00:1D:A2:86:CF:01 (managed)
* Found 00:1D:A2:86:CF:00 (managed, encrypted)
* Connecting to "blah-blah" in managed mode (WEP Disabled) ...
[ !! ]
* Couldn't associate with any access points on wlan1
* Failed to configure wireless for wlan1 [ !! ]
=============================================
However, running the following commands manually gets me online
without any problems:
=============================================
# modprobe -v ath5k
insmod /lib/modules/2.6.29-gentoo-r5/kernel/drivers/net/wireless/ath5k/ath5k.ko
# ip link set wlan1 up
# iwconfig wlan1 essid any
# dhcpcd wlan1 up
wlan1: dhcpcd 4.0.13 starting
wlan1: broadcasting for a lease
wlan1: offered 10.211.38.232 from 1.1.1.1
wlan1: acknowledged 10.211.38.232 from 1.1.1.1
wlan1: checking 10.211.38.232 is available on attached networks
wlan1: leased 10.211.38.232 for 86400 seconds
=============================================
I am a bit rusty will all this as I did not have to configure it for
years. If I am not doing anything wrong, any idea what I should enter
in my /etc/conf.d/net to allow the device to come up automatically
when plugged in?
--
Regards,
Mick
next reply other threads:[~2009-06-01 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 14:46 Mick [this message]
2009-06-01 17:15 ` [gentoo-user] ath5k and wpa_supplicant Michael Niggli
2009-06-01 18:51 ` Mick
2009-06-01 22:32 ` Michael Niggli
2009-06-01 22:55 ` Neil Bothwick
2009-06-02 5:31 ` Mick
2009-06-02 10:18 ` Stroller
2009-06-02 10:22 ` Neil Bothwick
2009-06-02 10:35 ` Mick
2009-06-02 12:24 ` Mick
2009-06-02 16:09 ` Neil Bothwick
2009-06-03 6:14 ` Mick
2009-06-03 7:54 ` Neil Bothwick
2009-06-03 15:56 ` Paul Hartman
2009-06-05 14:06 ` Mick
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=358eca8f0906010746j134d4cd3wf1248021cd6ac687@mail.gmail.com \
--to=michaelkintzios@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