after suspend to RAM -- unable to unlock or startx
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after suspend to RAM -- unable to unlock or startx
I am using Slackware 13 x86_4. I have it set so that when I close my lid, it suspends to RAM. When I open my lid, it asks for password, but after I enter it, it freezes. I force KDE down by Ctrl+Alt+Backspace then read the errors. It says:
Code:
xauth: error in locking authority file /home/ridwan/.Xauthority
rm: cannot remove '/home/ridwan/.serverauth.3457': Read-only file system
When I try to startx again, it says
Code:
/usr/bin/startx: line 158: cannot create temp file for here document: Read-only file system
/usr/bin/startx: line 174: cannot create temp file for here document: Read-only file system
/usr/bin/startx: line 174: cannot create temp file for here document: Read-only file system
Fatal server error:
Could not create lock file in /tmp/.tX0-lock
xauth: error in locking authority file /home/ridwan/.Xauthority
rm: cannot remove '/home/ridwan/.serverauth.4151': Read-only file system
It forces me to power off the laptop by holding down the power button. When I try ctrl+alt+delete, I get an error saying "can't execute from /sbin/shutdown/"
I've used Sasha's script and although it will allow me to resume my system after suspending to RAM, I have the same error with KDE. Whenever I try to open Home or click on any buttons, it doesn't allow it saying that it is "malformatted". I shut down x and try to restart again, followed by the same Read-only file system errors.
Here's what I get in konsole after my computer is revived from ./suspend mem using Sasha's script.
Code:
Cannot open '/var/log/kernel' for reading: No such file or directory
/usr/bin/tail: no files remaining
./suspend: line 249: /bin/killall: Input/output error
err, eth0: open '/etc/dhcpc/hdcpcd-th0.pid' : Ready-only file system
rm: cannot remove '/var/run/suspend2_logpid' : Read-only file system
rm: cannot remove '/var/run/suspend2_forkpid' : Read-only file system
It seems to me after my computer suspends and returns to KDE, the entire HDD is read-only? I am unable to run any commands. I am using an NVIDIA 8000 M Video card with the latest drivers, on a Compaq CQ-60.
Thanks again!
Last edited by Galib; 03-10-2010 at 10:30 PM.
Reason: Updated Errors
After my computer is revived from suspend to RAM, my KDE screen slowly deteriorates, forcing me to Ctrl+Alt+Backspace my way into the terminal. Once in the terminal, if I try to startx I get the errors I posted in the original post. If I try to run any other commands, such as shutdown -h now, I get errors like can't execute from /sbin/shutdown -- Input/output error. I also checked the entire / directory with ls -l, everything has the proper accessibility for root, even though root can not run anything either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.