Ladies & Gents

Thanks for all the great guidance and insight provide by the users of this site.

The issue: Acer Netbook stuck in suspend2ram loop unless booted to single user or gui (kde).

The system if I remember correctly was first install as Squeeze (testing) and when it went stable was upgraded to Stretch (testing). It served as a multimedia host of sorts in that it was used to play online radio and do some text2speach work. So not really hacked much at all.

I applied patches to it the other day and then the gui would not boot. I discovered that there were to may kernels installed, not sure why that should matter when the system is installed to a single partition but... after finally getting it booted to single user I was able to get the update finished.

Now the gui (kde) will not start and the login is in this continual suspend2ram state. It has done this for a long time when ever it was rebooted and was a pain but as reboots were seldom done babysitting the reboot was not a big deal. Now a much better machine has taken over the multimedia job so the boot issue needs to be fixed.

The netbook has an ssd in it or I wouldn't even mess with it because it is so slow.

I am able to login to the netbook but after about 10 seconds it suspend2ram and the power button flashes orange. Push the power button and it comes back up right where you were and you have about 10 seconds before the repeat.

It does not do this in single user mode, but packages can't be installed or updated.

It also does not do this if you can manage to get it booted to the KDE desktop, which is borked at the moment.

Any idea how to stop this so I stand a chance of figuring out why the gui is borked?

Thanks

FYI: holding the power button to force a power off does not stop the loop, and pulling the battery to force a power off does not stop the loop. As soon as the system comes back up and the gui fails it goes right back into the loop.

as root or normal user brings no joy

Its kludgy - but have you thought about renaming the s2ram executable so it stops running?

It appears that I got it stopped.

I edited /etc/systemd/logind.conf to "ignore" the lid and suspend switches.

:]

Now to see if I can get kde fixed

Thanks szboardstretcher

I didn't see that you had posted. If s2ram is what is doing the suspend I guess that would work. But as you say kludgy. But editing /etc/systemd/logind.conf seams to have worked.

As I remember it the issue first showed up about the time debian pushed systemd onto the machine.

Updating the machine now hoping that the updates will fix kde.

1 members found this post helpful.