MacNB Posted July 19, 2020 Share Posted July 19, 2020 16 minutes ago, Riley Freeman said: Thanks. That got me a little further along. I'm getting "OC: Prelink inject prepare error - Unsupported" instead, followed by a "couldn't allocate runtime area" stop shortly after loading the extensions.mkext from the SL volume. I tried dropping in OsxAptioFixDrv.efi from Clover and that got the system to boot a little further but it reboots almost straight away after TSC Deadline Timer. Remove OpenRuntime.efi for Legacy Boot. What's the hardware ? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731024 Share on other sites More sharing options...
Riley Freeman Posted July 19, 2020 Share Posted July 19, 2020 (edited) 8 minutes ago, MacNB said: Remove OpenRuntime.efi for Legacy Boot. What's the hardware ? I'll try that now. It's the X79 in my sig. Update: Removing OpenRuntime made no difference here. Same behaviour as before, with and without OsxAptioFixDrv. Edited July 19, 2020 by Riley Freeman Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731025 Share on other sites More sharing options...
MacNB Posted July 19, 2020 Share Posted July 19, 2020 13 minutes ago, Riley Freeman said: I'll try that now. It's the X79 in my sig. I have all the post-install required SL kexts already in /S/L/E and the kext cache built manually (Ethernet, HDA, etc..). So there's nothing OC need to do to inject kexts. In the config.plist, the kernel sections Add has MinKernel set to 14.05.00 so that OC does not inject anything. I am booting SL, YS, EC, SR, HS & Win 10 off the same config.plist (Hack 2 in my sig). Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731028 Share on other sites More sharing options...
Riley Freeman Posted July 19, 2020 Share Posted July 19, 2020 Ah I see. I'm trying to inject the kexts via OC, as I did with Clover before. Maybe that's the problem. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731029 Share on other sites More sharing options...
Sherlocks Posted July 19, 2020 Share Posted July 19, 2020 I have all the post-install required SL kexts already in /S/L/E and the kext cache built manually (Ethernet, HDA, etc..). So there's nothing OC need to do to inject kexts. In the config.plist, the kernel sections Add has MinKernel set to 14.05.00 so that OC does not inject anything. I am booting SL, YS, EC, SR, HS & Win 10 off the same config.plist (Hack 2 in my sig).hi can you upload your EFI?I want to boot SL on Sandy HP Probook나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731050 Share on other sites More sharing options...
MacNB Posted July 20, 2020 Share Posted July 20, 2020 1 hour ago, Sherlocks said: hi can you upload your EFI? I want to boot SL on Sandy HP Probook 나의 SM-N960N 의 Tapatalk에서 보냄 Here's my EFI for Dell Inspiron 530 Desktop (still going strong): MacNB-Dell-530-EFI.zip Note this is an OLD Legacy boot system. It does NOT have UEFI It does NOT have NVRAM There are a couple of issues booting OC Legacy on this system. The Devs have found one of the issues with Duet booting for system with SATA controller with Raid and is now fixed in the Master. There is another issue with Boot drive selection via Sys Pref Startup Disk for selecting Default boot drive (work-in-progress). Legacy boot without working NVRAM will have an issue with macOS Updates - it cannot automatically choose "macOS Installer" so you have to enable Boot Picker BEFORE starting an Update. This is so that you can manually select the macOS Installer entry in the Boot Picker (I had to do that with Clover on this system). But for Snow Leopard that will not be a problem as there will be no more Updates but if you are multi booting then beware of the issue. Regarding Snow Leopard, I had not touched it for a long long time. When I installed it a long time ago, it was the "old fashion" way: with the required Kexts installed in /S/L/E using KextUtil. That means patched AppleHDA, Ethernet kexts, etc. So even with Clover, nothing was injected. Same goes for OC. I may try injecting them as a test. The kexts in the EFI are for YS, EC, SR & HS. I had to add OsxFatBinaryDrv.efi in order to load SL. As I mentioned above, OC will eventually embed this driver. I am using iMac14,2 model ID but the system has an Intel Xeon 5450 CPU. In the config.plist I had PlatformInfo->Automatic=TRUE but gave an Unknown CPU in System Profiler because OC does not set the ProcessorType to the actual CPU but to CPU that a real iMac14,2 supports (I think). The only way to fix that was to set PlatformInfo->Automatic=FALSE and manually populate the SMBIOS section - just to add ProcessorType=0x0501. For your Sandy Bridge CPU you may have the same issue BTW, I had to redo the DSDT.aml completely in order for OC to boot Windows 10. With the original DSDT I did many years ago, Windows boot would blue-screen with ACPI_BIOS_ERROR. I had to add generous amounts of _OSI checks in many ACPI devices till it booted Windows. I will write a separate Topic on the subject. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731057 Share on other sites More sharing options...
Sherlocks Posted July 20, 2020 Share Posted July 20, 2020 Here's my EFI for Dell Inspiron 530 Desktop (still going strong):MacNB-Dell-530-EFI.zip Note this is an OLD Legacy boot system. It does NOT have UEFI It does NOT have NVRAM There are a couple of issues booting OC Legacy on this system. The Devs have found one of the issues with Duet booting for system with SATA controller with Raid and is now fixed in the Master. There is another issue with Boot drive selection via Sys Pref Startup Disk for selecting Default boot drive (work-in-progress). Legacy boot without working NVRAM will have an issue with macOS Updates - it cannot automatically choose "macOS Installer" so you have to enable Boot Picker BEFORE starting an Update. This is so that you can manually select the macOS Installer entry in the Boot Picker (I had to do that with Clover on this system). But for Snow Leopard that will not be a problem as there will be no more Updates but if you are multi booting then beware of the issue. Regarding Snow Leopard, I had not touched it for a long long time. When I installed it a long time ago, it was the "old fashion" way: with the required Kexts installed in /S/L/E using KextUtil. That means patched AppleHDA, Ethernet kexts, etc. So even with Clover, nothing was injected. Same goes for OC. I may try injecting them as a test. The kexts in the EFI are for YS, EC, SR & HS. I had to add OsxFatBinaryDrv.efi in order to load SL. As I mentioned above, OC will eventually embed this driver. I am using iMac14,2 model ID but the system has an Intel Xeon 5450 CPU. In the config.plist I had PlatformInfo->Automatic=TRUE but gave an Unknown CPU in System Profiler because OC does not set the ProcessorType to the actual CPU but to CPU that a real iMac14,2 supports (I think). The only way to fix that was to set PlatformInfo->Automatic=FALSE and manually populate the SMBIOS section - just to add ProcessorType=0x0501. For your Sandy Bridge CPU you may have the same issue BTW, I had to redo the DSDT.aml completely in order for OC to boot Windows 10. With the original DSDT I did many years ago, Windows boot would blue-screen with ACPI_BIOS_ERROR. I had to add generous amounts of _OSI checks in many ACPI devices till it booted Windows. I will write a separate Topic on the subject.thanks a lot.i will try나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731093 Share on other sites More sharing options...
paulog4 Posted July 21, 2020 Share Posted July 21, 2020 (edited) I need some help cleaning what was left by OpenCore after I tested it and went back to Clover. After the installation with Clover, everything works ok but it boots with boot-args=-v keepsyms=1 debug=0x100 alcid=1.Besides booting with verbose, these args are somehow breaking my sound. It worked before I tested the OC install.I tried everything I found on the issue to get rid of these parameters but I cannot. I tried Clover configurator (NVRAM parameter), sudo nvram -c and boot-args="" commands, bcdf boot rm at Clover terminal, bios reset, used VirtualSMC.kext instead of FakeSMC.kext, F11 at Clover boot screen.I even got another hd with a previous installation to test, but every time Clover boots it picks up these same options left over from Opencore in my NVRAM. Any help getting rid of these parameters or resetting the NVRAM will be appreciated. OC development team, please add instructions to completely clean OC settings. Thank you. Here is what is in my NVRAM somewhere and I cannot change. See below for example of nvram delete that did not work. [Restored Jul 20, 2020 at 21:06:05] Last login: Mon Jul 20 21:06:03 on console Restored session: Mon Jul 20 21:04:35 CDT 2020 Yoda:~ su$ nvram boot-args boot-args -v keepsyms=1 debug=0x100 alcid=1 Yoda:~ su$ nvram -p fakesmc-key-MSWr-ui8 %00 fakesmc-key-NATi-ui16 %00%00 fakesmc-key-RPlt-ch8* j78%00%00%00%00%00 fakesmc-key-RBr -ch8* j78j78a%00 EFILoginHiDPI %00%00%00%00 fakesmc-key-#KEY-ui32 %00%00%00%00 fakesmc-key-BATP-flag %00 prev-lang:kbd en-US:0 fakesmc-key-MSTc-ui8 %00 EmuVariableUefiPresent Yes fakesmc-key-BNum-ui8 %00 security-mode none csr-active-config g%00%00%00 fakesmc-key-$Num-ui8 %01 fakesmc-key-MSFW-ui8 %01%00 fakesmc-key-REV -ch8* %02"%0f%00%00%16 fakesmc-key-MSPS-ui16 %00%03 fakesmc-key-NATJ-ui8 %00 fakesmc-key-CLKH-{clh %00%00p%80%00%01%19@ fmm-computer-name Yoda fakesmc-key-$Adr-ui32 %00%00%03%00 fakesmc-key-NTOK-ui8 %01 fakesmc-key-EPCI-ui32 %08%00%f0%00 fakesmc-key-CLKT-ui32 %00%01(%89 fakesmc-key-MSAc-ui16 %00%00 boot-args -v keepsyms=1 debug=0x100 alcid=1 SystemAudioVolume F fakesmc-key-RMde-char A specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%04%ec%1b%00%00%00%00%bd%e5Q%82\:%03L%94}%a3%ed%de%fe%bdk%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB/%f2%f0,9%c1%b1H%b5R%80%95K%d5)%f2%7f%ff%04%00 flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 fakesmc-key-MSDW-ui8 %01 fakesmc-key-BEMB-flag %00 Yoda:~ su$ Yoda:~ su$ sudo -s Password: bash-3.2# nvram boot-args boot-args -v keepsyms=1 debug=0x100 alcid=1 bash-3.2# nvram -d boot-args bash-3.2# nvram boot-args nvram: Error getting variable - 'boot-args': (iokit/common) data was not found bash-3.2# bash-3.2# [Restored Jul 20, 2020 at 21:16:57] Last login: Mon Jul 20 21:16:55 on console Restored session: Mon Jul 20 21:15:39 CDT 2020 Yoda:~ su$ nvram -p | grep -i boot-args boot-args -v keepsyms=1 debug=0x100 alcid=1 Yoda:~ su$ Edited July 21, 2020 by paulog4 duplicated text Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731178 Share on other sites More sharing options...
mhaeuser Posted July 21, 2020 Share Posted July 21, 2020 5 hours ago, paulog4 said: OC development team, please add instructions to completely clean OC settings. OC writes to NVRAM exactly what you configure it to, so read and understand your own config... your issue looks more like you either have borked NVRAM write or disabled it (DisableVariableWrite in OcQuirks or new Clobber) 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731196 Share on other sites More sharing options...
ameenjuz Posted July 21, 2020 Share Posted July 21, 2020 (edited) On 7/16/2020 at 2:53 AM, fusion71au said: Hi @MorenoAv, Just a few tid bits on dual booting macOS and Windows with OC... 1. Since 0.5.9, OC can automatically detect UEFI Windows loader bootmgfw.efi --> no need for Custom Entry 2. From OC documentation (Configuration.pdf) re OEM Windows activation... "Windows may need to be reactivated. To avoid it consider setting SystemUUID to the original firmware UUID. Be warned, on old firmwares it may be invalid, i.e. not random. In case you still have issues, consider using HWID or KMS38 license or making the use Custom UpdateSMBIOSMode." Personally, I set Kernel/Quirks/CustomSMBIOSGuid to YES and PlatformInfo/UpdateSMBIOSMode to Custom in my OC config.plist ---> avoids Windows OEM activation problem (Windows keeps its original firmware UUID and macOS keeps its own SystemUUID). PS I moved my reply here since I think it would be off topic in the Big Sur beta thread OC cannot automatically detect UEFI Windows loader bootmgfw.efi using BlessOverride> \EFI\Microsoft\Boot\bootmgfw.efi when i restart my laptop then i don't see boot picker menu it is go to windows i don't know this issue is bootstrap or lenovo laptop how to fix this Spoiler my second question how to configure Custom SMBois to avoid SystemUUID to the original firmware UUID Edited July 21, 2020 by ameenjuz edited Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731242 Share on other sites More sharing options...
zhangzixian321 Posted July 21, 2020 Share Posted July 21, 2020 Thanks to the Acidanthera team, Opencore runs pretty well on my X58 platform. The 0.6.0 beta version fixes the 0.59 shutdown and restart freeze issues. This ensures that the Gulftown architecture's CPU is variable frequency and running at full speed..... ACPI->Quirks: FadtEnableReset=True ResetHwSig=True Kernel->Quirks: AppleCpuPmCfgLock=True AppleXcpmCfgLock=True AppleXcpmExtraMsrs=True UEFI->Quirks: IgnoreInvalidFlexRatio=True Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731252 Share on other sites More sharing options...
MagicNAS Posted July 21, 2020 Share Posted July 21, 2020 How can i remove the text that comes out before open core menu, I use 0.5.9 release version of OC. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731273 Share on other sites More sharing options...
tluck Posted July 22, 2020 Share Posted July 22, 2020 On 7/19/2020 at 1:18 AM, Matgen84 said: Just my stupid opinion: do you try to boot OC ---> Windows, without DSDT my stupid question - how do you do that ------------------------------------^ ? i can only boot windows currently via Clover - which of course just brings up bootmgfw natively. I presume the reason windows10 is crashing after about 1 spin of the dots is a macOS compatible DSDT via OC. On 7/18/2020 at 5:25 AM, Sherlocks said: i want to remove two EFI and bootmgfw entries. i tried to change Scan Policy bit. it is no luck. anyone who give me tip? uncheck FS_ESP Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731304 Share on other sites More sharing options...
arsradu Posted July 22, 2020 Share Posted July 22, 2020 20 hours ago, MagicNAS said: How can i remove the text that comes out before open core menu, I use 0.5.9 release version of OC. My guess is that there's probably something wrong with the data you're trying to add for TableSignature. My suggestion would be to compare your config.plist to the sample.plist provided by OC and see what's different. For example, here's what the TableSignature (in ACPI -> Delete) looks like. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731349 Share on other sites More sharing options...
tluck Posted July 22, 2020 Share Posted July 22, 2020 also it may be easier to debug when you "view as ASCII" to make sure your names match what you have. $ echo NTM1MzQ0NTQ=|base64 -D 53534454 hex to ascii 53 53 44 54 => S S D T 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731357 Share on other sites More sharing options...
markl18 Posted July 22, 2020 Share Posted July 22, 2020 hi I have installed Big Sur without any hangups right from usb but now while booting it is being busy imfi denying core dump from pid please help Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731358 Share on other sites More sharing options...
MacNB Posted July 22, 2020 Share Posted July 22, 2020 14 minutes ago, tluck said: also it may be easier to debug when you "view as ASCII" to make sure your names match what you have. $ echo NTM1MzQ0NTQ=|base64 -D 53534454 hex to ascii 53 53 44 54 => S S D T If you use PlistEdit Pro, then you edit & view the data ASCII, Hex, etc. Makes it real easy for patching ASCII where you literally entry the ASCII values e.g. EHC1 to EH01 See example below: Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731360 Share on other sites More sharing options...
MagicNAS Posted July 22, 2020 Share Posted July 22, 2020 3 hours ago, arsradu said: My guess is that there's probably something wrong with the data you're trying to add for TableSignature. My suggestion would be to compare your config.plist to the sample.plist provided by OC and see what's different. For example, here's what the TableSignature (in ACPI -> Delete) looks like. Тhat was my problem, thank you. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731366 Share on other sites More sharing options...
Andres ZeroCross Posted July 23, 2020 Share Posted July 23, 2020 @Download-Fritz, after update to Big Sur Beta 3 i got new entry with name "Preboot" in GUI OC (OpenCanopy), Actually i have Windows, Catalina and macOS Big Sur in my PC. Now i see entry of "Windows, macOS Catalina, macOS Big Sur" and new entry "Preboot" after update to latest Big Sur Beta and use latest commit OpenCore. is this normal?? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731601 Share on other sites More sharing options...
ghost8282 Posted July 23, 2020 Share Posted July 23, 2020 (edited) 57 minutes ago, Andres ZeroCross said: after update to Big Sur Beta 3 i got new entry with name "Preboot" Same here, and I noticed entries were different from beta 1 and 2 during the different reboots, so not sure if it's opencore or apple. However the system is running booting from Preboot in opencore: I'm not seeing any mac os big sur entry, only preboot and recovery with scanpolicy zero. Edited July 23, 2020 by ghost8282 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731603 Share on other sites More sharing options...
Sbrillo Posted July 24, 2020 Share Posted July 24, 2020 12 hours ago, ghost8282 said: Same here, and I noticed entries were different from beta 1 and 2 during the different reboots, so not sure if it's opencore or apple. However the system is running booting from Preboot in opencore: I'm not seeing any mac os big sur entry, only preboot and recovery with scanpolicy zero. me too. After update successfully from system preferences the Big Sur entry on the bootloader change name. Also, I want to know if there are methods to activate temperature sensors and PM in this OS. I have a 4th gen i5, but I had to set smbios as an iMac Pro 1,1 for AppleTV app. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731660 Share on other sites More sharing options...
dayo Posted July 24, 2020 Share Posted July 24, 2020 On 7/3/2020 at 5:19 PM, dayo said: @vit9696 @Download-Fritz Can you kindly help with pointer to where this output during the build process comes from? Any one able to help me with this please? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731796 Share on other sites More sharing options...
iCanaro Posted July 24, 2020 Share Posted July 24, 2020 On 7/21/2020 at 8:42 PM, MagicNAS said: How can i remove the text that comes out before open core menu, I use 0.5.9 release version of OC. are errors that you have in the config you have to correct them uses ocvalidate and OCConfigCompare to remedy Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731800 Share on other sites More sharing options...
ameenjuz Posted July 25, 2020 Share Posted July 25, 2020 anyone have Sandy Bridge working config for high sierra Model: AH512 IntelÆ CoreTM i3 processor 2.2 GHz 2GB DDR3 SDRAM hard drive 320GB Graphics Coprocessor Intel HD Graphics 3000 Screen Resolution 1366 x 768 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731958 Share on other sites More sharing options...
tluck Posted July 26, 2020 Share Posted July 26, 2020 4 hours ago, ameenjuz said: anyone have Sandy Bridge working config for high sierra Model: AH512 IntelÆ CoreTM i3 processor 2.2 GHz 2GB DDR3 SDRAM hard drive 320GB Graphics Coprocessor Intel HD Graphics 3000 Screen Resolution 1366 x 768 yes - see https://github.com/tluck/Lenovo-T420-Clover (clover and OC) Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/225/#findComment-2731993 Share on other sites More sharing options...
Recommended Posts