From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Levinson Date: Tue, 6 Apr 2010 00:46:54 -0700 Subject: [ath9k-devel] Question about Dlink DWA-556 and rhel 5.5 x86 64 kernel 2.6.18-194.el5 In-Reply-To: References: <23359.75.61.95.54.1270536718.squirrel@webmail.sonic.net> Message-ID: <002101cad55d$553657a0$ffa306e0$@com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Thanks, yea, I noticed this is a development list after I posted, sorry! -----Original Message----- From: Alan [mailto:lameventanas at gmail.com] Sent: Tuesday, April 06, 2010 12:44 AM To: eric at levinsong.com Subject: Re: [ath9k-devel] Question about Dlink DWA-556 and rhel 5.5 x86 64 kernel 2.6.18-194.el5 Dude, you are asking such a newbie question in a mailing list that is supposed to be for kernel development, this is not the right place to ask. A better place would be an irc channel, or your distro's mailing list. Besides all that, you don't even provide enough information. What you are trying to do? I'll assume you are just trying to set your network card in managed mode, and then connect using an access point. Are you are trying to use WEP, WPA, WPA2? Just read the man-pages of iwconfig and wpa_supplicant, or look for these terms in a search engine. I'm sure you will find the answer in 5 minutes if you just look for it. On Tue, Apr 6, 2010 at 3:51 PM, Eric wrote: > I have a Dlink DWA-556 which works great under Windows 7 64 , but under > rhel 5.4, > no go. There wasn't any 64 bit support for NDIS or any support in > madwifi. > > I just upgraded to rhel 5.5. In 5.5, at least I see a wlan0 /dev. If I > try to configure it with the gui tool or the iw cmd line tools, it does > everything except get an IP address and it times out. > > Linux kernel version 2.6.18-194.el5 > > > > Here are some details: > > dmesg: > > ath: EEPROM regdomain: 0x10 > ath: EEPROM indicates we should expect a direct regpair map > ath: Country alpha2 being used: CO > ath: Regpair used: 0x10 > GSI 23 sharing vector 0x4A and IRQ 23 > ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 74 > PCI: Setting latency timer of device 0000:00:1b.0 to 64 > hda_codec: ALC888: BIOS auto-probing. > phy0: Selected rate control algorithm 'ath9k_rate_control' > cfg80211: Calling CRDA for country: CO > cfg80211: Regulatory domain changed to country: CO > (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) > (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 1700 mBm) > (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm) > (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm) > Registered led device: ath9k-phy0::radio > Registered led device: ath9k-phy0::assoc > Registered led device: ath9k-phy0::tx > Registered led device: ath9k-phy0::rx > phy0: Atheros AR5418 MAC/BB Rev:2 AR2133 RF Rev:81: > mem=0xffffc20000040000, irq=169 > ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > lspci: > > 03:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless > Network Adapter (rev 01) > > The iwconfig: > > wlan0 IEEE 802.11bgn ESSID:"levinsong" > Mode:Managed Frequency:2.462 GHz Access Point: 00:22:75:62:3D:B0 > Bit Rate=54 Mb/s Tx-Power=27 dBm > RTS thr:off Fragment thr:off > Encryption key:33B8-BBF2-BD > Power Management:off > Link Quality=61/70 Signal level=-49 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > Any help would be greatly appreciated. > > Eric > eric at levinsong.com > > > _______________________________________________ > ath9k-devel mailing list > ath9k-devel at lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel >