Pavo Posted August 31, 2020 Share Posted August 31, 2020 (edited) @vit9696 or @Download-Fritz Can we get a little more clarity on using MMIOWhitelist? From my understanding you boot with OpenCore debug version and dump of the debug log, then go through the log and create the MMIOWhitelist based on what OpenCore shows in the log. How do we know which ones to enabled or disable? This is my current ones: 24:977 00:030 OCABC: MMIO devirt start 25:003 00:026 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 1 25:034 00:030 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 25:064 00:030 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 25:094 00:030 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 1 25:125 00:031 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 1 25:156 00:030 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 25:186 00:030 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 25:216 00:030 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 25:248 00:031 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 25:279 00:031 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 25:309 00:030 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 25:339 00:030 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 25:370 00:030 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 25:400 00:030 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 25:431 00:030 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 25:461 00:030 OCABC: MMIO devirt 0x2040000000 (0x10400 pages, 0x8000000000000001) skip 0 25:491 00:030 OCABC: MMIO devirt 0x7EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 25:522 00:030 OCABC: MMIO devirt 0x7F10000000 (0x10400 pages, 0x8000000000000001) skip 0 25:552 00:030 OCABC: MMIO devirt 0xDDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 25:582 00:030 OCABC: MMIO devirt end, saved 1064960 KB 25:611 00:028 OCABC: Only 128/256 slide values are usable! 25:638 00:027 OCABC: Valid slides - 128-255 Edited August 31, 2020 by Pavo Link to comment Share on other sites More sharing options...
Stefanalmare Posted August 31, 2020 Share Posted August 31, 2020 (edited) Maybe somebody can help me: Edited August 31, 2020 by Stefanalmare Link to comment Share on other sites More sharing options...
Matgen84 Posted August 31, 2020 Share Posted August 31, 2020 27 minutes ago, Stefanalmare said: Maybe somebody can help me: You're sur that HP Desktop Core2Duo config is compatible with Big Sur ! 1 Link to comment Share on other sites More sharing options...
Stefanalmare Posted August 31, 2020 Share Posted August 31, 2020 9 minutes ago, Matgen84 said: You're sur that HP Desktop Core2Duo config is compatible with Big Sur ! I have Quad Processor Q9300 and I suppose it works: https://dortania.github.io/OpenCore-Install-Guide/config.plist/legacy/penryn.html Link to comment Share on other sites More sharing options...
Matgen84 Posted August 31, 2020 Share Posted August 31, 2020 (edited) 24 minutes ago, Stefanalmare said: I have Quad Processor Q9300 and I suppose it works: https://dortania.github.io/OpenCore-Install-Guide/config.plist/legacy/penryn.html Opencore is a bootloader who can boot several macOS version. Apple specifies that macOS Big Sur runs on these Macs: MacBook (2015 and later) MacBook Air (2013 and later) MacBook Pro (Late 2013 and later) iMac Pro (2017 and later) iMac (2014 and later) --> at least Haswell Mac mini (2014 and later) Mac Pro (2013 and later) --> at least Core Xeon W Your HP corresponds to an Imac 2008-2009. Have a look to macrumors site for Unsupported Mac by Big Sur instructions. Old system patchedSorry for my bad English. Edited August 31, 2020 by Matgen84 1 Link to comment Share on other sites More sharing options...
MacNB Posted August 31, 2020 Share Posted August 31, 2020 44 minutes ago, Stefanalmare said: I have Quad Processor Q9300 and I suppose it works: https://dortania.github.io/OpenCore-Install-Guide/config.plist/legacy/penryn.html Mojave, Catalina AND Big Sur are NOT supported on Q9300 officially by Apple. You have to make sure that you have made the correct "workarounds". Eg. Install the Telemetrytrap kext or Mousse kext if you are using AMD graphics. 1 Link to comment Share on other sites More sharing options...
CVFZ Posted August 31, 2020 Share Posted August 31, 2020 (edited) Will OpenCore once Work from Firmware (Like oz)? @Download-Fritz@vit9696 Edited August 31, 2020 by CVFZ Link to comment Share on other sites More sharing options...
Stefanalmare Posted August 31, 2020 Share Posted August 31, 2020 34 minutes ago, MacNB said: Mojave, Catalina AND Big Sur are NOT supported on Q9300 officially by Apple. You have to make sure that you have made the correct "workarounds". Eg. Install the Telemetrytrap kext or Mousse kext if you are using AMD graphics. I use Telemetrytrap kext. I have Nvidia 710. I patched DSDT, use it and I pass KP. Now I'm stuck on Apple sign before first reboot.......... How many time should I wait? Link to comment Share on other sites More sharing options...
FredWst Posted August 31, 2020 Share Posted August 31, 2020 17 minutes ago, Stefanalmare said: I use Telemetrytrap kext. I have Nvidia 710. I patched DSDT, use it and I pass KP. Now I'm stuck on Apple sign before first reboot.......... How many time should I wait? @Stefanalmare Telemetrytrap kext is there release somewhere ? Google did'nt help to find it. Fred Link to comment Share on other sites More sharing options...
MacNB Posted August 31, 2020 Share Posted August 31, 2020 13 minutes ago, FredWst said: @Stefanalmare Telemetrytrap kext is there release somewhere ? Google did'nt help to find it. Fred It was developed by @Syncretic at macroumors.com. See here. Link to comment Share on other sites More sharing options...
Stefanalmare Posted August 31, 2020 Share Posted August 31, 2020 (edited) 1 hour ago, FredWst said: @Stefanalmare Telemetrytrap kext is there release somewhere ? Google did'nt help to find it. Fred Here you have: telemetrap.kext.zip Edited August 31, 2020 by Stefanalmare Link to comment Share on other sites More sharing options...
jmacie Posted August 31, 2020 Share Posted August 31, 2020 any other chipsets besides x99 that are not working with opencore for BigSur? Link to comment Share on other sites More sharing options...
vit9696 Posted September 1, 2020 Share Posted September 1, 2020 12 hours ago, Pavo said: @vit9696 or @Download-Fritz Can we get a little more clarity on using MMIOWhitelist? From my understanding you boot with OpenCore debug version and dump of the debug log, then go through the log and create the MMIOWhitelist based on what OpenCore shows in the log. How do we know which ones to enabled or disable? This is my current ones: 24:977 00:030 OCABC: MMIO devirt start 25:003 00:026 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 1 25:034 00:030 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 25:064 00:030 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 25:094 00:030 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 1 25:125 00:031 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 1 25:156 00:030 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 25:186 00:030 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 25:216 00:030 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 25:248 00:031 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 25:279 00:031 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 25:309 00:030 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 25:339 00:030 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 25:370 00:030 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 25:400 00:030 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 25:431 00:030 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 25:461 00:030 OCABC: MMIO devirt 0x2040000000 (0x10400 pages, 0x8000000000000001) skip 0 25:491 00:030 OCABC: MMIO devirt 0x7EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 25:522 00:030 OCABC: MMIO devirt 0x7F10000000 (0x10400 pages, 0x8000000000000001) skip 0 25:552 00:030 OCABC: MMIO devirt 0xDDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 25:582 00:030 OCABC: MMIO devirt end, saved 1064960 KB 25:611 00:028 OCABC: Only 128/256 slide values are usable! 25:638 00:027 OCABC: Valid slides - 128-255 There is no real answer. You normally do not need to add any entry to whitelist. But on some older models you need 1-2. You can diagnose this by early kernel panics. @CVFZ, OpenCore is designed in a way it is possible, but currently there are no plans. Link to comment Share on other sites More sharing options...
Guest Posted September 1, 2020 Share Posted September 1, 2020 (edited) Vit , using devirtualizemmio quirk on some new system ( which do not have support from you as you said in the past) allows these systems to boot fine now this produces the lack of some working functionality as the lack of Nvram and some weird sip state whitelisting helps to introduce again some of this functionality stuff and avoid kp or hangs Edited September 1, 2020 by Guest Link to comment Share on other sites More sharing options...
Pavo Posted September 1, 2020 Share Posted September 1, 2020 7 hours ago, vit9696 said: There is no real answer. You normally do not need to add any entry to whitelist. But on some older models you need 1-2. You can diagnose this by early kernel panics. @CVFZ, OpenCore is designed in a way it is possible, but currently there are no plans. Roger that, so.... is the ones that say skip 1 are the ones that are exposed to macOS or is it the skip 0 ones? Link to comment Share on other sites More sharing options...
oli.mathieu Posted September 1, 2020 Share Posted September 1, 2020 On 8/29/2020 at 3:05 AM, maleorderbride said: I have a different CPU now, but dropping the stock APIC and injecting the fixed APIC should be all you need that is specific to the i9-9820X. Depending on BIOS version you might need to deal with AWAC and the CFG-Lock, but that holds true for Clover and OC alike. thanks Link to comment Share on other sites More sharing options...
teewhydope Posted September 1, 2020 Share Posted September 1, 2020 (edited) removing all voodoo kexts except voodoops2controller solves the kernel panic for me, when booting big sur beta 2 Edited September 1, 2020 by teewhydope Link to comment Share on other sites More sharing options...
driftwood Posted September 2, 2020 Share Posted September 2, 2020 On 9/1/2020 at 5:41 AM, vit9696 said: There is no real answer. You normally do not need to add any entry to whitelist. But on some older models you need 1-2. You can diagnose this by early kernel panics. That's not a good answer! Surely MMiO whitelist is working at trapping the reserved paged memory space for devices under the bonnet and then flagging off what can/cant be seen by nvram? The MMIO hex memory addresses given in opencore debug txt together with their to reserved pages, how do I find out what devices these equate to? More specifically, what is OC doing here? If you don't know or can't say just say so? Thanks Link to comment Share on other sites More sharing options...
WeBeRiO Posted September 2, 2020 Share Posted September 2, 2020 Hi all, when I boot Win10 form OC no have audio in Win nor option suspend. If I boot from bios partition Win10 work both perfectly, please help me? Thks.- 1 Link to comment Share on other sites More sharing options...
紫米 Posted September 4, 2020 Share Posted September 4, 2020 On 8/26/2020 at 5:20 PM, Ron Lemmens said: I had issues with BS beta 5 initially, and none with beta 1..4 with an older build of OC 0.6.1 and associated kexts. I got beta 5 working (no KP) with the nightly builds of August 24th. Hello, @Ron Lemmens & @Gigamaxx. The boot error was fixed by updating Big Sur Beta 6. So, thanks for reply. 1 Link to comment Share on other sites More sharing options...
ghost8282 Posted September 4, 2020 Share Posted September 4, 2020 (edited) On 8/23/2020 at 11:12 AM, ghost8282 said: Hi all! I have a weird issue with Big Sur. The issue started with beta 1 and it was related to accessing the system preference panel --> Network: the panel opens soon but it took a long time (several minutes) to load the list of my two virtual networks (ethernet) on the left of the panel and nothing strange showed up in the mac os logs. The network panel issue was there from beta 1 to beta 4. In beta 5 the network panel and the list of networks loads faster, it's ok, but booting mac os takes a lot of time (like 4 to 5 minutes) with the following messages, that I think are related to this issue: IOKit Daemon (kernelmanagerd) stall[0], (60s): 'ISA' IOKit Daemon (kernelmanagerd) stall[1], (60s): 'ISA' IOKit Daemon (kernelmanagerd) stall[2], (60s): 'ISA' IOKit Daemon (kernelmanagerd) stall[3], (60s): 'ISA' The same messages were displayed during installation and recovery but with stall time of 240s each. I was using the latest versions of opencore and kexts (lilu, whatevergreen, applealc, virtualsmc), checked/updated every day. I never had these problems with other versions of mac os. I'm not really sure that this is related to the bootloader or to mac os, anyone with the same issue? Here's a log from open core:opencore-2020-08-23-093509.txt mmm..same issue with beta 6. Noone having the same issue or anybody knows what 'isa' refers to? Apparently not related at all to networks, since if I remove all network cards the issue is still there.. Spoiler @Pavo I know you are using vm too, did you have the same issue? Edited September 4, 2020 by ghost8282 Link to comment Share on other sites More sharing options...
Pavo Posted September 4, 2020 Share Posted September 4, 2020 8 hours ago, ghost8282 said: mmm..same issue with beta 6. Noone having the same issue or anybody knows what 'isa' refers to? Apparently not related at all to networks, since if I remove all network cards the issue is still there.. Hide contents @Pavo I know you are using vm too, did you have the same issue? ISA refers to your qemu arg you added to the VM settings, I switched to bare metal install on my TRX40 now. Everything is working perfect. 1 Link to comment Share on other sites More sharing options...
ghost8282 Posted September 4, 2020 Share Posted September 4, 2020 (edited) 2 hours ago, Pavo said: ISA refers to your qemu arg you added to the VM settings thank you for replying, unfortunately I'm using virtualsmc not a qemu arg for the osk Edited September 4, 2020 by ghost8282 Link to comment Share on other sites More sharing options...
ghost8282 Posted September 5, 2020 Share Posted September 5, 2020 (edited) On 9/4/2020 at 10:39 AM, ghost8282 said: IOKit Daemon (kernelmanagerd) stall[0], (60s): 'ISA' IOKit Daemon (kernelmanagerd) stall[1], (60s): 'ISA' IOKit Daemon (kernelmanagerd) stall[2], (60s): 'ISA' Finally I found the culprit. Big Sur >= beta 5 doesn't like my AppleLPCInjector kext. By disabling it no more stall messages and boot and shutdown a lot faster. So, nothing to do with opencore, but maybe useful for others searching google for the same issue. Update: My injector kext was injecting pci8086,2918; to load again AppleLPC without stall messages now I'm injecting without any kext but simply in opencore pci8086,2916. Edited September 5, 2020 by ghost8282 1 Link to comment Share on other sites More sharing options...
jmacie Posted September 6, 2020 Share Posted September 6, 2020 Beta 6 still unable to install/boot x99. Any ideas out there? If x299 needed awac or rtc0 for BigSur patch, couldn't x99 be something similar? Link to comment Share on other sites More sharing options...
Recommended Posts