You are not logged in.
Title tells the story. Using wicd-1.7 I can connect to wireless networks and the connection remains stable. Using various combinations of rc.conf settings, netcfg, /etc/conf.d/wireless getting a connection is impossible at boot time and problematic after boot. The problem occurs on every system I've tested arch on. Wicd works, network startup scripts don't or only occasionally if some magic spell is properly cast. I'm positive I've configured the settings in rc.conf correctly as I've been able to connect using those by some combination of rmmod WLAN_MODULE, modprobe WLAN_MODULE, /etc/rc.d/network restart or netcfg ESSID. The requirement is that I am willing to go through the sequence multiple times.
I have just started testing arch and don't know if the network scripts worked before, but I assume they must have. Were there changes in the network startup scripts recently? I'm seeing many topics in the forums related to wireless problems.
Offline
netcfg has just gotten an upgrade, so try that one (v2.5.2). I've been using netcfg2 for a long time now (and have it installed on multiple systems), and it has always worked for me, so I doubt that your problem (on all your systems) is caused by netcfg.
When you say that it works for you after issuing 'netcfg ESSID', then you should know that this behaviour is wanted - if you want to automatically connect, you should use net-auto-wireless instead of netcfg. If you haven't done that already, you should read the wiki on netcfg, and otherwise you should post your settings:
- /etc/rc.conf
- /etc/network.d/ (profiles)
- info on your network(s), your chipset(s)
etc.
Offline
When I say that netcfg ESSID works after startup, I mean that it works sometimes and that net-auto-wireless failed along with all other options that had the wireless start during boot. I'm not sure which version I tried but this was a new install in December or January and I was ready to remove arch by the end of February. A new version of wicd was released with some bug fixes that kept arch on the systems. Had that failed this laptop would likely have a BSD on it. Probably OpenBSD as I haven't tested that yet.
My current settings are configured for wicd and not causing any significant issues, other than having to reload the wireless driver when resuming from suspend.
Offline