hey... regarding toshiba satellite laptops.. and maybe any other atheros chip laptops. i've found the easiest way is to get an external usb wifi dongle, and to get madwifi, fire up system-config-network, and everything you need is there, ready to go. you're up/running wireless in ~5 mins... haven't had this process screw up once... as opposed to fighting out how to get an onboard atheros chipset to properly work. my time is worth way more than $45/hour. the device costs about that much!! peace -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx]On Behalf Of Mike Burger Sent: Friday, September 19, 2008 11:59 AM To: Community assistance, encouragement,and advice for using Fedora. Subject: Re: ath5k won't connect -- sometimes > On Fri, 2008-09-19 at 10:00 -0430, Patrick O'Callaghan wrote: >> Yesterday I ran a Live CD of F9 (i386 KDE version) on a Toshiba laptop. >> I found it could see my Wifi network but somewhat erratically, i.e. the >> connection would bounce up and down every few minutes. The access point >> is about 6 feet away so it's not a signal issue (and my phone connects >> with no problem so the AP is OK as well). >> >> I then went ahead and installed F9 on the hard disk, plugged in an >> Ethernet cable and updated everything via yum. Now the Wifi doesn't work >> at all. I even installed the latest NetworkManager from >> updates-testing-newkey but no joy, even after rebooting. >> >> All I can see in dmesg is a few lines saying: >> >> ath5k_pci 0000:04:00.0: registered as 'phy0' >> ath5k: pky0: Atheros AR2424 chip found (MAC: 0xaO, PHY: 0x61) >> ath5k: pky0: noise floor calibration timeout (2422MHz) >> ath5k: pky0: noise floor calibration timeout (2437MHz) >> >> As regards ifconfig, there are a couple of new interfaces: wlan0 and >> wmaster0, both marked as UP but with no IP addresses. >> >> wpa_supplicant is running, dhclient is not. >> >> The physical Wifi switch is on and the light is lit. >> >> "iwlist wlan0 scanning" gives no results. > > Just to add that I do know about Madwifi, the non-free driver available > from Livna. I've installed it before on pre-F9 systems and have usually > managed to get it working after a fair amount of agony. I was just > hoping not to have to go that route with F9 as it is claimed to have > Atheros support now. > > In any case, I suspect the problem isn't in the actual driver itself but > in some interaction with NM. Just a side note...unsupported by Red Hat/Fedora does not mean non-free. The MadWifi drivers are, as I recall, open source. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscribe@xxxxxxxxxxxxxxxxx -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
