Florian,
I'm glad that worked. What I found with initramfs-tools was that kernels I
built on my workstation were not working on my laptop because they ended up
having hardcoded device references built into the initramfs. Thus must be
especially relevant to people who build kernels for inclusion
On Sun, 23 Jan 2022 17:28:39 -0800
Bruce Perens wrote:
> Isn't this one of the things the "dracut" alternative to
> initramfs-tools was intended to fix?
Hallo Bruce,
thank you for the hint: My system just accomplished the second power-on
(of two, this time from hibernation) with its new
Hi,
Florian Zieboll via Dng writes:
> On Sun, 23 Jan 2022 12:07:07 +0900
> Olaf Meeuwissen via Dng wrote:
>
>> Hi,
>>
>> Florian Zieboll via Dng writes:
>>
>> > On Fri, 21 Jan 2022 10:34:28 -0500
>> > tempforever wrote:
>> >
>> >> Something to check/verify:
>> >> If swap is listed in
Isn't this one of the things the "dracut" alternative to initramfs-tools
was intended to fix?
On Sun, Jan 23, 2022 at 12:42 PM Florian Zieboll via Dng
wrote:
> On Sun, 23 Jan 2022 21:20:56 +0100
> Florian Zieboll via Dng wrote:
>
> > On Sun, 23 Jan 2022 20:29:39 +0100
> > aitor wrote:
> >
> >
On Sun, 23 Jan 2022 21:20:56 +0100
Florian Zieboll via Dng wrote:
> On Sun, 23 Jan 2022 20:29:39 +0100
> aitor wrote:
>
> > If the name swap happens randomly, then the required setting might
> > be:
> >
> > RESUME=none
> >
> > instead of:
> >
> > resume=UUID=
> >
> > in your
On Sun, 23 Jan 2022 20:23:51 +0100
tito via Dng wrote:
> On Fri, 21 Jan 2022 15:45:46 +0100
> Florian Zieboll via Dng wrote:
>
> >
> > Hallo list,
> >
> > after the latest kernel-update (chimaera, from 5.10.0-10-amd64 to
> > 5.10.0-11-amd64), my desktop's initramfs no longer finds the swap
>
On Sun, 23 Jan 2022 20:29:39 +0100
aitor wrote:
> If the name swap happens randomly, then the required setting might be:
>
> RESUME=none
>
> instead of:
>
> resume=UUID=
>
> in your /etc/initramfs-tools/conf.d/resume
>
> HTH,
>
> Aitor
Thank you Aitor, that was the crucial hint, the
On Sun, 23 Jan 2022 20:05:43 +0100
aitor wrote:
> Hi,
>
> On 23/1/22 19:54, Florian Zieboll via Dng wrote:
> > Returning to kernel 5.10.0-10-amd64 does NOT solve the issue, as
> > well as the upgrade to linux-image-5.15.0-0.bpo.2-amd64.
>
> If you are using several kernels, then you should
Hi Florian,
On 21/1/22 15:45, Florian Zieboll via Dng wrote:
Running 'update-initramfs -u' returns the correct UUID "to resume
from", and also adding the line
resume=UUID=
to '/etc/initramfs-tools/conf.d/resume' does not solve the issue:
Booting stalls for half a minute and then
On Sun, 23 Jan 2022 19:54:34 +0100
Florian Zieboll via Dng wrote:
> I also just swapped the cables at the two disks: No change.
Now the disk with the swap partition appears as sdb, persistent over
at least four reboots - so this issue seems to have "disappeared".
On Fri, 21 Jan 2022 15:45:46 +0100
Florian Zieboll via Dng wrote:
>
> Hallo list,
>
> after the latest kernel-update (chimaera, from 5.10.0-10-amd64 to
> 5.10.0-11-amd64), my desktop's initramfs no longer finds the swap
> (suspend/resume) partition.
>
> Running 'update-initramfs -u' returns
Hi,
On 23/1/22 19:54, Florian Zieboll via Dng wrote:
Returning to kernel 5.10.0-10-amd64 does NOT solve the issue, as well
as the upgrade to linux-image-5.15.0-0.bpo.2-amd64.
If you are using several kernels, then you should run:
# update-initramfs -u -k all
to update all the initramfs.
On Fri, 21 Jan 2022 13:29:11 -0600
Hector Gonzalez Jaime via Dng wrote:
>
> On 1/21/22 11:03, Florian Zieboll via Dng wrote:
> > On Fri, 21 Jan 2022 10:34:28 -0500
> > tempforever wrote:
> >
> >> Something to check/verify:
> >> If swap is listed in /etc/fstab, then make sure it is listed by
>
On Sun, 23 Jan 2022 12:07:07 +0900
Olaf Meeuwissen via Dng wrote:
> Hi,
>
> Florian Zieboll via Dng writes:
>
> > On Fri, 21 Jan 2022 10:34:28 -0500
> > tempforever wrote:
> >
> >> Something to check/verify:
> >> If swap is listed in /etc/fstab, then make sure it is listed by
> >> UUID rather
Hi,
Florian Zieboll via Dng writes:
> On Fri, 21 Jan 2022 10:34:28 -0500
> tempforever wrote:
>
>> Something to check/verify:
>> If swap is listed in /etc/fstab, then make sure it is listed by UUID
>> rather than block-id.
>> I mention this, since I have a (commented out) swap line in
Le 21/01/2022 à 15:45, Florian Zieboll via Dng a écrit :
after the latest kernel-update (chimaera, from 5.10.0-10-amd64 to
5.10.0-11-amd64), my desktop's initramfs no longer finds the swap
(suspend/resume) partition.
Running 'update-initramfs -u' returns the correct UUID "to resume
from", and
On 1/21/22 11:03, Florian Zieboll via Dng wrote:
On Fri, 21 Jan 2022 10:34:28 -0500
tempforever wrote:
Something to check/verify:
If swap is listed in /etc/fstab, then make sure it is listed by UUID
rather than block-id.
I mention this, since I have a (commented out) swap line in /etc/fstab
On Fri, 21 Jan 2022 10:34:28 -0500
tempforever wrote:
> Something to check/verify:
> If swap is listed in /etc/fstab, then make sure it is listed by UUID
> rather than block-id.
> I mention this, since I have a (commented out) swap line in /etc/fstab
Yes, in the fstab, the swap partition is
Florian Zieboll via Dng wrote:
> Hallo list,
>
> after the latest kernel-update (chimaera, from 5.10.0-10-amd64 to
> 5.10.0-11-amd64), my desktop's initramfs no longer finds the swap
> (suspend/resume) partition.
>
> Running 'update-initramfs -u' returns the correct UUID "to resume
> from", and
Hallo list,
after the latest kernel-update (chimaera, from 5.10.0-10-amd64 to
5.10.0-11-amd64), my desktop's initramfs no longer finds the swap
(suspend/resume) partition.
Running 'update-initramfs -u' returns the correct UUID "to resume
from", and also adding the line
resume=UUID=
20 matches
Mail list logo
