Hi Christian, On Fri, 2026-01-02 at 22:01 +0100, Christian Groessler wrote: > Using the same kernel config and adding a --ramdisk in palo.conf (using > install/initrd.gz from 2025-12-06 CD) lets the kernel crash early, like > the other kernels I've tried. No further output after the palo loading > messages. > > So it crashes right at the start of the kernel, unlike without an initrd > where the kernel boot messages appear normally and it crashes because it > has no rootfs and init program.
Maybe debugging with earlyprintk can help? Try passing "earlyprintk=serial,ttyS0,115200" to the kernel command line. See: https://wiki.gentoo.org/wiki/Kernel/Command-line_parameters > Then I tried extracting the initrd.gz file system (replacing lib/modules > with my kernel's version) and mounting it over NFS. I modifed the kernel > config to compile in NFS client support and not get it from modules. Would be good to figure out what the actual problem is so we can fix the issue in Debian or in the upstream kernel. > This worked so far that I could start the installer (it would find the > CD in the CD drive as installation media), but it complains that the > installer components (I believe kernel modules) are for a different > kernel than the booted version. Yes, that's expected. > So probably I really need to build myself the installation media, using > a kernel config where NFS is hardcoded in... That's unfortunately not trivial as the build process requires the kernel package to be part of the package repository where the CD image is being built from. It's possible, but quite some work. See: https://wiki.debian.org/PortsDocs/CreateDebianInstallerImages Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
