Bernard Guillot

After about a week of struggling, I now get SUCCESS... No more crashes and no more Black screen! But the cost is high since I also bought a new Mac M1pro!

Maldon is no more providing any accurate help! ;-((

00:000 00:000 BMF: GetTextInfo failed 00:001 00:001 OCUI: welcome label failed 18:589 18:587 AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82 18:590 00:001 AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82 18:591 00:001 AAPL: #[EB|H:IS] 0 18:592 00:001 AAPL: #[EB|LOG:INIT] 2022-03-03T13:52:32 18:593 00:001 AAPL: #[EB|VERSION] <"boot.efi 540.80.2~11 (Official), built 2021-12-17T18:41:20-0800"> 18:594 00:001 AAPL: #[EB|BUILD] <"BUILD-INFO[298]:{"DisplayName":"boot.efi","DisplayVersion":"540.80.2~11","RecordUuid":"4C1050E5-0AC2-49AF-A6E3-E8F54238A54E","BuildTime":"2021-12-17T18:41:20-0800","ProjectName":"efiboot","ProductName":"boot.efi","SourceVersion":"540.80.2","BuildVersion":"11","BuildConfiguration":"Release","BuildType":"Official"}"> 18:595 00:001 AAPL: #[EB.CFG.DEV|!] Err(0xE) <- RT.GV booter-strict-xmlparser 7C436110-AB2A-4BBB-A880-FE41995C9F82 OBVIOUSLY some fine tuning must be performed in the config.plist...

I still have the black screen after about only one hour: need to reboot... ;-(

Thanx! I already have latest BIOS A09 installed!

opencore-2022-03-03-135213.txt.zip

Hi Maldon, I mistakenly reported that it still crashes.... But it's WRONG: Because I have no crashlog ... The only issue is a black screen after 1 hour when the laptop goes to sleep! it's only a video setting issue I guess so PLEASE check what may be updated in config.plist to prevent the dark screen. I set the Battery preference to NEVER make the screen going to SLEEP while using a screen saver instead...

OK... In the meantime I made some mods in the config.plist regarding exactly what is recommended on Opencore for Skylake laptop...

Sorry but you may have an idea why I get black screen when it crashes instead of rebooting...? Please tell me how to have Bootcamp Windows as the 2nd choice....

Unfortunately, now after a crash I get a black screen and I have to force a shutdown before being able to restart... In the Boot menu the first choice is Bootcamp Windows? That's why it cannot automatically reboot to Monterrey... I set the Hibernate mode to happen after one hour... I guess the crash occurs after... But no more crashlog available? So this EFI must be updated...

THANK YOU so much! I just used you "untouched" new EFI and before booting resented NVRAM... I could boot with no hitch... crossed fingers to check if no more kernel panic...

OK... ;-( So the only solution is to backpedal to Big Sur?

Hi, the updated patch doesn't fix the panic issue yet? panic(cpu 3 caller 0xffffff8003abb71f): mbuf_watchdog: 1 waiters stuck for 14 secs 23652/23678 mbufs in use: 23652 mbufs allocated to data 26 mbufs allocated to caches 71/682 mbuf 2KB clusters in use 11276/11279 mbuf 4KB clusters in use 0/8 mbuf 16KB clusters in use 52761 KB allocated to network (approx. 96% in use) 0 KB returned to the system VM allocation failures: contiguous 0, normal 0, one page 0 worker thread runs: 35, expansions: 270, cl 0/0, bigcl 34/9049, 16k 0/0 worker thread last run time: 55742 (15 seconds ago) mbuf leak detection table: total captured: 4530 (one per 500) total allocs outstanding: 82 new hash recorded: 4521 allocs, 3093 traces hash collisions: 52 allocs, 10 traces overwrites: 3957 allocs, 0 traces lock conflicts: 0 top 5 outstanding traces: [1] 25 outstanding alloc(s), 25 hit(s), 0 collision(s) [2] 14 outstanding alloc(s), 30 hit(s), 3 collision(s) [3] 13 outstanding alloc(s), 22 hit(s), 3 collision(s) [4] 13 outstanding alloc(s), 192 hit(s), 1 collision(s) [5] 8 outstanding alloc(s), 16 hit(s), 0 collision(s) trace [1] trace [2] trace [3] trace [4] trace [5] ------------------ ------------------ ------------------ ------------------ ------------------ 1: 0xffffff80008b9eca 0xffffff80008b9eca 0xffffff80008b9eca 0xffffff80008b9eca 0xffffff80008b9eca 2: 0xffffff8000893802 0xffffff8000893802 0xffffff8000893802 0xffffff8000893760 0xffffff8000893760 3: 0xffffff80008b8d99 0xffffff80008be138 0xffffff80008c0742 0xffffff80008be138 0xffffff80008b8d46 4: 0xffffff80008936cf 0xffffff80008c23e1 0xffffff800088da31 0xffffff80008c23e1 0xffffff80008936cf 5: 0xffffff80008c0742 0xffffff800088cdf3 0xffffff8002b5706d 0xffffff800088cdf3 0xffffff80008c0742 6: 0xffffff800088da31 0x0 0x0 0x0 0xffffff800088da31 7: 0xffffff8002b5706d 0x0 0x0 0x0 0xffffff8002b5706d 8: 0x0 0x0 0x0 0x0 0x0 9: 0x0 0x0 0x0 0x0 0x0 10: 0x0 0x0 0xffffff8000a58c53 0x0 0x0 11: 0x0 0x0 0xffffff8000a574ae 0x0 0x0 12: 0xffffff8000a58c53 0x0 0xffffff8000a56ad7 0x0 0xffffff8000a58c53 13: 0xffffff8000a574ae 0x0 0x0 0xffffff8000a574ae 14: 0xffffff8000a56ad7 0x0 0x0 0xffffff8000a56ad7 15: 0x0 0x0 16: 0xffffff8000a58c53 0xffffff8000a58c53 Panicked task 0xffffff94f4bad090: 4 threads: pid 203: symptomsd Backtrace (CPU 3), panicked thread: 0xffffff94f35e9000, Frame : Return Address 0xffffffd01a6bae80 : 0xffffff8003485ffd mach_kernel : _handle_debugger_trap + 0x41d 0xffffffd01a6baed0 : 0xffffff80035e6035 mach_kernel : _kdp_i386_trap + 0x145 0xffffffd01a6baf10 : 0xffffff80035d5803 mach_kernel : _kernel_trap + 0x533 0xffffffd01a6baf60 : 0xffffff8003425a60 mach_kernel : _return_from_trap + 0xe0 0xffffffd01a6baf80 : 0xffffff80034863cd mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffd01a6bb0a0 : 0xffffff8003485b86 mach_kernel : _panic_trap_to_debugger + 0x2b6 0xffffffd01a6bb100 : 0xffffff8003d16409 mach_kernel : _panic + 0x54 0xffffffd01a6bb170 : 0xffffff8003abb71f mach_kernel : _mbuf_class_under_pressure + 0x35af 0xffffffd01a6bb200 : 0xffffff8003ab9452 mach_kernel : _mbuf_class_under_pressure + 0x12e2 0xffffffd01a6bb260 : 0xffffff8003a936cf mach_kernel : _cantrace + 0x1e3f 0xffffffd01a6bb2d0 : 0xffffff8003ab8d99 mach_kernel : _mbuf_class_under_pressure + 0xc29 0xffffffd01a6bb380 : 0xffffff8003a936cf mach_kernel : _cantrace + 0x1e3f 0xffffffd01a6bb3f0 : 0xffffff8003ac0742 mach_kernel : _m_mclfree + 0x1702 0xffffffd01a6bb480 : 0xffffff80037f3f5e mach_kernel : _nstat_ifnet_to_flags_extended + 0x570e 0xffffffd01a6bb4c0 : 0xffffff80037f4837 mach_kernel : _nstat_ifnet_to_flags_extended + 0x5fe7 0xffffffd01a6bbb20 : 0xffffff80037f319a mach_kernel : _nstat_ifnet_to_flags_extended + 0x494a 0xffffffd01a6bbc70 : 0xffffff8003a4a16b mach_kernel : _kctl_getstat + 0x1f9b 0xffffffd01a6bbcc0 : 0xffffff8003acbfcc mach_kernel : _sosend + 0xb4c 0xffffffd01a6bbde0 : 0xffffff8003ade872 mach_kernel : _sendto_nocancel + 0x4c2 0xffffffd01a6bbed0 : 0xffffff8003ade4cb mach_kernel : _sendto_nocancel + 0x11b 0xffffffd01a6bbf40 : 0xffffff8003b9d984 mach_kernel : _unix_syscall64 + 0x204 0xffffffd01a6bbfa0 : 0xffffff8003426226 mach_kernel : _hndl_unix_scall64 + 0x16 Process name corresponding to current thread (0xffffff94f35e9000): symptomsd Boot args: -v alcid=3 watchdog=0 keepsyms=1 igfxonln=1 agdpmod=vit9696 uia_exclude=HS02;SS01;SS02;SS04 -igfxnohdmi -disablegfxfirmware chunklist-security-epoch=0 -chunklist-no-rev2-dev Mac OS version: 21D62 Kernel version: Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64 Kernel UUID: 93729D02-FE6F-355B-BA76-BA930AA7103F KernelCache slide: 0x0000000003200000 KernelCache base: 0xffffff8003400000 Kernel slide: 0x0000000003210000 Kernel text base: 0xffffff8003410000 __HIB text base: 0xffffff8003300000 System model name: MacBookPro13,1 (Mac-473D31EABEB93F9B) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 55756594667669 Last Sleep: absolute base_tsc base_nano Uptime : 0x000032b5d804e89b Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x0000000aaa47d5ec 0x0000000000000000 Zone info: Foreign : 0xffffff801b69d000 - 0xffffff801b6aa000 Native : 0xffffff8027e85000 - 0xffffffa027e85000 Readonly : 0xffffff84f4b51000 - 0xffffff868e4e5000 Metadata : 0xffffffdd5b433000 - 0xffffffdd7b4fb000 Bitmaps : 0xffffffdd7b4fb000 - 0xffffffdd7e4fb000

OK but in your patch the string <key>device-id</key> <data>AhkAAA==</data> is missing? Is it an issue? Or it is no more required?

In my device property I found: <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data>AAAbGQ==</data> <key>device-id</key> <data>AhkAAA==</data> <key>framebuffer-fbmem</key> <data>AACQAA==</data> <key>framebuffer-patch-enable</key> <data>AQAAAA==</data> <key>framebuffer-stolenmem</key> <data>AAAwAQ==</data> </dict> So do I update it?