Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #245166 > unrolled thread

dpkg in Bookworm insists to rebuild initrd

Back to article view | Back to linux.debian.user

Contents

  dpkg in Bookworm insists to rebuild initrd Felix Miata <mrmazda@earthlink.net> - 2022-02-10 05:20 +0100
    Re: dpkg in Bookworm insists to rebuild initrd David Wright <deblis@lionunicorn.co.uk> - 2022-02-10 06:40 +0100
      Re: dpkg in Bookworm insists to rebuild initrd Felix Miata <mrmazda@earthlink.net> - 2022-02-10 08:50 +0100
        Re: dpkg in Bookworm insists to rebuild initrd David Wright <deblis@lionunicorn.co.uk> - 2022-02-10 16:30 +0100
    Re: dpkg in Bookworm insists to rebuild initrd Greg Wooledge <greg@wooledge.org> - 2022-02-10 13:30 +0100

#245166 — dpkg in Bookworm insists to rebuild initrd

# inxi -S
System:
  Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
    Distro: Debian GNU/Linux bookworm/sid
# dpkg --configure linux-image-5.15.0-3-amd64
Setting up linux-image-5.15.0-3-amd64 (5.15.15-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-3-amd64
mv: cannot move '/boot/initrd.img-5.15.0-3-amd64.new' to
'/boot/initrd.img-5.15.0-3-amd64': Operation not permitted
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-3-amd64 (--configure):
 installed linux-image-5.15.0-3-amd64 package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 linux-image-5.15.0-3-amd64
#

What can be done to make dpkg stop trying to replace the initrd that I have made
immutable? I don't want it replaced. Nothing (now) in 5.15 will solve the problem
that needs the solution reported here:
https://gitlab.freedesktop.org/drm/intel/-/issues/4762

The problem is dual displays cannot be used until after POST on LGA1200
motherboards with Intel a5## chipset and motherboard BIOS from Asus and ASRock.
So, I need a 5.17 kernel. Anything to do with 5.15 is a waste of time, unless and
untl the 4762 fix gets backported, or the motherboard makers release a fixed BIOS.
I don't want to beat up my SSD rebuilding bloated initrds needlessly, and dpkg
here is ignoring update_initramfs=no in update-initramfs.conf. :(
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

[toc] | [next] | [standalone]

#245167

On Wed 09 Feb 2022 at 23:09:40 (-0500), Felix Miata wrote:
> # inxi -S
> System:
>   Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
>     Distro: Debian GNU/Linux bookworm/sid
> # dpkg --configure linux-image-5.15.0-3-amd64
> Setting up linux-image-5.15.0-3-amd64 (5.15.15-2) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-5.15.0-3-amd64
> mv: cannot move '/boot/initrd.img-5.15.0-3-amd64.new' to
> '/boot/initrd.img-5.15.0-3-amd64': Operation not permitted
> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> dpkg: error processing package linux-image-5.15.0-3-amd64 (--configure):
>  installed linux-image-5.15.0-3-amd64 package post-installation script subprocess
> returned error exit status 1
> Errors were encountered while processing:
>  linux-image-5.15.0-3-amd64
> #
> 
> What can be done to make dpkg stop trying to replace the initrd that I have made
> immutable? I don't want it replaced. Nothing (now) in 5.15 will solve the problem
> that needs the solution reported here:
> https://gitlab.freedesktop.org/drm/intel/-/issues/4762

Would:

# INITRD='No' dpkg --configure linux-image-5.15.0-3-amd64

manage to propagate INITRD through to the third¹ test in
/etc/kernel/postinst.d/initramfs-tools?

¹ I'm reading buster; adjust as necessary.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#245168

David Wright composed on 2022-02-09 23:36 (UTC-0600):

> On Wed 09 Feb 2022 at 23:09:40 (-0500), Felix Miata wrote:

>> # inxi -S
>> System:
>>   Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
>>     Distro: Debian GNU/Linux bookworm/sid
>> # dpkg --configure linux-image-5.15.0-3-amd64
>> Setting up linux-image-5.15.0-3-amd64 (5.15.15-2) ...
>> /etc/kernel/postinst.d/initramfs-tools:
>> update-initramfs: Generating /boot/initrd.img-5.15.0-3-amd64
>> mv: cannot move '/boot/initrd.img-5.15.0-3-amd64.new' to
>> '/boot/initrd.img-5.15.0-3-amd64': Operation not permitted
>> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>> dpkg: error processing package linux-image-5.15.0-3-amd64 (--configure):
>>  installed linux-image-5.15.0-3-amd64 package post-installation script subprocess
>> returned error exit status 1
>> Errors were encountered while processing:
>>  linux-image-5.15.0-3-amd64
>> #
 
>> What can be done to make dpkg stop trying to replace the initrd that I have made
>> immutable? I don't want it replaced. Nothing (now) in 5.15 will solve the problem
>> that needs the solution reported here:
>> https://gitlab.freedesktop.org/drm/intel/-/issues/4762
 
> Would:
 
> # INITRD='No' dpkg --configure linux-image-5.15.0-3-amd64
 
> manage to propagate INITRD through to the third¹ test in
> /etc/kernel/postinst.d/initramfs-tools?
 
> ¹ I'm reading buster; adjust as necessary.

Didn't help. But, I don't know if your third test equates to my third
test. What I did was prepend # to the last line in that file:

# cat initramfs-tools
#!/bin/sh -e

version="$1"
bootopt=""

command -v update-initramfs >/dev/null 2>&1 || exit 0

# passing the kernel version is required
if [ -z "${version}" ]; then
        echo >&2 "W: initramfs-tools: ${DPKG_MAINTSCRIPT_PACKAGE:-kernel package} did not pass a version number"
        exit 2
fi

# exit if kernel does not need an initramfs
if [ "$INITRD" = 'No' ]; then
        exit 0
fi

# absolute file name of kernel image may be passed as a second argument;
# create the initrd in the same directory
if [ -n "$2" ]; then
        bootdir=$(dirname "$2")
        bootopt="-b ${bootdir}"
fi

# avoid running multiple times
if [ -n "$DEB_MAINT_PARAMS" ]; then
        eval set -- "$DEB_MAINT_PARAMS"
        if [ -z "$1" ] || [ "$1" != "configure" ]; then
                exit 0
        fi
fi

# we're good - create initramfs.  update runs do_bootloader
# shellcheck disable=SC2086
#update-initramfs -c -k "${version}" ${bootopt} >&2

Thanks. That pacified the scripts. Now I can get on with finding a
kernel that supports booting with two displays connected at boot,
if there exists one packaged for Debian yet. ;)
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

[toc] | [prev] | [next] | [standalone]

#245178

On Thu 10 Feb 2022 at 02:44:50 (-0500), Felix Miata wrote:
> David Wright composed on 2022-02-09 23:36 (UTC-0600):
> > On Wed 09 Feb 2022 at 23:09:40 (-0500), Felix Miata wrote:
> 
> >> # inxi -S
> >> System:
> >>   Host: ab560 Kernel: 5.15.0-3-amd64 x86_64 bits: 64 Desktop: Trinity
> >>     Distro: Debian GNU/Linux bookworm/sid
> >> # dpkg --configure linux-image-5.15.0-3-amd64
> >> Setting up linux-image-5.15.0-3-amd64 (5.15.15-2) ...
> >> /etc/kernel/postinst.d/initramfs-tools:
> >> update-initramfs: Generating /boot/initrd.img-5.15.0-3-amd64
> >> mv: cannot move '/boot/initrd.img-5.15.0-3-amd64.new' to
> >> '/boot/initrd.img-5.15.0-3-amd64': Operation not permitted
> >> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> >> dpkg: error processing package linux-image-5.15.0-3-amd64 (--configure):
> >>  installed linux-image-5.15.0-3-amd64 package post-installation script subprocess
> >> returned error exit status 1
> >> Errors were encountered while processing:
> >>  linux-image-5.15.0-3-amd64
> >> #
>  
> >> What can be done to make dpkg stop trying to replace the initrd that I have made
> >> immutable? I don't want it replaced. Nothing (now) in 5.15 will solve the problem
> >> that needs the solution reported here:
> >> https://gitlab.freedesktop.org/drm/intel/-/issues/4762
>  
> > Would:
>  
> > # INITRD='No' dpkg --configure linux-image-5.15.0-3-amd64
>  
> > manage to propagate INITRD through to the third¹ test in
> > /etc/kernel/postinst.d/initramfs-tools?
>  
> > ¹ I'm reading buster; adjust as necessary.
> 
> Didn't help. But, I don't know if your third test equates to my third test.

Yes, as in:

¹ > command -v update-initramfs >/dev/null 2>&1 || exit 0
² > if [ -z "${version}" ]; then
³ > if [ "$INITRD" = 'No' ]; then

It then becomes a matter of where to introduce the INITRD.

So the commandline failed, but there are a couple of configuration
files in /etc/initramfs-tools/. There are environment variables
(uppercase) in initramfs.conf; update-initramfs.conf looks less
promising as the parameters are lowercase.

Greg has pointed to do_initrd in /etc/kernel-img.conf, which might
well work, but won't prevent it trying when, say, grub is upgraded.
Of course, it's always possible that do_initrd might work from
update-initramfs.conf. There might even be some documentation
somewhere (and there's always the source).

> What I did was prepend # to the last line in that file:

Sure. Hacks will usually work, but it's nice to find the
appropriate configuration variable, which the existence of
INITRD seems to confirm as being available somewhere.

> Thanks. That pacified the scripts. Now I can get on with finding a
> kernel that supports booting with two displays connected at boot,
> if there exists one packaged for Debian yet. ;)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#245174

On Wed, Feb 09, 2022 at 11:09:40PM -0500, Felix Miata wrote:
> mv: cannot move '/boot/initrd.img-5.15.0-3-amd64.new' to
> '/boot/initrd.img-5.15.0-3-amd64': Operation not permitted

> What can be done to make dpkg stop trying to replace the initrd that I have made
> immutable? I don't want it replaced.

Easy answer: make a copy of your special initrd, then turn off the
immutable bit, then let dpkg do its thing and be happy, then replace
the initrd with your copy and restore the immutable bit.

Harder answer: probably edit /etc/kernel-img.conf and change the
setting of do_initrd.  But I've never tried that, so I don't know
exactly what it does.  At best, I'd imagine it might turn off *all*
initrd creations, which would affect your *other* kernels too, not
just this one.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web