Anto65 Posted Tuesday at 05:44 PM Share Posted Tuesday at 05:44 PM (edited) Spoiler Edited Tuesday at 07:13 PM by Anto65 7 1 Link to comment Share on other sites More sharing options...
eSaF Posted Tuesday at 06:09 PM Share Posted Tuesday at 06:09 PM (edited) For real Macs I wager??!! EDIT: I stand corrected, I just saw the Update. Edited Tuesday at 06:11 PM by eSaF 7 Link to comment Share on other sites More sharing options...
Anto65 Posted Tuesday at 06:16 PM Author Share Posted Tuesday at 06:16 PM I also thought it was intended for real Macs... instead it downloaded and installed correctly ... everything works 7 Link to comment Share on other sites More sharing options...
Max.1974 Posted Tuesday at 06:17 PM Share Posted Tuesday at 06:17 PM (edited) Spoiler Spoiler Edited Tuesday at 06:21 PM by Max.1974 9 2 Link to comment Share on other sites More sharing options...
eSaF Posted Tuesday at 06:49 PM Share Posted Tuesday at 06:49 PM Done!!! 11 Link to comment Share on other sites More sharing options...
strangeron Posted Tuesday at 06:54 PM Share Posted Tuesday at 06:54 PM 10 Link to comment Share on other sites More sharing options...
D-an-W Posted Tuesday at 06:56 PM Share Posted Tuesday at 06:56 PM 5 minutes ago, eSaF said: Done!!! At least now I have an update to test why updates don't show up! My OC 1.0.1 EFI folder shows the update fine but the OC 1.0.2 EFI folder refuses to, has to be a kext...right?!? 3 Link to comment Share on other sites More sharing options...
Max.1974 Posted Tuesday at 07:11 PM Share Posted Tuesday at 07:11 PM Done again! 10 Link to comment Share on other sites More sharing options...
kaoskinkae Posted Tuesday at 07:13 PM Share Posted Tuesday at 07:13 PM macOS 15.1 BETA 4 + ocpl 2.0.1 perfect en NEW: 7 Link to comment Share on other sites More sharing options...
D-an-W Posted Tuesday at 07:20 PM Share Posted Tuesday at 07:20 PM (edited) @deeveedee other than the two additional kexts and kext version numbers there are no differences. I have tried with each of the new kexts disabled so will now try replacing each of the kexts with the older versions in turn. EDIT: It is the RestrictEvents.kext v1.15 I updated to, if I replace it with v1.14 the update shows up. Anyone understand what might be going on? Edited Tuesday at 07:38 PM by D-an-W 2 Link to comment Share on other sites More sharing options...
deeveedee Posted Tuesday at 08:05 PM Share Posted Tuesday at 08:05 PM (edited) @D-an-W where did you get v1.1.5? According to this repo, the only change was the version number. BTW - If you can't figure it out, I wouldn't recommend debugging. Usually not worth the effort to debug Acidanthera kexts that haven't yet been released. Edited Tuesday at 08:07 PM by deeveedee 3 Link to comment Share on other sites More sharing options...
ANTIKO Posted Tuesday at 08:14 PM Share Posted Tuesday at 08:14 PM Everything is fine 5 Link to comment Share on other sites More sharing options...
D-an-W Posted Tuesday at 08:17 PM Share Posted Tuesday at 08:17 PM 10 minutes ago, deeveedee said: @D-an-W where did you get v1.1.5? According to this repo, the only change was the version number. BTW - If you can't figure it out, I wouldn't recommend debugging. Usually not worth the effort to debug Acidanthera kexts that haven't yet been released. Yes, that's where I got it from and I noticed that was the only change too. 1 Link to comment Share on other sites More sharing options...
D-an-W Posted Tuesday at 08:52 PM Share Posted Tuesday at 08:52 PM (edited) @deeveedee the file that works for me is one by @lorys89 posted a while ago here. Could it be because I don't use any boot arguments other than "agdpmod=pikera"? EDIT: Probably the "revpatch=sbvmm" boot-arg Edited Tuesday at 09:10 PM by D-an-W 2 Link to comment Share on other sites More sharing options...
Max.1974 Posted Tuesday at 09:16 PM Share Posted Tuesday at 09:16 PM (edited) 2 hours ago, D-an-W said: @deeveedee other than the two additional kexts and kext version numbers there are no differences. I have tried with each of the new kexts disabled so will now try replacing each of the kexts with the older versions in turn. EDIT: It is the RestrictEvents.kext v1.15 I updated to, if I replace it with v1.14 the update shows up. Anyone understand what might be going on? Hi @D-an-W i compile my entire other folder kexts yesterday, before appears new update, and all kexts releases shows up beta update. Are you have this patches configs on your config.plist Nvram ? Check if ScanPolice is 0, and if SecureBootModel is Default or Disabled (I recommend Disabled). Im use clover, but in Opencore is the same boot-args. Update your Lilu and WG, VirtualSMC . . . My easy Clover is configured like that: Spoiler Edited Tuesday at 09:21 PM by Max.1974 4 1 Link to comment Share on other sites More sharing options...
D-an-W Posted Tuesday at 09:29 PM Share Posted Tuesday at 09:29 PM Thank you @Max.1974 and @deeveedee, I had forgotten I used to use "revpatch=sbvmm" for updates to show as no longer needed it with the modified RestrictEvents.kext What I didn't know is I could also add "pci" to the boot-arg to prevent the memory config error showing up. 2 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted Tuesday at 10:10 PM Share Posted Tuesday at 10:10 PM (edited) @D-an-W enjoy it !! Don't forget put this args "Delete" menu Edited Tuesday at 10:19 PM by Max.1974 4 Link to comment Share on other sites More sharing options...
Wayang-NT Posted Tuesday at 11:14 PM Share Posted Tuesday at 11:14 PM Beta 4 ... 😂 3 1 Link to comment Share on other sites More sharing options...
D-an-W Posted yesterday at 05:47 AM Share Posted yesterday at 05:47 AM 7 hours ago, Max.1974 said: @D-an-W enjoy it !! Don't forget put this args "Delete" menu I will check if I have them thanks, what do they do for me? 2 Link to comment Share on other sites More sharing options...
Max.1974 Posted yesterday at 07:06 AM Share Posted yesterday at 07:06 AM This args avoid KP on boot and break your update. 1 Link to comment Share on other sites More sharing options...
bluenote56 Posted yesterday at 11:22 AM Share Posted yesterday at 11:22 AM (edited) Hi I could successfully update to the official Sequoia 15.0 and now the 15.1 beta update shows up but no download. I don't know if it's related to OCLP. Amazing. Edit: after about 2 hours while working it started. It's a strange world. Edit: I give up for now. It's stuck. Edited yesterday at 11:52 AM by bluenote56 2 2 Link to comment Share on other sites More sharing options...
hiphopboy Posted yesterday at 11:50 AM Share Posted yesterday at 11:50 AM Done 15.1 beta 4, from 15.0 to 15.1 beta 4 :___:😆 6 Link to comment Share on other sites More sharing options...
Matgen84 Posted yesterday at 12:13 PM Share Posted yesterday at 12:13 PM (edited) Hi @bluenote56 If I understand well Apple's channel: we must use macOS Developer Beta instead of macOS Developer 15.1 Beta. Maybe the 15.1 Beta is for Apple Silicon. This macOS 15.1 Beta 4 is only for Intel Mac, I suppose. Edited yesterday at 12:14 PM by Matgen84 2 1 Link to comment Share on other sites More sharing options...
deeveedee Posted yesterday at 12:21 PM Share Posted yesterday at 12:21 PM (edited) I have selected "macOS Sequoia 15.1 Developer Beta" and the 15.1 update is available to me on my HackMini8,1. Booting with OC 1.0.1. Not using OCLP. EDIT: ... and finished. Upgrade from 15.0 RC to 15.1 Beta 4 proceeded without issues. Spoiler EDIT2: Sequoia 15.1 Beta 4 appears to have resolved the Ethernet connectivity issue that I observed with Microsoft Remote Desktop in Sequoia 15.0 Beta 1 & 2 and then again in Sequoia 15.0 RC. Edited yesterday at 12:50 PM by deeveedee 5 Link to comment Share on other sites More sharing options...
MaLd0n Posted yesterday at 01:02 PM Share Posted yesterday at 01:02 PM 5 Link to comment Share on other sites More sharing options...
Recommended Posts