I recently downloaded the latest JWM image to install on a new Zen 5 system but I'm running into an issue Ive never experienced with an Obarun install and not sure how to proceed. Of note, during the install I've always utilized the EfiStub installation, but at the point of choosing to install the boot loader during the last phase of the installation it kicks me from the install back to the cli and I have to run the install script again and it succeeds the second time, though of course still doesn't actually boot. I tried to use Grub as a work around to simply get things installed, but Grub kicks me out of the install at the same point but no matter how many times I try rerunning the obarun-install script it will not complete the installation. I've attempted to install to NVME and sata SSD with the same results. I've got secure boot, TPM & CSM disabled in the BIOS. Attached is a picture of the screen where it ends the boot process. Any guidance would be greatly appreciated.

/run/66/log/0/current -

2024-11-27 12:10:54.794137918  [Start services of tree boot...]
2024-11-27 12:10:54.802252265  66-execute: info: Starting service: boot@system:tty-earlier@tty12
2024-11-27 12:10:54.802253275  start: info: Initialized successfully: boot@system
2024-11-27 12:10:55.806751955  signal: info: Initialized successfully: boot@system:system-hostname
2024-11-27 12:10:55.806763424  signal: info: Initialized successfully: boot@system:mount-run
2024-11-27 12:10:55.806774834  signal: info: Initialized successfully: boot@system:populate-run
2024-11-27 12:10:55.806775594  signal: info: Initialized successfully: boot@system:mount-tmp
2024-11-27 12:10:55.806776154  signal: info: Initialized successfully: boot@system:populate-tmp
2024-11-27 12:10:55.806781724  signal: info: Initialized successfully: boot@system:mount-proc
2024-11-27 12:10:55.806783944  signal: info: Initialized successfully: boot@system:mount-sys
2024-11-27 12:10:55.806795573  signal: info: Initialized successfully: boot@system:populate-sys
2024-11-27 12:10:55.806799553  signal: info: Initialized successfully: boot@system:mount-dev
2024-11-27 12:10:55.806808263  signal: info: Initialized successfully: boot@system:mount-pts
2024-11-27 12:10:55.806814023  signal: info: Initialized successfully: boot@system:mount-shm
2024-11-27 12:10:55.806821662  signal: info: Initialized successfully: boot@system:populate-dev
2024-11-27 12:10:55.806828812  signal: info: Initialized successfully: boot@system:mount-cgroups
2024-11-27 12:10:55.806836082  signal: info: Initialized successfully: boot@system:mount-branch
2024-11-27 12:10:55.806843472  signal: info: Initialized successfully: boot@system:system-hwclock
2024-11-27 12:10:55.806850221  signal: info: Initialized successfully: boot@system:modules-kernel
2024-11-27 12:10:55.806857291  signal: info: Initialized successfully: boot@system:system-random
2024-11-27 12:10:55.806864471  signal: info: Initialized successfully: boot@system:modules-system
2024-11-27 12:10:55.806871341  signal: info: Initialized successfully: boot@system:system-sysctl
2024-11-27 12:10:55.806882600  signal: info: Initialized successfully: boot@system:udevd-log
2024-11-27 12:10:55.806892370  signal: info: Initialized successfully: boot@system:udevd
2024-11-27 12:10:55.806899020  signal: info: Initialized successfully: boot@system:udevadm
2024-11-27 12:10:55.806905700  signal: info: Initialized successfully: boot@system:system-fontnkey
2024-11-27 12:10:55.806913029  signal: info: Initialized successfully: boot@system:system-fsck
2024-11-27 12:10:55.806920269  signal: info: Initialized successfully: boot@system:mount-fstab
2024-11-27 12:10:55.806927809  signal: info: Initialized successfully: boot@system:system-branch
2024-11-27 12:10:55.806934549  signal: info: Initialized successfully: boot@system:mount-rw
2024-11-27 12:10:55.806941398  signal: info: Initialized successfully: boot@system:local-loop
2024-11-27 12:10:55.806948098  signal: info: Initialized successfully: boot@system:local-authfiles
2024-11-27 12:10:55.806955658  signal: info: Initialized successfully: boot@system:local-time
2024-11-27 12:10:55.806962908  signal: info: Initialized successfully: boot@system:local-sethostname
2024-11-27 12:10:55.806970737  signal: info: Initialized successfully: boot@system:local-tmpfiles
2024-11-27 12:10:55.806978227  signal: info: Initialized successfully: boot@system:local-dmesg
2024-11-27 12:10:55.806985807  signal: info: Initialized successfully: boot@system:mount-netfs
2024-11-27 12:10:55.806992417  signal: info: Initialized successfully: boot@system:local-branch
2024-11-27 12:10:55.806998986  signal: info: Initialized successfully: boot@system:runtime-branch
2024-11-27 12:10:55.807005736  signal: info: Initialized successfully: boot@system:canopy
2024-11-27 12:10:55.807013136  signal: info: Initialized successfully: boot@system:tty-rc@tty1
2024-11-27 12:10:55.807020806  signal: info: Initialized successfully: boot@system:tty-rc@tty2
2024-11-27 12:10:55.810504068  66-execute: info: Starting service: boot@system:udevd-log
2024-11-27 12:10:55.811222994  signal: info: Successfully started service: boot@system:udevd-log
2024-11-27 12:10:55.819303102  signal: info: Successfully started service: boot@system:mount-run
2024-11-27 12:10:55.819359350  signal: info: Successfully started service: boot@system:mount-proc
2024-11-27 12:10:55.823315947  signal: info: Successfully started service: boot@system:system-hostname
2024-11-27 12:10:55.833146057  signal: info: Successfully started service: boot@system:mount-sys
2024-11-27 12:10:55.839478534  signal: info: Successfully started service: boot@system:system-sysctl
2024-11-27 12:10:55.839495673  signal: info: Successfully started service: boot@system:mount-dev
2024-11-27 12:10:55.849407829  signal: info: Successfully started service: boot@system:mount-tmp
2024-11-27 12:10:55.850602029  signal: info: Successfully started service: boot@system:mount-shm
2024-11-27 12:10:55.852058451  signal: info: Successfully started service: boot@system:mount-pts
2024-11-27 12:10:55.852932951  signal: info: Successfully started service: boot@system:populate-tmp
2024-11-27 12:10:55.853388436  signal: info: Successfully started service: boot@system:populate-run
2024-11-27 12:10:55.865323974  signal: info: Successfully started service: boot@system:populate-dev
2024-11-27 12:10:55.870782501  signal: info: Successfully started service: boot@system:populate-sys
2024-11-27 12:10:55.960751484  signal: info: Successfully started service: boot@system:mount-cgroups
2024-11-27 12:10:55.964055773  signal: info: Successfully started service: boot@system:mount-branch
2024-11-27 12:10:55.969701173  signal: info: Successfully started service: boot@system:system-random
2024-11-27 12:10:56.026282620  signal: info: Successfully started service: boot@system:system-hwclock
2024-11-27 12:10:56.136735555  signal: info: Successfully started service: boot@system:modules-system
2024-11-27 12:10:56.195671182  signal: info: Successfully started service: boot@system:modules-kernel
2024-11-27 12:10:57.217455862  signal: info: Successfully started service: boot@system:udevd
2024-11-27 12:11:01.355894245  signal: info: Successfully started service: boot@system:udevadm
2024-11-27 12:11:01.389928920  signal: info: Successfully started service: boot@system:system-fontnkey
2024-11-27 12:11:01.409818361  signal: info: Successfully started service: boot@system:system-fsck
2024-11-27 12:11:01.413945682  signal: info: Successfully started service: boot@system:mount-fstab
2024-11-27 12:11:01.417136435  signal: info: Successfully started service: boot@system:system-branch
2024-11-27 12:11:01.424707370  signal: info: Successfully started service: boot@system:mount-rw
2024-11-27 12:11:01.428601749  signal: info: Successfully started service: boot@system:mount-netfs
2024-11-27 12:11:01.432074162  signal: info: Successfully started service: boot@system:local-sethostname
2024-11-27 12:11:01.435854946  signal: info: Successfully started service: boot@system:local-authfiles
2024-11-27 12:11:01.436730196  signal: info: Successfully started service: boot@system:local-time
2024-11-27 12:11:01.464665626  signal: info: Successfully started service: boot@system:local-loop
2024-11-27 12:11:01.499053880  signal: info: Successfully started service: boot@system:local-tmpfiles
2024-11-27 12:11:01.509413851  signal: info: Successfully started service: boot@system:local-dmesg
2024-11-27 12:11:01.512868845  signal: info: Successfully started service: boot@system:local-branch
2024-11-27 12:11:01.530082676  66-execute: info: Starting service: consolekit-log
2024-11-27 12:11:01.530102455  66-execute: info: Starting service: openntpd-log
2024-11-27 12:11:01.530214271  66-execute: info: Starting service: dbus-log
2024-11-27 12:11:01.530220761  66-execute: info: Starting service: connmand-log
2024-11-27 12:11:01.530316978  66-execute: info: Starting service: wpa_supplicant-log
2024-11-27 12:11:02.535642641  66-execute: info: Starting service: scandir@oblive:svscan@oblive-log
2024-11-27 12:11:02.576852545  signal: info: Successfully started service: boot@system:runtime-branch
2024-11-27 12:11:02.580118355  signal: info: Successfully started service: boot@system:canopy
2024-11-27 12:11:02.581770590  signal: info: Successfully started service: boot@system:tty-rc@tty1
2024-11-27 12:11:02.581984613  signal: info: Successfully started service: boot@system:tty-rc@tty2
2024-11-27 12:11:02.582268853  signal: info: Successfully started service: boot@system
2024-11-27 12:11:02.583742894  tree: info: Successfully started tree: boot
2024-11-27 12:11:02.585825123  66-execute: info: Starting service: boot@system:tty-rc@tty1
2024-11-27 12:11:02.585889371  66-execute: info: Starting service: boot@system:tty-rc@tty2

/run/66/log/populate-tmp
66-execute: info: Starting service: boot@system:populate-tmp
populate-tmp: info: create .X11-unix and ICE-unix file

One more thing of note is that on my old system I was able to boot using a USB drive made utilizing any number of ISO to USB or dd methods. It would have no issue loading the Obarun UEFI method, but now I can't even get a normal USB drive to boot at all when made using dd. The only way I can get the live USB to boot is by using Ventoy and selecting Grub2 boot. When I would boot using Ventoy before (old system and before the latest Obarun image) I was also able to utilize the usual Obarun UEFI boot without issue. It seems likely its something I'm overlooking as far as the boot procedure is concerned with this new system, though I'm not sure what exactly.

This is where the boot process hangs when attempting to boot the JWM image via USB using "Obarun iso UEFI CD"

I went ahead and added the old Obarun image from the previous release that worked on my old machine (obarun-JWM-2024.05.04-x86_64.iso) back onto my Ventoy drive to see if it would load on my new machine and it loads up no problem at all without having to select grub2 boot. I also created a new DD imaged USB drive with the previous release of Obarun and it boots up no problem as well. It would seem since the old image works fine but the new one does not that there is something different with the new Obarun image that is causing an issue with the boot process.

Since I was able to successfully boot using the previous release of Obarun (using standard Obarun UEFi boot from a DD created USB drive), I went ahead with an installation to see if it would work. The installation itself proceeds just as it always had previously and EFISTUB was able to be selected and installed without kicking me from the installer and forcing me to run the script again. It successfully completed as it always had when using this image but when I went to reboot into the newly installed system, it hung at the same place as the newly released Obarun image. Whatever is causing the issue seems to be downloaded via the installer due to the way Obaruns installer functions by pulling all of the latest packages via internet connection at install time.

That's wonderful news. Will a new iso image need to be put out for download or is this something that will eventually be resolved via the currently available image due to the real time internet connected installation method that Obarun employs?