[gentoo-user] wicd not restarting after hibernation

[gentoo-user] wicd not restarting after hibernation

[»Q«]

On my amd64 laptop, on resume from hibernation, wicd almost always
fails to restart.  This problem goes back to when I set up the machine,
over a year ago, but it seems to have gotten a lot worse in the last
month or so.

I'm using openrc and sys-power/hibernate-script.  I run mostly stable;
AFAIK stable everything to do with power management, init, and
networking.  I use stable gentoo-sources.  AFAICS, resuming works
normally except for wicd.

The configuration for hibernate-script has:

RestartServices fcron wicd

When it wicd fails to start, in /var/log/messages I see entries like
this:

Apr 23 08:38:28 sepulchrave dbus[1369]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
Apr 23 08:38:28 sepulchrave dbus[1369]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1

`sudo /etc/init.d/wicd start` always works to get it going again.  And
on (re)boot, wicd starts fine.

[gentoo-user] Re: wicd not restarting after hibernation

[james]

»Q« <boxcars <at> gmx.net> writes:


> On my amd64 laptop, on resume from hibernation, wicd almost always
> fails to restart.  This problem goes back to when I set up the machine,
> over a year ago, but it seems to have gotten a lot worse in the last
> month or so.


Shot in the dark: Check (and google for issues with obscure bios settings
for your version of the bios. Sometime a bios upgrade|downgrade can help,
but my understanding is that hibernate on laptops is so varied that 
often some brands do not work even with redmond products.

some marginally useful keywords: PXE and (u)efi

hth,
James

[gentoo-user] Re: wicd not restarting after hibernation [solved]

[»Q«]

On Sat, 25 Apr 2015 21:32:27 +0000 (UTC)
james <wireless@tampabay.rr.com> wrote:

> »Q« <boxcars <at> gmx.net> writes:
>
> > On my amd64 laptop, on resume from hibernation, wicd almost always
> > fails to restart.  This problem goes back to when I set up the
> > machine, over a year ago, but it seems to have gotten a lot worse
> > in the last month or so.  
> 
> Shot in the dark: Check (and google for issues with obscure bios
> settings for your version of the bios. Sometime a bios
> upgrade|downgrade can help, but my understanding is that hibernate on
> laptops is so varied that often some brands do not work even with
> redmond products.
> 
> some marginally useful keywords: PXE and (u)efi

I was hoping someone would hand me a magic bullet so I wouldn't have to
go fishing for that stuff, heh.  Your advice didn't help me directly,
but I think just seeing it in writing was enough to prompt me to some
better thinking than I was doing before, so thanks!

I procrastinated about the search until my brain cell fired and I tried
`hibernate --no-suspend` a few times and found that wicd didn't restart
even when the machine didn't actually hibernate.  Then with wicd
running, I tried just `/etc/init.d/wicd restart` -- every time, it
stopped but failed to restart.  But if I waited a few seconds after
stopping wicd, then it would start.   It was a great relief to have
isolated the problem from the hibernate process itself.

I've solved it by abandoning hibernate's RestartServices directive and
instead stopping and starting wicd more explicitly with

OnSuspend 10 /etc/init.d/wicd stop
OnResume 10 /usr/local/bin/wicd-delayed-start

Where wicd-delayed-start is a script with

/usr/bin/sleep 3 && /etc/init.d/wicd start

I have no idea what's at the root of the apparent timing issue -- I
figure it's that the networking gremlins refuse to be called back to
work too soon once they've been told they can take a break.

In case it helps future searchers, I think the relevant hardware info
is: Lenovo IdeaPad y510p with Intel Corporation Centrino Wireless-N
2230 (rev c4).