hrm. i got tired of my wifi dropping again and did a quick search.
… Once I am connected the card seems to work good. The problem is that I have to be very close (1 or 2 meters ) to the wifi access point for being able to connect. Once I am connected I can go further away without problems.
sure enough, just walk over to the access point and reconnect. boo. atleast it’s a relatively painless fix till i can figure out what’s going on.
i’m still not happy with the way avahi or NetworkManager start networking in gutsy. i was having an issue with an nm connecting to an open access point instead of my access point, quick look at the NetworkManager faq and i found how to remove essids from NetworkManager.
How do I remove networks I no longer wish to connect to?
From the command line run the following replacing <SSID> with the SSID of the network you wish to remove:
$gconftool-2 –recursive-unset /system/networking/wireless/networks/<SSID>
You can use the “Configuration Editor” (gconf-editor) to browse the networks listed in that configuration directory, but you cannot remove the SSID’s folder using the GUI tool.
[here]
arg. everytime i have to play with ‘gconf’ and ‘tool’ in it reminds me of a windows registry. unix/linux is supposed to use flatfiles for config files! eh, atleast i can remove the unwanted networks/access points now. oh, and if you’re working how nm picks networks….
How does NetworkManager select which wireless network to connect to?
NetworkManager only attempts to automatically connect to networks you have previously told it to connect to. If it finds multiple wireless networks that you have connected to in the past, NetworkManager selects the network one you connected to. If NetworkManager isn’t connecting to the network you want, try to force it to connect to the network you wish to be connected, and NetworkManager will remember that setting next time.
[here]
even better, it looks like debian/ubuntu modified NetworkManager for their distos.
My Card is not recognized by NetworkManager and I am running Debian or Ubuntu:
Debian and Ubuntu modified NetworkManager so that it would not manage any devices listed in /etc/network/interfaces. If you open this file and comment out the lines for the interfaces you want to manage and reboot NetworkManager will see them. **Do not comment out l0**
[here]
bleh. not sure whether to try a new NetworkManager build or just remove it completely and use something else to manage my wifi.
hrm. the rt73 serialmonkey drivers howto didn’t work out so well for me. sweet!
Troubleshooting: If your system hard locks after installing this driver, you should try to install a different kernel, boot into that and follow the guide again.
ha! after installing the new module and rebooting, svgalib recieves a signal 15 and shuts down the machine. booo. after booting into a new kernel it looks like the shuttle is overheating and shutting itself down. arg, gotta figure out how to cool the shuttle down a little more since it has the pvr-500 in it now.
