Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #75064 > unrolled thread
| Started by | Raul Tambre <raul@tambre.ee> |
|---|---|
| First post | 2022-04-18 12:40 +0200 |
| Last post | 2022-04-30 19:30 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#1009807: Kernels with no compression support no longer work Raul Tambre <raul@tambre.ee> - 2022-04-18 12:40 +0200
Bug#1009807: Kernels with no compression support no longer work Ben Hutchings <ben@decadent.org.uk> - 2022-04-18 21:30 +0200
Processed: Re: Bug#1009807: Kernels with no compression support no longer work "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-04-18 21:30 +0200
Bug#1009807: marked as done (Kernels with no compression support no longer work) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-04-30 19:30 +0200
| From | Raul Tambre <raul@tambre.ee> |
|---|---|
| Date | 2022-04-18 12:40 +0200 |
| Subject | Bug#1009807: Kernels with no compression support no longer work |
| Message-ID | <EdwXv-9xyN-7@gated-at.bofh.it> |
Package: initramfs-tools
Version: 0.141
Severity: important
Dear maintainer,
I was using a custom downstream kernel required for my hardware. The
kernel had only CONFIG_RD_XZ enabled, which I wasn't aware of.
With version 0.141 initramfs creation fails with:
Processing triggers for initramfs-tools (0.141) ...
update-initramfs: Generating /boot/initrd.img-4.14.102-rt53
grep: /boot/config-4.14.102-rt53: No such file or directory
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
grep: /boot/config-4.14.102-rt53: No such file or directory
E: gzip compression (CONFIG_RD_GZIP) not supported by kernel
update-initramfs: failed for /boot/initrd.img-4.14.102-rt53 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script
subprocess returned error exit status 1
After commit 035190cc4385c0441dddc1bbaba000cf7f1f179b the code tries to
default to gzip if the first method didn't work, and errors if so.
Previously it would fall back to no compression.
While the setup is a bit exotic, falling back to no compression as a
last resort (with a warning) would be what I expect.
For robustness it would probably even be ideal to test support for all
that known methods in some order of preference and only then fall back
to no compression.
All the best,
Raul
[toc] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2022-04-18 21:30 +0200 |
| Message-ID | <EdFep-9CIM-3@gated-at.bofh.it> |
| In reply to | #75064 |
[Multipart message — attachments visible in raw view] — view raw
Control: tag -1 moreinfo On Mon, 2022-04-18 at 13:30 +0300, Raul Tambre wrote: > Package: initramfs-tools > Version: 0.141 > Severity: important > > Dear maintainer, > > I was using a custom downstream kernel required for my hardware. The > kernel had only CONFIG_RD_XZ enabled, which I wasn't aware of. > With version 0.141 initramfs creation fails with: > > Processing triggers for initramfs-tools (0.141) ... > update-initramfs: Generating /boot/initrd.img-4.14.102-rt53 > grep: /boot/config-4.14.102-rt53: No such file or directory > W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip > grep: /boot/config-4.14.102-rt53: No such file or directory > E: gzip compression (CONFIG_RD_GZIP) not supported by kernel > update-initramfs: failed for /boot/initrd.img-4.14.102-rt53 with 1. > dpkg: error processing package initramfs-tools (--configure): > installed initramfs-tools package post-installation script > subprocess returned error exit status 1 > > After commit 035190cc4385c0441dddc1bbaba000cf7f1f179b the code tries to > default to gzip if the first method didn't work, and errors if so. > Previously it would fall back to no compression. [...] I think you are being confused by the "early initramfs" that is prepended to the main initramfs. The early initramfs contains x86 microcode and must be uncompressed. The main initramfs presumably can be uncompressed, but initramfs-tools has never supported that and has only ever had a fallback to gzip, which was assumed to be supported by all kernel configurations. It seems to me that your custom kernels have been booting without actually using the main initramfs, because they could not decompress it and they had all the necessary drivers built-in. If you don't want or need an initramfs then (assuming you use "make deb-pkg") you can disable CONFIG_BLK_DEV_INITRD and the package will then also disable building an initramfs on installation. If you do want an initramfs, then you should make sure the initramfs- tools and kernel configurations agree on which compression method to use. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer.
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2022-04-18 21:30 +0200 |
| Subject | Processed: Re: Bug#1009807: Kernels with no compression support no longer work |
| Message-ID | <EdFep-9CIM-5@gated-at.bofh.it> |
| In reply to | #75064 |
Processing control commands: > tag -1 moreinfo Bug #1009807 [initramfs-tools] Kernels with no compression support no longer work Added tag(s) moreinfo. -- 1009807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009807 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2022-04-30 19:30 +0200 |
| Subject | Bug#1009807: marked as done (Kernels with no compression support no longer work) |
| Message-ID | <EhZ4R-cgey-1@gated-at.bofh.it> |
| In reply to | #75064 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sat, 30 Apr 2022 20:16:25 +0300 with message-id <52759981-e674-578e-a358-3cc8a6a6d9ee@tambre.ee> and subject line Re: Bug#1009807: Kernels with no compression support no longer work has caused the Debian Bug report #1009807, regarding Kernels with no compression support no longer work to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1009807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009807 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web