linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Jerry Quinn <jlquinn@optonline.net>
Cc: linux-wireless@vger.kernel.org, mcgrof@gmail.com, mickflemm@gmail.com
Subject: Re: ath5k can't connect on 5424
Date: Tue, 27 May 2008 20:28:14 -0400	[thread overview]
Message-ID: <20080528002814.GF7779@tuxdriver.com> (raw)
In-Reply-To: <4838A467.1000700@optonline.net>

On Sat, May 24, 2008 at 07:27:35PM -0400, Jerry Quinn wrote:
> Hi.  I just installed compat-wireless 2008-05-24.
>
> The good news is that ath5k now loads into the kernel and can talk to the 
> chip.  However, beyond that, the device doesn't do anything.  During 
> modprobe ath5k, I get
>
>
> ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:03:00.0 to 64
> ath5k_pci 0000:03:00.0: registered as 'phy1'
> phy1: Selected rate control algorithm 'pid'
> ath5k phy1: Atheros AR5424 chip found (MAC: 0xa3, PHY: 0x61)
> udev: renamed network interface wlan0 to ath0
>
> The pci id for the chip is 168c:1014 (rev 01).  This is an IBM Thinkpad 
> T60p, running Debian testing with kernel 2.6.25-2-686, the latest dist 
> kernel available.
>
> When I try to bring up the interface I just get a link is not ready message 
> in the kernel log with no other info.  Also, iwlist ath0 scan gives me no 
> results either (I did ifconfig ath0 up beforehand).
>
> Let me know if there's any further diagnosis I can provide to help out.

You might wish to post the results of running the ath_info tool
available from the madwifi project (sorry, I don't have the URL handy).

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-05-28 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-24 23:27 ath5k can't connect on 5424 Jerry Quinn
2008-05-28  0:28 ` John W. Linville [this message]
2008-05-29  4:57   ` Michael Renzmann
2008-05-29 15:10   ` Jerry Quinn (ibm)
2008-05-29 18:52     ` Pavel Roskin
2008-05-29 19:18       ` Bob Copeland

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=20080528002814.GF7779@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=jlquinn@optonline.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=mickflemm@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).