[Mageia-dev] What the hell is wrong with MGA2s suspend/sleep/hibernate?

[Colin Guthrie]

'Twas brillig, and Johnny A. Solbu at 20/11/12 14:54 did gyre and gimble:
> On Tuesday 20. November 2012 14.29, Barry Jackson wrote:
>> What's the output of
>> # systemctl status network.service ?
> 
> I tested just a few minutes ago:
> http://www.solbu.net/mageia-pm/resume-failure.txt
> 
>> Does it show as disabled?
> 
> No.
> 
>> # systemctl start network.service
>> should start it.
> 
> Did not help. I even tried «restart», to no avail.
> A ping to my gw gave network unreachable.
> And again «ifconfig» and «route -n» was normal.
> 
> The only fix seems to be a complete reboot.

Does "ifdown eth0; ifup eth0" help or is the device managed by Network
Manager? (in which case ifdown+ifup should be noops).

If there is no NM interferance does a stop of the network, removal of
the eth driver kernel module + a modprobe + a start of the network help?

I had to do this on my wifi card a at various points when the kernel
support wavered. Maybe that's the same problem for you?

If this is the case, you can maybe try a newer kernel. I know Thomas was
going to push 3.4 to mga2 at some point.

Col




-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/