All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Kossifidis <mickflemm@gmail.com>
To: Alf <alf@mypals.org>
Cc: Bob Copeland <me@bobcopeland.com>,
	Tulio Magno Quites Machado Filho <tuliom@quites.com.br>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: ath5k in 2.6.29.1 won't associate with AP
Date: Wed, 6 May 2009 14:54:13 +0300	[thread overview]
Message-ID: <40f31dec0905060454s513c5eeas44389e6527eed1fd@mail.gmail.com> (raw)
In-Reply-To: <200905052142.38780.alf@mypals.org>

2009/5/6 Alf <alf@mypals.org>:
> On Monday 04 May 2009 11:36:06 pm Bob Copeland wrote:
>> Yes, 2413 should work -- also can you try latest
>> wireless-testing tree? =C2=A0It has a boatload of updates for
>> ath5k. =C2=A0If something there works then we can perhaps narrow
>> it down a bit.
>
> I tried it a few days ago and it still didn't work. =C2=A0Even the la=
test
> snapshot from madwifi didn't work. =C2=A0They only thing that has wor=
ked is
> ndiswrapper.
>

Can you please post the full dmesg output when ath5k loads ?



--=20
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-05-06 11:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02 18:18 ath5k in 2.6.29.1 won't associate with AP Alf
2009-05-02 21:14 ` Johannes Berg
2009-05-02 21:16   ` Johannes Berg
2009-05-02 21:53   ` Alf
2009-05-04 22:49     ` Tulio Magno Quites Machado Filho
2009-05-05  5:36       ` Bob Copeland
2009-05-06  3:42         ` Alf
2009-05-06 11:54           ` Nick Kossifidis [this message]
2009-05-07  4:00             ` Alf
2009-05-12 13:36           ` Nick Kossifidis
2009-05-13  5:29             ` Alf

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=40f31dec0905060454s513c5eeas44389e6527eed1fd@mail.gmail.com \
    --to=mickflemm@gmail.com \
    --cc=alf@mypals.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=tuliom@quites.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.