public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>,
	Stefan Schantl <stefan.schantl@ipfire.org>
Cc: Arne Fitzenreiter <arne_f@ipfire.org>,
	"IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Kernel 6.18 fist tests...
Date: Thu, 11 Dec 2025 21:01:10 +0000	[thread overview]
Message-ID: <348B531B-2DD7-4069-9445-F164B2E40541@ipfire.org> (raw)
In-Reply-To: <faddd1c9-1ef9-4d20-a00d-a05cc8a0f399@ipfire.org>

Hello Adolf,

The initqueue module is probably quite important. As far as I know it kind of replaces some systemd functionality which we don’t have.

But looking at our root file, it is adding some systemd unit files:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/rootfiles/common/dracut-ng;hb=d656b7af6411d0306513b853a552f56d6713c174#l484

We might have found a breaking change in dracut-ng if we don’t properly support mdraid any more.

Lacking support for btrfs in the initramdisk could be less severe, but that also needs to be tested. @Stefan, will you do this for c199?

-Michael

> On 11 Dec 2025, at 18:04, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi Arne,
> 
> On 11/12/2025 18:28, Adolf Belka wrote:
>> Hi All,
>> On 11/12/2025 18:20, Adolf Belka wrote:
>>> Hi Arne,
>>> 
>>> I have tried it out on a vm clone running CU199 Testing.
>>> 
>>> In the readme.txt file I think you meant to have
>>> 
>>> tar xvaf KERNEL-ARCHIV.tar.xz -C /
>>> 
>>> instead of
>>> 
>>> tar xvaf KERNEL-ARCHIV.tar.xz -C \
>>> 
>>> At least it only extracted for me with the / and not the \.
>>> 
>>> I then ran the dracut command and got the following messages.
>>> 
>>> sudo dracut --regenerate-all --force
>>> dracut[I]: Executing: /usr/bin/dracut --kver=6.12.58-ipfire --force
>>> dracut[E]: Module 'btrfs' depends on module 'initqueue', which can't be installed
>>> dracut[E]: Module 'lvm' depends on module 'initqueue', which can't be installed
>>> dracut[E]: Module 'mdraid' depends on module 'initqueue', which can't be installed
>>> dracut[I]: *** Including module: modsign ***
>>> dracut[I]: *** Including module: i18n ***
>>> dracut[I]: *** Including module: btrfs ***
>>> dracut[I]: *** Including module: dm ***
>>> dracut[I]: *** Including module: fs-lib ***
>>> dracut[I]: *** Including module: kernel-modules ***
>>> dracut[I]: *** Including module: kernel-modules-extra ***
>>> dracut[I]: *** Including module: lvm ***
>>> dracut[I]: *** Including module: mdraid ***
>>> dracut[I]: *** Including module: qemu ***
>>> dracut[I]: *** Including module: rootfs-block ***
>>> dracut[I]: *** Including module: terminfo ***
>>> dracut[I]: *** Including module: udev-rules ***
>>> dracut[I]: *** Including module: base ***
>>> dracut[I]: *** Including modules done ***
>>> dracut[I]: *** Installing kernel module dependencies ***
>>> dracut[I]: *** Installing kernel module dependencies done ***
>>> dracut[I]: *** Resolving executable dependencies ***
>>> dracut[I]: *** Resolving executable dependencies done ***
>>> dracut[I]: *** Generating early-microcode cpio image ***
>>> dracut[I]: *** Constructing AuthenticAMD.bin ***
>>> dracut[I]: *** Constructing GenuineIntel.bin ***
>>> dracut[I]: *** Store current command line parameters ***
>>> dracut[I]: *** Creating image file '/boot/initramfs-6.12.58-ipfire.img.tmp' ***
>>> dracut[I]: *** Hardlinking files ***
>>> dracut[I]: *** Hardlinking files done ***
>>> 
>>> 
>>> Not sure about the "module 'initqueue', which can't be installed" bits.
>>> 
>>> After the above last line I then got
>>> 
>>> cp: error writing '/boot/initramfs-6.12.58-ipfire.img.tmp': No space left on device
>>> 
>>> So I suspect I need to make the IPFire vm disk larger.
>> The problem was that I made a clone of a system that I had tested out upgrading from CU150 to CU198 and the boot size was obviously smaller back in CU150 as I only have 110MB but the more current systems have 488MB so I will create a clone of one of my newer systems and repeat the test.
> 
> Repeated with a newer IPFire vm which had a 488MB boot partition and the dracut section went fine with no problems beside the initqueue module not being able to be installed. However that did not seem to cause a problem with the grub-mkconfig command or the subsequent reboot.
> 
> I will evaluate the install tomorrow to check if anything has a problem.
> 
> Regards,
> 
> Adolf.
> 
> 
>> Regards,
>> Adolf.
>>> 
>>> Will give that a try later but would like to know if there is anything I need to do with regard to the initqueue module that is mentioned in the dracut output.
>>> 
>>> Regards,
>>> 
>>> Adolf.
>>> 
>>> On 11/12/2025 14:57, Adam Gibbons wrote:
>>>> Nice!
>>>> 
>>>> I will test this over the weekend.
>>>> 
>>>> Thanks,
>>>> Adam
>>>> 
>>>> 
>>>> On 11 December 2025 12:00:23 GMT, Arne Fitzenreiter <arne_f@ipfire.org> wrote:
>>>> 
>>>>     Hi,
>>>> 
>>>>     i have compiled a first test kernel 6.18 for x86_64.
>>>> 
>>>>     https://people.ipfire.org/~arne_f/highly-experimental/kernel/ <https://people.ipfire.org/~arne_f/highly-experimental/kernel/>
>>>> 
>>>>     please help testing and report your findings...
>>>> 
>>>>     Arne




  reply	other threads:[~2025-12-11 21:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 12:00 Arne Fitzenreiter
2025-12-11 13:57 ` Adam Gibbons
2025-12-11 17:20   ` Adolf Belka
2025-12-11 17:28     ` Adolf Belka
2025-12-11 18:04       ` Adolf Belka
2025-12-11 21:01         ` Michael Tremer [this message]
2025-12-11 22:35           ` Adolf Belka
2025-12-12 11:30             ` Adolf Belka
2025-12-12 13:57               ` Adolf Belka
2025-12-15 11:46                 ` Adolf Belka
2025-12-15 20:13                   ` Adam Gibbons
2025-12-17 13:50 ` ummeegge
2025-12-17 15:38   ` ummeegge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=348B531B-2DD7-4069-9445-F164B2E40541@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=arne_f@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=stefan.schantl@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox