Mercury Neo 2025.03.19 not booting from iVentoy netboot

I think this is something for this category. I’m using iVentoy as Netboot Server on my LAN which for some reason can’t boot the latest ISO.
Standard UEFI BIOS and PXE Boot over IPv4 brings me to the boot selection of the ISO but then starting the UEFI or fallback variant only shows barely readable text which says something like INIT NOT FOUND

Checksums of the ISO are fine. No idea how to fix this so I went with an older ISO file…

Maybe ventoy needs to be updated?

Never got it working to use PXE with EndeavourOS ISO, as we do only have a graphical installer… it’s not the same as with pure arch ISO, where things happen in terminal way.

With this… I am not sure if EndeavourOS ISO is properly prepared to work in pxe mode.

What ISO exactly is working?

[Cassini 22.12] archiso_pxe_common hook fails to configure network - #12 by dalto seems the hint? If you want, I can provide an ISO with this package included.

Just see i was already adding this package back then..

issue must be something else.

i bet @Moonbase59 will give some nice hints now :wink:

If not “fattening” the ISO too much with it, that might be nice. Think classroom use: We could use Clonezilla or iVentoy to start out classroom PCs with a fresh OS.

If ever I’ll manage to convince some people they want Linux classes, that is. :wink:

EDIT: @joekamprad can read minds, it seems… :rofl:

i had a teacher asking me some times ago was using EndeavourOS to teach about Linux :wink:

1 Like

Ventoy works fine, i did the February iso and march iso installation with it on 4 machines.

i do not think it will be much to add.. we only need to find out what is missing or changed and testing it. I have easy to manage builder dockers for ISO its always possible to create ISOs with changed settings and packages.

1 Like

Ventoy & iVentoy are different beasts (iVentoy being a PXE server).

With Ventoy, I’m still pondering about the persistence issue. Ordered some USB sticks to try on bare metal, turns out the shop had a .de web address but are actually in Denmark, so I still wait for delivery. (Nothing wrong with this, shoutout to our Danish friends.)

I might come back on that… :wink:

Thanks for that, thought OP made a typo. Never heard of “iVentoy”.

iVentoy is a rather “new” invention of that same guy who gave us Ventoy, looks promising. Free tier goes up to 20 clients, if I remember correctly. Reasonable free # clients for small non-profit teaching, I’m thinking.

Interestingly enough, he has EOS on his “Tested ISO” listing, maybe he tried Cassini or earlier.

1 Like

says cassini

1 Like

i just checked around that and i was able to find some changes on the boot entries that could be related.
@daren in case you want to test i can give you a link to download ISO with the changes. But i will not post this public.

I’d gladly test it. Just got a new Laptop in which needs a new setup. :grinning_face:

I was using the EndeavourOS_Galileo-Neo-2024.01.25 - quite some time in between but it works without an issue. I also used Cassini before that too. As Moonbase59 mentioned iVentoy is a beast but for 99% of my needs it gives me practically every OS under the sun for easy netbooting (together with netboot.xyz via chainloading)

Thanks for the ISO @joekamprad.
Just tried to spin it up but the issue persists.

After choosing the UEFI boot option from the ISO it fails to INIT NOT FOUND

strange .. build with latest mkarchiso and all boot entries are even with latest changes.
Could be it has issue as we have multiple entries for INITRD?

arch has no ucode entries:

@daren Shot in the dark—you using iVentoy 1.0.20 already?

Latest versions hat some ominous bug fixes like:

  • Fix the crash when boot some special ISO files.

Yea, using 1.0.20

tried the fallback boot entry too? as of it does not load the ucodes

Yes, ends with the same error