telepati Posted March 29, 2020 Share Posted March 29, 2020 9 minutes ago, nutro said: Thank you for the fast reply @telepati. I was hoping 0.5.7 would fix the issue. I guess I could try with 0.5.5. Any idea how to revert to 0.5.5 without to have to install from scratch? I am already using v0.5.7 and the problem still persists. You can download v0.5.5 from here. https://github.com/acidanthera/OpenCorePkg/releases Note: Do not use the same files and config.plist in V0.5.6. Use the files and sample.plist in v0.5.5. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714483 Share on other sites More sharing options...
Pene Posted March 29, 2020 Share Posted March 29, 2020 (edited) Hello, I have a question regarding BlessOverride functionality: I added to bless override the following: "\EFI\ubuntu\grubx64.efi" However, the same HDD also has Windows on it, thus also having "\EFI\Microsoft\Boot\BCD". The presence of the BCD results in mistakenly displaying the grubx64.efi entry as "BOOTCAMP WINDOWS". (is this a bug?) To confirm the above, I removed the BCD file, and then the grubx64.efi entry appeared just as "EFI". So, I am wondering, wouldn't it make sense to have a type-by-path-detection for BlessOverride similar to what Boot Entries have? P.S. The reason Custom Entry didn't work well for this in my case, is that the HDD with ubuntu isn't always connected, and it seems that Custom Entries are displayed regardless of the actual presence of the specified file (I wish the entry to be displayed only when the HDD is connected). Edited March 29, 2020 by Pene Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714533 Share on other sites More sharing options...
Andrey1970 Posted March 29, 2020 Share Posted March 29, 2020 1 hour ago, Pene said: Hello, I have a question regarding BlessOverride functionality: I added to bless override the following: "\EFI\ubuntu\grubx64.efi" However, the same HDD also has Windows on it, thus also having "\EFI\Microsoft\Boot\BCD". The presence of the BCD results in mistakenly displaying the grubx64.efi entry as "BOOTCAMP WINDOWS". (is this a bug?) To confirm the above, I removed the BCD file, and then the grubx64.efi entry appeared just as "EFI". So, I am wondering, wouldn't it make sense to have a type-by-path-detection for BlessOverride similar to what Boot Entries have? P.S. The reason Custom Entry didn't work well for this in my case, is that the HDD with ubuntu isn't always connected, and it seems that Custom Entries are displayed regardless of the actual presence of the specified file (I wish the entry to be displayed only when the HDD is connected). You can use file .contentDetails with entry name text. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714536 Share on other sites More sharing options...
markl18 Posted March 30, 2020 Share Posted March 30, 2020 Quote hi all of my previous problems I managed to get by by googling and stuff but this one I dont really understand is it part of acpi loading all of those aml files or is it that one of them is in conflict with one of the kext Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714539 Share on other sites More sharing options...
GOOGE Posted March 30, 2020 Share Posted March 30, 2020 I just switched from Clover to OpenCore 0.5.6, everything is working fine. I just wanted to ask what are the steps to get bootliquor.efi to work. Hopefully this is the right thread to ask... thanks Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714541 Share on other sites More sharing options...
mhaeuser Posted March 30, 2020 Share Posted March 30, 2020 12 hours ago, Pene said: However, the same HDD also has Windows on it, thus also having "\EFI\Microsoft\Boot\BCD". The presence of the BCD results in mistakenly displaying the grubx64.efi entry as "BOOTCAMP WINDOWS". (is this a bug?) No-ish... OC detects Windows as Windows the same way Apple EFI does, though I agree it is suboptimal. Apple EFI has no concept of multiple loaders per one partition outside of bless (e.g. HFS FV2 or APFS Preboot), and thus OC support for it is suboptimal. But I'd not say I like the solution either. You can use .contentDetails in the loader folder to rename though. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714574 Share on other sites More sharing options...
AudioGod Posted March 30, 2020 Share Posted March 30, 2020 (edited) @Download-Fritz Sorry to bother you or anybody else but I am using the latest build and I’m finding I’m no longer able to boot into windows via OC, I’m not using any patches or a dsdt and just to make sure it wasn’t somthing like that breaking windows I compiled the latest version of NDK OC and the same thing happens. I don’t know if it’s me or a bug in the latest build but If i use my older build of Oc from the 23rd of this month it works fine and I have made no changes between then and now other then updating to the latest build this morning. im super confused but hoping somebody can confirm or resolve the problem for me? here is the error getting thrown up 9900k, Gigabyte Z390 Master, 5700XT, Samsung 970 EVO 1tb, Win10 WD Black NVMe 1tb Catalina Thanks Guys, Edited March 30, 2020 by AudioGod Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714591 Share on other sites More sharing options...
Matgen84 Posted March 30, 2020 Share Posted March 30, 2020 (edited) 11 minutes ago, AudioGod said: @Download-Fritz Sorry to bother you or anybody else but I am using the latest build and I’m finding I’m no longer able to boot into windows via OC, I’m not using any patches or a dsdt and just to make sure it wasn’t somthing like that breaking windows I compiled the latest version of NDK OC and the same thing happens. I don’t know if it’s me or a bug in the latest build but If i use my older build of Oc it works fine and I have made no changes between then and now other then updating to the latest build this morning. im super confused but hoping somebody can confirm or resolve the problem for me? here the error getting thrown up Thanks Guys, Hi @AudioGod You've to rebuild Windows BCD You know that. Before a new test, with OC or NDK. Do you try to boot Windows! I think you can't. Edited March 30, 2020 by Matgen84 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714593 Share on other sites More sharing options...
AudioGod Posted March 30, 2020 Share Posted March 30, 2020 2 minutes ago, Matgen84 said: Hi @AudioGod You've to rebuild Windows BCD You know that. Before a new test, with OC or NDK. Do you try to boot Windows! I don't think you can't. Nope it isn’t the BCD, it’s happening with a fresh install via my test drive too and like I said if I use my EFI from a few days ago it works normally but the latest build causes that to happen. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714594 Share on other sites More sharing options...
markl18 Posted March 30, 2020 Share Posted March 30, 2020 (edited) hihi does anyone have any idea what this means Edited March 30, 2020 by markl18 solved partial prob this one i dont even understand what died Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714606 Share on other sites More sharing options...
LunairsmAlpha Posted March 30, 2020 Share Posted March 30, 2020 (edited) im doing clover to opencore conversion and i have problem with applealc on opencore as it doesnt work even with layout id that proven work under clover i use oc 0.5.6, applealc 1.4.7, macos mojave 10.14.5 my device is lenovo B40 | i3 5005U | Realtek ALC 235 i use layout id 3 --> mirone alc235 codec with resethda and afglowpowerstate enabled on clover this is my clover config https://1drv.ms/u/s!ApcQm0L9RYS5iro5qyhp4sbz6A6GAQ this is my oc config https://drive.google.com/file/d/127sfe3zahcnm-hBSJWXFYSHPf1zBCmhO/view?usp=drivesdk UPDATE:Somehow fixed when i block com.driver.appleHPET and still show on kextstat https://github.com/acidanthera/bugtracker/issues/422#issuecomment-523642854 if there're another elegant solutions please kindly reply Edited March 30, 2020 by LunairsmAlpha because i found some fix on it Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714608 Share on other sites More sharing options...
Matgen84 Posted March 30, 2020 Share Posted March 30, 2020 2 hours ago, AudioGod said: @Download-Fritz Sorry to bother you or anybody else but I am using the latest build and I’m finding I’m no longer able to boot into windows via OC, I’m not using any patches or a dsdt and just to make sure it wasn’t somthing like that breaking windows I compiled the latest version of NDK OC and the same thing happens. I don’t know if it’s me or a bug in the latest build but If i use my older build of Oc from the 23rd of this month it works fine and I have made no changes between then and now other then updating to the latest build this morning. im super confused but hoping somebody can confirm or resolve the problem for me? here is the error getting thrown up Same issue with my Z390 Aorus Master config. All works fine before latest commits. I double check OC EFI folder and config.plist, remove all devices: problem remain. Any ideas for a solution. Thanks. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714620 Share on other sites More sharing options...
hardcorehenry Posted March 30, 2020 Share Posted March 30, 2020 (edited) 1 hour ago, LunairsmAlpha said: im doing clover to opencore conversion and i have problem with applealc on opencore as it doesnt work even with layout id that proven work under clover i use oc 0.5.6, applealc 1.4.7, macos mojave 10.14.5 my device is lenovo B40 | i3 5005U | Realtek ALC 235 i use layout id 3 --> mirone alc235 codec with resethda and afglowpowerstate enabled on clover this is my clover config https://1drv.ms/u/s!ApcQm0L9RYS5iro5qyhp4sbz6A6GAQ this is my oc config https://drive.google.com/file/d/127sfe3zahcnm-hBSJWXFYSHPf1zBCmhO/view?usp=drivesdk UPDATE:Somehow fixed when i block com.driver.appleHPET and still show on kextstat https://github.com/acidanthera/bugtracker/issues/422#issuecomment-523642854 if there're another elegant solutions please kindly reply You need couple HPET related renames, run this stuff. Put kexts in correct order in your config. In DevicesProperties add layout-id. Edited March 30, 2020 by hardcorehenry Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714623 Share on other sites More sharing options...
texem Posted March 30, 2020 Share Posted March 30, 2020 (edited) 2 hours ago, Matgen84 said: Same issue with my Z390 Aorus Master config. All works fine before latest commits. I double check OC EFI folder and config.plist, remove all devices: problem remain. Any ideas for a solution. Thanks. me too, using latest OC from GIT : booting Win via OC results in same blue screen as shown above confirming that issue since commits on Mar 29, 2020 . Edited March 30, 2020 by texem Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714642 Share on other sites More sharing options...
markl18 Posted March 30, 2020 Share Posted March 30, 2020 2 hours ago, hardcorehenry said: You need couple HPET related renames, run this stuff. Put kexts in correct order in your config. In DevicesProperties add layout-id. how do you get the ssdttime to recognize the dsdt.aml file it just doesnt want to be recognized Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714658 Share on other sites More sharing options...
Cass67 Posted March 30, 2020 Share Posted March 30, 2020 1 hour ago, texem said: me too, using latest OC from GIT : booting Win via OC results in same blue screen as shown above confirming that issue since commits on Mar 29, 2020 . Suspect its related to the change in openruntime .. putting the old openruntime.efi back with nothing else changed from compiling the latest code fixes Windows booting.. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714664 Share on other sites More sharing options...
hardcorehenry Posted March 30, 2020 Share Posted March 30, 2020 (edited) 1 hour ago, markl18 said: how do you get the ssdttime to recognize the dsdt.aml file it just doesnt want to be recognized What do you mean? Double click SSDTTime.command, rest is clear. Edited March 30, 2020 by hardcorehenry Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714669 Share on other sites More sharing options...
Tank8484 Posted March 30, 2020 Share Posted March 30, 2020 where can I find out why OC is better than the good old clover? Does it has mouse? where can I find out why OC is better than the good old clover? Does it has mouse? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714670 Share on other sites More sharing options...
markl18 Posted March 30, 2020 Share Posted March 30, 2020 35 minutes ago, hardcorehenry said: What do you mean? Double click SSDTTime.command, rest is clear. because when it says please drop dsdt.aml here i drop it and it doesnt recognize it Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714676 Share on other sites More sharing options...
hardcorehenry Posted March 30, 2020 Share Posted March 30, 2020 21 minutes ago, markl18 said: because when it says please drop dsdt.aml here i drop it and it doesnt recognize it Post your untouched DSDT.aml Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714678 Share on other sites More sharing options...
darthsian Posted March 30, 2020 Share Posted March 30, 2020 7 hours ago, AudioGod said: @Download-Fritz Sorry to bother you or anybody else but I am using the latest build and I’m finding I’m no longer able to boot into windows via OC, I’m not using any patches or a dsdt and just to make sure it wasn’t somthing like that breaking windows I compiled the latest version of NDK OC and the same thing happens. I don’t know if it’s me or a bug in the latest build but If i use my older build of Oc from the 23rd of this month it works fine and I have made no changes between then and now other then updating to the latest build this morning. im super confused but hoping somebody can confirm or resolve the problem for me? here is the error getting thrown up 9900k, Gigabyte Z390 Master, 5700XT, Samsung 970 EVO 1tb, Win10 WD Black NVMe 1tb Catalina Thanks Guys, Same problem here. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714679 Share on other sites More sharing options...
markl18 Posted March 31, 2020 Share Posted March 31, 2020 2 hours ago, hardcorehenry said: What do you mean? Double click SSDTTime.command, rest is clear. do you think you could help me figure what exactly wrong with this DSDT.aml Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714684 Share on other sites More sharing options...
nobinbd Posted March 31, 2020 Share Posted March 31, 2020 My PC configuration is motherboard : Gigabyte Z390 Gaming SLI Processor: Intel i7 8700K GPU: Built in Graphics Intel UHD 630 Ram: 16GB 3300MHz SSD: Samsung NVMe 970 EVO Plus 256GB I want to install Mac os catalina in my pc. But when booting from installation media it's stuck at some point and I don't know what it means. I attached some photos of this problem... opencore-2020-03-31-114310.txt Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714704 Share on other sites More sharing options...
Matgen84 Posted March 31, 2020 Share Posted March 31, 2020 37 minutes ago, nobinbd said: My PC configuration is motherboard : Gigabyte Z390 Gaming SLI Processor: Intel i7 8700K GPU: Built in Graphics Intel UHD 630 Ram: 16GB 3300MHz SSD: Samsung NVMe 970 EVO Plus 256GB I want to install Mac os catalina in my pc. But when booting from installation media it's stuck at some point and I don't know what it means. I attached some photos of this problem... opencore-2020-03-31-114310.txt Post your EFI folder. Maybe users can help you. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714709 Share on other sites More sharing options...
texem Posted March 31, 2020 Share Posted March 31, 2020 (edited) 12 hours ago, Cass67 said: Suspect its related to the change in openruntime .. putting the old openruntime.efi back with nothing else changed from compiling the latest code fixes Windows booting.. @vit9696 seems the problem is here , i'm not _that_ expert but if i remove the build options in OpenCorePkg.dsc (this should fix Linux boot as far I understand, Bug #491 ?) Windows boot is fine. Only OpenRuntime.efi is newly generated btw. Quote [BuildOptions.common.EDKII.DXE_RUNTIME_DRIVER] GCC:*_*_*_DLINK_FLAGS = -z common-page-size=0x1000 XCODE:*_*_*_DLINK_FLAGS = -seg1addr 0x1000 -segalign 0x1000 XCODE:*_*_*_MTOC_FLAGS = -align 0x1000 CLANGPDB:*_*_*_DLINK_FLAGS = /ALIGN:4096 Edited March 31, 2020 by texem 3 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/149/#findComment-2714713 Share on other sites More sharing options...
Recommended Posts