I think you have an intel 3945 card... If it is, maybe the ipw3945d daemon gets confused on suspend. I have an 3945 on my notebook, and I need to unload totally the driver before suspend..... Perhaps they are working on a new driver that doesn't have that daemon (called iwlwifi), but I didn't tried it, it's in an early development stage.
Dmitri Hrapof ha scritto: > Emilio Scalise <emisca <at> email.it> writes: > > >> Do the scripts call ifdown at suspend time? >> > yes > >> If you call ifdown, wpa_supplicant process is killed? >> > yes > > Now, after two yeses, it looks strange, but still it doesn't work without > killall and explicit start. Worse, sometimes I have to ifdown/ifup eth1 by > hand > after resume. > > >> To control wpa settings from gnome you could try network-manager, but I >> don't personally like it too much. >> > > I used network-manager, and it worked well with suspend, but it seemed to me > it > started only after user log-on in Gnome (ie no network without X11). Also, it > asked for password to unlock the keyring. > And I was too lazy to install additional programs that make it use the > password > of the current user. Are these issues resolved in Feisty? > > >> I prefer use wpa_supplicant in >> roaming mode. See /usr/share/doc/wpasupplicant/README.modes.gz for an >> howto (it's the third section). >> > > Thanks for info! > > Dmitri > > > -- laptop-testing-team mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/laptop-testing-team