Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

On Tue, 13 Feb 2018 01:03:43 + Ben Hutchings wrote: Now that I think about it, initramfs-tools does allow other packages to override the configuration for mkinitramfs through shell scripts in /usr/share/initramfs-tools/conf-hooks.d. This seems like a good reason to do that. I've recently

Processed: Re: Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Processing control commands: > tag -1 - moreinfo Bug #890262 [flash-kernel] flash-kernel: QNAP TS109, Not enough space for initrd in MTD Removed tag(s) moreinfo. -- 890262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890262 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Control: tag -1 - moreinfo On Mon, 2018-02-12 at 22:24 +0100, Gunnar Thorburn wrote: > Hi, > > Creating this file with COMPRESS=xz worked fine > /etc/initramfs-tools/conf.d/compress > > Obviously, with xz there is plenty of space left. There was a little > warning though (see below). > >

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Hi, Creating this file with COMPRESS=xz worked fine /etc/initramfs-tools/conf.d/compress Obviously, with xz there is plenty of space left. There was a little warning though (see below). Generating kernel u-boot image... done. Flashing kernel (using 2050440/2097152 bytes)... done. Flashing

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Hi Martin, I sincerely apologize for setting the wrong severity to the wrong package in the original report. (I thought the system could be in a state where it would not reboot at all) I am sorry to inform you that changing to MODULES=dep in initramfs.conf did not help. (driver-policy already

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Unfortunately my memory is quite bad. I *thought* the current installer configured XZ compression by default but it seems that's not the case. So the documentation on my web site is correct. * The installer sets MODULES=dep * It has done so for a long time * But you've upgraded from a really

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

The other thing you can do is to enable XZ compression: http://www.cyrius.com/debian/orion/qnap/ts-109/troubleshooting/#bootable I thought this was documented in the release notes but I can't find it. -- Martin Michlmayr http://www.cyrius.com/

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

* Gunnar Thorburn [2018-02-12 17:52]: > The initial ramdisk is too large. This is often due to the unnecessary > inclusion > of all kernel modules in the image. To fix this set MODULES=dep in one or both > /etc/initramfs-tools/conf.d/driver-policy (if it exists) and >

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Control: severity -1 important Control: tag -1 moreinfo On Mon, 2018-02-12 at 17:52 +0100, Gunnar Thorburn wrote: [...] > I have not tried editing > /etc/initramfs-tools/initramfs.conf > > I suppose i could try to change MODULES=most to MODULES=dep. [...] This is definitely not a critical bug

Processed: Re: Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Processing control commands: > severity -1 important Bug #890262 [flash-kernel] flash-kernel: QNAP TS109, Not enough space for initrd in MTD Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #890262 [flash-kernel] flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

Package: flash-kernel Version: 3.79 Severity: critical Justification: breaks the whole system Dear Maintainer, I have been running Debian on a QNAP TS109 for many years. I successfully upgraded from Squeeze to Wheezy in 2013 and to Jessie in 2015. As I now upgrade to Stretch (basically