LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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-11-2010, 11:35 AM   #16
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69

That probably means they're still in use/busy. Well, what are the logs in /var/log/suspend2* looking like? Where do they cut off?
 
Old 03-11-2010, 01:08 PM   #17
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
The thing is... after I resume, I get into terminal and
Code:
vi /var/log/suspend2.log
only to get an error saying
Code:
-bash: /usr/bin/vi: Input/output error
Although, if I open suspend2.log with vim, I get an empty file. I've tried pico & nano, but it seems as though I can't run anything after resuming. On that note when I exit vim, I get errors at the bottom saying
Code:
E138: Can't write viminfo file /root/.viminfo!
Thanks for helping out, suspend is something that I really need on my laptop
 
Old 03-11-2010, 01:59 PM   #18
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
What about if you ctrl+alt+F1 or F2? Is it that one tty?

Also, you're using an older script:
http://www.linuxquestions.org/questi...cript.-734443/
 
Old 03-11-2010, 02:12 PM   #19
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
I've copied the script found in the URL you gave. Ran that and upon resuming, same issue. This time I tried switching ttys and logging in. Tried tty 2 and 3, still the same errors after logging into them.
 
Old 03-11-2010, 02:16 PM   #20
jamescondron
Member
 
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
Annoying, let me think on it this evening, see what I can come up with.
 
Old 03-11-2010, 02:20 PM   #21
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
No problem. Thanks again, I really appreciate your help.
 
Old 03-13-2010, 01:33 AM   #22
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
Bump
 
Old 03-13-2010, 01:42 AM   #23
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,336

Rep: Reputation: 231Reputation: 231Reputation: 231
Type mount / -o remount,rw to restore the filesystem to read/write.

Last edited by smeezekitty; 03-13-2010 at 01:22 PM.
 
Old 03-13-2010, 01:53 AM   #24
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
When I did
Code:
mount / -o remount,rw
I got the following errors:
Code:
ext4_abort called.
EXT4-fs error (device sda2): ext4_remount: Abort forced by user
mount: block device /dev/sda2 is write-protected, mounting read-only
ext4_abort called.
EXT4-fs error (device sda2): ext4_remount: Abort forced by user
This is after I suspended to RAM and woke it back up, having KDE crash and being in terminal.
 
Old 03-13-2010, 02:10 AM   #25
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,336

Rep: Reputation: 231Reputation: 231Reputation: 231
Quote:
Originally Posted by Galib View Post
When I did
Code:
mount / -o remount,rw
I got the following errors:
Code:
ext4_abort called.
EXT4-fs error (device sda2): ext4_remount: Abort forced by user
mount: block device /dev/sda2 is write-protected, mounting read-only
ext4_abort called.
EXT4-fs error (device sda2): ext4_remount: Abort forced by user
This is after I suspended to RAM and woke it back up, having KDE crash and being in terminal.
Ok...Thats wierd.
 
Old 03-13-2010, 05:58 PM   #26
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
Maybe I've setup something wrong. Anyone that has suspend to RAM working willing to tell me what they've done? I haven't messed with any settings yet, just using the default Suspend to RAM option Slackware 13 64bit came with and Sasha's script.

Thanks!
 
Old 03-13-2010, 06:09 PM   #27
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,336

Rep: Reputation: 231Reputation: 231Reputation: 231
Quote:
Originally Posted by Galib View Post
Maybe I've setup something wrong. Anyone that has suspend to RAM working willing to tell me what they've done? I haven't messed with any settings yet, just using the default Suspend to RAM option Slackware 13 64bit came with and Sasha's script.

Thanks!
Post the output of free -m
 
Old 03-13-2010, 06:16 PM   #28
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
Smile

Code:
ridwan@slackware13:~$ free -m
             total       used       free     shared    buffers     cached
Mem:          3686        976       2710          0         82        445
-/+ buffers/cache:        447       3238
Swap:         7812          0       7812
Here ya go. Thanks again.
 
Old 03-13-2010, 06:28 PM   #29
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,336

Rep: Reputation: 231Reputation: 231Reputation: 231
^ every thing looks good
Did it just start doing it or did you install a different OS?
If its #2 what was the previous OS and how did suspend to RAM work?
 
Old 03-13-2010, 06:30 PM   #30
Galib
Member
 
Registered: Mar 2009
Location: $HOME
Distribution: Slackware64
Posts: 69

Original Poster
Rep: Reputation: 17
I was using Windows 7 before. Just wiped it completly off and put Slackware 13 64bit on it. So to answer your question, it just started doing it out of box on Slackware.
 
  


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 09:35 PM
Suspend to RAM yegnal Linux - Hardware 1 05-23-2009 06:21 PM
Plz explain Suspend to Disk and Suspend to Ram pkhera_2001 Linux - Newbie 2 02-18-2008 07:23 AM
Unable to unlock session with KDE 3.5.4 swampdog2002 Slackware 4 09-06-2006 11:41 PM
Unable to unlock sessions in kubuntu badbunny Ubuntu 0 03-14-2006 04:33 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:21 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