New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ventoy does not boot any OS #282
Comments
I also have a computer that won’t boot any ISO’s. It is a 2011 iMac, and I wish I could figure out what the incompatibility is. |
I have the same issue on a MacBook Pro 2011, Ventoy boots, but any ISO I select (supported, as listed) only results in a blinking cursor. |
At work, we use "HP Compaq dc7800 Small Form Factor PC", "HP Compaq Pro 6300 Small Form Factor PC", "HP Compaq Pro 6200 Small Form Factor PC" and "HP Compaq Pro 6000 Small Form Factor PC". I have updated to the latest BIOSes from HP, but when trying to legacy boot Ventoy (GPT formatted) on any of them, I get a blinking cursor before the menu appears. I am sure it is a problem with the way HP bootstraps the legacy code, as I have a Dell at home and it legacy boots a GPT formatted USB drive without issue. |
Hi there, just wanted to chime in. |
Same issue on a 2010 Mac desktop computer. I can get to the ventoy screen but once I select an OS to boot from it just shows a white underscore line in the middle of the screen |
Here testing a Vento 1.0.27, both GPT or MBR formated, with or without SecureBoot enabled on an updated (Catalina 10.15.7 firmware) MacbookPro11,3: Same problem verified, using different images I could found a curious fenomena: ISO's simply don't boot but some IMG files could, apparently those that use 'ELILO' booting manager: OpenELEC-Generic.x86_64-8.0.4.img or Lakka-Generic.x86_64-2.3.2.img (both linux for Kodi) actually boots kernel but could not mount it's root, only img that boot without problems was UEFI's free commercial version of memtest86-usb.img. Hope this help for developers to find what's going on here... Cheers. |
I tried the same Ventoy USB stick on thinkpads t440,x240 and x250. Almost the same bios settings for all those because I use Hackintosh but noticed only on x250, Ventoy was not able to boot any iso on it. I had Arch, Fendora, windows and ubuntu on the usb stick but none of those Iso worked. |
@NovaViper did you end up getting anywhere with this? I'm having the same issue. Have tested on multiple computers with both MBR and GPT options |
No, I eventually have up on flashing with ventoy and used etcher for the Mac, in every other device however I use ventoy |
Can't boot on Asus G73Jw with UEFI set in BIOS. 1.0.49 |
I tried Ventoy for the first time yesterday...encountered similar problem whereby several attempts at different ISOs did not work; just blank screen with blinking cursor. Later I discovered a trick (https://www.ventoy.net/en/doc_compatible_mark.html) to copy and paste ventoy.dat onto the usb's root directory of the image(ISO) file(s), and now able to boot... |
That page says Note that it says 'INSIDE THE ISO' - it does not say anything about placing the file the root directory of the USB drive??? Are you sure that fixed the problem - or could you use any name for the file or any file or any file in any folder? |
I have the same problem on my 2016 macbook pro. all my iso linux distros don't work but tails (a .img) does
I feel like this is key to fixing the problem. I'm investigating this but I don't know much about boot processes so any help is appreciated! edit: I've read more about iso and img files, basically an iso file is an img file with an iso filesystem. So somehow that's causing the problem |
I have this issue on my 2011 mid mac mini. I've tried windows10 21H2, Pop_OS21.10, ubuntu and so on. Using rufus all ISOs work |
I was able to accomplish inconsistent boots but it was locked up after the boot. Seems to me this is best left alone. |
Just adding to the pile of complaints. *Turn off computer, remove USB stick, turn on computer, press F9 for boot menu, insert USB stick, select USB drive. |
Does it boot on other systems? |
The 32GB flash did boot on this Samsung R-580 notebook. |
*Turn off computer, remove USB stick, turn on computer, press F9 for boot menu, insert USB stick, select USB drive. ???? *Turn off computer, insert USB stick, turn on computer, press F9 for boot menu, , select USB drive. |
See here for one: https://serverfault.com/a/1015987 BTW the 4GB flash formatted as GPT just booted an ASUS M2N-CM DVI board. |
Well, if you tried 'EVERY POSSIBLE WAY' then there is no solution in the world!
Note that when booting from USB, if legacy booting then I would use an MBR partitioned USB drive not GPT. You may also like to rename (temporarily) the \EFI folder on partition 2 of the Ventoy drive to some other name to prevent UEFI booting (e.g. \EFIxxx). |
Found this - seems improbable but you can try it: Also |
https://www.bleepingcomputer.com/forums/t/579505/at-wits-end-hp-dc7800-sff-will-not-boot-from-usb/ Fiddling with the BIOS is risky and I'm no longer young and eager to experiment. I did at least try with the original BIOS versions prior to updating them and still wouldn't boot from the Ventoy USB, at least not the dc7800. Did reset to defaults, did clear the BIOS through jumper and button, did disable/enable HDD through F5 and all that. |
Maybe you know someone with a Windows system and you can make some alternative boot sticks? Winsetupfromusb uses Microsoft Legacy boot files (MBR + bootmgr) and should be the most compatible or maybe a Rufus + Win10 stick. |
PS/2 keyboard and mouse, no other USB device external or internal. Tried 5 out of 6 rear USB ports so far. The 2 front ports don't work for some reason, there's voltage but no device gets detected there. Unfortunately got no other spare sticks and no access to Windows other than a 8.1 and maybe an XP. No easy way to transfer files between Mint and any of the Windows (except for using the sticks themselves), and no common access to Internet - need to move HSDPA modem from Mint to the other machine(s). Honestly, old 486/Pentium generic BIOS versions were much more resiliant and compliant despite their myriad of settings. Proprietary stuff is bad and limited. And they call it 'progress'. |
Tests on HP dc7800 SFF in Linux Mint 19.2 x64:
From the little observed that machine will only accept plain MBR disks, meaning no GPT or hybrid MBR, and it will happily boot with SYSLINUX from either FAT32 or NTFS. |
With sardu, why not just remove all usb devices except for the one you want? |
Let's say the other USB devices are busy at the moment; should I stop everything I do because of a poorly designed software? The E2B site is so badly designed that important information is easy to overlook. I see now the scripts are buried deep into a subfolder. But still there are too many hoops to jump through compared to all other tools. Anyway, on a whim I just installed *FreeNAS 9.2.1.9 (last MBR version) to the same 4GB USB disk using Mint's built-in tool Disk Image Writer, and the HP booted from it right away; it's currently running but too weird to configure for usage. Bottom line is, the combination of FAT16 + exFAT + GPT used by Ventoy is more than likely never gonna be accepted by that machine and probably other close models. Sad thing is none of the tested tools provides a true and reliable multiboot environment usable with such machines. |
Ventoy can make an MBR usb disk, just use the options tab. |
I did not only once. No dice. |
I tried putting ventoy.dat into an iso and it still didn't work. I followed these instructions to add the file to an iso, and then mounted the resulting iso to confirm ventoy.dat was in it, and it still had the same problem |
I've installed latest ventoy on my usb stick. It's working fine in general. Installed some computers with it.
But now I have an old notebook (hp pavilion dv6) from ~2011 which was shipped with Windows 7, where I only get a blinking cursor after selecting an operating system. Tried many different operating systems, but everytime I only get a blinking cursor on the upper left corner.
Do you have any ideas what I can do?
The text was updated successfully, but these errors were encountered: