OpenCore General Discussion

[zisqo]

17 hours ago, Andrey1970 said:

Do not use the modified forks of drivers from Clover.

Use the original from the author: https://github.com/Goldfish64/AudioPkg

 

i was downloaded from https://github.com/Goldfish64/AudioPkg but doesn't working.

 

• Asus X299 TUF Mk1
• i7-7800X
• AMD Radeon VII
   
• OC 0.0.4 (08032019_014528.zip)

Edited August 3, 2019 by zisqo

[obus]

11 hours ago, vandroiy2012 said:

This patches are already implemented in WhateverGreen.kext as symbolic patch. No need to use them in bootloader. Just build latest WEG from master. 

Problems solved with agdpmod = pikera and newly compiled Lilu and WEG.

[Andrey1970]

8 hours ago, zisqo said:

 

i was downloaded from https://github.com/Goldfish64/AudioPkg but doesn't working.

 

• Asus X299 TUF Mk1
• i7-7800X
• AMD Radeon VII
   
• OC 0.0.4 (08032019_014528.zip)

 

 

You have to understand that it is an offtopic.

[rusty-bits]

Having trouble booting, getting stuck on SmcReadValueKey right after End RandomSeed

 

Here is my latest log file opencore-2019-08-03-141553.txt with Serial# hidden

 

Here is my current config.plist with serial# hidden

 

my EFI folder

and what I see when I try to boot

 

 

I'm hoping I have made a simple error and someone can point it out

I also notice a reference to CLOVER in the log file, this doesn't seem right.

maybe there is a NVRAM variable I have to delete? I don't know.

 

I built the latest debug version of OpenCore and all kexts right before this latest attempt.

I hope someone can point me in the right direction.

  Thank you.

Edited August 3, 2019 by rusty-bits
wrong link for log file

[Erroruser]

out of curiosity is there a way to stop from making a new file for every boot without turning the log off an just reuse 1 txt?

[justin]

20 hours ago, errorexists said:

out of curiosity is there a way to stop from making a new file for every boot without turning the log off an just reuse 1 txt? 

 

since you have nvram.plist showed on your ESP partition, that means you're using LogoutHook.command, so just add

 

rm -f /Volumes/EFI/opencore-*.txt

 

(you have to look at the code to find out what's best way to add this command, this is just an example/idea)

 

to the end of LogoutHook.command?

Edited August 4, 2019 by justin

[MacPato]

51 minutes ago, justin said:

 

since you have nvram.plist showed on your ESP partition, that means you're using LogoutHook.command, so just add

 

rm -f /Volumes/EFI/opencore-*.txt

 

(you have to look at the code to find out what's best way to add this command, this is just an example/idea)

 

to the end of LogoutHook.command?

The logs have nothing to do with the nvram.plist file, I have native NVRAM and mine generates a new log every boot with Target set to xx

if we move the Target level then if we get a problem it won't generate a log, why couldn't the logging just be left the way it was as an overwritable *.log file.

Edited August 4, 2019 by MacFriedIntel

[Erroruser]

51 minutes ago, justin said:

 

since you have nvram.plist showed on your ESP partition, that means you're using LogoutHook.command, so just add

 

rm -f /EFI/opencore-*.txt

 

to the end of LogoutHook.command?

what are your talking about this has nothing to do with nvram.plist as its for the logging

[justin]

10 minutes ago, errorexists said:

what are your talking about this has nothing to do with nvram.plist as its for the logging

 

You were looking for a method to get only one txt log file, i gave you a method. Please take a look at how LogoutHook.command works. Basically, you can add a script to somewhere so macOS can run your script on shutdown/reboot:

 

sudo defaults write com.apple.loginwindow LogoutHook  /path/to/your/script

 

and in your script, you can include "rm -f /Volumes/EFI/opencore-*.txt", well you have to mount ESP first in your script, before this command.

 

this means every time you shutdown/reboot. logs will be deleted, and then opencore will generate a new log on boot.

 

now do you get me? 

Edited August 4, 2019 by justin

[MacPato]

 

 

 

 

 

8

 Advanced issues found

▲

 

4

9 minutes ago, justin said:

 

You were looking for a method to get only one txt log file, i gave you a method. Please take a look at how LogoutHook.command works. Basically, you can add a script to somewhere so macOS can run your script on shutdown/reboot:

 

sudo defaults write com.apple.loginwindow LogoutHook  /path/to/your/script

 

and in your script, you can include "rm -f /Volumes/EFI/opencore-*.txt", well you have to mount ESP first in your script, before this command.

 

this means every time you shutdown/reboot. logs will be deleted, and then opencore will generate a new log on boot.

 

now do you get me? 

I get it, but seems a lot of effort just to remove something that shouldn't fill up the ESP like that.

[justin]

20 minutes ago, MacFriedIntel said:

if we move the Target level then if we get a problem it won't generate a log, why couldn't the logging just be left the way it was as an overwritable *.log file.

 

Any system (macOS, Linux, Windows) would have multiple logs in case you wanted to trace, i don't see that's a problem, for example, run this command on your macOS: "ls /var/log/", what do you see. 

[MacPato]

4 minutes ago, justin said:

 

Any system (macOS, Linux, Windows) would have multiple logs in case you wanted to trace, i don't see that's a problem, for example, run this command on your macOS: "ls /var/log/", what do you see. 

Multiple logs are fine, but in macos, you don't see them all over the root of a partition, tidy them up in a folder that would make better sense to me.

 

and running that command I see a log that overwrites itself.

[justin]

8 minutes ago, MacFriedIntel said:

Multiple logs are fine, but in macos, you don't see them all over the root of a partition, tidy them up in a folder that would make better sense to me.

 

and running that command I see a log that overwrites itself.

 

I see a lot ... 

 

Edited August 4, 2019 by justin

[MacPato]

the point I am making is there should be something set within open core not to generate a log if there is nothing to put into the log, instead of creating empty files

i wasn't talking about macOS logs. there's no point having blank log files. 

[zsirmo]

Hello,

 

I have a problem with OpenCore boot loader. Many many ACPI ERROR

Mainboard: Asus Z97-K

 

I follow Opencore Haswell document.

 

Attached screenshot, and EFI folder.

EFI_opencore.zip

Edited August 4, 2019 by zsirmo

[Pavo]

49 minutes ago, zsirmo said:

Hello,

 

I have a problem with OpenCore boot loader. Many many ACPI ERROR

Mainboard: Asus Z97-K

 

I follow Opencore Haswell document.

 

Attached screenshot, and EFI folder.

EFI_opencore.zip

This is your issue:

As the documentation says, you should not do ACPI table renames in config. You should use SSDTs.

Test this EFI

EFI.zip

Edited August 5, 2019 by Pavo

[zisqo]

On 8/3/2019 at 8:57 PM, Andrey1970 said:

 

 

You have to understand that it is an offtopic.

 

already copy a bootchimedxe.efi to efi/oc/drivers folder but some delay(2-3secs) when i saw a apple logo  and no sound play even plug a spk at internal speaker or lint out port

[darkbluecode]

who one can help me to change clover to open core GL553VD?
link : https://github.com/MohammadtaghiFarkhondekar/macOS-Mojave-For-Asus-ROG-GL553VD

Edited August 5, 2019 by darkbluecode

[maddie]

About the aforementioned supplemental update problem, my Z370 rig updates just fine, but my another Z97 rig also fails, boots into Apple logo with progress bar, hangs at about 1/3 of the progress and reboots. So this makes 2 out of 3 of my hacks fail to install the update (one Asrock Deskmini 310 with i7-8700 and UHD 630, one Z97 rig with i7-4790K and RX580)

 

Just compiled the latest OpenCore and its components from the repository, and updated the configuration according to the latest Configuration.pdf and SampleFull.plist (also comments in OcAppleBootCompatLib.h from OcSupportPkg for the Booter section), then tried again.

 

This time:

 

1. In normal boot (not booting into update installer), OpenCore menu just stays on screen for a while, then suddenly the Apple logo with an almost done progress bar shows up (second stage?) and went into login screen in a second

2. Now I'm able to select both update installer (macOS Installer) and macOS itself (wasn't able to when I was using the older build, only macOS Installer shows up if I selected "Restart to update" in the OS)

3. Selecting "macOS Installer", OpenCore menu also stays on screen for a while, then reboots

 

Attached is my config.plist for my Z97 rig with board info redacted. Am I doing anything wrong?

config.plist

[MacPato]

2 hours ago, maddie said:

About the aforementioned supplemental update problem, my Z370 rig updates just fine, but my another Z97 rig also fails, boots into Apple logo with progress bar, hangs at about 1/3 of the progress and reboots. So this makes 2 out of 3 of my hacks fail to install the update (one Asrock Deskmini 310 with i7-8700 and UHD 630, one Z97 rig with i7-4790K and RX580)

 

Just compiled the latest OpenCore and its components from the repository, and updated the configuration according to the latest Configuration.pdf and SampleFull.plist (also comments in OcAppleBootCompatLib.h from OcSupportPkg for the Booter section), then tried again.

 

This time:

 

1. In normal boot (not booting into update installer), OpenCore menu just stays on screen for a while, then suddenly the Apple logo with an almost done progress bar shows up (second stage?) and went into login screen in a second

2. Now I'm able to select both update installer (macOS Installer) and macOS itself (wasn't able to when I was using the older build, only macOS Installer shows up if I selected "Restart to update" in the OS)

3. Selecting "macOS Installer", OpenCore menu also stays on screen for a while, then reboots

 

Attached is my config.plist for my Z97 rig with board info redacted. Am I doing anything wrong?

config.plist

If you have used the latest compiled version of Opencore, there have been some changes as to how it works, Booter has been added to config with no documentation yet. also, Aptio has been merged into AppleSupport. so it's probably best to stick to release version until the documentation is updated.

[Andres ZeroCross]

Still get smooth booting with latest OpenCore Bootloader and new drivers

[maddie]

1 hour ago, MacFriedIntel said:

If you have used the latest compiled version of Opencore, there have been some changes as to how it works, Booter has been added to config with no documentation yet. also, Aptio has been merged into AppleSupport. so it's probably best to stick to release version until the documentation is updated.

 

Yeah, I'm aware of that, I found some comments regarding the Booter section, so I think it should be fine. Also, I'm aware that Aptio has been merged into AppleSupport. I'm booted into macOS just fine with the HEAD version, it's just the supplemental update that can't run properly.

[maddie]

Here's the log from the updater's reboot. Can't really spot anything though..

opencore-2019-08-06-100737.txt

[Andres ZeroCross]

@Download-Fritz Any clue how to hidden auto discover entry by OC?? I have added these 4 entry. I jus need to hidden entry from 1 -> 6. Entry from 7 -> B are My Custom entry. 

[mhaeuser]

@Andres ZeroCross There is no way to hide detected entries and we do not see any reason to implement such