[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: F10 -- How do I start AR5413 interface?

Rodney Morris wrote:
On 12/4/08, Robert Moskowitz <rgm htt-consult com> wrote:
Rodney Morris wrote:

On 12/4/08, Robert Moskowitz <rgm htt-consult com> wrote:

Rodney Morris wrote:

The stock F10 kernel should support the ar5413, according to the ath5k
website.[1]  Is the ath5k module being loaded?  What does "lsmod |
grep ath" return?

 dm_multipath 17164 0
 ath5k 112520 0
 mac80211 173668 1 ath5k
 cfg80211 23816 2 ath5k,mac80211

The ath5k module is definitely loaded.  For NetworkManager to use your
wireless card, it must be present in HAL.  Run "lshal" from the
command line and see if "atheros" or "ar5413" appears in the output.

 No. Nothing like that there.

Hmmm. . ..  Other than looking through the log file and dmesg for
anything odd, I only have a couple of more things for you to try.

1.  Edit /etc/modprobe.conf and add "alias wifi0 ath5k", making sure
to include a blank line at the end of the file.  Then, reboot.

NO /etc/modprobe.conf !!!!!!

Why? This is probably why no sound either!

#locate modprobe.conf

# ls -ls /etc/modprobe.d/
total 28
4 -rw-r--r-- 1 root root 52 2008-12-01 11:42 anaconda
4 -rw-r--r-- 1 root root 845 2008-07-23 06:25 blacklist
4 -rw-r--r-- 1 root root 16 2008-01-04 03:43 blacklist-visor
4 -rw-r--r-- 1 root root 26 2008-11-10 13:24 floppy-pnp
4 -rw-r--r-- 1 root root 177 2008-10-01 01:28 i915modeset
8 -rw-r--r-- 1 root root 5766 2008-10-13 06:11 modprobe.conf.dist

2.  If you can obtain your wireless card's MAC address, add an entry
to /etc/udev/rules.d/70-persistent-net, using what is listed for eth0
as a guide.  (I don't know if modifying the udev rules in this manner
is considered the best practice.)
Well it looks like something is recognized:

# iwconfig wlan0
wlan0 IEEE 802.11b ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
wlan0: 0000 0 0 0 0 0 0 0 0 0

If neither of the above work, file a bug (my guess would be against
HAL or udev) and use the madwifi packages from rpmfusion or atrpms
until the bug is fixed.

Challenge with atrpms is kernel patching. I got to like the dkms approach that is available via rpmforge for Centos. I was hoping that things would be more integrated...

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]