I'm dual-booting Slackware and Jolicloud (Ubuntu-based) on my netbook, and noticed that Slackware takes much longer to reconnect to the internet after resuming from suspend to RAM.

Slackware takes about 35-40 seconds to reconnect, but Jolicloud reconnects instantly. This isn't a big enough problem for me to stop using Slackware, but I'd like to try and figure out what Jolicloud is doing to reconnect so fast. Any ideas?

My netbook connects to my router wirelessly (router is using WPA2 encryption), and the IP address is assigned via dhcp.

On Slackware I'm using Wicd, and it hangs the longest at "wpa_supplicant: validating authentication..."

On Jolicloud, I'm using NetworkManager

Note: I've tried using NetworkManager and just configuring my internet through inet1.conf on Slackware, but both took just as long as Wicd.

If you need any more info, let me know.

Thanks

EDIT:
I guess it would probably be a good idea to tell you about my wireless card
It's using the Broadcom STA driver (wl.ko) on both Slackware and Jolicloud

Compare the versions of wpa_suplicant, and look to see if Ubuntu Ubuntu-ized the app with any patches. wpa_supplicant was recently updated in Slackware current to 0.7.3 from 0.6.10.

1 members found this post helpful.

I finally figured it out.

It's not that Slackware takes longer than Jolicloud to connect, they actually take about the same amount of time. It's just that Jolicloud stays connected during suspend.

Here's how I made Slackware do the same:
-Install NetworkManager/network-manager-applet (available on SBo)
-Disable this pm-utils hook that shuts down networking during suspend:

2 members found this post helpful.

...interesting, possibly a workaround for wowlan.

cheers,