Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,888 posts in this topic

Recommended Posts

NorthAmTrans
NorthAmTrans
Posted
Posted
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. 

Link to comment
Share on other sites
Erroruser
Erroruser
Posted
Posted
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

Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
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.

Link to comment
Share on other sites
startergo
startergo
Posted
Posted
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.

Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
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?

Link to comment
Share on other sites
MustafaK1
MustafaK1
Posted
Posted

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
Link to comment
Share on other sites
MustafaK1
MustafaK1
Posted
Posted
35 minutes ago, vit9696 said:

Hi, that's not us, but perhaps your BIOS firmware. We do not create anything alike, and code search gives no findings in our repositories aside EDK II copy, which part we do not use (https://github.com/search?q=org%3Aacidanthera+MonotonicCounter&type=Code). 

 

No, I don't think that it is intentional. But then again I never see this problem before using clvoer grub2 etc. I checked the code before I posted and I didn't see anything. Only in Datahub.c was mention of monotonic. But then again edk2 does some strange things, so I will check there.

  • Like 1
Link to comment
Share on other sites
valinor61
valinor61
Posted
Posted (edited)

Hi, I have weird issue since catalina. My bios suddenly becomes a black screen I cant enter my bios settigs. The problem is in both opencore and clover. In clover every boot was causing black screen. I succesfully managed to switch opencore and its nvram reset option fixed that black screen issue but after few reboots I'm getting black screen error again when error occurs my bios also removes opencore from boot selection part. Only way to access it again reflashing my nvram with a bios tool. 

I have never experianced that kind of issue before on mojave. 

Device: Asus FX553VD/GL553VD i-7700hq. 

Here is my opencore files.

OpenCoreGL553VD.zip

Edited by valinor61
Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted

Has anyone had trouble with SATA since moving to Catalina? I get an immediate panic and restart at the progress bar.

 

I can boot with ACHI enabled in bios. However, I as soon as I enable any one of the 6 ports (with or without a drive connected) I get the panic/reboot.

 

Note: the SATA Rename SSDT has no effect here. Please excuse if this has been addressed.

 

 

EFI.zip

Link to comment
Share on other sites
Guest
Guest
Posted
Posted

Hi @vit9696

Hi @Download-Fritz

I know it is a low priority for your OpenCore's bootloader project but I would like to ask you

AMD TRX40 user of new threadripper3 have the same initial problem (memmap error or an instant reboot if DevirtualizeMMIO is used) after ++++++++endseed stage

this happens with different motherboard and different bios settings and also using all Aptio memory EFI driver available 

 

Do you think this problem could be superated with a new aptiomemory efi driver? Or it is unrelated in your experience?

 

Thank you in advance

 

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

We have no technical information on the matter and we neither have the hardware, nor time or ambition to investigate. If someone researches and describes the issue technically(!) (what causes the bug, not "it reboots when blah blah"), we will merge the fix.

Please do not tag for no reason.

Link to comment
Share on other sites
Guest
Guest
Posted
Posted

Ok sorry for bothering you with my tag

But i see people open issue on openCore GitHub and i think people do not know "what causes the bug" otherwise we could be more useful to debug

thank you for your time

 

Link to comment
Share on other sites
tyufhl
tyufhl
Posted
Posted
32 minutes ago, DanielMac said:

 

Thank you for that information, but I don't understand the implications of disabling HPET. Do I need HPET for something? Why does it take up 4 IRQs?

 

if the processor supports XCPM (Xnu CPU Power Management), HPET is not needed.

Link to comment
Share on other sites
Guest
Guest
Posted
Posted
5 minutes ago, hardcorehenry said:

@fabiosun try DevirtualiseMmio+MmioWhitelist

thank you but all things found on public forums  have been tested with the same result from different users with different motherboard

could you help for a serious debugging?

 

Link to comment
Share on other sites
hardcorehenry
hardcorehenry
Posted
Posted (edited)

What I meant, I wasn’t able to boot with DevirtualiseMmio quirk alone(KP), MmioWhitelist also had to be enabled. I don’t need that quirk, just wanted try it, out of curiosity. Addresses can be extracted from DarwinDumper(Memory), if you are able to boot with clover.  But no sadly I can’t provide help for serious debugging.

 

MMio.png.269a7615067ae240675f506ad9c01939.png

Edited by hardcorehenry
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
29 minutes ago, hardcorehenry said:

What I meant, I wasn’t able to boot with DevirtualiseMmio quirk alone(restart), MmioWhitelist also had to be enabled. I don’t need that quirk, just wanted try it, out of curiosity. Addresses can be extracted from DarwinDumper(Memory), if you are able to boot with clover.  But no sadly I can’t provide help for serious debugging.

 

MMio.png.269a7615067ae240675f506ad9c01939.png

 

Addresses undertake from OpenCore log.

  • Like 1
Link to comment
Share on other sites
Guest
Guest
Posted
Posted
1 minute ago, Andrey1970 said:

At first to add all addresses, but then to delete not necessary addresses. What addresses to leave, it is necessary to define experimentally.

Could you define better this?

Then,  how to debug seriously this new AMD cpu/bios  problem?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...