Not Booting KLA-OT2baseCE

[nnriyer]

I have installed KLA-OT2baseCE on my HP Laptop. However, the same is not booting. The method of installation is frugal and boot loader is limine.

[nnriyer]

Please see the folder view of frugal Installation.

[wiak]

So next step would definitely be to try a different kernel-vmlinuz/00zdr(modules)/01fdr(firmware) combination, since both vmlinuz and initrd.gz are definitely being found by limine, but nvme partition is not then being 'seen/mounted' by Linux kernel. The file arrangement in the directory is fine, though lots of the files there are FirstRib utilities and play no part in the boot, but do no harm anyway. (SAVEMARK is totally irrelevant since FirstRib-based KL distros are not Puppy Linux versions and SAVEMARK is a Puppy file).

I suggest the following since I also have an nvme partition and booting with below fine for me. These are huge-kernel plus modules and firmware from a previous upup (or maybe it was a dpup, I can't remember):

Code: Select all

wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/initrd-latest.gz -O initrd.gz  # FR skeleton initrd
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup_22_04/vmlinuz
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup22_04/00zdrv_upup_22.04.sfs  # modules
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup22_04/01fdrv_upup_22.04.sfs  # firmware

Move the old ones somewhere out of bootfrom directory (/arch) and replace with above and then try booting it with these new alternatives.

As rockedge suggested, you should also try first to boot in RAM0 (no persistence) mode rather than RAM2 (save on demand) mode by using w_changes=RAM0 rather than w_changes=RAM2 on your limine kernel line:

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path arch)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch w_changes=RAM0
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/initrd.gz

[wiak]

Okay, I looked at the BK link you mentioned: https://bkhome.org/news/202211/kernel-5 ... iltin.html

I see that he suggests a module was missing for your nvme drive: vmd.ko

That's a problem since if it is not compiled (i.e. not a builtin) into the kernel the FR initrd.gz would have to have that manually included in there (which can be done if vmd module is available in /usr/lib/modules of 00zdr provided for KLA-OT2, but I've looked in modules.dep and it doesn't seem to be included...). We'll get back to you on that likely reason for your issue then. The alternative kernel I suggested may or may not have that driver built in; I didn't compile it so I don't know. Worth a try first though, prior to one of our team building a special FR initrd.gz for you instead. Alternatively a more recent puppy kernel may have vmd.ko built in - that would do for use with KLA. Since my understanding is you have puppy linux distro booting already from your nvme drive therefore, just take copy of the vmlinuz, zdrXXX.sfs (renamed to 00zdrv.sfs) and fdrXXX.sfs (renamed to 00fdrv.sfs) from that and use that instead of what came by default with KLA - should then work.

[nnriyer]

I will try your suggestion upon reaching back to my native place. I am looking for integrated vmd.ko built in KLA Arch files. It will be helpful to me and also all others who have nvme SSD.

[wiak]

I will try your suggestion upon reaching back to my native place. I am looking for integrated vmd.ko built in KLA Arch files. It will be helpful to me and also all others who have nvme SSD.

Okay the kernel combination I suggested earlier should work fine. I just opened its 00zdrv and vmd.ko is indeed a builtin:

I suggest the following since I also have an nvme partition and booting with below fine for me. These are huge-kernel plus modules and firmware from a previous upup (or maybe it was a dpup, I can't remember):

Code: Select all

wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/initrd-latest.gz -O initrd.gz  # FR skeleton initrd
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup_22_04/vmlinuz
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup22_04/00zdrv_upup_22.04.sfs  # modules
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup22_04/01fdrv_upup_22.04.sfs  # firmware

Move the old ones somewhere out of bootfrom directory (/arch) and replace with above and then try booting it with these new alternatives. In fact, above kernel (which has vmd.ko built in), 00zdrv, and 00fdrv are the ones supplied with KLA-OT2base already, just not with the most recent CE release of the latter. You should have been able to boot KLA a long time ago therefore, but maybe didn't get your limine stanza correct back then. Let's hope that's all the problem is - sounds like it though.

[nnriyer]

Thank so much for prompt reply and help. I will get back to you after applying your suggestions. Till then kindly bear with me.

[Sofiya]

It will be easier for you to download and install the KLA-OT2baseCE-2.6 final - stable version with the Upup core 00zdrv_upup_22.04.sfs .
and see if it works for you.

viewtopic.php?t=9223

[nnriyer]

Dear Wiak Sir

Please see the output

# wget -c https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs # modules
--2023-08-18 21:42:19-- https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs
Resolving gitlab.com... 2606:4700:90:0:f22e:fbec:5bed:a9b9, 172.65.251.78
Connecting to gitlab.com|2606:4700:90:0:f22e:fbec:5bed:a9b9|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-08-18 21:42:20 ERROR 404: Not Found.

# wget -c https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs # firmware
--2023-08-18 21:42:24-- https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs
Resolving gitlab.com... 2606:4700:90:0:f22e:fbec:5bed:a9b9, 172.65.251.78
Connecting to gitlab.com|2606:4700:90:0:f22e:fbec:5bed:a9b9|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-08-18 21:42:27 ERROR 404: Not Found.

[nnriyer]

It will be easier for you to download and install the KLA-OT2baseCE-2.6 final - stable version with the Upup core 00zdrv_upup_22.04.sfs .
and see if it works for you.

viewtopic.php?t=9223

Regret to inform you that KLA-OT2baseCE-2.6 final also failed to boot.

[Sofiya]

It will be easier for you to download and install the KLA-OT2baseCE-2.6 final - stable version with the Upup core 00zdrv_upup_22.04.sfs .
and see if it works for you.

viewtopic.php?t=9223

Regret to inform you that KLA-OT2baseCE-2.6 final also failed to boot.

What can I say, it’s sad.you need a special kernel with vmd.ko module.Although, as @wiak writes above, that there is this module in 00zdrv_upup_22.04.sfs, then I don’t understand why you can’t boot .try changing the controller to AHCI in the BIOS.

Disable Intel VMD Controller

[wiak]

Dear Wiak Sir

Please see the output

# wget -c https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs # modules
--2023-08-18 21:42:19-- https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs
Resolving gitlab.com... 2606:4700:90:0:f22e:fbec:5bed:a9b9, 172.65.251.78
Connecting to gitlab.com|2606:4700:90:0:f22e:fbec:5bed:a9b9|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-08-18 21:42:20 ERROR 404: Not Found.

# wget -c https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs # firmware
--2023-08-18 21:42:24-- https://gitlab.com/firstrib/firstrib/-/ ... _22.04.sfs
Resolving gitlab.com... 2606:4700:90:0:f22e:fbec:5bed:a9b9, 172.65.251.78
Connecting to gitlab.com|2606:4700:90:0:f22e:fbec:5bed:a9b9|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-08-18 21:42:27 ERROR 404: Not Found.

I think the vmlinuz downloaded okay though? If you checked the wget lines I posted you can see I missed an underscore in url for the zdr and fdr. Here are the fixed links for download, however if KLA-OT2baseCE Sofiya asked you to download didn't work this won't work either since same kernel I think:

Code: Select all

wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/initrd-latest.gz -O initrd.gz  # FR skeleton initrd
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup_22_04/vmlinuz
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup_22_04/00zdrv_upup_22.04.sfs  # modules
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup_22_04/01fdrv_upup_22.04.sfs  # firmware

vmd.ko is certainly built in to that kernel. If isn't working then must be something else required in kernel, sorry.

[TerryH]

The KLA-OT2 2.7 with kernel 6.4.7 arch1-1 does contain vmd.ko, the path is /usr/lib/modules/6.4.7-arch1-1/kernel/drivers/pci/controller/vmd.ko

I have a laptop(see signature below) with an nvme drive which this release boots on using grub2. I do experience an occasional boot problem, but generally it boots without issue. I would think that it may be an issue with trying to boot with limine boot loader. I currently don't have a drive using limine, so can't assist with limine.

[wiak]

The KLA-OT2 2.7 with kernel 6.4.7 arch1-1 does contain vmd.ko, the path is /usr/lib/modules/6.4.7-arch1-1/kernel/drivers/pci/controller/vmd.ko

I have a laptop(see signature below) with an nvme drive which this release boots on using grub2. I do experience an occasional boot problem, but generally it boots without issue. I would think that it may be an issue with trying to boot with limine boot loader. I currently don't have a drive using limine, so can't assist with limine.

Ah, wait though. That's different. That's an external-to-kernel module, so won't work. We are looking for a kernel that has vmod.ko 'built-in' to the kernel.

I 'think' the ones I've suggested have vmod.ko built-in to kernel. I might be wrong so will check again. If worst comes to the worst we could later make a vmlinuz/00modules/00firmware from EasyOS if the later OS does indeed work (or antiX), but please try the one I suggested first to save time and effort. However, the problem is, I think the second KLA-OT2baseCE Sofiya suggested uses same kernel I am suggesting (not 6.4.7 arch1_1) and if that alternative not working it is a surprise.

EDIT: just double checked the kernel I was suggesting to use and it definitely has vmd.ko as a built-in (per modules-builtin) to the kernel so should have worked if that is all that was missing from other kernels. But worst comes to the worst we'll end up trying EasyOS or antiX kernel/modules/firmware with KLA, and if that doesn't work, makes no sense to me and I'd give up.

EDIT2: Probably won't use EasyOS components. It has unusual arrangements (though might be ok; I'll check) - if necessary I'd download AntiX and hope its kernel/modules/firmware would do if the alternative I suggested doesn't. Do any versions of Puppy Linux boot?

EDIT3: EasyOS kernel components might do for you though. I've extracted them into own sfs files and uploaded temporarily for you to try. See my immediately next post for download commands. You need to remove all previous 00xxx.sfs and 01yyy.sfs files as well as old vmlinuz before trying these ones. The almost working Limine config should just stay the same.

[wiak]

Temporarily available/stored only so @nnriyer can see if he can boot his KLA-OT2baseCE with the easyOS kernel/modules/firmware. Please keep your own copy since temporary stored only for this trial. Should work since he can boot EasyOS itself, but if not, last try I'd make would be with AntiX components instead.

EDIT: Forget the EasyOS kernel/modules: Don't waste your time. Doesn't support overlay filesystem. I'll try AntiX.

[wiak]

Okay, my last try. The following will download AntiX vmlinuz, modules and firmware, which you say boot on your machine. That is surprising though since I checked and they DO NOT contain vmd.ko built-in (just supplied as an external module by antiX...), so something wrong in earlier diagnosis and supposed 'solution' methinks. Are you sure AntiX boots on your nmve drive? We will see.

Code: Select all

wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/5.10.142-antix.2-amd64-smp/vmlinuz
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/5.10.142-antix.2-amd64-smp/00modules.sfs
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/5.10.142-antix.2-amd64-smp/01firmware.sfs

Replace the vmlinuz, 00zdrvXXX.sfs, and 01fdrvXXX.sfs with these (be careful no other files in boot directory start with either 00 or 01 as their filenames.

EDIT: see my post immediately below. I forgot one extra detail since this is a special arrangement that may or may not work with current FR initrd.gz; the 'trick' has hardly been used for years so not tested/maintained and, by its nature, has limitations anyway so I won't be putting further time into that bit of code.

[wiak]

A problem with that AntiX kernel is that it doesn't have overlay built into the kernel and KL/FR builds need overlay working.

There is an old FR initrd 'trick' that 'might' work - worth a try and certainly would be needed with that kernel:

At end of limine kernel line you need to add an extra argument:

Code: Select all

w_00modules=usrlib

i.e. limine:

:Puppy Linux Arch (partition nvme0n1p8, path arch)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch w_changes=RAM0 w_00modules=usrlib
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/initrd.gz

EDIT: If that doesn't work, or hangs at udev trying to settle or something, the only way I can think of getting it to work would be to identify a kernel/modules/firmware from Puppy Linux that you definitely know boots (not EasyOS because as I say its current kernel doesn't even seem to support overlayfs as a module) and we could make a special FR initrd.gz that would work with that (perhaps could do that for the AntiX modules situation, but may be other issues there in terms of huge-kernel situation with that (may not have sufficient in-built drivers).

[nnriyer]

Dear Waik

Currently my laptop having Antix Linux on separate partition and working fine. Earlier occasions, when easyos was not booting, I have inter changed easyos kernel with Antix linux. There was a slight improvement still not booted. All these were intimated in the forum and separate email to Barry.

Now Vanilla and SPup all are booting now without problem after discovering the issue by the Barry Sir. Earlier this also not booting. !!! Gurus in the forum may be aware that I had reported the boot issue about my HP Laptop. You have also provided some suggestions. However, none of these suggestions worked. I had also done lot of trail and error method. I have also many booting issue on internet on booting from Nvme ssd. Finally, after my repeated requests through email and forum, a solution was provided by Barry Sir.

Waik Sir , Please note that vmlinuz and initrd downloaded via wget.

Please see my earlier post on easyos thread

viewtopic.php?p=73572#p73572

[nnriyer]

Dear Sofiya Sir

Please note that BIOS setting in HP Laptop are limited or unavailable as suggested by you. HP UEFI-setup does not have a setting to change "raid mode" to "ahci mode.

[wiak]

If newest vpup (EDIT: I mean Vanilla Upup; forget about spup...) boots then its vmlinuz, zdrv and fdrv sfs will also definitely boot KLA. Just copy these three files to KLA dir and rename zdrv to 00zdrv sfs and its fdrv to 01fdrv sfs. Remove old ones. Newest vpup kernel has the needed inbuilt overlayfs support. Make sure to also wget new FR skeleton initrd.gz per my previous instruction; that is correct one for this case

[nnriyer]

Wiak

I have copied vmlinux (spup) and downloaded the sketon initrd from your link and (zdrv and fdrv from SPup) folder to arch pup folder. No booting !!.

[wiak]

Wiak

I have copied vmlinux (spup) and downloaded the sketon initrd from your link and (zdrv and fdrv from SPup) folder to arch pup folder. No booting !!.

Well, you need to again send photo of that happening to see where it stalls like you did here: viewtopic.php?p=96597#p96597

Thinking about this logically (the only way), if spup boots, that means:

1. its vmlinuz gets found by Limine.
2. its initrd gets found and used
3. its zdrv provides the modules required to allow the initrd/init to mount the nvme partition
4. its fdrv provides any (later) firmware required by the boot process.

If you have given KLA that same vmlinuz, and its zdrv (renamed to 00zdrv...) and fdrv (renamed to 01fdrv) then we already know from spup situation that:

1. Its vmlinux will be found by Limine (but if it is an aufs-only kernel that is no use anyway for booting KLA that needs overlayfs...).
2. the FirstRib skeleton initrd.gz will be found by Limine and used by the booting vmlinuz (according to your earlier report viewtopic.php?p=96597#p96597).
3. At that stage the difference is that the initrd/init being used is that of FirstRib, which is known to reliably mount the bootfrom partition as long as the vmlinuz has the required inbuilt drivers (including overlayfs) and the 00zdrv has any required external modules. Since that same vmlinuz and zdrv were used by successfully booting spup then there is no reason that I can see that FirstRib initrd/init should fail to mount the bootfrom partition.
4. Assuming the bootfrom partition is therefore found, any further boot error should be indicated during boot and you need in any case to provide what that error screen looks like.

That is: if you correct removed KLA usual vmlinuz and replaced that with spup vmlinuz, zdrv (to 00zdrv) and fdrv (to 00fdrv) then, to me there would be one issue only. Does spup kernel have overlayfs built-in to the kernel or does it only have aufs built into its kernel? I asked you that already, but you have never replied to that vital question.

My real question, however, was: does recent vanilla upup (not spup) boot on your system. I know that vpup does have overlayfs built into its kernel and that is the one I asked you to use - not spup... I can't help if you don't use the kernel advised really, but anyway, show the boot screen. Only chance of getting an aufs-only vmlinuz to work (which may be the case for spup kernel) is if you used my other suggestion to add w_00modules=usrlib to the limine linux kernel stanza line (and if that doesn't work try the alternative, which is w_00modules=lib). Did you try that.

But to not waste further time on a kernel I know nothing about (spup) please, as already advised try to first boot most recent vanilla upup as a distro, and if that works, please use its vmlinuz, and zdrv (changed to 00zdrv) and fdrv (changed to 00fdrv) before we go any further. I'm not really interested in a spup boot that probably is aufs only. KLA needs overlayfs built kernel, and overlayfs is a built-in-to-kernel in recent vpup kernel as far as I know(?). You can currently download recent vanilla upup, and try to first boot that, from here: https://github.com/puppylinux-woof-CE/w ... 5873282985

i.e. does vanilla upup boot on your machine is the critical question. Forget about spup since that is probably an old-style aufs-only kernel so no use to KLA without 'tricks' that vanilla upup shouldn't require if it has an overlayfs kernel (KL has no interest or need of aufs...).

SUMMARY: Please concentrate on first successfully booting most recent Vanilla Upup: get a zip of that. i.e. https://github.com/puppylinux-woof-CE/w ... 5873282985
If that boots for you we will concentrate on trying to make KLA boot with its parts. If you get even one thing wrong of course the computer can't boot so lets simplify the problem by concentrating on Vanilla Upup boot first. If that won't boot then we'll have to think of something else. If it does boot then we can then use its kernel/module/firmware parts to try boot KLA. And always post boot photo or nothing can be determined at all.

[wiak]

Wiak

I have copied vmlinux (spup) and downloaded the sketon initrd from your link and (zdrv and fdrv from SPup) folder to arch pup folder. No booting !!.

So do same for Vanilla Upup instead, but make sure that distro does boot on your machine prior to then trying to get KLA working...

And make sure you did rename zdrv sfs to 00zdrv sfs and fdrv 01fdrv sfs. You did not mention that important necessary step above at all. Please be precise in your reports or I can't help you further. This is taking a lot of testing/dev time so we should give up on KLA booting if not successful soon and use what works for you instead.

Nor have you tried my other suggestion of AntiX, where you must also use limine argument w_00modules=usrlib

But forget AntiX until you have concentrated on Vanilla Upup only (which 'probably', with KLA, won't need that extra limine argument w_00modules=usrlib). In fact, if you use w_00modules=usrlib when it isn't needed, boot will fail, and if you don't use w_00modules=usrlib when it is needed, boot will fail, or if instead you need w_00modules=lib (instead of usrlib) then boot will fail. Computers need perfect setup; even tiniest thing wrong and boot will fail. So let's just concentrate on seeing if normal Vanilla Upup boots on your machine, and if so, we will have last attempts to make KLA boot via Vanilla Upup parts (hopefully without needing w_00modules= line).

[nnriyer]

Wiak

I

That is: if you correct removed KLA usual vmlinuz and replaced that with spup vmlinuz, zdrv (to 00zdrv) and fdrv (to 00fdrv) then, to me there would be one issue only. Does spup kernel have overlayfs built-in to the kernel or does it only have aufs built into its kernel? I asked you that already, but you have never replied to that vital question.

M

Sir Please note that I dont have any technical knowledge and also not a technical persons. I am just a layman only. I am nowhere near to your technical knowledge. I am fiddling with linux because of my interest. I cann't answer your technical aspects .

[wiak]

Wiak

I

That is: if you correct removed KLA usual vmlinuz and replaced that with spup vmlinuz, zdrv (to 00zdrv) and fdrv (to 00fdrv) then, to me there would be one issue only. Does spup kernel have overlayfs built-in to the kernel or does it only have aufs built into its kernel? I asked you that already, but you have never replied to that vital question.

M

Sir Please note that I dont have any technical knowledge and also not a technical persons. I am just a layman only. I am nowhere near to your technical knowledge. I am fiddling with linux because of my interest. I cann't answer your technical aspects .

I am not asking for you to be at all a technical expert and nor did I ask that of you months ago in trying to get KL to boot for you.
However, when a computer won't boot, that is a technical matter and if you can't provide boot information accurately no technical person can work out what is going wrong so can't help you. Yes, you can try Vanilla Upup if you want to (you already succeeded with booting spup), and yes you can provide photo of boot errors when these occur (you already did earlier), and yes I believe (despite your not being a technical expert) you can provide limine boot stanzas that worked for other distros (and partly worked for KLA) - you've already shown you can do that much. The problem is when you later just say: 'not booting', which helps no one since you didn't include absolute details of what you did or photo that time. Without technical details of what you tried, I simply can't help then: I am not a mind-reader regarding what you did or didn't do.

[nnriyer]

I will provide. Now folder view of Vanilla Dpup. Just for your information only.

[nnriyer]

QUIET=no
TIMEOUT=20
GRAPHICS=no
DEFAULT_ENTRY=1
EDITOR_ENABLED=yes
INTERFACE_BRANDING=EasyOS Limine Boot Manager

:EasyOS Kirkstone64 (partition nvme0n1p6, path easyos)
COMMENT=EasyOS bootup
PROTOCOL=linux
KERNEL_CMDLINE=rw wkg_uuid=e77f9da7-35db-4b43-a3ef-c773cca9d5c5 wkg_dir=easyos
KERNEL_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/vmlinuz
MODULE_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/initrd

:Linux Debian GNU/Linux (partition nvme0n1p7)
COMMENT=Linux bootup
PROTOCOL=linux
KERNEL_CMDLINE=root=PARTUUID=b44c818b-3204-4292-b7e9-b79c5ab6c07f rw
KERNEL_PATH=guid://b44c818b-3204-4292-b7e9-b79c5ab6c07f/boot/vmlinuz-5.10.57-antix.1-amd64-smp
MODULE_PATH=guid://b44c818b-3204-4292-b7e9-b79c5ab6c07f/boot/initrd.img-5.10.57-antix.1-amd64-smp

:Puppy Linux s15pup64 (partition nvme0n1p8, path spup15)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=spup15 pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/spup15/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/spup15/initrd.gz

:Puppy Linux vanilladpup (partition nvme0n1p8, path vaniladpup)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=vaniladpup pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/vaniladpup/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/vaniladpup/initrd.gz

:Puppy Linux Arch (partition nvme0n1p8, path arch)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch w_changes=RAM0 w_00modules=usrlib
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/initrd.gz

:Windows 10
COMMENT=Windows bootup
PROTOCOL=chainload
IMAGE_PATH=guid://21e3bf30-0631-40c4-a470-537756576dcc/EFI/Microsoft/Boot/bootmgfw.efi

[wiak]

I will provide. Now folder view of Vanilla Dpup. Just for your information only.

Vanilla Dpup is not the same as Vanilla Upup... (now apparently re-vamped and published as ubuntu-jammy64 per later post in Vanilla Upup thread): https://github.com/puppylinux-woof-CE/w ... 5873282985

Does Vanilla Dpup boot for you?
More important to me: Does Vanilla Upup (note Upup), being what is now apparently called ubuntu-jammy64, boot for you?

You also need to state version number of the distro since the developer changes what is inside (including if kernel is aufs or overlayfs including) between different versions. We need to find an overlayfs including kernel version.

[nnriyer]

Please see the error while booting archKLA. Seeking boot partition...

[nnriyer]

Vanilla Dpup 11.0.26
6.1.27 SMP preempt mod_unload modversions

-Version-
Kernel : Linux 6.1.27 (x86_64)
Command Line : psubdir=vaniladpup pmedia=ataflash
Version : #1 SMP PREEMPT_DYNAMIC Fri May 12 09:07:05 UTC 2023
C Library : GNU C Library / (Debian GLIBC 2.36-9) 2.36
Distribution : Vanilla Dpup 11.0.26
-Current Session-
Computer Name : puppypc12294
User Name : root (root)
Language : en_US.UTF-8 (en_US.UTF-8)
Home Directory : /root
Desktop Environment : wlroots on wayland
-Misc-
Uptime : 9 minutes
Load Average : 1.21, 1.07, 0.60