AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Easy2boot vs ventoy9/25/2023 ![]() Sh CreatePersistentImg.sh -> persistence.dat in 1GB size and ext4 filesystem and casper-rw label I have provided a CreatePersistentImg.sh script here.ĭownload it and just run sudo bash CreatePersistentImg.sh in the linux shell, by default a persistence.dat file will be created with size=1GB fs=ext4 label=casper-rw. If you don't want to use the pre-created file and want to create it by yourself. You can download pre-created image files from Create by yourself You can directly download the pre-created image files or create it by yourself. The backend image file is a disk image with a label. Please refer Multi-Mode Option for details. You can set different configurations for different BIOS mode. If autosel not exist, it's the same as it set equal to 0. If autosel exist, then the corresponding menu item will be used and the prompt menu will NOT be popped up anymore. Prompt menu will be popped up, the default selected menu item is as described above, no timeout, will wait for user selection all the time. Prompt menu will be popped up, the default selected menu item is as described above, when timeout the corresponding menu item will be selected. Optional, if you set it, the value must be greater than or equal to 0 ![]() If not set, default is 1.Ġ: boot without persistence backend image fileġ: boot with the 1st persistence backend image fileĢ: boot with the 2nd persistence backend image fileģ: boot with the 3rd persistence backend image file If you set it, that means you auto select the corresponding option in the prompt menu. The persistence backend image file path for the iso file. This option supports fuzzy matching, please refer About Path Matching Refer VentoyPlugsonĪ persistence array is defined to describe the configuration in /ventoy/ventoy.json. Recommend to use VentoyPlugson, a GUI ventoy.json configurator. And use Live USB Persistence boot option.įedora-Workstation-Live-x86_64-33-1.2.iso Nothing makes it possible to boot pure UEFI ISO's in Ventoy on my x250.Arch/ArchMan/ArchBang/ArchLabs/BlackArch. UPDATE: Downgraded my BIOS till 1.27 (the 2017 version) and Ventoy down to 1.0.67. Will post an update on this if I succeed (hopefully). If someone tries to solve this issue just like I'm trying (will probably downgrade the BIOS eventually), my UEFI BIOS Version is N10ET63W (1.42), the UEFI BIOS Date is (YYYY-MM-DD). We seriously need more bootloader freedom on computers, clearly the computer 'companies' are as always not doing their job they are getting paid for. Like everyone else said here when booting legacy all ISO's work just fine, Windows or Linux, normal boot or other methods. My USB is an MBR partitioned and Secure boot enabled one, but of course on my computers Secure Boot is disabled. ![]() Before that in UEFI only mode I was able to boot Linux ISO's in normal mode too, and Windows ISO's all worked fine whether wimboot or normal mode. This all happened after updating my BIOS after 2-3 years last week. When booting UEFI only, I can boot all Linux ISO's (only in grub2 mode), but WinPE and Windows based ones are not working in normal, wimboot or memdisk mode. I have the same issue many described here, boot process hangs after install block io protocol XXXXXXXX. ![]()
0 Comments
Read More
Leave a Reply. |