I tested two of my own generated kernel that did previously boot on my
headless nas: 6.12.57 and 6.12.58. Both failed.
So even in the eventuality, I wrongly modified kernel config for the
more recent one and did a rebuild, the previous one should have booted.
I cannot debug anything as I have no input when stuck on initramfs
prompt. I have input in BIOS and Grub stage but no more in the
initramfs. I have input once linux is booted with kernel that works...
I restarted the process I used in the past via linux-source 6.12 (this
time using 6.12.57+...).
Booted that 6.12.57 debian kernel, installed the corresponding sources,
followed
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-building
used "make localmodconfig"
Found some bugs (I have no DRM_XE loaded, and no USB4) but the config
entry where still there. Some NEW debug information should also be
removed besides the one already mentioned in the page. Nothing really
annoying. Does not hurt.
used grub-reboot to be sure, even if it fails, to not have to plug
monitor and keyboard to debug...
And it booted.
I checked the kernel config to find differences between working and non
working kernel in MD related conf but nothing popped up (I do not use
raid456, ...)
In the meantime, I did systemd-hwdb update because probably my
/etc/database was obsolete (this hardware runs debian for more than 10
years and config was previously stored there). See bug #1120578.
So I will be unable to help anymore except I'm sure something related to
boot/initramfs did change and broke my working config.
Use this bug as a warning for people wanting to stay on longterm kernel
even if running unstable.
--
Eric Valette
