Jump to content
8755 posts in this topic

Recommended Posts

Hello. I just installed OpenCore on my desktop but I can't figure out how to solve this issue: while the picker is disabled, i tried to use apple hotkeys, like keeping pressed cmd+r or cmd+v (after enabling them), but it doesn't work.

If i enable the picker, pressing cmd+v before loading osx, works...

What can i do? Thanks!

config.plist

hi guys!

after I upgrade from 10.15.3 to 10.15.4, it boots quite well, except it show up `EB|` problems as the image shows up below:

image.thumb.png.9b9001940efc275bdf957ebf30374ad8.png

then I upgrade Lilu to 1.4.3 and Whatevergreen to 1.3.8, after I reboot it 2 times successfully later it couldn't boot to login window any longer

opencore:0.5.7

boot-args: -v igfxfw=2 agdpmod=vit9696,pikera

console log shows up below:

image.thumb.png.b1ffc03b5d2cc33fb3f6189627035bfd.png


77766190-412cd680-707a-11ea-8139-0bbbded5c691.thumb.jpeg.21f7ccfd6a6571a23af2bdef0343c370.jpeg

I tried to use Opencore 0.5.6 but still the same problem

Just now, markl18 said:

hi can some kind sole please look at my kp file tell me what is wrong I dont even know what it failed upon is it USBHostHIDDevice0-x100003ec

IMG-1129.jpg

No it didn't panic on USBHostHIDDevice0-x100003ec, it panicked on AppleIntelFramebufferAzul.

20 hours ago, asstastic said:

This is normal, the nvidia card drivers are not loaded in recovery mode and so graphics are running in basic software mode without acceleration.

 

Thank, that's logical.. And do you have any thoughts about no display output when booting to Recovery mode? Picture appears only when I reconnect display cable to video card, or if system with booted Recovery goes to sleep and then woke up again.

10.15.4 XCPM

I test  for X99 & X299 Board.

xcpm_bootstrap not for X299
XCPM Patches 10.15.4  Modify By N.Mano

#1

Base: xcpm_core_scope_msrs
Comment: xcpm_core_scope_msrs (c) Pike R. Alpha Modify By N.Mano
Count: 1
Enabled: YES
Find:    31D2E857 D2FFFF
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 31D29090 909090
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0


#2

Base:  _xcpm_pkg_scope_msrs
Comment:  _xcpm_pkg_scope_msrs (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   31D2E8E9 F9FEFF
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 31D29090 909090
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

#3

Base: _xcpm_SMT_scope_msrs #1
Comment: _xcpm_SMT_scope_msrs #1 (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   BE060000 005DE908 000000
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: BE060000 005DC390 909090
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0


#4

Base: _xcpm_SMT_scope_msrs_2
Comment: _xcpm_SMT_scope_msrs_2 (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   31D2E838 FDFFFF
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 31D29090 909090
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

#5

Base: _xcpm_enable_pstate
Comment: _xcpm_enable_pstate_patch (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   41C1E608 4963D689 D048C1EA 20
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 41C1E608 B800FF00 0031D290 90
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

#6 This patch for X99(Not for X299)

Base: xcpm_bootstrap
Comment: xcpm_bootstrap_HASwell_E (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   80C3C480 FB42
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 80C3C180 FB42
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

#7

Base: xcpm MSR Patch 4206
Comment:xcpm MSR Patch 4206 (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   42060000 DC330000 00000000 00000000 1F000000 00000000 18000000 00000000 00000000 00000000 00000000 00000000 
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 42060000 00000000 00000000 00000000 1F000000 00000000 18000000 00000000 00000000 00000000 00000000 00000000 
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

#8

Base: xcpm E2 Patch 
Comment:C6/C7_If=E2-Enabled=0x7E000403  (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   E2000000 4C000000 00000000 00000000 0F040000 00000000 0500001E 
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: E2000000 4C000000 00000000 00000000 0F040000 00000000 0304007E 
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

#9

Base: xcpm 3A06 Patch 
Comment: xcpm support /0x82D390/MSR_PP0_POLICY 0x63a (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   3A060000 DC330000 00000000 00000000 1F 
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 3A060000 00000000 00000000 00000000 00 
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

23617368_ScreenShot2020-03-28at9_39_02AM.thumb.png.e4a73bda08fd529c0267ae02543f0de2.png

Edited by nmano
  • Like 2

I update XCPM _bootstrap for Haswell-E 10.15.4

 

Base: _xcpm_bootstrap
Comment: xcpm_bootstrap_HASwell_E (c) Pike R. Alpha Modify By N.Mano
Count: 0
Enabled: YES
Find:   80C3C480 FB42
Identifier: kernel
Limit: 0
Mask: (LEAVE THIS EMPTY)
MatchKernel: 
Replace: 80C3C180 FB42
ReplaceMask: (LEAVE THIS EMPTY)
Skip: 0

 

Edited by nmano
  • Like 2

661136591_ScreenShot2020-03-29at2_58_35AM.thumb.jpg.f0a3282d4a80ca11a6728472fc546561.jpg

 

PowerTimeoutKernelPanic=true was working in 10.15.3 but didn't work PowerTimeoutKernelPanic in 10.15.4 automatically restart issue

anyone can help me 

Edited by anmool
insert of jpg file
20 hours ago, elapse said:

This happens to me too.

Clearing the nvram, removes opencore from bios boot menu.

I guess it is normal?

Happens here was well. But it shouldn't be normal. The only entry OC throws in NVRAM is the boot arguments. Outside of that, it's pretty basic. BT delay, computer name, keyboard language, location services, audio, and your iCloud tokens are pretty much the only values stored. None of which should really mess with OC.

 

It seems more like a bug than working as intended.

Resetting NVRAM means resetting NVRAM not just from OpenCore supplied values, but also from other values safe to delete. It is a full system reset, so it is normal that OpenCore entry, which is created by the BIOS itself in the first place, is removed.

 

PowerTimeoutKernelPanic should be fixed.

  • Like 2

In Acidanthera ocbuild there is Update mtoc to 949.0.1 and I recently installed mtoc via brew (927.0.2) and can't be upgraded to 949.0.1 via brew. Should I expect any complications with this version or it's better to uninstall it and reinstall from ocbuild?

Edited by hardcorehenry
2 hours ago, hardcorehenry said:

In Acidanthera ocbuild there is Update mtoc to 949.0.1 and I recently installed mtoc via brew (927.0.2) and can't be upgraded to 949.0.1 via brew. Should I expect any complications with this version or it's better to uninstall it and reinstall from ocbuild?

Does not matter much, I do not think there were (m)any meaningful changes in mtoc. We updated from a really old version to check something.

  • Like 2
  • Thanks 1

Can somebody help me with slow boot with Opencore 0.5.6.

I've got an HP Elitedesk 800 g1 with 12gb ram, Intel HD4600, BX500 240GB SSD.

Did a sanity check on my plist and everything is green. But my boot time is around 1 minute.

Ataching my latest log from opencore.

Thank you!

opencore-2020-03-29-144713.txt

Ok, so I got almost working everything on my x220 (even brightness control and battery status!) but for some reason VoodooPS2/VoodooInput is not loading, and I tried acidanthera version and also one from T420 thread and I'm not sure what is wrong.

Any advice? It /was/ working previously on Clover so I assume this is OpenCore quirk. Maybe kexts order?

1 hour ago, nutro said:

Can somebody help me with slow boot with Opencore 0.5.6.

I've got an HP Elitedesk 800 g1 with 12gb ram, Intel HD4600, BX500 240GB SSD.

Did a sanity check on my plist and everything is green. But my boot time is around 1 minute.

Ataching my latest log from opencore.

Thank you!

opencore-2020-03-29-144713.txt

Suddenly there are many people starting to get the slow boot problem on v0.5.6 and v0.5.7 including me. Boot logs do not give any clue about this issue, and @vit9696 says this is not related to OpenCore. But some people go back to v.0.5.5 and say that this problem does not happen in v0.5.5. You can try it.

×
×
  • Create New...