deeveedee Posted July 27, 2022 Share Posted July 27, 2022 (edited) Ventura Beta 4 update to my HackMini 8,1 proceeded without issues using the same EFI that I used for Ventura Beta 3 (OC 0.8.3 Beta, Lilu 1.6.2 Beta). Update was smooth with what I believe were four reboots. This update include an XCode Beta update. About This Mac: Ventura Beta 4 Spoiler I did notice that after applying the update, Apple did provide a reminder about its Beta data collection policy. I don't remember seeing this for previous Beta releases, but that's probably just failing memory with old age. Following acknowledgement of the data collection policy, I disabled "Share Mac Analytics" in my System Preferences. Beta Analytics & Privacy Policy Spoiler Thank you again, Developers, for your awesome work on Open Core! @antuneddu and @miliuco - I have trained my cat to check for updates. Spoiler Edited July 27, 2022 by deeveedee 3 3 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789934 Share on other sites More sharing options...
Common_Sense Posted July 27, 2022 Share Posted July 27, 2022 (edited) 11 minutes ago, Slice said: 745Mb? What is your SMBIOS model? Hi Slice, I cannot see the update with MacPro7,1 smbios because there seems to be an issue with Clover and HWTarget not being set properly. I have the latest version of Clover with HWTarget tag set correctly in config.plist. When I check with sysctl I cannot see it being set properly. Can I do something with the config.plist to fix the issue, or is it a bug in Clover? EDIT: There seems to be another update with XCode command line tools that is 745mb if I am not remembering wrong, these updates usually appears at the same time as a new Developer Beta of macOS. It is probably these updates that is visible in the above case, and not the macOS update. Edited July 27, 2022 by Common_Sense 1 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789935 Share on other sites More sharing options...
Slice Posted July 27, 2022 Share Posted July 27, 2022 8 minutes ago, Common_Sense said: Hi Slice, I cannot see the update with MacPro7,1 smbios because there seems to be an issue with Clover and HWTarget not being set properly. I have the latest version of Clover with HWTarget tag set correctly in config.plist. When I check with sysctl I cannot see it being set properly. Can I do something with the config.plist to fix the issue, or is it a bug in Clover? EDIT: There seems to be another update with XCode command line tools that is 745mb if I am not remembering wrong, these updates usually appears at the same time as a new Developer Beta of macOS. It is probably these updates that is visible in the above case, and not the macOS update. Yes, there is a bug. To get the update you may set iMac18,1 model which is not required HWTarget. 2 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789938 Share on other sites More sharing options...
D3v1L Posted July 27, 2022 Share Posted July 27, 2022 (edited) 54 minutes ago, Slice said: 745Mb? What is your SMBIOS model? MacPro7,1 smbiios... Same with real MacPro 745mb Edited July 27, 2022 by D3v1L Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789941 Share on other sites More sharing options...
Guest ricoc90 Posted July 27, 2022 Share Posted July 27, 2022 Installing DP4 went, albeit incredibly slow, without a hitch Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789942 Share on other sites More sharing options...
Slice Posted July 27, 2022 Share Posted July 27, 2022 Done 5 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789945 Share on other sites More sharing options...
MorenoAv Posted July 27, 2022 Share Posted July 27, 2022 Done... 6 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789950 Share on other sites More sharing options...
PoMpIs Posted July 27, 2022 Share Posted July 27, 2022 (edited) I'm late today... downloading 😄 EDIT: Everything went well Edited July 27, 2022 by PoMpIs 6 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789954 Share on other sites More sharing options...
bisdak4920 Posted July 27, 2022 Share Posted July 27, 2022 Updated smooth as a silk in 15 minutes to login screen. 4 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789955 Share on other sites More sharing options...
Ellybz Posted July 27, 2022 Share Posted July 27, 2022 X299 Ventura Beta 4 . All good. Spoiler 4 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789963 Share on other sites More sharing options...
PoMpIs Posted July 28, 2022 Share Posted July 28, 2022 4 hours ago, Hervé said: A no brainer update on my Skylake/HD520 Latitude E7270 laptop. No change to the Clover r5148 setup, same as for beta #3. Totally kosher for me. 1.5xGB size for me, not 745MB! In my case it marked 1.52Gb but it is because it also marked xcode update... when I downloaded that, it went to 754.5Mb of system update 2 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789964 Share on other sites More sharing options...
PC IT Posted July 28, 2022 Share Posted July 28, 2022 Thank you for al your support in helping me finding a solution to this ancient lcd big panel, it is working properly with full qc, the trick which did it is @aben suggestion to add these lines, framebuffer-patch-enable DATA 01000000 framebuffer-con0-enable DATA 01000000 framebuffer-con0-alldata DATA 00000800 02000000 90000000 Thanks to Herv'e who found the internal display on (con0), As Aben mentioned that the sequence basically drops LVDS connector flag CNConnectorAlwaysConnected, which forces built-in displays as external. Known to have fixed certain problematic eDP connectors in the past When added these lines, the display worked, i changed the display flag from 90000000 to 98000000 and it worked perfectly in both Monterey and Ventura. Thanks to @deeveedee for raising my issue properly I am still having problems: 1: Airplay not working at all, i have apple tv and using AirportItlwm kext, airplay is working perfectly on Monterey 2:Display never wake after sleep esp if closing the lid, it keep dimmed-black. 3:Mac os installer and recovery work just in vesa mode. 4:Can we make a small ssdt containing these display flags to for kbl spoofing that it may help other who are having troubles to solve the problem? I want to thank you for all your support to me that solved my problem which last for about 2 months without successful booting, i was on Montery and using Ventura on vesa mode. i will post my working efi for this model so it may help others solve their problems without changing the display to a new fhd one. i need a small ssdt for this display including the flags if that is possible, I updated the system to beta 4 and it is working with only the above mentioned problems, wishing we will be able to find any solutions asap Attached is my EFI forlder to help others in this issue. Thank you so much SKYLAKE EFI.zip 5 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789965 Share on other sites More sharing options...
SavageAUS Posted July 28, 2022 Share Posted July 28, 2022 Update not showing for me on my laptop here in Australia. Sent from my iPhone using Tapatalk 2 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789967 Share on other sites More sharing options...
aben Posted July 28, 2022 Share Posted July 28, 2022 4 hours ago, PC IT said: Thank you for al your support in helping me finding a solution to this ancient lcd big panel, it is working properly with full qc, the trick which did it is @aben suggestion to add these lines, framebuffer-patch-enable DATA 01000000 framebuffer-con0-enable DATA 01000000 framebuffer-con0-alldata DATA 00000800 02000000 90000000 As Aben mentioned that the sequence basically drops LVDS connector flag CNConnectorAlwaysConnected, which forces built-in displays as external. Known to have fixed certain problematic eDP connectors in the past When added these lines, the display worked, i changed the display flag from 90000000 to 98000000 and it worked perfectly in both Monterey and Ventura. Awesome! Good to know the above suggestion to patch LVDS connector flags helped solve your display issue finally. Congrats and enjoy Please note that this approach is a mere workaround to this incompatibility situation with your panel when using KBL framebuffers, and as such should not be considered a native solution for a built-in display, until a proper/more meaningful patch that addresses this issue has been implemented. It's still best recommended to upgrade panel to FHD, if possible, to achieve full proper/native functionality of LVDS panels when using macOS framebuffers untouched, otherwise you'll be forced to compromise on native LVDS features such as backlight control, lid wake/Sleep etc. Also, display specifications are not defined at UEFI/ACPI level, only EDID which is accessed from EEPROM and thus not possible to deploy SSDTs for such patches, only via kernel space. 2 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789976 Share on other sites More sharing options...
Cyberdevs Posted July 28, 2022 Share Posted July 28, 2022 Alder Lake went fine (sort of) the system is a bit unstable due to a BIOS update I might need to fine tune my EFI or do a clean install and see how it performs afterwards. 6 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789979 Share on other sites More sharing options...
Slice Posted July 28, 2022 Share Posted July 28, 2022 3 hours ago, SavageAUS said: Update not showing for me on my laptop here in Australia. Sent from my iPhone using Tapatalk Clover? SIP? Other information? 1 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789980 Share on other sites More sharing options...
aben Posted July 28, 2022 Share Posted July 28, 2022 (edited) Update to Beta 4 completed successfully on Skylake machine here. Oh and BTW, x86PlatformPlugin continues to load natively, by default, without having to inject plugin-type=1 flag to ACPI (SSDT-PLUG), for those interested. Also, Metal 3 support is still present on Kaby Lake iGPUs as of Beta 4. . Edited July 28, 2022 by aben 5 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789982 Share on other sites More sharing options...
greythorne Posted July 28, 2022 Share Posted July 28, 2022 5 minutes ago, aben said: Update to Beta 4 completed successfully on Skylake machine here. Oh and BTW, x86PlatformPlugin continues to load natively, by default, without having to inject plugin-type=1 flag to ACPI (SSDT-PLUG), for those interested. Also, Metal 3 support is still present on Kaby Lake iGPUs as of Beta 4. . meaning that is it ok to remove the SSDT-Plug.aml? Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789986 Share on other sites More sharing options...
Guest ricoc90 Posted July 28, 2022 Share Posted July 28, 2022 4 hours ago, SavageAUS said: Update not showing for me on my laptop here in Australia. Sent from my iPhone using Tapatalk Re-enroll into the beta program Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789988 Share on other sites More sharing options...
Cyberdevs Posted July 28, 2022 Share Posted July 28, 2022 Just now, ricoc90 said: Re-enroll into the beta program Yeah thanks for that, I had the sam issue on my Z270 rig and re-enrolling fixed my issue. 3 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789989 Share on other sites More sharing options...
Anto65 Posted July 28, 2022 Share Posted July 28, 2022 Yesterday after trying several previous commits of OC 0.8.3, Clover, OC-Debug, with and without Fakesmc, OC- Mod ... nothing the error persisted Spoiler I came up with posts about Beta3 ... I think @ricoc90 ( thx ) Well disabled BlueToolFixup.kext ... boom ! taken and updated quietly I do not know if this is the solution valid for everyone, I also notice several problems, but still to be taken into consideration Spoiler 2 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789991 Share on other sites More sharing options...
Guest ricoc90 Posted July 28, 2022 Share Posted July 28, 2022 @antuneddu Yep, BluetoolFixup alters /usr/sbin/BlueTool which makes that macOS wants to do a full replacement rather than doing an incremental patch. Booting without BlueToolFixup indeed works around that, or you can download the full installer instead. Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789992 Share on other sites More sharing options...
Anto65 Posted July 28, 2022 Share Posted July 28, 2022 Strange anyway because up to DP3 it hadn't given me any problems Thanks anyway ... solved by disabling it 1 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789993 Share on other sites More sharing options...
surenmunoo Posted July 28, 2022 Share Posted July 28, 2022 Update to Beta 4 went thru flawlessly. No need to touch OC config, it just worked Yay 3 Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789996 Share on other sites More sharing options...
Slice Posted July 28, 2022 Share Posted July 28, 2022 48 minutes ago, antuneddu said: Strange anyway because up to DP3 it hadn't given me any problems Thanks anyway ... solved by disabling it I had problems with BlueToolFixup before Ventura. Link to comment https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/page/80/#findComment-2789997 Share on other sites More sharing options...
Recommended Posts