Re: An answer to "Gave up waiting for suspend/resume device"

2019-08-04 Thread Panos Kotzanikolaou
It worked for me too. Thanks a lot!

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-29 Thread Pascal Hambourg
Le 29/09/2017 à 18:31, Larry Dighera a écrit : Note what occurs when there is no image in the swap FS and initramfs is expecting to find one. A swap is not a filesystem. The initramfs does not expect to find a hibernation image. If the swap contains a hibernation image then it is used to

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-29 Thread Larry Dighera
On Sat, 23 Sep 2017 04:42:07 + (UTC), Mark Luxton <truthseek...@yahoo.ca> wrote: >RE:Re: Gave up waiting for suspend/resume device > > >| >| | >Re: Gave up waiting for suspend/resume device > | | > > | > > > >Try:Use blkid to determi

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-28 Thread David Wright
On Thu 28 Sep 2017 at 10:29:27 (+0200), Pascal Hambourg wrote: > Le 28/09/2017 à 09:39, Jimmy Johnson a écrit : > >On 09/27/2017 02:38 AM, Pascal Hambourg wrote: > >>Le 27/09/2017 à 10:37, Jimmy Johnson a écrit : > > > >>>  But if everything is correct and you are using lets say sda1 > >>>as root

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-28 Thread Pascal Hambourg
Le 28/09/2017 à 09:39, Jimmy Johnson a écrit : On 09/27/2017 02:38 AM, Pascal Hambourg wrote: Le 27/09/2017 à 10:37, Jimmy Johnson a écrit :   But if everything is correct and you are using lets say sda1 as root in your fstab your system will use sda1 as the LABEL, I've seen this over and

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-28 Thread Jimmy Johnson
On 09/27/2017 02:38 AM, Pascal Hambourg wrote: Le 27/09/2017 à 10:37, Jimmy Johnson a écrit : On 09/26/2017 02:25 AM, Pascal Hambourg wrote: Le 26/09/2017 à 03:55, Jimmy Johnson a écrit : Hi Mark, while multi-booting I use the device name in fstab, /dev/sd?? none swap sw 0 0, it works for all

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-27 Thread Pascal Hambourg
Le 27/09/2017 à 10:37, Jimmy Johnson a écrit : On 09/26/2017 02:25 AM, Pascal Hambourg wrote: Le 26/09/2017 à 03:55, Jimmy Johnson a écrit : Hi Mark, while multi-booting I use the device name in fstab, /dev/sd?? none swap sw 0 0, it works for all my installed systems. It is not always

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-27 Thread Jimmy Johnson
On 09/26/2017 02:25 AM, Pascal Hambourg wrote: Le 26/09/2017 à 03:55, Jimmy Johnson a écrit : Hi Mark, while multi-booting I use the device name in fstab, /dev/sd?? none swap sw 0 0, it works for all my installed systems. It is not always reliable with multiple drives, because device names

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-26 Thread Pascal Hambourg
Le 26/09/2017 à 03:55, Jimmy Johnson a écrit : Hi Mark, while multi-booting I use the device name in fstab, /dev/sd?? none swap sw 0 0, it works for all my installed systems. It is not always reliable with multiple drives, because device names are not stable across reboots. So it is advised

Re: An answer to "Gave up waiting for suspend/resume device"

2017-09-25 Thread Jimmy Johnson
On 09/22/2017 09:42 PM, Mark Luxton wrote: RE:Re: Gave up waiting for suspend/resume device | | | Re: Gave up waiting for suspend/resume device | | | Try:Use blkid to determine the UUID of your swap partition, and while at it, make sure all other partitions have correct

An answer to "Gave up waiting for suspend/resume device"

2017-09-22 Thread Mark Luxton
RE:Re: Gave up waiting for suspend/resume device | | | Re: Gave up waiting for suspend/resume device | | | Try:Use blkid to determine the UUID of your swap partition, and while at it, make sure all other partitions have correct UUID's in /etc/fstab. Also can use lsblk -f

Re: Gave up waiting for suspend/resume device

2017-08-17 Thread David Christensen
On 08/17/17 17:20, Ben Caradoc-Davies wrote: On 18/08/17 11:27, David Christensen wrote: On 08/17/17 00:44, Curt wrote: On 2017-08-17, David Christensen wrote: Is there a configuration file I can edit so that the kernel does not wait 30 seconds on boot for a

Re: Gave up waiting for suspend/resume device

2017-08-17 Thread Ben Caradoc-Davies
On 18/08/17 11:27, David Christensen wrote: On 08/17/17 00:44, Curt wrote: On 2017-08-17, David Christensen wrote: Is there a configuration file I can edit so that the kernel does not wait 30 seconds on boot for a suspend/resume device? "kernel parameter

Re: Gave up waiting for suspend/resume device

2017-08-17 Thread David Christensen
On 08/17/17 00:44, Curt wrote: On 2017-08-17, David Christensen wrote: Is there a configuration file I can edit so that the kernel does not wait 30 seconds on boot for a suspend/resume device? "kernel parameter 'noresume' or 'resume='" Into which file do I

Re: Gave up waiting for suspend/resume device

2017-08-17 Thread Curt
ter I enter the LUKS passphrase, there is > a ~30 second pause and then the subject message appears: > > Gave up waiting for suspend/resume device > > > As I don't use suspend (or hibernate). > > > STFW, apparently this is a feature, not a bug: > > https://duckduckgo.com/

Gave up waiting for suspend/resume device

2017-08-16 Thread David Christensen
945, Core 2 Duo T7400) with unencrypted /boot, encrypted swap, and encrypted root partitions. When booting every machine, after I enter the LUKS passphrase, there is a ~30 second pause and then the subject message appears: Gave up waiting for suspend/resume device As I don't use

Re: Bug#860543: 'Gave up waiting for suspend/resume device'

2017-05-14 Thread Larry Dighera
gt;> Todays update appears to have caused my Debian Stretch Linux system >> to fail to boot with this error message:  >> >>     "Gave up waiting for suspend/resume device..." > >That (by itself) does not indicate a boot failure; it only means that >resume from

'Gave up waiting for suspend/resume device'

2017-05-12 Thread Larry Dighera
Dear Mr. Hutchings, Todays update appears to have caused my Debian Stretch Linux system to fail to boot with this error message:     "Gave up waiting for suspend/resume device..." The Grub menu is still accessible, but I'm clueless how to return the system to operational status. Plea

Re: multiple drives, 'Gave up waiting for suspend/resume device'

2017-04-25 Thread Felix Miata
gt; All other references in fstab to the target drive. > > If remove one of the drives, the new install has problems booting with > or without the second swap. Booting takes a very long time, etc... One > message is 'Gave up waiting for suspend/resume device'. > > Here is a

multiple drives, 'Gave up waiting for suspend/resume device'

2017-04-25 Thread craigswin
problems booting with or without the second swap. Booting takes a very long time, etc... One message is 'Gave up waiting for suspend/resume device'. Here is a possibly related thread: https://mail-archive.com/debian-bugs-dist@lists.debian.org/msg1513355.html When the boot menu appears, grub