Re: [Madwifi-users] Atheros modules seem to load fine, but don't seem transmit or receive
Status: Beta
Brought to you by:
otaku
From: Frank K. <ma...@fp...> - 2007-04-13 14:53:14
|
I boot... modprob ath_pci : : then: # ifconfig ath0 down # iwconfig ath0 channel 0 # iwpriv ath0 mode 11g ath0 no private ioctls. # iwconfig ath0 channel 6 # ifconfig ath0 up # iwlist ath0 scan ath0 Interface doesn't support scanning : Bad address # The last thing in dmesg and /var/log/messages is the module load. Frank > On Thu, 2007-04-12 at 21:06 -0500, Frank Kujawski wrote: >> my results: >> >> # iwlist ath0 scan >> ath0 Interface doesn't support scanning : Bad address >> >> # iwconfig ath0 >> ath0 IEEE 802.11a ESSID:"" >> Mode:Managed Frequency:5.24GHz Access Point: >> 00:00:00:00:00:00 >> Bit Rate:0kb/s Tx-Power:14 dBm Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off > > You may want to set the cards to a channel in the 2.4 GHz band. It's > better tested. This should work even if the card is "stuck" in 802.11a: > > ifconfig ath0 down > iwconfig ath0 channel 0 > iwpriv ath0 mode 11g > iwconfig ath0 channel 6 > ifconfig ath0 up > > Make sure the interface is up when scanning. Please see the kernel log > as shown by the dmesg command for possible reasons for this error. > > -- > Regards, > Pavel Roskin > |