Ventura testing #84
Comments
|
While installing the latest beta I got asked for a username and password when selecting a target disk haha. It's a bug. The workaround is to do a text install of macOS. 1: Format disk as normal Replace TARGETDISK with whatever you named the disk when formatting it. |
|
Everything seems to work, including wireless and bluetooth. I paired up a Microsoft mouse and it works as it should. Not really liking the new design but maybe it will grow on me. In the screenshot "about this Mac" and the new system preferences.
|
|
It took a long time to sleep on its own but I think thats due to a lot of background activity that macOS does on first boot/clean installs. I recall it used to show a notification about slower performance while it's doing its post install things. I assume once it is done it will sleep faster when idle. Putting it to sleep manually works as expected. |
|
The beta can be downloaded directly from Apple: Once the package is installed you will find |
|
Ventura is more iPadOS than macOS. At some point it'll all be the same AppleOS 😅 |
|
OpenCore 0.8.3 Ventura Beta 3 Not working boot testing ? please thank you |
|
OpenCore 0.8.3 is not released yet. Please test with the Ventura EFI attached to this issue. If beta 3 doesn't boot with that EFI let me know what errors you get. This time around I can't download and test every single beta release. Apple can change things too quickly so I only test the beat when I am bored. Once the final version is released I will release an EFI updated for it. Till then the current EFI is perfectly fine for Monterey and earlier and the EFI in this issue can be used for Ventura testing. |
|
When EFI boot a few seconds then it stops stuck see photo. thank you |
|
Try disabling the NVMe fixup kext. Other than that I see nothing that could indicate why it isn't booting. Are you doing this for fun or do you need it or something? If you want a stable machine stick to Ventura or earlier. If you want to run beta's be ready for things breaking and not being able to fix it or even figure out why. Your machine just hangs at boot seems. No fatal error displayed, no panic, just a silent crash. There's not much I do do with that. You'll have to do a lot of work to figure it out, starting with debug versions of OpenCore and the important kexts. I can't help with that. I don't have the spare time for it now. There are many bugs. Not all caused by the EFI or OpenCore or kexts, some are macOS bugs. Like automated sleep is currently not working properly. My beta 2 test machine won't fall asleep on its own within the time all my other NUCs fall asleep automatically. Putting it to sleep myself works fine. But what is the cause? There's nothing in the logs to indicate why it's not going to sleep on its own. Nothing is preventing automated sleep, yet is is not working. It might be a kext. It might be OpenCore. It might just be a Ventura bug. From previous beta's I've learned it is not worth the time to fix it until the final is released. Good luck! |
|
I tried "NVMeFix Monterey It works well great! |
|
Good Morning |
|
Ventura OpenCore 0.8.3-current test EFI. |
|
No problems here updating from beta 2 to beta 3 using the 0.8.3 EFI posted above. |
zearp
changed the title
|
Finally works Ventura Beta 3 Thank you very much |
|
@DANDEBAND You mentioned OpenCore 0.8.3 here: #84 (comment) Were you testing with OpenCore 0.8.3 there? If yes, where did you get it from because I had only posted 0.8.2 till then. Please only test with the EFI posted. If you test with an EFI where you updated kexts or OpenCore itself then its pointless to post about it here. For testing purposes it is very important to use the EFI posted. |
yes, I always download this link https://dortania.github.io/builds/ |
|
No wonder it didn't work for you and worked fine for me. If you go venture on your own please don't post in here. We can't do any meaningful testing when you use a different EFI. |
|
I might give this a try this weekend. It should be okay if I use the config.plist from my current working EFI and just overwrite the kext I need and the new opencore from you file posted above, right? |
|
Only if your config has no missing fields. I suggest to copy the serials to the new config file instead of overwriting. |
|
I'm still having issues with the machine not going to sleep on its own. Manually putting it to sleep works. Logs aren't very helpful at the moment. Could be a macOS bug. Updating to a new beta first fails to installer the smaller incremental update but updating goes ok once it has downloaded the full 12gb installer. Other than that everything seems to work as expected. |
|
If I am using a native Wifi/Bluetooth card do I need the FeatureUnclock.kext? |
|
Without FeatureUnlock.kext the follow things stop working, or stop working properly:
There might be more but this is what I observed just now on my test machine with an Apple Airport card (BCM94360CS2). I remember adding the kext a while ago to get AirPlay receiver to show up. |
|
No problems on the install. Also, all the features, continuity, etc. are working without the FeatureUnlock.kext with my native card. I don't use the timed sleep feature but tapping the NUC power button still puts it to sleep no problem. |
|
Both Universal Control and extend desktop to my iPad Air 3 worked. Can't test Airplay. |
|
Thanks! What card do you use? I have only BCM94360CS2's installed as I got a bunch of them for a nice price. If I disable FeatureUnlock and try to extend the desktop to my iPad it tries to but the screen just remains black. With FeatureUnlock enabled it works as expected. Does the Airplay Receiver option show for you without loading the kext? For me it disappears as soon as the kext is not loaded anymore. Maybe only older Airport cards need it? Very interesting!
|
|
I have a BCM94360CS2 also. Were is that menu... can't find it with this new system settings! |
|
|
|
I upgraded using software updater no problem. |
|
I was only able to use the small 1-2g upgrade from beta 1 to 2. After that it always errored out on my test machine. When I let it try again software updater would download the full 12gb installer which then installed fine. All of these things are out of our control to fix so it's not really a big deal as long as Apple fixes it before the final release. Maybe something got messed up on my test machine causing those failures, I don't know. Will do a clean install if I get really bored. following the beta's can be a big waste of time trying to fix things that might be caused by OS bugs Apple has yet to fix. |
I didn't notice the icon even on BigSur and Monterey actually.. When I have the time, I will try to look into past EFIs and see if there were any differences.. |
|
So I updated to Beta 5 and the powerd issue is gone. |
|
Haven’t tried it yet myself but I don’t have any usb issues waking from sleep. I use a usb keyboard connected directly and one via a usb-c hub. I always wake up the machines from the keyboard. I don’t know if you run stock or changed any hardware. Broadcom cards require editing of the usb map. Could it be a bios setting perhaps? Running an io registry dump before and after sleep may help getting some insights. |
|
If I wake the machine using the keyboard there is no problem. It only happens when the machine wakes itself from sleep. I do use a native wifi/bluetooth card so my usb map is edited. I'll check my bios and also see about running some io dumps. |
|
What do you mean with wakes itself up? I can't think of a way to to try and reproduce this as it shouldn't wake up on its own unless you scheduled it. If it wakes up on its own then thats a different issue. It would explain why some h/w isn't working properly because it probably didn't wake the usb controller properly. In order for me to help I need to be able to reproduce the issue. I have both an unmodified NUC and one with an Apple Airport card running Ventura beta's. |
|
Sorry, been out of town. So yeah, I put the machine to sleep by pressing the power button, the LED turns amber, then in the morning it is blue, but the monitor is off and I can hear my external HDD spinning but the keyboard and mouse don't work. I have the pmset options set as you recommend in your guide. I couldn't figure out how to do a io registry dump. I googled it but couldn't find a how to. |
|
Sounds like dark wake got stuck somehow. Please check the logs for those events. If possible check if you can login using Remote Desktop from another device when in that state. Replugging the mouse or keyboard can't fully wake it? |
|
Replugging the mouse and keyboard doesn't work. The mouse is plugged into my keyboard (it has a usb hub built in). Here is the log from last night;
I will try remote desktop the next time it half wakes up. |
|
Updated my stock test machine to the latest beta today and it's been sleeping about 3-4 hours now. I'll keep an eye on it and see when/if it wakes up on its own and if it gets stuck in DarkWake purgatory. |
|
Had some issues with Intel wireless, seem to be fixed now.
|
|
So I couldn't remote desktop in. I tested the remote desktop before I put it to sleep last night and this morning I tried remote desktop and got an error saying it couldn't be found. I had to hard restart as usual. The blue LED was on but no response from the keyboard/mouse and a black screen. I am using this cmd for the logs; |
|
The log shows it entering DarkWake and thats all. If there was a panic or crash you should get a popup on the next startup. Could check system logs with the Console app but I would wipe all the logs before sleep so you won't have to wade thought irrelevant old logs. Are you logged into iCloud? I think thats the only difference between yours and my test NUC. Which its completely stock and has an NVMe drive. I can try to login to iCloud and see if I I can reproduce your issue. It has been sleeping for many hours and still is. If it's not woken up tomorrow I would guess it has something todo with iCloud if you use that and pmset not disabling not everything. There could be new things relating power management that you somehow run into and I don't. It's very difficult for me to do anything if I can't reproduce the issue. We have the exact same hardware (if yours is stock too) and should have the exact same bios settings and the exact same EFI. In theory I should be able to reproduce this issue if you can find the steps to always run into it. But takes a lot of time for you and I wouldn't recommend diving too deep into these kind of things then the OS is still in beta. This is the main reason I'm hesitant about following beta's. Many things can end up being a waste of time as the problem wasn't caused by the EFI/config but needed to be fixed in OpenCore/etc. Reproducible steps would be something like: If you have multiple machines it is feasible as you can do other things but if you have one machine it is a chore. I think we're at dev beta 5 and public beta 1 now. A few more beta's before the final. I would guess 4-6 weeks from now and then a few more weeks for OpenCore and kexts to be updated to supportVentura properly. |
|
I am logged into iCloud and I use that feature for my calendar, email, etc. so I don't really want to log out. I use this machine daily. I keep backups of course since starting to test Ventura but trying clean installs and such wouldn't be worth it since, as you say, we are still in beta. As for my hardware. I have a m.2 sata drive and am using a BCM94360CS2 airport card for bluetooth and wifi. I think at this point we can safely say it is something on my setup and not an issue with opencore or the kexts since your install is not showing the same behavior. Thank you for taking the time and troubleshooting though. I think once the final build is out I will be performing a clean install anyway. If the problem persists after that then I might seek your input again. |
|
Next week Apple has an event where they probably going to announce the release of Ventura. This issue has served its purpose. |
|
OTA update to latest beta went fine this time. Before it would fail with the smaller OTA file and end up downloading the whole 12gb installer.
|
|
It seems paired bluetooth devices are forgotten after a reboot. This might be due to my Ventura beta install being upgraded so much but I also read others have BT issues with the latest beta build. I can pair devices and they work fine but after a reboot they are gone and have to be paired again. |
|
Probably related is the wireless is always off on boot. When a new beta build is released I will do a clean install to rule out the many upgrades are causing these. It may just be a case of the Intel wifi/bt kexts need to be fixed upstream for Ventura support. |
|
A clean install fixed bluetooth devices not being remembered but wifi is still disabled on each boot and it thinks my network is a hidden one. It does work once turned on. I'm pretty sure the itlwm kext needs some fixes for Ventura. |
|
New build installed using the small OTA update went ok.
|
|
It appears with the latest beta I can wake up the machine from sleep using Intel bluetooth. Last time I tried this it did not work. This will probably only apply to the onboard Intel bluetooth as the power to the bluetooth module on m.2 Airport cards is cut when it sleeps. |
|
Latest beta installed without issues. Wireless can still be spotty on cold boots but once it's connected its fine. I can still wake for sleep using a bluetooth device. Which is pretty cool and not possible when using an Airport card as it loses power during sleep. Next month the final should be released and the repo will migrate to defaulting to Ventura as install target. |
|
Beta nine! I'm pretty confident it will update just fine. |
|
macOS Ventura Release Candidate (RC) has arrived, this could be the final version unless some serious bugs are found. An 800mb update if you're on the latest beta. I can't seem to find a link to the full 12gb installer. When I do I'll post it here. |
|
RC2 here we go. |
|
Still no full installer. RC1 also didn't get one. |
|
RC2 has become the final version and can be downloaded here: After running the .pkg file the macOS installer will be in /Applications. |
Starting with OpenCore 0.8.2 macOS 13 aka Ventura support was added.
Please report your experiences here if you're up for trying Ventura.
Usage: Download the latest release EFI and replace AirportItlwm.kext with the Ventura compatible one.
The text was updated successfully, but these errors were encountered: