Jump to content

Kernelspace errors when I try to boot up macOS from OpenCore on a Fujitsu Lifebook E549 in order to install it.


cherries
 Share

10 posts in this topic

Recommended Posts

Hello!

I'm a newbie to Hackintoshing, so I decided to use the OpenCore starter guide. After being done with configurating everything (adding base files, like kexts and ACPI files, generating SMBIOS, and so on...), I booted up my USB, went to the picker, choose the 2nd option (that boots to macOS, the first option is Windows). However, after selecting macOS, it suddenly puts out a lotttt of errors, as seen in the logs (logs files below, 0902 till 1126 are the logs for RELEASE version, the rest is on DEBUG).

Either way, I have Imgur galleries about my specs, and other related things, so here they are:

Specs: https://imgur.com/a/adWHgL8

Kexts/ACPI/Drivers/Tools folders: https://imgur.com/a/zx5kube

I also have my config.plist in the files, so if you want to, go check it out for me! (pretty pls?)

 

opencore-2022-08-07-090251.txt opencore-2022-08-07-092151.txt opencore-2022-08-07-112649.txt opencore-2022-08-07-131240.txt opencore-2022-08-07-131336.txt

config.plist

Edited by cherries
readded the config.plist file (now with sensitive data removed)
Link to comment
Share on other sites

3 minutes ago, cherries said:

Hello!

I'm a newbie to Hackintoshing, so I decided to use the OpenCore starter guide. After being done with configurating everything (adding base files, like kexts and ACPI files, generating SMBIOS, and so on...), I booted up my USB, went to the picker, choose the 2nd option (that boots to macOS, the first option is Windows). However, after selecting macOS, it suddenly puts out a lotttt of errors, as seen in the logs (logs files below, 0902 till 1126 are the logs for RELEASE version, the rest is on DEBUG).

Either way, I have Imgur galleries about my specs, and other related things, so here they are:

Specs: https://imgur.com/a/adWHgL8

Kexts/ACPI/Drivers/Tools folders: https://imgur.com/a/zx5kube

I also have my config.plist in the files, so if you want to, go check it out for me! (pretty pls?)

 

opencore-2022-08-07-090251.txt 256 kB · 0 downloads opencore-2022-08-07-092151.txt 256 kB · 0 downloads opencore-2022-08-07-112649.txt 256 kB · 0 downloads opencore-2022-08-07-131240.txt 256 kB · 0 downloads opencore-2022-08-07-131336.txt 256 kB · 0 downloads config.plist 37.7 kB · 0 downloads

Oh wait, I forgot one thing! My EFI partition is placed at the end of my hard drive, as seen in the picture below

Annotation 2022-08-07 160018.png

Link to comment
Share on other sites

UPDATE: I got into the installation menu! I had to use the 

-igfxvesa

boot argument to get into the menu, however, so that means no GPU acceleration for me.

16598660989904432291309375875458.jpg

Link to comment
Share on other sites

I suspect the error is caused by my GPU (which is, well, an Intel UHD Graphics 620, if you haven't seen my pic about it before.) Might have to patch it up after installation.

Link to comment
Share on other sites

11 hours ago, ricoc90 said:

There is no SMBios data in your config. Did you null them out for the sake of posting, or have you forgotten to fill them in?

It's intentionally nulled out for posting, but if you want the uncensored version, give me a private message

Link to comment
Share on other sites

Guest ricoc90

No, no worries. Just wanted to make sure.

Could you try the following?

EnableWriteUnprotector = False
RebuildAppleMemoryMap = True
SyncRuntimePermissions = True

 

Link to comment
Share on other sites

4 hours ago, ricoc90 said:

No, no worries. Just wanted to make sure.

Could you try the following?

EnableWriteUnprotector = False
RebuildAppleMemoryMap = True
SyncRuntimePermissions = True

 

Firstly, an UPDATE: I got into the macOS installation menu with GPU acceleration, by using 

framebuffer-patch-enable

and

framebuffer-stolenmem

Yes, I know, those two entries will limit myself from being able to use higher resolution and refresh rate than 1366x768 and 60Hz, but I never have a need for them, anyway. Everything worked out well, until when I added in the HorNDIS.kext kext. Somehow, when it's there, I cannot boot into macOS, nor get into the boot picker for some reason, because OpenCore would just show some logs, then boot straight into Windows after being stuck in a black screen for a while. But without the kext, I cannot use USB tethering

Link to comment
Share on other sites

On 8/9/2022 at 7:14 AM, ricoc90 said:

No, no worries. Just wanted to make sure.

Could you try the following?

EnableWriteUnprotector = False
RebuildAppleMemoryMap = True
SyncRuntimePermissions = True

 

what do they do for this situation, by the way? in the second UPDATE, I said that using "framebuffer-patch-enable" and "framebuffer-stolenmem", I was able to get into the installer with GPU acceleration, but I don't really know if those options you are suggesting there would help me

Link to comment
Share on other sites

Guest ricoc90

The reason why I suggested the earlier mentioned changes was to rule out write protection conflicts, as mentioned here: https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html#stuck-on-eb-log-exitbs-start

But since you are able to boot without these changes you can assume that those changes won't help your case.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...