From: Dan Williams <dcbw@redhat.com>
To: Irwan Siajadi <dev.bahamot@yahoo.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath5k: can't browse at all.
Date: Mon, 24 Nov 2008 13:54:32 -0500 [thread overview]
Message-ID: <1227552872.25089.3.camel@localhost.localdomain> (raw)
In-Reply-To: <978525.69086.qm@web59613.mail.ac4.yahoo.com>
On Mon, 2008-11-24 at 09:41 -0800, Irwan Siajadi wrote:
> The AR2425 is able to obtain IP address from the router,
> able to ping with good results, but can't browse at all.
> Below are the info on my setup, if you need more info please let me know.
Can you traceroute to some IP, say like 4.2.2.1 or 4.2.2.2?
Dan
> Driver version: compat-wireless-2008-11-24.tar.bz2.
> Kernel: 2.6.27.4-2mnbcustom (mandriva), compiled with mandriva provided
> ..config but without any WLAN support except WIRELESS_EXT.
> Access point/router is configured to use channel 1 (2.412GHz).
>
> dmesg:
> "...
> cfg80211: Using static regulatory domain info
> cfg80211: Regulatory domain: JP
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2494000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
> (5160000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
> (5250000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
> cfg80211: Calling CRDA for country: JP
> .....
> ath5k 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> ath5k 0000:05:00.0: setting latency timer to 64
> ath5k 0000:05:00.0: registered as 'phy0'
> phy0: Selected rate control algorithm 'minstrel'
> ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
> .....
> wlan0: authenticate with AP 00:04:ed:42:60:67
> wlan0: authenticated
> wlan0: associate with AP 00:04:ed:42:60:67
> wlan0: RX AssocResp from 00:04:ed:42:60:67 (capab=3D0x431 status=3D0 id=3D)
> wlan0: associated
> ....."
>
> lspci:
> "05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg
> Wireless PCI Express Adapter (rev 01)
> Subsystem: Device 1a3b:1026
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at feaf0000 (64-bit, non-prefetchable) [size=3D64K]
> Capabilities: [40] Power Management version 2
> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit Queue=3D0/0 Enable-
> Capabilities: [60] Express Legacy Endpoint, MSI 00
> Capabilities: [90] MSI-X: Enable- Mask- TabSize=3D1
> Capabilities: [100] Advanced Error Reporting <?>
> Capabilities: [140] Virtual Channel <?>"
>
> TIA,
> Irwan.
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-24 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 17:41 ath5k: can't browse at all Irwan Siajadi
2008-11-24 18:53 ` Pavel Roskin
2008-11-25 2:36 ` Irwan Siajadi
2008-11-25 17:24 ` Irwan Siajadi
2008-11-25 20:02 ` Pavel Roskin
2008-11-30 16:53 ` Irwan Siajadi
2008-12-01 17:11 ` Luis R. Rodriguez
2008-11-24 18:54 ` Dan Williams [this message]
2008-11-25 2:30 ` Irwan Siajadi
-- strict thread matches above, loose matches on Subject: below --
2008-12-02 3:11 Irwan Siajadi
2008-12-01 21:36 ` Luis R. Rodriguez
2008-12-02 7:27 ` Irwan Siajadi
2008-12-02 8:00 ` Luis R. Rodriguez
2008-12-02 13:04 ` Irwan Siajadi
2008-12-07 19:39 ` Irwan Siajadi
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=1227552872.25089.3.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=dev.bahamot@yahoo.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).