Comment # 17 on bug 1226122 from Felix Miata

I had no problem getting kernels installed, as this installation like all mine
is in a multiboot environment, precisely why no bootloader is wanted. Current
state:
# rpm -qa | egrep 'nel-def|nel-lon|grub|boot|tlets' | sort
efibootmgr-18-1.6.x86_64
kernel-default-6.9.3-1.1.x86_64
kernel-longterm-6.6.32-2.1.x86_64
ruby3.3-rubygem-cfa_grub2-2.0.0-1.22.x86_64
suse-module-tools-scriptlets-16.0.44-1.1.x86_64
systemd-boot-255.7-2.1.x86_64
yast2-bootloader-5.0.10-1.1.x86_64
# ls -gGl /boot/
total 117304
-rw------- 1 22703918 Jun 10 03:27 .initrd-6.6.32-2-longterm1
-rw------- 1 22916356 Jun 10 14:02 .initrd-6.9.3-1-default1
lrwxrwxrwx 1       22 Jun 10 14:04 initrd -> initrd-6.9.3-1-default
-rw------- 1 22703918 Jun 10 03:27 initrd-6.6.32-2-longterm
-rw------- 1 22916356 Jun 10 14:02 initrd-6.9.3-1-default
lrwxrwxrwx 1       22 Jun 10 14:04 initrd-cur -> initrd-6.9.3-1-default
lrwxrwxrwx 1       24 Jun 10 03:28 initrd-lt -> initrd-6.6.32-2-longterm
lrwxrwxrwx 1       23 Jun 10 14:04 vmlinuz -> vmlinuz-6.9.3-1-default
-rw-r--r-- 1 14248304 May 25 13:52 vmlinuz-6.6.32-2-longterm
-rw-r--r-- 1 14625136 May 30 04:00 vmlinuz-6.9.3-1-default
lrwxrwxrwx 1       23 Jun 10 14:04 vmlinuz-cur -> vmlinuz-6.9.3-1-default
lrwxrwxrwx 1       25 Jun 10 03:25 vmlinuz-lt -> vmlinuz-6.6.32-2-longterm
#
Installing kernels with rpm via chroot was simple enough, but I had to run
dracut manually for both kernels, and put vmlinuz and symlinks in /boot/
manually. I've changed /etc/sysconfig/bootloader' LOADER_TYPE="none" from none
to grub, but done nothing yet I might anticipate it affecting. ATM on 6.6.32,
uptime is  12:25. I forgot to shut it down before I left the house for 10
hours.

I suspect, but haven't made plans to test yet, that the default installation
selections by including sdbootutil-rpm-scriptlets and sdbootutil and not
including suse-module-tools-scriptlets, and me not addressing those
selections/deselection, that the system selected an alternate-to-traditional
booting environment that requires nothing in boot, and having found no ESP
selected for mounting, had nowhere to put anything outside /usr/lib/modules/,
and may be the reason why the situation described in comment #3.

I suspect absent ESP in UEFI installation possibly the only significant
difference between mine and Mario's.
Maybe next up here I should do another fresh installation that includes
suse-module-tools-scriptlets and not sdbootutil-rpm-scriptlets or sdbootutil.