Rescuezilla 2.5 will not boot on 6th gen intel i7-6700t with iGPU via Intel AMT

[pcmike]

[x]: This bug persists when memory is increased beyond 8GB.

Describe the bug I have an old(er) HP EliteDesk that I run proxmox on and I wanted an easy (eg. graphical) way to backup an image of the host in between major PVE upgrades so I could easily roll back to previous state if something blew up. It has AMT enabled and I'm accessing it from mesh central. The system has two DPs and one of then has a DP<>HDMI>HDMI dummy plug inserted. I'm "running" (quotes because the container is running, but you can't bind port 69 to the container and must use DSM's tftp server, which I've pointed to netboot's remote menus) netbook.xyz on synology and passing the netbook.xyz.kxpe by way of my UDM SE's DHCP server (no files edited for various BIOS' just within the Network GUI). So far I've been able to boot redorescue and pop os from within mesh central/amt's Remote Desktop, but I cannot boot rescuezilla 2.5; all I get is a blank screen. When I read up on rescuezilla's website it says for users who've made a USB key to choose graphical fallback mode at boot, but obviously I don't get such an option when booting through netboot. If that doesn't work it says to use 2.4.2 which isn't based on Noble. First, is there a way to pass options to rescuezilla 2.5 to use this graphical fallback mode? If not, is there any chance that 2.4.2 can be added to the remote assets? If not, how would I add 2.4.2 to my local assets? I'm not sure how to split their image into the 3 separate parts and then add it locally, but either way.. I'm hoping having 2.4.2 available remotely may benefit for than just me.

"If you have a blank screen, try "Graphical Fallback Mode" from the Rescuezilla boot menu (after selecting a language). If that doesn't work, try the alternative ISO image. Each variant has slightly different video drivers and Linux kernel versions, so often have slightly different graphics support." << https://github.com/rescuezilla/rescuezilla/releases/tag/2.5

To Reproduce Steps to reproduce the behavior:

1. Boot Rescuezilla 2.5.

Expected behavior Expect it to boot.. instead just get a blank screen.

[pcmike]

Came back to say I dropped the menus back to 2.0.78 which has rescuezilla 2.4.2 and it still doesn't boot into the "desktop" so I guess that isn't the answer. I'm open to any help I may be able to come by. Thank you.

[TheLinuxGuy]

I'm also having issues booting rescuezilla 2.5 on proxmox VM - not sure if your error is similar to mine. "Failure writing output to destination"

[antonym]

@pcmike You can try some of these options from the grub.cfg to see if they work by adding kernel params from the utility menu. If you find on that works, I can add the kernel option:

    submenu "$enduser_readable_language" $lang $locale_opts --id ${lang}-item {
        # Re-assign internal GRUB variables, cleared through change of context
        set lang="$2"
        set theme=/boot/grub/theme/theme.txt
        shift 2
        set locale_opts="$*"
        # If boot fails, reboot and try selecting Safe Mode instead
        menuentry $"Start Rescuezilla" $locale_opts --id standard-start-item {
            shift 1
            set locale_opts="$*"
            linux  /casper/vmlinuz boot=casper quiet splash fastboot fsck.mode=skip noprompt edd=on ${locale_opts} ${isoboot} --
            initrd /casper/initrd.lz
        }

        # VESA video mode
        menuentry $"Graphical fallback mode" $locale_opts --id graphical-fallback-item {
            shift 1
            set locale_opts="$*"
            linux  /casper/vmlinuz boot=casper xforcevesa nomodeset vga=791 fsck.mode=skip noprompt edd=on ${locale_opts} ${isoboot} --
            initrd /casper/initrd.lz
        }

        # Loads the image into RAM, so the USB or CD-ROM can be ejected
        menuentry $"Load USB into RAM" $locale_opts --id load-into-ram-item {
            shift 1
            set locale_opts="$*"
            linux  /casper/vmlinuz boot=casper quiet splash fastboot toram fsck.mode=skip noprompt edd=on ${locale_opts} ${isoboot} --
            initrd /casper/initrd.lz
        }

       # Verify integrity of USB drive
        menuentry $"Check USB for defects" $locale_opts --id verify-integrity-item {
            shift 1
            set locale_opts="$*"
            # The absence of fsck.mode=skip causes md5sum to be checked, to help detect bitrot data corruption
            linux  /casper/vmlinuz boot=casper quiet splash fastboot noprompt ${locale_opts} ${isoboot} --
            initrd /casper/initrd.lz
        }

[antonym]

I'm also having issues booting rescuezilla 2.5 on proxmox VM - not sure if your error is similar to mine. "Failure writing output to destination"

Make sure you have enough memory, sounds like it's having issues writing the disk to memory.