mrpawlos345 Posted December 9, 2022 Share Posted December 9, 2022 Hello, i found on github EFI folder, that allowed me to install Monterey, everything works except the left speaker and bluetooth. Memory panic pops up when I try to update to Ventura. Now even dmg image from macrecovery can't load. Could someone review my EFI? https://www5.zippyshare.com/v/q0yY1W40/file.html Quote Link to comment Share on other sites More sharing options...
aben Posted December 9, 2022 Share Posted December 9, 2022 (edited) As per IntelBluetoothFirmware documentation, IntelBluetoothInjector.kext should not be injected when booting macOS Monterey and above. More importantly, macOS will also require the Bluetooth USB port (where the BT module attaches) to be correctly mapped to an internal header (type 255). Detailed info here. Also, I believe your machine is Skylake, which lost official support in Ventura however you can update by: using a supported SMBIOS (MacBookPro14,1) and spoofing iGPU to KabyLake by injecting KBL equivalent fb values via device-id and AAPL,ig-platform-id under iGPU's DeviceProperties in config.plist. More info here Edited December 9, 2022 by aben Update info from OpenIntelWireless Quote Link to comment Share on other sites More sharing options...
mrpawlos345 Posted December 9, 2022 Author Share Posted December 9, 2022 Thanks for reply, i corrected the EFI thanks to your tip, but i am having trouble loading the dmg file from the pendrive. On other EFI it reads without a problem. What could it be? Quote Link to comment Share on other sites More sharing options...
aben Posted December 9, 2022 Share Posted December 9, 2022 From a quick glance, I believe the EFI has not been updated to support Ventura. You will require OpenCore ver. 0.8.3 and above to be able to boot Ventura. Also ensure to include the necessary driver to load HFS formatted drives (you may utilize OpenHfsPlus.efi driver that comes bundled with OpenCore). Get the latest Release version of OpenCore here. Quote Link to comment Share on other sites More sharing options...
mrpawlos345 Posted December 9, 2022 Author Share Posted December 9, 2022 I have OpenCore ver. 0.8.7 Quote Link to comment Share on other sites More sharing options...
aben Posted December 9, 2022 Share Posted December 9, 2022 Try this EFI for the installation process: EFI.zip Quote Link to comment Share on other sites More sharing options...
mrpawlos345 Posted December 9, 2022 Author Share Posted December 9, 2022 Thanks for your help, but when loading restore dmg there is the same error. When booting from disk it stops at "SmcReadValue". I am attaching logs from opencore. running dmg.txt running installes.txt Quote Link to comment Share on other sites More sharing options...
aben Posted December 10, 2022 Share Posted December 10, 2022 (edited) Do you have Monterey currently installed on your machine, to which you are able to boot into? If so, try updating to Ventura via System Settings after applying the necessary changes to the EFI mentioned on my first post above (that is, SMBIOS + iGPU spoof to KBL). You will also need to add boot-arg: -igfxsklaskbl to the same adjusted EFI to allow boot to Monterey with the iGPU spoof. Once Ventura installs successfully you may safely remove the boot-arg (although no harm with its presence) Good luck! Edited December 10, 2022 by aben Quote Link to comment Share on other sites More sharing options...
mrpawlos345 Posted December 10, 2022 Author Share Posted December 10, 2022 I get LAPIC panic all the time. I used SMBios and iGPU from KabyLake Quote Link to comment Share on other sites More sharing options...
aben Posted December 10, 2022 Share Posted December 10, 2022 Hi, thanks for confirming this info on IM. Yes - I’m seeing similar reports elsewhere that current LAPIC-kernel-patch does not work when attempting to boot Ventura on HP mobos (due to kernel changes from Apple’s end). Suggested workaround, at the moment, is to utilize boot-arg: cpus=1 Quote Link to comment Share on other sites More sharing options...
Slice Posted December 10, 2022 Share Posted December 10, 2022 1 hour ago, aben said: Hi, thanks for confirming this info on IM. Yes - I’m seeing similar reports elsewhere that current LAPIC-kernel-patch does not work when attempting to boot Ventura on HP mobos (due to kernel changes from Apple’s end). Suggested workaround, at the moment, is to utilize boot-arg: cpus=1 This is common misconception that LAPIC-kernel-patch doesn't work on new kernels. No! It works as before. I checked with kernel Ventura 13.0.1 and the pattern is fine and replace to correct codes. Look for other errors. Quote Link to comment Share on other sites More sharing options...
aben Posted December 11, 2022 Share Posted December 11, 2022 @Slice Thanks for confirming on the kernel status for LAPIC however I should have mentioned that some HP laptops (with latest BIOS) have been reported (by same OP of this thread and other HP users on Discord) to seeing confirmed LAPIC_interrupt panics on current Ventura release but no issues with Monterey, Big Sur using same boot-loader version. I believe something on the firmware-side (maybe newer BIOS update/OEM restriction?) is causing panics for these affected mobos. More investigation is required for these machines. Quote Link to comment Share on other sites More sharing options...
Slice Posted December 11, 2022 Share Posted December 11, 2022 6 hours ago, aben said: @Slice Thanks for confirming on the kernel status for LAPIC however I should have mentioned that some HP laptops (with latest BIOS) have been reported (by same OP of this thread and other HP users on Discord) to seeing confirmed LAPIC_interrupt panics on current Ventura release but no issues with Monterey, Big Sur using same boot-loader version. I believe something on the firmware-side (maybe newer BIOS update/OEM restriction?) is causing panics for these affected mobos. More investigation is required for these machines. May be but LAPIC patch applied to Ventura kernel no matter of hardware. This is the patch to kernel and it is absolutely fine. Quote Link to comment Share on other sites More sharing options...
mrpawlos345 Posted February 7, 2023 Author Share Posted February 7, 2023 If you want to run Ventura without LAPIC on HP skylake, you must delete debug=100 from boot-args in config.plist Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.