Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

Helipilot2
Helipilot2
Posted
Posted

Can anyone help me?

 

I'm trying to get sound on my Hackintosh with open core. 

Sadly it is not working. I have a ALC892 sound card, AppleALC.kext is in the kext folder, but not loaded (results in no sound)

Can anyone please config the config.plist file correctly for the ALC892 sound?

 

Mainboard: Z170M-D3H, 6600K, Radeon RX480

 

Kinds regards

Helipilot

 

config.plist

Erroruser
Erroruser
Posted
Posted
1 minute ago, Helipilot2 said:

Can anyone help me?

 

I'm trying to get sound on my Hackintosh with open core. 

Sadly it is not working. I have a ALC892 sound card, AppleALC.kext is in the kext folder, but not loaded (results in no sound)

Can anyone please config the config.plist file correctly for the ALC892 sound?

 

Mainboard: Z170M-D3H, 6600K, Radeon RX480

 

Kinds regards

Helipilot

 

config.plist

use hackintool to get the pci devices an add in to your config an give that a try

Helipilot2
Helipilot2
Posted
Posted
7 minutes ago, errorexists said:

sorry my bad

Thanks it works! Another question, The boot loader has a very bad resolution (the apple logo is very big) is there a way to correct that? How do I auto boot macOS (now I have to chose a drive before the os is booting)

 

 

Erroruser
Erroruser
Posted
Posted (edited)
5 minutes ago, Helipilot2 said:

 

to get the bless to work select start up in the system preferences an for the setting for the logo like so
image.thumb.png.c8d2923fb46b9a9985512be6be13e565.png
 

hope this helps you out

Edited by errorexists
Helipilot2
Helipilot2
Posted
Posted
19 minutes ago, errorexists said:

sorry my bad

Thanks it works! Another question, The boot loader has a very bad resolution (the apple logo is very big) is there a way to correct that? How do I auto boot macOS (now I have to chose a drive before the os is booting)

 

Thnx it is now autobooting, sadly the resolution is still bad 

NorthAmTrans
NorthAmTrans
Posted
Posted
On 8/10/2019 at 10:07 AM, dracoflar said:

 

_DSM to XDSM:

Your hardware shouldn't need this

 

 

You were absolutely right. I've now got zero patches and a much much much slimmer config with no redundancies. Now I can start building my OC config.

NorthAmTrans
NorthAmTrans
Posted
Posted (edited)

Hey friends. 2 questions.

 

Converting my ROM number from Hackintool to whatever is used in OC's config. Can anyone help me with what/how to get 1831BFE049C8 into the right format?

 

Second question, the first time I got this to boot (pure luck) I definitely set something wrong and confused iCloud and such. Im guessing I set Automatic or UpdateSMBIOS. Which setting says "use this dude?"

 

EDIT ABOVE: Read the guide. Automatic uses generic. 

Edited by NorthAmTrans
dumb ass
Andrw0380
Andrw0380
Posted
Posted
2 hours ago, FredWst said:

 

Will try but don't think this is the trouble, 3 hacks and same issue nothing has been change in my configs.

 

I did not get Apple boot logo too when removing -v

 

Fred

I can confirm I am having the same issue. Was fine when building from OpenCore source a month ago, but this latest release, using '-v', doesn't show verbose. Not sure if it's just -v that is affected as I have a Kaby Lake CPU and use 'lilucpu=8' to fix the Graphical issues that Kaby Lake has with Mojave. The reason I don't think it's working is when using that flag, my laptop screen won't go black for 1 second when the second boot stage process to starting, but during this build, the screen does black out for that duration. I did confirm with the following commands 'nvram -p | grep boot-args' that boot-args are being passed to NVRAM so know NVRAM is working.

Pavo
Pavo
Posted
Posted (edited)

I don't know why no one reads the docs. Located under Tips and Tricks in the docs. The key quirk here is ProvideConsoleGop in UEFI quirks.

  

How can I migrate from AptioMemoryFix?
Behaviour similar to that of AptioMemoryFix can be obtained by installing FwRuntimeServices driver and enabling the quirks listed below. Please note, that most of these are not necessary to be enabled. Refer to their individual descriptions in this document for more details.
• ProvideConsoleGop (UEFI quirk) 
• AvoidRuntimeDefrag
• DiscardHibernateMap
• EnableSafeModeSlide
• EnableWriteUnprotector 
• ForceExitBootServices 
• ProtectCsmRegion
• ProvideCustomSlide
• SetupVirtualMap 
• ShrinkMemoryMap

 

Edited by Pavo
  • Like 2
  • Thanks 1
Andrw0380
Andrw0380
Posted
Posted (edited)
1 hour ago, Pavo said:

I don't know why no one reads the docs. Located under Tips and Tricks in the docs. The key quirk here is ProvideConsoleGop in UEFI quirks.

  


How can I migrate from AptioMemoryFix?
Behaviour similar to that of AptioMemoryFix can be obtained by installing FwRuntimeServices driver and enabling the quirks listed below. Please note, that most of these are not necessary to be enabled. Refer to their individual descriptions in this document for more details.
• ProvideConsoleGop (UEFI quirk) 
• AvoidRuntimeDefrag
• DiscardHibernateMap
• EnableSafeModeSlide
• EnableWriteUnprotector 
• ForceExitBootServices 
• ProtectCsmRegion
• ProvideCustomSlide
• SetupVirtualMap 
• ShrinkMemoryMap

 

Yeah sorry I did research and found the Vanilla Desktop guide for Kaby Lake, but can't find this guide that you mentioned. Do you have a link for reference?

 

Thanks for the suggestion as that did fix the issue! Wanted to ask another question. I was looking at the guides I could find and how do you drop say the PtidDevc and xh_OEMBD ACPI tables? In Clover, I could just define the table names, but with OC in the examples I see to drop CPU tables, you have to define the table numbers. Just wanted to clear up some ACPI errors I see in verbose.

Edited by Andrw0380
maddie
maddie
Posted
Posted
42 minutes ago, NorthAmTrans said:

First attempt. Failure at the very beginning. "Missing plist for Lilu.kext"

 

Everything seems right in Xcode to my eyes but clearly something is wrong. 

EFI.zip

 

Your 'drivers' and 'kext' folder should be 'Drivers' and 'Kexts'. It's case-sensitive.

  • Like 1
NorthAmTrans
NorthAmTrans
Posted
Posted (edited)
28 minutes ago, maddie said:

 

Your 'drivers' and 'kext' folder should be 'Drivers' and 'Kexts'. It's case-sensitive.

And BOOTED. Big thanks.

 

Now to figure out why my ACPI stuff isn’t loading. I’m thinking I mislabeled the folder there as well. 

 

EDIT: Definitely need to change it from Custom to "Add" and I have no idea how I landed there in the first place.

 

Helpful for others who aren't as knowledgable. Im sure its posted it well before this comment but if you're this far in here it is again. https://insanelymacdiscord.github.io/Getting-Started-With-OpenCore/

Edited by NorthAmTrans
Dumb Ass Again
FredWst
FredWst
Posted
Posted
4 hours ago, Pavo said:

I don't know why no one reads the docs. Located under Tips and Tricks in the docs. The key quirk here is ProvideConsoleGop in UEFI quirks.

  


How can I migrate from AptioMemoryFix?
Behaviour similar to that of AptioMemoryFix can be obtained by installing FwRuntimeServices driver and enabling the quirks listed below. Please note, that most of these are not necessary to be enabled. Refer to their individual descriptions in this document for more details.
• ProvideConsoleGop (UEFI quirk) 
• AvoidRuntimeDefrag
• DiscardHibernateMap
• EnableSafeModeSlide
• EnableWriteUnprotector 
• ForceExitBootServices 
• ProtectCsmRegion
• ProvideCustomSlide
• SetupVirtualMap 
• ShrinkMemoryMap

 

@Pavo

 

I read doc but when an option is present since many months how to believe (explain) that it was the issue ?

I just enable ProvideConsoleGop now works fine -v and Apple boot screen. (Strange for an option related to console)

Dont understand the relation between AptioFixMemory and this option.

 

so

with AptioFixMemory : ProvideConsoleGop = false

with FwRuntimeServices : ProvideConsoleGop = true

Works now on all my hack. (Aptio IV or Aptio V)

 

Fred

 

 

Matgen84
Matgen84
Posted
Posted
12 hours ago, LAbyOne said:

I maybe have misunderstood your point, 

but, hackintosh is not a brand, just a choice anyone make for its own purpose

hence the unavoidable need to understand what they are doing, its something you take on yourself first, then using places like insanelymac you can find help to solve issues, but the base is you have to learn first

Sure Clover simplified the installation providing an installer.... but if you then have to modify your config or any other file you will mount your EFI and make the changes... 

its only a bootloader nothing similar to what dosdude1 did

So i can't really see what would make this one so uncomfortable to set up.

then again I maybe have misunderstood your point...

 

The real problem in my opinion 

is that there are also many people now too *miseducated to be able to give real contribution, quoting what you said " people want things to be easier and faster", well people must understand also that sometimes things are different and require a different spirit.

 

PS

*miseducated = people who just want to find the supper ready, and can't even make a sandwich by themselves :)

 

Right. But:

The question: hackintosh for all or for specialists. A bootoader, this is just my opinion, is not just about specialists. It must be usable by everyone, and the community is used only in case of particular problems. That's because I understand Chris's post. If it takes days, sharp knowledge to parameterize it can affect its dissemination.

 

Just my opinion. A bootloader must remain accessible to the largest number of users :)

vandroiy2012
vandroiy2012
Posted
Posted (edited)
2 hours ago, FredWst said:

so

with AptioFixMemory : ProvideConsoleGop = false

with FwRuntimeServices : ProvideConsoleGop = true

Works now on all my hack. (Aptio IV or Aptio V)

 

Fred

 

 

 

AptioMemoryFix is deprecated. Part of it migrated to OpenCore and other part to FwRuntimeServices. 

You should not use AptioMemoryFix in OpenCore at all!! Forget about it!!! It is now only for Clover. 

Edited by vandroiy2012
  • Like 2
FredWst
FredWst
Posted
Posted
19 minutes ago, vandroiy2012 said:

 

AptioMemoryFix is deprecated. Part of it migrated to OpenCore and other part to FwRuntimeServices. 

You should not use AptioMemoryFix in OpenCore at all!! Forget about it!!! It is now only for Clover. 

 

Yes I know that.

I just want to explain that before dropping AptioMemoryFix (old OC 0.0.4)  ProvideConsoleGop = false was working fine for me.

And I don't understand why now I need it. if u can explain.

 

Fred 

 

 

  • Like 1
vit9696
vit9696
Posted
Posted

@FredWst, not to offend, but you did not even open the docs. Look here:

https://github.com/acidanthera/OpenCorePkg/commit/e611445f46179837d2ad22349c46457226615718#diff-567688bcd4741f8bbfd57acebc9f644cL3031

The warning not to rely on AptioMemoryFix for this behaviour was in the docs for ages, as you see I removed it 5 days ago after AptioMemoryFix died. It is just you that ignored most of the file =)

  • Like 2
 Share
Go to topic listing
×
×
  • Create New...