|
Well, Gustin, I'm not sure what distro you're advising me on, but it's
not 64studio 3b3 :-) There is no /etc/init.d/NetworkManager at all. I
did try disabling the new module as you suggested, but now the wifi
hardware isn't seen in Network Manager at all. Perhaps I'm using the wrong kernel? The linux-rt package was automatically removed by Synaptic during my first general update, and I am running linux-2.6.29-1-multimedia-686. Should I put the linux-rt package back in, going backwards as needed? Or how about that new 2.6.31 rt kernel I keep hearing about? J.E.B. It looks like the newer ath5 driver is being used. Try this: Temporarily change your AP to not require security (for testing only, you do not want this long term).sudo /etc/init.d/NetworkManger stop sudo ifdown wlan0 sudo ip link set wlan0 up sudo iwconfig wlan0 essid <youressid> Now we need to check to see if the wifi device has actually connected to the AP. sudo iwconfig You should see something like this: wlan0 IEEE 802.11abgn ESSID:"myessid" Mode:Managed Frequency:5.18 GHz Access Point: 00:0B:6B:86:EB:AF Bit Rate=54 Mb/s Tx-Power=14 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Power Management:off Link Quality=100/100 Signal level:-50 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Of course your Frequency and link quality will differ (in this example, my machine is connected to an 802.11a AP in the 5Ghz spectrum, and is on the desk next to the AP). If the Mac address after the "Access Point" matches your AP's wireless interface, we need to configure IPv4. Automatic method: Check to see if a dhcp client is running: ps axf | grep dhclient If you do not see one, then start one: sudo dhclient wlan0 Manual method: sudo ip addr add 192.168.0.20/24 dev wlan0 sudo ip route add default via 192.168.0.1 You will also need to configure a DNS server in /etc/resolv.conf Failing the above, we can disable the new ath5k driver to see if there is some weirdness with the newer driver: sudo echo "ath5k" >> /etc/modprobe.d/blacklist Reboot and report. To reverse these changes simply remove ath5k from the end of the /etc/modprobe.d/blacklist file. I have far more experience with the older ath_pci driver as I build my own APs (for fun and for profit) and the ath5k driver has issues acting as an AP. Hope this helps, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKwZipwRXgH3rKGfMRAhD9AJwPQRMlPoK5+dm42VnBArOqrnftLwCdGIPv 8YZYOgn0pg0wkI2ZUYSiTe4= =xjmL -----END PGP SIGNATURE----- _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel |
_______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
