back in the day can put patched kernel.. but not sure if ventura would work with some custom kdk stuff. when I boot kdk kernels it always hangs on hacktonish but not on real macbook. haven't figure it why
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Instead of guessing wildly, just read what @Syncretic wrote and explained about it. There is even a whole thread about it.
Sorry. Too much work and I have other things to do.
macOS Ventura 13 beta 7 released to developers.
Last edited:
Last edited:
Everything working... My tree devices are updated to Ventura 13.0 Beta 7. Fresh install for all.
can you please teach me how to get oclp 0.5.0? I can only see 0.4.10, Im not a tech expert but hey, thanks
I understand the risks I will face and accept full responsibility. Please teach me how to get oclp0.5.0, by the way, I have backup option, don't worry. thanks
When your computer's bricked down backup won't save you.
I read that it's a alpha version and can brick the hardware. I bet to stay for a while. I'm as spectating like you
Well, either compile it from the sources or twiddle around a bit with the download path for the compiled package. Hints were on this thread already - and still work.
Until someone can explain how it might brick "the hardware", I'd regard that as a rumor. We're on Mac, not iPad/iPhone etc. If things go wrong to a non-boot situation, boot from external drives and restore/re-install the internal volume.
(corrupting the boot flash with an update/upgrade payload within the installer package does not count - as there are no suitable blobs there any more for our unsupported machines and thus will not trigger the flash process. Doing this on purpose (like in @dosdude1 times with i.e. specially modified APFS or NVMe boot patches in "ROM") cannot happen by chance).
So, anyone... ?
Last edited:
iMacs have been bricked before (needing a hardware flasher to resolve) because of bugs in Apple's firmware update process. It is noted in the OCLP bugtracker.
Noted. Thanks.
I recall the issue when it occurred to Apple-supported iMacs a couple of months ago. Unsupported machines also affected? This would only mean "don't upgrade your stuff because if Apple screws it, you'll be in trouble on any machine - supported or unsupported" ;-)
Countermeasure then: remove the firmware payload off any installer during early first runs as a precaution.
(Different story applying Open Core boot to machines still receiving upgrades/updates).
Last edited:
It is possible that by a "backup option" he is saying that he has more than one computer.
Its always possible that an installer or the OS botches the nvram volume of the firmware. There were examples of Monterey writing large blobs of kernel panic logs into the nvram exceeding the limit on Mac Pro 4.1/5.1
If things run mad and the nvram is filled due to the end of the periodic circle of filling/clearing nvram it can lead to a bricked Mac what can not start and needs nvram/firmware cure by re-programming the flash chip with a backup of this particular machine (as firmware contains hardware IDs). So everyone should have a firmware backup.
What helps a bit to overcome this situation is to force a manual nvram garbage collection by a multiple nvram reset.
If things run mad and the nvram is filled due to the end of the periodic circle of filling/clearing nvram it can lead to a bricked Mac what can not start and needs nvram/firmware cure by re-programming the flash chip with a backup of this particular machine (as firmware contains hardware IDs). So everyone should have a firmware backup.
What helps a bit to overcome this situation is to force a manual nvram garbage collection by a multiple nvram reset.
Another 5K Background sharing
Ventura Graphic Design
Enloy
Pretty nice in Desktop Background and also OC boot screen
Ventura Graphic Design
EnloyPretty nice in Desktop Background and also OC boot screen
Besides my MBA 7,2 with Broadwell I could install Ventura beta 7 on my iMac 14,1 with Haswell. No crashes at all with Haswell post patch. Fotos now works. No chance atm with Broadwell post patch. Fotos crashes at once.
I used the latest compiled 0.50 OCLP.
Thanx so lot for the hard work by the developers.
New: Fotos does`t crash on Broadwell with new compiled build👍👍 with update over Monterey.
On a fresh Ventura install still Fotos crashes - very strange!
I used the latest compiled 0.50 OCLP.
Thanx so lot for the hard work by the developers.
New: Fotos does`t crash on Broadwell with new compiled build👍👍 with update over Monterey.
On a fresh Ventura install still Fotos crashes - very strange!
Attachments
Last edited:
Added a new machine to page #1 list of Macs that can boot Ventura: MacBook Air3,2
(C2D with Nvidia 320 Tesla GPU). Of course, no accel at all at the moment.
(C2D with Nvidia 320 Tesla GPU). Of course, no accel at all at the moment.
Any rumors out there about any progress on accel for non-metal? Anything at all?
Just FYI (but probably already known by the developers): the latest Photoshop reports the Kepler dGPU of my MBP11,3 (KDK-less root patched for Intel iGPU and Nvidia dGPU, on an external SSD for experimenting with Ventura, with the latest alpha OCLP 0.5.0) as partially unsupported: so, it looks like currently it has no OpenCL support in Ventura (while in Monterey it passes all checks, OpenCL included); let’s hope that all this can be fixed in a future OCLP release…
Last edited:
Did you change the os.dmg with the IPSW file of the bêta 7? Normally the size is 4 225 761 280 (4,23 GB).
Had exactly the same problems. Then remembered to have read somewhere of apparent differences between "amfi_get_out_of_my_way=0x1" and "...=1". Edited the config plist to the latter - and from then on it worked and boots beta 7 with latest OS.dmg.
Not sure if this was "placebo" or not. Pls try and report back...