Search Linux Wireless

Re: Broadcom 4318 not working with bleeding edge kernels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 21, 2009 at 10:34 PM, Celejar <celejar@xxxxxxxxx> wrote:
> On Wed, 21 Oct 2009 11:29:17 -0400
> Pavel Roskin <proski@xxxxxxx> wrote:
>
>> On Tue, 2009-10-20 at 21:47 -0400, Celejar wrote:
>>
>> > Oct 17 19:44:19 localhost wpa_supplicant[3477]: Trying to associate
>> > with 00:14:d1:3e:ff:30 (SSID='cranford' freq=2437 MHz) Oct 17
>> > 19:44:19 localhost wpa_supplicant[3477]: Association request to the
>> > driver failed
>>
>> Since the message is from wpa_supplicant, it must be something between
>> wpa_supplicant and mac80211.  I don't think any code in b43 is
>> involved.
>>
>> Perhaps you should include some information about wpa_supplicant, i.e.
>> its version and the command line.  Please try the latest
>> wpa_supplicant. Please try both wext and nl80211 drivers.  That would
>> help understand the extent of the problem.
>
> Version is 0.6.9, from the Debian package version 0.6.9.3.  I don't
> know the exact command line, since I've been invoking it through the
> Debian ifupdown scripts.  I haven't been specifying a backend, and the
> Debian documentation states that wext is used in that case.

'ps -lax -w -w' should show the full command line of currently running
processes. Read the documentation of ps.

also, have a look inside /var/log/wpa_supplicant.log (or wherever
Debian puts it) for the log.

> I have been playing with it some more, and it sometimes works, and
> sometimes doesn't.  The only absolutely consistent pattern that I've
> seen is that (in my limited testing) it seems to always work right
> after unloading / reloading the driver (b43) (or a fresh boot).
>
> As I mentioned, I've been using the Debian ifupdown scripts.  I have
> now tried running wpa_supplicant directly, and so far it has worked
> consistently, with a very minimal, mostly default config:
>
> 'wpa_supplicant -iwlan0 -c/wpa.conf'
>
> where wpa.conf contains:
>
> ctrl_interface=/var/run/wpa_supplicant
>
> network={
>        ssid="my-ssid"
>        psk="my passphrase"
> }
>
>
> So at this point, I guess the problem is something that I need to
> report to Debian, some sort of bugginess with their scripts.  Thanks
> for the help ;)
>
> Celejar
> --
> mailmin.sourceforge.net - remote access via secure (OpenPGP) email
> ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux