Am 20.12.2011 16:11, schrieb Albert W. Hopkins: > At it's core NM is just a daemon. The gnome/kde stuff are just > front-ends that talk to the daemon via dbus when need-be. So likely > it "appears" faster when you boot because the NetworkManager service > is already started and connecting to your AP before you even see X > come up. When you resume, all that other machinery is already up, so > you are waiting on the card and the AP to associate.
Another thing in the game: my home-dir is encrypted. So afai understand NM is only able to read the settings of my user AFTER I logged in (and mounted /home via pam_mount). Correct? So it should be faster after resume ... ? > Question: have you tried associateting with the AP manually? How > long does that take? Have you tried associating with other APs? I did but that was without specifically watching times ... at customers I had other things in mind. Here in my office I currently only have that AP available for now. > Should not take too long unless you have a very slow connection... > it's a 306K file (took me less than 1 second to wget). It's uses the > H.264 video codec so I'm guessing you don't have that. Exactly. Never mind. Thanks anyway. >>> Also, you didn't mention your kernel. Could be an anomaly of >>> your kernel/firmware. >> >> Latest and greatest: >> >> gentoo-sources-3.1.5 ~amd64 ... iwlagn-kernel-module ... with >> firmware net-wireless/iwl6005-ucode-17.168.5.3 >> >> lspci says: >> >> Intel Corporation Centrino Advanced-N 6205 (rev 34) > > Intel Corporation Centrino Wireless-N 1000 here. I guess mine's not > "Advanced" but it's fast :D. I'm on the 3.2 rc's but don't recall > any issues in the 3.1 days... I'm using a different firmware though.. > the iwlwifi.. but maybe it's because my card is different. very likely, yes. I found my firmware by doing some trial-and-error and googling. S
