Re: Can't resume ThinkPad from suspend

2014-01-31 Thread Suvayu Ali
Hi, On Tue, Jan 28, 2014 at 04:44:06PM +0100, poma wrote: > On 28.01.2014 14:10, Suvayu Ali wrote: > > On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: > >> On 27.01.2014 14:46, Suvayu Ali wrote: > >> … > >>> How do I debug this? How can I get more information why the resume > >>> fails? Th

Re: Can't resume ThinkPad from suspend

2014-01-31 Thread Suvayu Ali
On Wed, Jan 29, 2014 at 08:31:23PM +0100, poma wrote: > On 29.01.2014 17:59, Steven Rosenberg wrote: > > What worked for me was adding a line pointing to my swap space to the > > GRUB bootline: > > > > resume=/dev/path/to/swap > > > > Find where your swap is with swapon: > > > > $ swapon -s > >

Re: Can't resume ThinkPad from suspend

2014-01-29 Thread poma
On 29.01.2014 17:59, Steven Rosenberg wrote: > What worked for me was adding a line pointing to my swap space to the > GRUB bootline: > > resume=/dev/path/to/swap > > Find where your swap is with swapon: > > $ swapon -s SWAP != RAM I'm pretty sure Suvayu wrote "systemd-suspend.service" i.e. abo

Re: Can't resume ThinkPad from suspend

2014-01-29 Thread Steven Rosenberg
What worked for me was adding a line pointing to my swap space to the GRUB bootline: resume=/dev/path/to/swap Find where your swap is with swapon: $ swapon -s I wrote this up here: http://stevenrosenberg.net/blog/linux/fedora/2014_0118_suspend_resume_in_fedora_20 -- Steven Rosenberg http://stev

Re: Can't resume ThinkPad from suspend

2014-01-28 Thread poma
On 28.01.2014 16:44, poma wrote: > On 28.01.2014 14:10, Suvayu Ali wrote: >> On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: >>> On 27.01.2014 14:46, Suvayu Ali wrote: >>> … How do I debug this? How can I get more information why the resume fails? Thanks for any ideas. >>> >>> Fir

Re: Can't resume ThinkPad from suspend

2014-01-28 Thread poma
On 28.01.2014 14:10, Suvayu Ali wrote: > On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: >> On 27.01.2014 14:46, Suvayu Ali wrote: >> … >>> How do I debug this? How can I get more information why the resume >>> fails? Thanks for any ideas. >> >> First check S3/resume without X11, >> # syste

Re: Can't resume ThinkPad from suspend

2014-01-28 Thread Suvayu Ali
On Mon, Jan 27, 2014 at 01:51:41PM +, Hiren Joshi wrote: > I had a similar issue when I moved to the 3.12 kernel, this may be unrelated. > If you have NVidia and the nouveau driver installed, the workaround: > https://ask.fedoraproject.org/en/question/37476/fedora-20-unable-to-boot-after-updat

Re: Can't resume ThinkPad from suspend

2014-01-28 Thread Suvayu Ali
On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: > On 27.01.2014 14:46, Suvayu Ali wrote: > … > > How do I debug this? How can I get more information why the resume > > fails? Thanks for any ideas. > > First check S3/resume without X11, > # systemctl set-default multi-user.target > # system

Re: Can't resume ThinkPad from suspend

2014-01-27 Thread poma
On 27.01.2014 14:46, Suvayu Ali wrote: … > How do I debug this? How can I get more information why the resume > fails? Thanks for any ideas. First check S3/resume without X11, # systemctl set-default multi-user.target # systemctl isolate multi-user.target # systemctl suspend # dmesg -> ACPI & PM

RE: Can't resume ThinkPad from suspend

2014-01-27 Thread Hiren Joshi
worked. But as I say, your problem may be entirely different. Josh. -Original Message- From: users-boun...@lists.fedoraproject.org [mailto:users-boun...@lists.fedoraproject.org] On Behalf Of Suvayu Ali Sent: 27 January 2014 13:47 To: Fedora users Subject: Can't resume ThinkPad from su

Can't resume ThinkPad from suspend

2014-01-27 Thread Suvayu Ali
Hi, I have a new ThinkPad (x240) running 3.12.8-300.fc20.x86_64. I can suspend it just fine, but I can't resume. This is what I see in the journal: Jan 27 03:49:05 localhost systemd[1]: Starting Sleep. -- Subject: Unit sleep.target has begun with start-up -- Defined-By: systemd -- Support: http