LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 03-10-2010, 04:33 AM   #1
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Rep: Reputation: 17
Question 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!

Last edited by Galib; 03-10-2010 at 04:35 AM.
 
Old 03-10-2010, 04:51 AM   #2
tallship
Member
 
Registered: Jul 2003
Location: On the Beaches of Super Sunny Southern San Clemente, California USA
Distribution: Slackware - duh!
Posts: 524
Blog Entries: 3

Rep: Reputation: 116Reputation: 116
Exclamation 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
 
Old 03-10-2010, 12:45 PM   #3
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
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. :\
 
Old 03-10-2010, 09:13 PM   #4
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
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 11:30 PM. Reason: Updated Errors
 
Old 03-11-2010, 11:56 AM   #5
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
Bump!
 
Old 03-11-2010, 11:57 AM   #6
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
well /etc/mtab will tell you if it's all ro
 
Old 03-11-2010, 12:03 PM   #7
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
Question

Quote:
Originally Posted by jamescondron View Post
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.
 
Old 03-11-2010, 12:05 PM   #8
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
Well, replicate it and lets see if it is doing so
 
Old 03-11-2010, 12:06 PM   #9
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
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.
 
Old 03-11-2010, 12:15 PM   #10
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
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

Last edited by Galib; 03-11-2010 at 12:16 PM. Reason: Nothing has changed post suspend to RAM, although I get the "read-only" errors posted above.
 
Old 03-11-2010, 12:18 PM   #11
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
Okay, then its the script that has the problems Give me a few minutes and I'll see what I can do with it
 
Old 03-11-2010, 12:23 PM   #12
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
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?
 
Old 03-11-2010, 12:27 PM   #13
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
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

Last edited by Galib; 03-11-2010 at 12:30 PM.
 
Old 03-11-2010, 12:29 PM   #14
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
Odd; you can't type anything on the screen?
 
Old 03-11-2010, 12:33 PM   #15
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
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.

Last edited by Galib; 03-11-2010 at 12:35 PM. Reason: script URL
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Lock screen (requiring password to unlock) when resuming from suspend theoldman Linux - Laptop and Netbook 2 12-17-2009 10:35 PM
Suspend to RAM yegnal Linux - Hardware 1 05-23-2009 07:21 PM
Plz explain Suspend to Disk and Suspend to Ram pkhera_2001 Linux - Newbie 2 02-18-2008 08:23 AM
Unable to unlock session with KDE 3.5.4 swampdog2002 Slackware 4 09-07-2006 12:41 AM
Unable to unlock sessions in kubuntu badbunny Ubuntu 0 03-14-2006 05:33 AM


All times are GMT -5. The time now is 11:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration