LinuxQuestions.org
Page 1 of 3 1 23
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   after suspend to RAM -- unable to unlock or startx (https://www.linuxquestions.org/questions/linux-newbie-8/after-suspend-to-ram-unable-to-unlock-or-startx-794397/)

Galib 03-10-2010 03:33 AM
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/"

Thanks!

tallship 03-10-2010 03:51 AM
Try this thread...
 
This thread might lend some insight into your problem, Although I see you're actually running Windows 7 ;)

http://www.linuxquestions.org/questi...suspend+laptop

Hope that helps :)

Galib 03-10-2010 11:45 AM
It looks as though that everything is getting changed to read only after suspending to RAM. Even if I run
Code:
echo mem > /sys/power/state
it will start back to the desktop but things become unusable. :\

Galib 03-10-2010 08:13 PM
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!

Galib 03-11-2010 10:56 AM
Bump!

jamescondron 03-11-2010 10:57 AM
well /etc/mtab will tell you if it's all ro

Galib 03-11-2010 11:03 AM
Quote:
Originally Posted by jamescondron (Post 3894438)
well /etc/mtab will tell you if it's all ro
I just restarted my system and looked at mtab, looks as though everything has r/w permissions. The problem seems to occur after I suspend to RAM.

jamescondron 03-11-2010 11:05 AM
Well, replicate it and lets see if it is doing so

Galib 03-11-2010 11:06 AM
Sure, give me a sec. I am going to suspend to RAM then look at mtab. I will probably have to hard reset afterwards, so it'll be a min.

Thanks again.

Galib 03-11-2010 11:15 AM
This is what my /etc/mtab looks like, before and after suspend to RAM (the seconds I have before I have to hard reset).
Code:
/dev/root / ext4 rw,barrier=1,data=ordered 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0

jamescondron 03-11-2010 11:18 AM
Okay, then its the script that has the problems ;) Give me a few minutes and I'll see what I can do with it

jamescondron 03-11-2010 11:23 AM
Have you editted this script? Line249, as reported, is giving an error with killall, which isn't on this line in the script provided.

Also, can you give me the exact command you're running for this?

Galib 03-11-2010 11:27 AM
Sure. With Sasha's script, I am doing
Code:
su
password
./suspend mem
That makes my system suspend to RAM sucessfully, it looks like. When I go to wake it up via key press, the
Code:
./suspend: line 249: /bin/killall: Input/output error
appears along with the others. I am unable to run any other commands after the system starts up, not even shutdown, giving me the same error.

My line 249 is
Code:
[ "$(ps ax | grep dhcpcd)" ] && killall -q dhcpcd
Thanks again :)

jamescondron 03-11-2010 11:29 AM
Odd; you can't type anything on the screen?

Galib 03-11-2010 11:33 AM
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.

EDIT:
I am using Sasha's script from here.


All times are GMT -5. The time now is 02:38 PM.
Page 1 of 3 1 23
Show 50 post(s) from this thread on one page