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