Downloaded Lakka-Generic.x86_64-3.1.img.gz , extracted to ventoy partition and tried to boot but it fails with kernel mod errors related to device mapper and mounting problems.

I see that 2.3.2 is shown in the supported list of ventoy, does the new version need tweaking at ventoy end?

Tried in legacy as well as uefi ventoy boot mode, same issue.

Please suggest.

I am encountering a UEFI boot issue with a 32 GB Ventoy USB drive that I prepared. The menu with the list of ISO images appears, but when I select one I get a black screen with a white cursor, unless I boot in BIOS mode. I am using supported ISOs (Clonezilla and Manjaro Linux). Here is a screenshot of the vtdebug output:







The motherboard is an ASUS P8H67V and UEFI boot works ok with another tool called AIO Boot. What could be the problem here?

{ "VTOY_DEFAULT_IMAGE": "/sources/WinPE/Z-Win10PE_x64_UEFI.ISO"}

The ventoy version is output as a setting value in the ventoy.json file.
Default lower left version output



{ "VTOY_DEFAULT_IMAGE": "F6> Windows 10 HDD 부팅 메뉴"}

The ventoy version is not output as the value set in the ventoy.json file.
at the coordinates I set
The version is not printed.[/size]


coordinates i set I want to print the version from

I asked the following on the MX-Linux forum:
I can now successfully create a bootable Ventoy customized MX-Linux iso.
However, when I add the Ventoy "backend" persistence configuration, it
boots into an UN-customized instance!
Is there some option to boot skipping the persistence (until shutdown,
that is) ??
Thanks..

MX-Linux user 'fehlix' replied...
Justed booted up a couple of month older ventoy stick. ISTM, they
somehow have "hardcoded" the persistence option, without a way for the
user to choose whether persistence to use or not, when choosing ventoy's
persistence "backend". So I tend to agree with JayM that's rather a
ventoy issue, b/c they tweaked internal MX LiveUSB options, which was
always meant to allow the user to choose. In the way they done it (as I
see it), you can use the ventoy persistence "backend" but have not an
option to finetune. That might also be the reason why you see the
"vanilla" Live System without your data, b/c the missed to offer to the
user to copy over the saved persistence data (under/home) from the
compressed linuxfs file into the new persistence file.

Does this make sense?
Is there any way around this?

Thanks.

PaulJayD

Suggestion for ventoy installer (script and webui, app for windows):

Option to choose filesystem type for the ventoy data partition: (eg- ExFAT/NTFS/EXT/etc.)

Along with a warning for obvious limitations/pros-cons in a small message shown while installing if its an unconventional selection.

Comments from @longpanda and others appreciated.

Hello,

I would like to use TinyCore with Ventoy but when I download the ISO from the website :
http://tinycorelinux.net/12.x/x86/releas...urrent.iso

I have the following Error :
No bootfile found for UEFI!
Maybe the image does not support X64 UEFI!

Do you know how to do to use it ?
Kind regards

Hi there!



Can Ventoy be configured on an architecture not listed in the /INSTALL/tools folder? (i386, x86_64, arm, aarch64)

Does the partition style setting make a difference?   Does it affect the ability for a drive to boot thru UEFI or Legacy???

Thanks..

首先感谢作者开发了这么方便好用的程序。

问题描述如下：我把Ventoy安装到硬盘上使用（设备为清华同方一体机，CPU为9代i5），在分区设置中保留了400G空间用来存放其它数据（整个硬盘容量为1T，实际可用931G）。用最新的1.0.45版本升级后，400G空间上建立的分区被清除，用DiskGenius可以发现丢失分区并找回，数据还在。开始以为是偶然现象，后来在另一台联想商务机上进行Ventoy升级（4代i5，1T硬盘同样保留400G空间），结果相同，efi分区后的空间上建立的分区被清除，需要用分区软件找回。

不知道是否有其他用户也遇到了这个问题，毕竟影响到数据安全，请作者进行测试，如果确实存在这种情况请在后续版本中进行修正，谢谢！

Greetings, I would like to ask about a question I have. I have created a 1 Tera pendrive, with the Ventoy program, version 0.45. But when I try to boot from the pendrive, instead of leaving the ISO selection window, to install ... I get a window in CMD, which I attach a screenshot. I don't know what it is, in a previous version, Ventoy had worked very well for me, it started in the iso files selection menu ... but now, I don't know if it will be because of the size of the pendrive, but it doesn't start me ... .Thank you