Jump to content
scanray

opencore startup problems

13 posts in this topic

Recommended Posts

hello, I have installed Catalina in:


Asus P8Z77-V deluxe
I7 3770K
2x8 GB ram
1 Intel 250GB SSD
MSI AMD 5500xt

 

thanks to the help of @jsl2000 in this link.

The problem I have is that I put a second disk with win10.
From that moment I cannot enter the OSX. Gives me KP.
The only solution I found was to boot into recovery mode and from there assign the OSX disk as the startup disk.
After this it starts in Catalina and it works very well.
The downside is that I have to do it every time I turn on the PC.

Anyone have any idea how to solve this problem?

 

Thanks

Share this post


Link to post
Share on other sites
Advertisement
On September 15, 2020 at 6:19 AM, scanray said:

hello, I have installed Catalina in:


Asus P8Z77-V deluxe
I7 3770K
2x8 GB ram
1 Intel 250GB SSD
MSI AMD 5500xt

 

thanks to the help of @jsl2000 in this link.

The problem I have is that I put a second disk with win10.
From that moment I cannot enter the OSX. Gives me KP.
The only solution I found was to boot into recovery mode and from there assign the OSX disk as the startup disk.
After this it starts in Catalina and it works very well.
The downside is that I have to do it every time I turn on the PC.

Anyone have any idea how to solve this problem?

 

Thanks

My advice:

Use BIOS to select your booting.

For example Windows in Disk1 and Mac OS in Disk2.

F8 to select either Disk1 or Disk2 to boot.

No need to edit your config.plist of OpenCore.

If future Clover can boot Big Sur, no problem to boot Windows at all !

Or try .contentDetails method posted today in OpenCore discussion !

Edited by jsl2000

Share this post


Link to post
Share on other sites

Hi @jsl2000,

 

It seems that I did not explain myself well.
My problem is not with the bios. I don't need to press F8.
The bios recognizes my disk with opencore. There is no problem. I can select win or Catalina in the OC menu.
When I select Catalina it gives a KP error. But if I enter the osx recovery mode and there I select that my boot disk is Catalina, the computer restarts, opens OC, I select Catalina and it no longer gives me a KP error.
I have a feeling it's something with nvram, but I don't know how to fix it.

 

thanks

Share this post


Link to post
Share on other sites
3 hours ago, scanray said:

Hi @jsl2000,

 

It seems that I did not explain myself well.
My problem is not with the bios. I don't need to press F8.
The bios recognizes my disk with opencore. There is no problem. I can select win or Catalina in the OC menu.
When I select Catalina it gives a KP error. But if I enter the osx recovery mode and there I select that my boot disk is Catalina, the computer restarts, opens OC, I select Catalina and it no longer gives me a KP error.
I have a feeling it's something with nvram, but I don't know how to fix it.

 

thanks

In this case please show me your current config.plist to check because my original one not related to windows booting.

Share this post


Link to post
Share on other sites

Hi @jsl2000,

 

Sorry for the delay, I've been doing several tests.
Once Catalina boots, I can reboot without problems. The KP appears when I turn on the PC.
Almost always when I turn on the PC it starts Catalina and KP, it automatically reboots and if I let it continue sometimes it reaches the login.
Otherwise: recovery -> startup disk: catalina -> restart: all OK

 

thanks

config.plist

Share this post


Link to post
Share on other sites
1 hour ago, scanray said:

Hi @jsl2000,

 

Sorry for the delay, I've been doing several tests.
Once Catalina boots, I can reboot without problems. The KP appears when I turn on the PC.
Almost always when I turn on the PC it starts Catalina and KP, it automatically reboots and if I let it continue sometimes it reaches the login.
Otherwise: recovery -> startup disk: catalina -> restart: all OK

 

thanks

config.plist

Try my modified config.plist for yours hardware.

config-Z77.plist

Share this post


Link to post
Share on other sites

Hi @jsl2000,

 

Thanks for the config.
It worked very well. Go back to the release version of the OC and disable the debug options. So far so good.
At the end I remove the (-v) from the boot arguments. Oh ... surprise, KP again.
This is the OSX report, there it gives us a light.

panic(cpu 0 caller 0xffffff80242469aa): Kernel trap at 0xffffff7fa4d1349d, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002d5ac000, CR4: 0x00000000001626e0
RAX: 0xffffff7fa4d13492, RBX: 0x0000000000000000, RCX: 0x0000000000000001, RDX: 0x0000000000000000
RSP: 0xffffff8216073880, RBP: 0xffffff8216073880, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8:  0xffffff8216073968, R9:  0xffffff8216073968, R10: 0xffffff804adf7c00, R11: 0x0000000000007340
R12: 0xffffff82160738e8, R13: 0x0000000000000000, R14: 0xffffff8048d08dc0, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7fa4d1349d, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff82160732e0 : 0xffffff802411a65d 
0xffffff8216073330 : 0xffffff8024254a75 
0xffffff8216073370 : 0xffffff80242465fe 
0xffffff82160733c0 : 0xffffff80240c0a40 
0xffffff82160733e0 : 0xffffff8024119d27 
0xffffff82160734e0 : 0xffffff802411a117 
0xffffff8216073530 : 0xffffff80248c1abc 
0xffffff82160735a0 : 0xffffff80242469aa 
0xffffff8216073720 : 0xffffff80242466a8 
0xffffff8216073770 : 0xffffff80240c0a40 
0xffffff8216073790 : 0xffffff7fa4d1349d 
0xffffff8216073880 : 0xffffff7fa76907e8 
0xffffff82160738d0 : 0xffffff7fa7a914d4 
0xffffff8216073930 : 0xffffff7fa7a879eb 
0xffffff82160739b0 : 0xffffff7fa7a830bf 
0xffffff8216073a00 : 0xffffff7fa7aeb69a 
0xffffff8216073a80 : 0xffffff7fa768fb88 
0xffffff8216073b10 : 0xffffff7fa768d79c 
0xffffff8216073b60 : 0xffffff7fa7681410 
0xffffff8216073bb0 : 0xffffff7fa7692bb6 
0xffffff8216073bd0 : 0xffffff7fa7628167 
0xffffff8216073c10 : 0xffffff7fa76257b5 
0xffffff8216073d00 : 0xffffff7fa6a5ade3 
0xffffff8216073d80 : 0xffffff7fa7623823 
0xffffff8216073de0 : 0xffffff80248075c6 
0xffffff8216073e40 : 0xffffff8024807101 
0xffffff8216073ef0 : 0xffffff802480649e 
0xffffff8216073f50 : 0xffffff8024808c56 
0xffffff8216073fa0 : 0xffffff80240c013e 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000->0xffffff7fa4d39fff
         com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7fa6a22000->0xffffff7fa6ae5fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5922E20B-D148-30DC-ABBA-0E99B3BE6940]@0xffffff7fa4b87000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000
            dependency: com.apple.iokit.IOSurface(269.11)[8AF51385-7435-3E2F-9724-6CD27894229D]@0xffffff7fa5e8f000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7fa69c7000
            dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7fa4c2f000
         com.apple.kext.AMDRadeonX6000(3.1)[9C58499D-A52A-346A-A6BA-86FA6190C70E]@0xffffff7fa7622000->0xffffff7fa783ffff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000
            dependency: com.apple.iokit.IOSurface(269.11)[8AF51385-7435-3E2F-9724-6CD27894229D]@0xffffff7fa5e8f000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7fa69c7000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7fa6a22000
         com.apple.kext.AMDRadeonX6000HWLibs(1.0)[436BD2A5-02C2-3F44-8109-26DAAC7C7C05]@0xffffff7fa7840000->0xffffff7faa176fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000

BSD process name corresponding to current thread: kernel_task
Boot args: vsmcgen=1 -lilubetaall npci=0x2000 agdpmod=pikera alcid=3 

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide:     0x0000000023e00000
Kernel text base: 0xffffff8024000000
__HIB  text base: 0xffffff8023f00000
System model name: iMac20,1 (Mac-CFF7D910A743CAAF)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 9779852609

 

Share this post


Link to post
Share on other sites
3 hours ago, scanray said:

Hi @jsl2000,

 

Thanks for the config.
It worked very well. Go back to the release version of the OC and disable the debug options. So far so good.
At the end I remove the (-v) from the boot arguments. Oh ... surprise, KP again.
This is the OSX report, there it gives us a light.


panic(cpu 0 caller 0xffffff80242469aa): Kernel trap at 0xffffff7fa4d1349d, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002d5ac000, CR4: 0x00000000001626e0
RAX: 0xffffff7fa4d13492, RBX: 0x0000000000000000, RCX: 0x0000000000000001, RDX: 0x0000000000000000
RSP: 0xffffff8216073880, RBP: 0xffffff8216073880, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8:  0xffffff8216073968, R9:  0xffffff8216073968, R10: 0xffffff804adf7c00, R11: 0x0000000000007340
R12: 0xffffff82160738e8, R13: 0x0000000000000000, R14: 0xffffff8048d08dc0, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7fa4d1349d, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff82160732e0 : 0xffffff802411a65d 
0xffffff8216073330 : 0xffffff8024254a75 
0xffffff8216073370 : 0xffffff80242465fe 
0xffffff82160733c0 : 0xffffff80240c0a40 
0xffffff82160733e0 : 0xffffff8024119d27 
0xffffff82160734e0 : 0xffffff802411a117 
0xffffff8216073530 : 0xffffff80248c1abc 
0xffffff82160735a0 : 0xffffff80242469aa 
0xffffff8216073720 : 0xffffff80242466a8 
0xffffff8216073770 : 0xffffff80240c0a40 
0xffffff8216073790 : 0xffffff7fa4d1349d 
0xffffff8216073880 : 0xffffff7fa76907e8 
0xffffff82160738d0 : 0xffffff7fa7a914d4 
0xffffff8216073930 : 0xffffff7fa7a879eb 
0xffffff82160739b0 : 0xffffff7fa7a830bf 
0xffffff8216073a00 : 0xffffff7fa7aeb69a 
0xffffff8216073a80 : 0xffffff7fa768fb88 
0xffffff8216073b10 : 0xffffff7fa768d79c 
0xffffff8216073b60 : 0xffffff7fa7681410 
0xffffff8216073bb0 : 0xffffff7fa7692bb6 
0xffffff8216073bd0 : 0xffffff7fa7628167 
0xffffff8216073c10 : 0xffffff7fa76257b5 
0xffffff8216073d00 : 0xffffff7fa6a5ade3 
0xffffff8216073d80 : 0xffffff7fa7623823 
0xffffff8216073de0 : 0xffffff80248075c6 
0xffffff8216073e40 : 0xffffff8024807101 
0xffffff8216073ef0 : 0xffffff802480649e 
0xffffff8216073f50 : 0xffffff8024808c56 
0xffffff8216073fa0 : 0xffffff80240c013e 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000->0xffffff7fa4d39fff
         com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7fa6a22000->0xffffff7fa6ae5fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5922E20B-D148-30DC-ABBA-0E99B3BE6940]@0xffffff7fa4b87000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000
            dependency: com.apple.iokit.IOSurface(269.11)[8AF51385-7435-3E2F-9724-6CD27894229D]@0xffffff7fa5e8f000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7fa69c7000
            dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7fa4c2f000
         com.apple.kext.AMDRadeonX6000(3.1)[9C58499D-A52A-346A-A6BA-86FA6190C70E]@0xffffff7fa7622000->0xffffff7fa783ffff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000
            dependency: com.apple.iokit.IOSurface(269.11)[8AF51385-7435-3E2F-9724-6CD27894229D]@0xffffff7fa5e8f000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7fa69c7000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7fa6a22000
         com.apple.kext.AMDRadeonX6000HWLibs(1.0)[436BD2A5-02C2-3F44-8109-26DAAC7C7C05]@0xffffff7fa7840000->0xffffff7faa176fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7fa4d01000

BSD process name corresponding to current thread: kernel_task
Boot args: vsmcgen=1 -lilubetaall npci=0x2000 agdpmod=pikera alcid=3 

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide:     0x0000000023e00000
Kernel text base: 0xffffff8024000000
__HIB  text base: 0xffffff8023f00000
System model name: iMac20,1 (Mac-CFF7D910A743CAAF)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 9779852609

 

Please update your OpenCore to 0.6.2 and use my config.plist without any change.

If it worked without any issue, you can remove -v again.

Share this post


Link to post
Share on other sites

Hi @jsl2000,

 

9 hours ago, jsl2000 said:

Please update your OpenCore to 0.6.2 and use my config.plist without any change.

where I find 0.6.2 ?

here acidanthera/OpenCorePkg the last is 0.6.1

 

thanks

 

 

Edited by scanray

Share this post


Link to post
Share on other sites

ok, I did it. But it stops here and I cant go to recovery

 

KP-S.jpg

Edited by scanray

Share this post


Link to post
Share on other sites
1 hour ago, scanray said:

ok, I did it. But it stops here and I cant go to recovery

 

KP-S.jpg

That means your networking kext need update or change to the compatible one.

No more support of AppleEthernetE1000.

You should change it to IntelMausi.kext or IntelMausiEthernet.kext as mine.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

×