Bootloader fails to install correctly

[pogof]

Follow the instructions on screen. Stick around for the installation process because you will be prompted to select the drive where to install the bootloader on.

This doesn't happen, instalation fails with grub error

grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.

I tried fixing it but was unfortunately unsuccessful.

[voidderef]

I don't have the capacity to debug and fix this myself, but I can try to assist you in triaging the issue, and maybe you find a workaround. What have you tried in order to address this issue?

[pogof]

I have sort of fixed the issue by installing on a HDD instead of SSD.

But to address the original problem still:

On PopOS 22.04, all depends were installed, I was using Samsung PM871a 256GB sata SSD with SATA to USB reader/dongle.

Bit of googling and copiloting lead me to belive that for grub to install successfully I need few MB as a extra partition and to install the bootloader there. After modifying the scripts a little bit I was able to get past Grub setup, however when I tried the disk in MK9 it was not booting and not visible to the machine. I unfortunately don't have the folder with my modifications (I probably deleted it by accident).

Installed like that it did sort of start in qemu, but it didn't boot into a game.

However I have found out that using this SSD was a dead end anyway as any attempts to use it to install Windows PX, 7 and 8.1 were not successful on MK as installing an (supposedly) working image of one of the games. I am unsure if it is the SSD's fault or MK's.

Installing on another computer with HDD (Some Seagate 1TB, not sure the exact model) and with the disk connected internally, it installed without an issue and I am able to boot it up (right now just without a game).

I do however see some weird errors something about BMDMA, failed command: READ DMA, I am attaching a screenshots. I have seen very similarly looking errors with the other disk in qemu so I assume it is a quirk of the os and not my disks dying?

Lastly very unrelated, since I intend to use this with lxio, do I need to configure something differently or can I just use the default "for cab" configs that are bundled in the pumpos download?

[pogof]

I have tried to load NXA with 1.13 tools, but am stuck in this error loop (pic 2).

[pogof]

Update, I have just followed the steps manually, installing the OS from ISO, then rewriting the install script to be as basic as possible. OS now boots without error.

I did deploy game, tools rest of the files manually too. Although the game doesn't boot on startup (I forgot to copy new boot.sh) I was able to run NXA.

I have wrote few scripts already to help with the setup, I will publish them to my repository later, not sure if it is really usable to be merged as it is going to be very basic. (No ITG, no single/batch setup, rather just batch setup where possible, etc)

[voidderef]

Update, I have just followed the steps manually, installing the OS from ISO, then rewriting the install script to be as basic as possible. OS now boots without error.

I did deploy game, tools rest of the files manually too. Although the game doesn't boot on startup (I forgot to copy new boot.sh) I was able to run NXA.

I have wrote few scripts already to help with the setup, I will publish them to my repository later, not sure if it is really usable to be merged as it is going to be very basic. (No ITG, no single/batch setup, rather just batch setup where possible, etc)

Great to hear you got it working and yhanks for replying that you figured it out and how. That can be useful to anyone else reading this in the future.

Feel free to link/post these scripts here in the issue if you want. Might be useful for others who also want to customize the setup.

Please close this issue once you consider this done.