Thanks for the responce fred.
This is the first dog that was almost 100% "drop-in" replacement of my bullseye system. I just changed 01-filesystem and the kernel files and the system booted. This is the easiest upgrade process ever
fredx181 wrote: Wed Jul 31, 2024 4:31 pm@trister
I used the appimage
Tested making a build with mklive-bookworm64 (appimage) using your attached config "build_setup__240730bookworm02.conf.txt" and it boots fine for me, so, no idea what can be the problem for you.
The system boots ok when using i915.modeset=1 .
It seems to me like it doesn't produce output at the start of the boot process (during the part which it loads initrd , squashfs files etc). It could send signal to HDMI instead of VGA or something like that and it then does the correct detections.
Is there a way to force detection or output to the screen from the start of the boot proccess .
fredx181 wrote: Wed Jul 31, 2024 4:31 pmI planned to do it after you added the option for non-merged filesystem.
Btw, I noticed in your config that it's containing
NMU="TRUE"
(no-merged-usr) but the appimage can only build with merged-usr.
The mklive-bookworm script from first post does have the choice for no-merged-usr though .EDIT: You may want to try booting with a different (older?) kernel, but be sure it's usr-merged or no-usr-merged matching with the filesystem.
It seems to me that I got a non-merged filesystem.I used the first file from the topic and renamed .gz to appaimage.