Jump to content
8755 posts in this topic

Recommended Posts

12 hours ago, Shaneee said:

What would stop OC booting one version of macOS but not the other? My current EFI will boot my Catalina install with no issues but stalls when booting either a HS installer or a Mojave Installer with 3 kexts not being injected.

 

 

Just my opinion: Have you define MaxKernel/MinKernel for different Darwin version or at least MinKernel (HSierra):

 

				<key>BundlePath</key>
				<string>Lilu.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/Lilu</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key> 
				<string></string> <------
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>

 

 

 

 

  • Like 1

@Pavo So here is my dilemma:

I inject only the board I'd and the SKU of the imacpro and with shikigva=144 I got HEVC encoding/decoding and all DRM playback. The SMC recognises all keys properly, but the CPU is locked at 3500 without idling. So my goal is to load my original SSDT CpuPM properly and discard the one which is not working. Or patch the ACPI names for proper reference. How can that be achieved in OC?

 

Edited by startergo
Missing details
On 12/14/2019 at 1:21 AM, Andrey1970 said:

 

564220431_2019-12-1403_19_08.thumb.png.fd001f6ab494d38dad1b730a29d058e8.png

 

OK, so after hours of googling, it looks like OpenCore has a bug/issue/feature (whatever you want to call it), but the problem is that it doesn't load AppleHDA and so I get no sound.

 

Do I need to open a bugtracker ticket somewhere for this?

 

I have found a temporary solution, which is kind of weird, but OpenCore loads AppleHDA if I block a kext (I block HPET for what it's worth).

 

I can give complete specs of my machine if required. Would be great if OpenCore could be fixed so I don't need this workaround.

 

2 hours ago, DanielMac said:

 

OK, so after hours of googling, it looks like OpenCore has a bug/issue/feature (whatever you want to call it), but the problem is that it doesn't load AppleHDA and so I get no sound.

 

Do I need to open a bugtracker ticket somewhere for this?

 

I have found a temporary solution, which is kind of weird, but OpenCore loads AppleHDA if I block a kext (I block HPET for what it's worth).

 

I can give complete specs of my machine if required. Would be great if OpenCore could be fixed so I don't need this workaround.

 

Here you might find interesting info and you might want to take a look at this repository and the way HPET is disabled via small SSDT, don't know if it cause any problems in Windows, you'd have to check it.

14 minutes ago, hardcorehenry said:

Here you might find interesting info and you might want to take a look at this repository and the way HPET is disabled via small SSDT, don't know if it cause any problems in Windows, you'd have to check it.

 

I don't use Windows, so not an issue. I see in IOReg that HPET came back anyway (must have been loaded by another kext later?)

Real issue has nothing to do with HPET in fact, but that the sound system is not working without this "hack" (AppleHDA not loading).

 

Over the past week, many many hours (too many), I'm still unable to get my ASUS Gryphon Z97 machine to even boot with OpenCore. 

 

I configured the OpenCore config.plist exactly as displayed on:
https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/config.plist/haswell

 

Since that base didn't work, changed a million settings, and nothing will get this hardware to boot, OpenCore Menu just hangs in most cases.

 

Maybe this ASUS Gryphon Z97 board is just buggy, not entirely surprised. I had 2 Z87 Gryphon's replaced and 3 Z97 Gryphons replaced because none of them were able to power/charge iPads on any USB port albeit ASUS product market say the USB ports have special additional power for this function, it never worked in any OS. Not even Android devices when connected ever get recognised!! Also strange random things happen with Video Cards in different PCI slots, monitors connected would switch around constantly, left would be boot screen, the right would be boot screen (Windows and Mac) sometimes no monitor will get signal if video card in last PCIe slot. Nvidia blamed Asus, Asus blamed Nvidia, sigh, Windows and Hackintosh.


I have a Clover config working but can't get SATA Hot Plug working though.

 

MaciASL won't compile my system DSDT or SSDT, some compile errors.

 

Is there a Linux equivalent to MaciASL I could try test if compile on a Linux Live Boot?

 

I attach Asus_Gryphon_Z97_MaciASL.dsl_aml_Files.zip with my System DSDT.dsl and System SSDT-1.dsl that won't compile and all the aml files that did compile.

 

Attach my working Clover EFI folder.

 

Attach a fresh new OpenCore Builder EFI folder, untouched.

 

Anyone able to take a look?

 

I trashed all the previous config files and decide to start fresh.

 

wetransfer.com link for Clover EFI folder:

EFI-Clover-Mojave-Gryphon-Z97-RX580-Working-Full_HW_Accell_H264_HVEC.zip

 

https://we.tl/t-kwvnMvgNCO

Asus_Gryphon_Z97_MaciASL.dsl_aml_Files.zip

OpenCore-ASUS_Gryphon_Z97_Build.zip

5 hours ago, DanielMac said:

 

OK, so after hours of googling, it looks like OpenCore has a bug/issue/feature (whatever you want to call it), but the problem is that it doesn't load AppleHDA and so I get no sound.

 

Do I need to open a bugtracker ticket somewhere for this?

 

I have found a temporary solution, which is kind of weird, but OpenCore loads AppleHDA if I block a kext (I block HPET for what it's worth).

 

I can give complete specs of my machine if required. Would be great if OpenCore could be fixed so I don't need this workaround.

 

 

Fix HPET in ACPI. (Add IRQ in HPET)

For example:

2091822797_2019-12-2017_04_06.png.cf601d682c12426a508d8c94b272dc04.png

Edited by Andrey1970

I thought I was ready for Catalina 10.15.2 from Mojave 10.14.6 but it seems I didn't read enough. Im sure I've missed something simple. I get to the progress bar then I just reboot.

 

Attached are two screen shots I grabbed with the fast scrolling in -v along with my current EFI. 

 

For what its worth I can reset NVRAM and enter Recovery. Im currently reinstalling from here now.

 

One note, even though I've renamed the drive to "Catalina", the OS shows up in Picker as Mojave. Im assuming this is my best lead. Any help is more than welcome.

IMG_0186.JPG

IMG_0188 2.JPG

OC EFI 20191207 2.zip

41 minutes ago, NorthAmTrans said:

I thought I was ready for Catalina 10.15.2 from Mojave 10.14.6 but it seems I didn't read enough. Im sure I've missed something simple. I get to the progress bar then I just reboot.

 

Attached are two screen shots I grabbed with the fast scrolling in -v along with my current EFI. 

 

For what its worth I can reset NVRAM and enter Recovery. Im currently reinstalling from here now.

 

One note, even though I've renamed the drive to "Catalina", the OS shows up in Picker as Mojave. Im assuming this is my best lead. Any help is more than welcome. 

OC EFI 20191207 2.zip try this but not sure why you have a ACPI/whatever kexts

  • Like 1
20 minutes ago, errorexists said:

OC EFI 20191207 2.zip try this but not sure why you have a ACPI/whatever kexts

 

Still no go. This is a new one for me.

 

I use WEG for my RX580 though it's not completely necessary I guess. Do you not?

 

Hmm any other ideas?

 

EDIT: 

00:000 00:000 OCC: No compatible mode for 1900x1600@0 (max: 0) resolution
00:056 00:056 OC: Changed resolution to 1900x1600@0 (max: 0) from 1900x1600 - Not Found
09:384 09:327 OC: Nested ReRun is not supported
09:701 00:317 BS: Failed to start OpenCore image - Already started
09:760 00:058 BS: Failed to load OpenCore from disk - Already started
09:814 00:054 OC: Boot failed - Not Found
09:871 00:057 OCB: StartImage failed - Not Found
 

Edited by NorthAmTrans
12 minutes ago, NorthAmTrans said:

 

Still no go. This is a new one for me.

 

I use WEG for my RX580 though it's not completely necessary I guess. Do you not?

 

Hmm any other ideas?

the only thing i can think of you bios is not correct an these 2 kexts in pic an for bios


update to current bios (2401) adjust
Boot/secure boot
os type other

key management clear secure boot keys
Adanced/system agent
VT-d disable
above 4g doesnt matter
Graphics configuration/ primary Display PCIE
PCH storage config / SATA mode selection/AHCI

image.png.37a14b79309dcf1f85e01c74a71960b2.png

 

an block out these ssdt
image.thumb.png.26ef19afed4371f16fdb3a8623f9400f.png

  • Like 1
24 minutes ago, errorexists said:

the only thing i can think of you bios is not correct an these 2 kexts in pic an for bios


update to current bios (2401) adjust
Boot/secure boot
os type other

key management clear secure boot keys
Adanced/system agent
VT-d disable
above 4g doesnt matter
Graphics configuration/ primary Display PCIE
PCH storage config / SATA mode selection/AHCI

image.png.37a14b79309dcf1f85e01c74a71960b2.png

 

an block out these ssdt
image.thumb.png.26ef19afed4371f16fdb3a8623f9400f.png

 

Bios is updated and I tried slimming down the ACPI patches as well. So strange.

 

I feel like there's one more step to the installation that isn't launching. 

9 minutes ago, NorthAmTrans said:

Bios is updated and I tried slimming down the ACPI patches as well. So strange.

 

I feel like there's one more step to the installation that isn't launching. 

you should have a running system before attempting to use opencore an must be functioning first on an established machine

1 minute ago, errorexists said:

you should have a running system before attempting to use opencore an must be functioning first on an established machine

 

Sorry I don't think I gave you enough info here. My apologies.

 

This is was a fully functioning Mojave 10.14.6 machine with OC 0.5.4. I started at 0.5.0 and have been following along with each update. 

 

I've been waiting on a piece of software to become compatible with Catalina to update and it finally did yesterday. Yay!

 

So in short I've got an established system and working EFI, I'm just for some reason getting caught up here. Also, I receive the same error with Clover.

 

@Pavo, have you come across this? If you don't have time for this then just ignore the tag.

On 12/19/2019 at 4:19 PM, Erroruser said:

no one will be able to help you if you do not set your signature to know what your specs are

Not sure why was it not visible. So here is the issue. When booted normally and I grep the CPU info everything appears correctly.

When I boot through OC the CPU frequency is improperly set in about this mac and grepped.:
 

g5@G5s-Mac-Pro ~ % sysctl -a | grep cpu
hw.ncpu: 24
hw.activecpu: 24
hw.physicalcpu: 12
hw.physicalcpu_max: 12
hw.logicalcpu: 24
hw.logicalcpu_max: 24
hw.cputype: 7
hw.cpusubtype: 4
hw.cpu64bit_capable: 1
hw.cpufamily: 1463508716
hw.cpufrequency: 3500000000
hw.cpufrequency_min: 3500000000
hw.cpufrequency_max: 3500000000
hw.cputhreadtype: 1
machdep.cpu.max_basic: 11
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Xeon(R) CPU           X5690  @ 3.47GHz
machdep.cpu.family: 6
machdep.cpu.model: 44
machdep.cpu.extmodel: 2
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 2
machdep.cpu.feature_bits: 188838921972218879
machdep.cpu.extfeature_bits: 5034215680
machdep.cpu.signature: 132802
machdep.cpu.brand: 0
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES PCID
machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF RDTSCP TSCI
machdep.cpu.logical_per_package: 32
machdep.cpu.cores_per_package: 16
machdep.cpu.microcode_version: 0
machdep.cpu.processor_flag: 0
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.sub_Cstates: 4384
machdep.cpu.thermal.sensor: 1
machdep.cpu.thermal.dynamic_acceleration: 1
machdep.cpu.thermal.invariant_APIC_timer: 1
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.thermal.core_power_limits: 0
machdep.cpu.thermal.fine_grain_clock_mod: 0
machdep.cpu.thermal.package_thermal_intr: 0
machdep.cpu.thermal.hardware_feedback: 0
machdep.cpu.thermal.energy_policy: 0
machdep.cpu.arch_perf.version: 3
machdep.cpu.arch_perf.number: 4
machdep.cpu.arch_perf.width: 48
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.events: 4
machdep.cpu.arch_perf.fixed_number: 3
machdep.cpu.arch_perf.fixed_width: 48
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 8
machdep.cpu.cache.size: 256
machdep.cpu.tlb.inst.small: 64
machdep.cpu.tlb.inst.large: 7
machdep.cpu.tlb.data.small: 64
machdep.cpu.tlb.data.large: 32
machdep.cpu.tlb.shared: 512
machdep.cpu.address_bits.physical: 40
machdep.cpu.address_bits.virtual: 48
machdep.cpu.core_count: 6
machdep.cpu.thread_count: 12
machdep.cpu.tsc_ccc.numerator: 0
machdep.cpu.tsc_ccc.denominator: 0
machdep.xcpm.cpu_thermal_level: 0

As you can see the CPU frequency is

 hw.cpufrequency: 3500000000
hw.cpufrequency_min: 3500000000

Yet it is read properly from OCCPU at boot:

00:000 00:000 OC: OpenCore is now loading (Vault: 0/0, Sign 0/0)...
00:060 00:060 OC: Boot timestamp - 2019.12.19 20:42:34
00:129 00:069 OCCPU: Hypervisor: 0
00:188 00:058 OCCPU: Found Intel(R) Xeon(R) CPU           X5690  @ 3.47GHz
00:251 00:062 OCCPU: Signature 206C2 Stepping 2 Model 2C Family 6 Type 0 ExtModel 2 ExtFamily 0
00:310 00:059 OCCPU: Detected Apple Processor Type: 05 -> 0501
00:368 00:058 OCCPU: Ratio Min 12 Max 26 Current 0 Turbo 28 28 27 27
00:428 00:059 OCCPU: Timer address is 408 from LPC
00:587 00:159 OCCPU: CPUFrequencyFromTSC  3457998909Hz  3457MHz
00:645 00:057 OCCPU: CPUFrequency  3457998909Hz  3457MHz
00:704 00:059 OCCPU: FSBFrequency   132999958Hz   132MHz
00:763 00:058 OCCPU: Pkg 1 Cores 6 Threads 12

Also the microcode version is 0 instead of 31.

4 hours ago, NorthAmTrans said:

 

Sorry I don't think I gave you enough info here. My apologies.

 

This is was a fully functioning Mojave 10.14.6 machine with OC 0.5.4. I started at 0.5.0 and have been following along with each update. 

 

I've been waiting on a piece of software to become compatible with Catalina to update and it finally did yesterday. Yay!

 

So in short I've got an established system and working EFI, I'm just for some reason getting caught up here. Also, I receive the same error with Clover.

 

@Pavo, have you come across this? If you don't have time for this then just ignore the tag.

Update: I disabled SATA in my bios and everything is fine. Likely due to my rename of SAT0 to SATA.

 

@Erroruser when you sent me back an adjusted config, why did you enable Legacy Schema?

My windows partition stopped booting after using opencore. I narrowed this down to and UEFI variable called MonotonicCounter-8be4df61-93ca-11d2-aa0d-00e098032b8c that is being created by simply using booting opencore. To fix windows I have to remove this variable from linux (cd /sys/firmware/efivars && chattr -i Mono.. && rm -f Mono...)

 

Why does opencore do this? What is this used for and where is the code that is creating this actually located?

 

Kind regars

 

Mustafa

 

  • Like 1
×
×
  • Create New...