Hi Jonathan, Jonathan E. Brickman wrote: > 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 have not tried 64studio 3b3 yet, but on recent debian it's called /etc/init.d/network-manager Anyways `sudo killall NetworkManager` will have the same result. > 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? I don't think this is a kernel issue. If you succeed configuring it "by hand" as outlined by Gustin below with `iwconfig` it is a network-manager problem, not a kernel/driver issue. Maybe it's even simpler: try hitting the WiFi-en/disable button (Fn+F5?!) or flick the Wifi kill-switch ;) > 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? On 64studio "linux-rt" is only a 'dummy package' that installs the "latest stable kernel", which is linux-2.6.29-1-multimedia-686. If you have a mixed installation with Ubunutu repositories: Ubunutu also provides a package named "linux-rt", which is actually linux-rt_2.6.28.3.1_i386.deb It seems likely that you have a mixed system, which would also explain the NetworkManager vs. network-manager naming difference. Maybe that's the whole issue: Are you mixing different versions of the network-manager-applet and the network-manager service: what does dpkg-query -l network-manager-gnome and pkg-query -l network-manager say? Are they the same version? (0.7.1) Does `nm-tool` detect wlan0 as "Type: 802.11 WiFi" ? Can you detect WiFi-networks by running `sudo iwlist wlan0 scan` ? Anyways. the at5k should be detected as ath0 not wlan0. Is this a new install of 64studio, or did you upgrade from a previous System? It could be due to some relic udev rule: Do you have a file /etc/udev/rules.d/70-persistent-net.rules (`ls /etc/udev/rules.d/*net*` , the name may be slightly different), there might be a clue in there. There's plenty of reasons why things could not work as expected; maybe you once used /etc/iftab with `ifrename` or set up mii-tools.. - or maybe the device is simply defect.. Anyways the issue of Network-manager detecting a WiFi interfaces as "wired" is unprecedented to my knowledge. If the iwconfig steps below work, you can be pragmatic and use wpa_supplicant and wpagui to /work around/ network-manager. > 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. ath5k /should/ work for the AR5212/AR5213 chipset. >> Try this: >> Temporarily change your AP to not require security (for testing only, >> you do not want this long term). Why not? Since most AP ship with password enabled by default, there's too few Free-WiFi access points in this world!! The security involved in that technology is not secure anyway. Just leave it open, share with your neighbors and use SSL when appropriate. >> 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 That won't work. "echo" is executed as root (due to sudo) bit the ">>" are still intepreted by the shell running as normal user. You want echo "ath5k" | sudo tee -a /etc/modprobe.d/blacklist >> Reboot and report. instead of blacklisting & re-booting, you can simply call sudo ifconfig wlan0 down sudo rmmod ath5k But I don't know what either should accomplish but for disabling Wifi. Load a different driver?! madwifi-ng is long time obsolete. >> 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, _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
