-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[issue]: Not Booting ISOs on Macbook #1056
Comments
Ventoy actually doesn't support Macbook. I never test it on Macbook.
|
Not press |
I tried that prior to posting my pervious comment:
|
Sounds like #282 |
Currently ventoy does not support mac
…On Sat, Oct 2, 2021 at 10:43 PM Jack R ***@***.***> wrote:
Sounds like #282 <#282>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1056 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARAGYL7BH4NGZZVH2XDNWHTUE4SAJANCNFSM5B6KKKGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Was able to boot Linux ISOs on an old iMac 2009 using CTRL+R (grub2). Thank you! |
I respect that the author does not support a Mac. Because others will search for and find this issue, I'll add my tests/success: Using Ventoy With an Apple Macbook Pro A1278 - 13" Laptop (Mid 2012) For OpenCore this Macbook is
Tested and working with these live distributions:
This did not work with:
Note that if you are testing multiple distributions, then it is best to power off the system. Simply rebooting may not present the USB stick as a boot option. Using Wimboot mode (instead of
macOS ( |
FYI, booting Linux with grub2 mode works, but booting with normal mode fails (shows a white MX did work for me with v1.0.87 and 1.0.88. Windows 10 (21h2) and Windows 11 (22H2) both booted and installed with WIMboot mode. I tested this on a Late 2011 13" MBP. Also @spiralofhope Ventoy doesn't support macOS ISOs at all... macOS stores the EFI files on a different location then the standard locations (see Eclectic Light's article on this) |
This solved my issue of not being able to Vintoy-boot Linux ISOs on a 2013 Mac Pro. Thanks! |
In versions 1.0.80 and newer those options show up without keyboard shortcuts. |
@ventoy it seems that using grub2 makes it work, maybe it should default to it when detecting a macbook? |
But the Macbook is not supported. The author does not have one or write software for it. Perhaps someone will provide a pull request with necessary programming, but that code still might not be included since, again, Ventoy unfortunately does not support a Macbook. Maybe someone will buy the author a Macbook? |
why does the author have to have access to a physical macbook to accept a community-tested proposal? Do you think Linus Torvalds has access to every existing pc and tests every change on them in order to push changes into the kernel? |
The kernel project is not just a bunch of people, it is a network of curated strata of developers who check the code of one another. Submissions make their way up the chain, each being examined and tested before maybe making it into the mainstream codebase. Ventoy is not that. Adopting someone else's alien and untestable code is not good practice for this project. I have been subject to the following statement, and I hate it: You are free to fork it. That is what some other developer would have to do to implement Macbook features. Whatever developer writes Macbook code for Ventoy would themselves need to have a Macbook. Although no developer should rely on some random contributor's code and testing, it's hypothetically possible someone else's code could be so simple that the Ventoy developer could understand and trust it with no testing, so that it would not need to be forked. That is a hypothetical though, and so no promises get made. It's difficult to trust a stranger. Some more on that topic... Users should themselves also be wary of such code being introduced. What if the original side-developer becomes unavailable and that code becomes orphaned? Perhaps the user grows fond or reliant of the code. Perhaps that code causes weird bugs later and cannot be fixed easily (since the lead developer cannot test properly). Perhaps it becomes tangled into the codebase and can't even be removed easily. Even projects which have multiple trusted developers end up with problems when one of the developers become unavailable. While this has been an interesting thought experiment, I hope you understand why I will end this topic with: "I hope this minor Macbook support is simple to be included and supported by a different developer, and could be disabled by the main developer if it causes problems in the future." And so I hope it is understandable when this developer says, politely, no. |
@spiralofhope that's now perfectly clear |
I hope I came across as respectful. :) |
Official FAQ
Ventoy Version
1.0.49
What about latest release
Yes. I have tried the latest release, but the bug still exist.
BIOS Mode
UEFI Mode
Partition Style
MBR
Disk Capacity
16Gb, 128Gb
Image file checksum (if applicable)
Yes.
Image file download link (if applicable)
No response
What happened?
Device - Macbook Air A1466 (Core i5).
Context - Use Ventoy to chainload other ISOs. Tried Windows 10 20H2, Hirens Boot CD (WinPE), Ubuntu 16.04, Linux Mint 20.04, voidlinux, Alpine Linux 3.14.1.
n.b. - tried Ventoy with both MBR & GPT partition types.
Behaviour - Ventoy boots, lists ISOs, but further chainloading them (any of the above) results in a black screen with a non-blinking cursor.
The same Ventoy USB boots fine on a typical laptop (Lenovo Thinkpad T420).
Other bootable USBs (using the same stick) prepared by other apps (Rufus, Balena Etcher) boot fine on the Macbook Air.
The text was updated successfully, but these errors were encountered: