=== chris14_ is now known as chris14 === matttbe4 is now known as matttbe [17:09] Hi everybody, I have a couple of questions about the changes to the install ISO image for 24.04. This is probably not the right forum but I have not found a forum that fits. Please feel free to refer to a better place. [17:12] I am trying to update an install ISO from 22.04 to 24.04. The system I am working on required a couple of kernel changes to boot. In the 22.04 ISO image I was able to copy the new kernel to casper/vmlinuz. The initrd required a bit more work because the there was a script in the initrd also. So I modified it and created the casper/initrd file and it all worked. [17:14] 24.04 has a number of changes. I am copying the correct vmlinuz file and preinstalled initrd for for that image to the casper directory vmlinuz and initrd files. I have looked at the contents of both the original initrd and new initrd files and the new one would seem to be a new version of the old. There does not seem to be any extra files I need to add to the image. [17:15] However, the kernel boots and finds the initrd but then gives the error: [17:15] egin: Loading essential drivers ... done. [17:15] Begin: Running /scripts/init-premount ... done. [17:15] Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. [17:15] Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems [17:15] done. [17:15] No root device specified. Boot arguments must include a root= parameter. [17:15] BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3) built-in shell (ash) [17:15] Enter 'help' for a list of built-in commands. [17:16] (initramfs) [17:26] I am building the kernel packages used to produce the vmlinuz and initrd files using the "fakeroot debian/rules binary" command so it creates the initrd using compressed modules as the original initrd included. [17:28] Is there something special about the kernel configuration for vmlinuz in the 24.04 ISO image? This does not seem to have been try for previous releases. [17:28] I would appreciate any information to help make progress. [17:43] johnnie, checkout annotations [17:43] annotations.py [17:44] also to me it sounds like you have a broken grub.cfg. [17:45] "No root device specified. Boot arguments muts include a root= parameter." means that the bootloader isn't telling it what drive is the root drive. Usually a parameter like that will exist in grub.cfg, but either the kernel doesn't see it or grub.cfg doesn't contain it (most likely the latter). [17:45] if you're booting the kernel "by hand" (i.e., from the GRUB command line), you need to type that parameter when you run the `linux` command to load the kernel. [17:48] The grub.cfg works fine with the original ISO image vmlinuz file and it does not include a root= parameter. The kernel boot messages show the same kernel command line parameters being passed to the kernel for both images. [17:50] huh, sure enough, I didn't expect that. Never mind, carry on [17:50] The ISO image does not include a matching config-xxx file for the kernel with the kernel config it was built for and /proc/config.gz is not there to get it that way. I can change the annotations file but I do not know what needs to be changed. [17:50] https://discourse.ubuntu.com/t/kernel-configuration-in-ubuntu/35857/4 [23:04] Hi again, I have the ramdisk loading now. It appears no modules are being loaded but looking in the /usr/lib/modules/6.8.... directory shows a file tree with compressed modules. So I tried an insmod and I get [23:04] (initramfs) insmod ./kernel/drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko [23:04] .zst [23:04] [ 572.497813] Invalid ELF header magic: != ELF [23:04] insmod: error inserting './kernel/drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko.zst': -1 Invalid module format === matttbe2 is now known as matttbe