Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

iGPU
iGPU
Posted
Posted (edited)
23 hours ago, justin said:

LogoutHook has nothing to do with Emulated NVRAM, if you look inside into the code, the only thing this command does is to save your custom nvram items to nvram.plist, so opencore can restore your custom nvram items next boot.

 

For Emulated NVRAM, you need VariableRuntimeDxe.efi compiled from audk. Please search this thread for how to do that (my post)

 

Q1. So is it then best to use both LogoutHook and VariableRuntimeDxe.efi simultaneously?

 

I've got LogoutHook working with OC 0.0.4 on a Z390 GB Designare mobo on Mojave 10.14.6. The nvram.plist file is properly created in the EFI drive root directory.

 

Q2. Does the nvram.mojave file need to remain in the EFI drive root directory once nvram.plist is created?

Edited by iGPU
maddie
maddie
Posted
Posted
12 hours ago, iGPU said:

 

Q1. So is it then best to use both LogoutHook and VariableRuntimeDxe.efi simultaneously?

 

I've got LogoutHook working with OC 0.0.4 on a Z390 GB Designare mobo on Mojave 10.14.6. The nvram.plist file is properly created in the EFI drive root directory.

 

Q2. Does the nvram.mojave file need to remain in the EFI drive root directory once nvram.plist is created?

 

For Q1, if I understand correctly, for NVRAM to work correctly on Z390 platforms, both VariableRuntimeDxe.efi and LogoutHook script is needed. The LogoutHook saves the current NVRAM key value pairs into a plist file, and when boot up VariableRuntimeDxe loads this plist back to the NVRAM.

Slice
Slice
Posted
Posted

Not exactly.

VariableRuntimeDxe creates a protocol working with variables but in RAM instead of NVRAM. Loaded system can use them but after shutdown all variables will be lost. For this purpose LogoutHook will save some part of the variables set into the file nvram.plist. It is not full list but mostly all needed.

At computer start one must read the file to fill new RAM with this variables. It is Clover or OpenCore itself, not efi driver.

  • Like 3
yooouuridafdssdfs
yooouuridafdssdfs
Posted
Posted

GigaByte Z390 UD over here.

 

The Logouthook does not create a nvram.plist on my EFI drive.

 

I enabled the hook: 

$ sudo defaults read com.apple.loginwindow LogoutHook
/Users/yooouuri/Documents/LogoutHook.command

 

When I run the hook from the console, I'm getting a lot of errors: 

$ ./LogoutHook.command
nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080': (iokit/common) data was not found
File Doesn't Exist, Will Create: ./nvram.plist
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:BootCurrent': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:BootNext': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0081': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0082': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0083': (iokit/common) data was not found
nvram.mojave: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path': (iokit/common) data was not found
Fatal error: Illegal UUID or unknown loader!

 

But it created a folder with a nvram.plist.

 

Loaded drivers: VariableRuntimeDxe, AptioMemoryFix. Enabled LegacyEnable in my config.plist

 

How can I make the Logouthook working properly?

justin
justin
Posted
Posted
2 hours ago, yooouuridafdssdfs said:

GigaByte Z390 UD over here.

 

The Logouthook does not create a nvram.plist on my EFI drive.

 

I enabled the hook: 


$ sudo defaults read com.apple.loginwindow LogoutHook
/Users/yooouuri/Documents/LogoutHook.command

 

When I run the hook from the console, I'm getting a lot of errors: 


$ ./LogoutHook.command
nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080': (iokit/common) data was not found
File Doesn't Exist, Will Create: ./nvram.plist
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:BootCurrent': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:BootNext': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0081': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0082': (iokit/common) data was not found
nvram.mojave: Error getting variable - '8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0083': (iokit/common) data was not found
nvram.mojave: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path': (iokit/common) data was not found
Fatal error: Illegal UUID or unknown loader!

 

But it created a folder with a nvram.plist.

 

Loaded drivers: VariableRuntimeDxe, AptioMemoryFix. Enabled LegacyEnable in my config.plist

 

How can I make the Logouthook working properly?

 

 

Read configuration.pdf, keywords:

 

ExposeSensitiveData

boot-path

3. LegacyEnable

justin
justin
Posted
Posted
On 7/30/2019 at 11:09 AM, Slice said:

The issue closed as not a bug.

 

I have no idea what Vit9696 thinks, priority:low? Lol

On 7/31/2019 at 4:06 AM, iGPU said:

 

Q1. So is it then best to use both LogoutHook and VariableRuntimeDxe.efi simultaneously?

 

I've got LogoutHook working with OC 0.0.4 on a Z390 GB Designare mobo on Mojave 10.14.6. The nvram.plist file is properly created in the EFI drive root directory.

 

Q2. Does the nvram.mojave file need to remain in the EFI drive root directory once nvram.plist is created?

 

 

Q1 was answered by Slice

 

Q2 nvram.mojave was meant for the /usr/sbin/nvram which does not support -x args, e.g. on older macOS. If you are running Mojave already, this file is most likely not needed. 

  • Like 1
yooouuridafdssdfs
yooouuridafdssdfs
Posted
Posted
1 hour ago, justin said:

 

 

Read configuration.pdf, keywords:

 

ExposeSensitiveData

boot-path

3. LegacyEnable

 

Thanks for your help!

 

Now I got 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path :thumbsup_anim:, but Boot0080 BootNext etc data not found when I run the Logouthook...

 

How can I get those variables?

 

The LogoutHook created a nvram.plist on my EFI partition, so I'm getting there

justin
justin
Posted
Posted
42 minutes ago, yooouuridafdssdfs said:

 

Thanks for your help!

 

Now I got 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path :thumbsup_anim:, but Boot0080 BootNext etc data not found when I run the Logouthook...

 

How can I get those variables?

 

The LogoutHook created a nvram.plist on my EFI partition, so I'm getting there

 

If you don't have BootXXXX then you don't bother. They are on the way to ship, current nvram.plist is enough to make things work. 

Pavo
Pavo
Posted
Posted
1 hour ago, yooouuridafdssdfs said:

 

Thanks for your help!

 

Now I got 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path :thumbsup_anim:, but Boot0080 BootNext etc data not found when I run the Logouthook...

 

How can I get those variables?

 

The LogoutHook created a nvram.plist on my EFI partition, so I'm getting there

use Startup Disk an assign macOS as your startup disk in System Preferences before running LogoutHook to generate the nvram.plist.

tmbt
tmbt
Posted
Posted (edited)

Hi guys,

i'm trying to find where OpenCore create a log file but i can't. According to documentation it shoud be in the EFI root but i don't have it so i'm thinking that i've disabled it in the OpenCore config file. Which are the variables i should check to be sure OpenCore is writing a log ?

When i switch on the laptop before OpenCore boot menu appears i can see two lines but can't read them because they disappear too fast and that's why i want to enable logs.


Could someone help me ?

 

Thanks

Mattia

 

Edited by tmbt
maddie
maddie
Posted
Posted

Has anyone installed the 10.14.6 Supplemental Update? Link: http://osxdaily.com/2019/08/01/supplemental-update-for-macos-mojave-10-14-6-released/

 

I have tried to update it but when it gets into the installer, just a few seconds in, the computer just reboots, so I can't get the update installed and stuck with the installer on OpenCore's boot menu.

 

I had to switch back to a Clover backup that I had on a USB to finish the update. After that, I can boot into macOS with OpenCore again.

 

Did anyone have the same problem?

vandroiy2012
vandroiy2012
Posted
Posted
2 minutes ago, maddie said:

Has anyone installed the 10.14.6 Supplemental Update? Link: http://osxdaily.com/2019/08/01/supplemental-update-for-macos-mojave-10-14-6-released/

 

I have tried to update it but when it gets into the installer, just a few seconds in, the computer just reboots, so I can't get the update installed and stuck with the installer on OpenCore's boot menu.

 

I had to switch back to a Clover backup that I had on a USB to finish the update. After that, I can boot into macOS with OpenCore again.

 

Did anyone have the same problem?

 

Everything is fine with both rigs in signature. Updated with OpenCore without any problems. 

maddie
maddie
Posted
Posted
 
 
 
1
8 minutes ago, vandroiy2012 said:

 

Everything is fine with both rigs in signature. Updated with OpenCore without any problems. 

Hmm, then it must be the problem with this rig I have, which is an Asrock Deskmini 310 with i7-8700. It always had some problem somehow, and it works okay enough to not have me look into it.

 

I'll test on my other two rigs and report back. Thanks!

Andrey1970
Andrey1970
Posted
Posted
9 hours ago, zisqo said:

does support boot-chime sound with BootChimeDxe.efi?

 

or only support Clover yet?

Do not use the modified forks of drivers from Clover.

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

justin
justin
Posted
Posted
2 hours ago, tmbt said:

Hi guys,

i'm trying to find where OpenCore create a log file but i can't. According to documentation it shoud be in the EFI root but i don't have it so i'm thinking that i've disabled it in the OpenCore config file. Which are the variables i should check to be sure OpenCore is writing a log ?

When i switch on the laptop before OpenCore boot menu appears i can see two lines but can't read them because they disappear too fast and that's why i want to enable logs.


Could someone help me ?

 

Thanks

Mattia

 

 

see here

hardcorehenry
hardcorehenry
Posted
Posted (edited)

I'm on desktop Haswell system and it seems I have embedded controller of PNP0C09 type.

 

Embeded.png.4a0d9d46c8c48825bcf61ab16ef02d46.png

 

Did I understood well, and my SSDT-EC.aml should look like this?

 

GOT_EC.png.b133e08f2dd9985f3bd8f763612bcc2d.png

 

or just use one of this methods and then add power to my USB legacy kext ? Please some hints.

Edited by hardcorehenry
justin
justin
Posted
Posted
1 hour ago, hardcorehenry said:

I'm on desktop Haswell system and it seems I have embedded controller of PNP0C09 type.

 

Embeded.png.4a0d9d46c8c48825bcf61ab16ef02d46.png

 

Did I understood well, and my SSDT-EC.aml should look like this?

 

GOT_EC.png.b133e08f2dd9985f3bd8f763612bcc2d.png

 

or just use one of this methods and then add power to my USB legacy kext ? Please some hints.

 

Your H_EC PNP0C09 Return (Zero), it was not enabled (and don't try to enable it), you need Fake EC, so just use Device (EC), comment out everything else. 

  • Thanks 1
obus
obus
Posted
Posted (edited)

Hi all!

 

Trying to apply this kextpatch to my config.plist but can't get it to work.

 

<dict>

<key>Comment</key>

<string>ATIController TestVRAM boot failure patch</string>

<key>Disabled</key>

<false/>

<key>Find</key>

<data>

uapVqlU7DJA=

</data>

<key>InfoPlistPatch</key>

<false/>

<key>Name</key>

<string>AMDSupport</string>

<key>Replace</key>

<data>

uapVqlU5yZA=

</data>

    </dict>

    <dict>

<key>Comment</key>

<string>ATIController TestVRAM magenta-colored lines patch</string>

<key>Disabled</key>

<false/>

<key>Find</key>

<data>

xwSxqlWqVQ==

</data>

<key>InfoPlistPatch</key>

<false/>

<key>Name</key>

<string>AMDSupport</string>

<key>Replace</key>

<data>

kJCQkJCQkA==

</data>

    </dict>

 

 

This way is not working.420470052_Screenshot2019-08-02at23_14_31.thumb.png.9c345fc12e123b87e5da411a390b2b8b.png

 

Any help appreciated.

Edited by obus
obus
obus
Posted
Posted
4 minutes ago, justin said:

TableSignature key is missing

 

Sorry @justin Could you please elaborate little further?

I don't understand this:

  1. TableSignatureType:

    textttplist data, 4 bytes
    Failsafe: All zero
    Description: Match table signature to be equal to this value unless all zero.

 

2 minutes 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. 

Sorry but I can't use WEG. As soon as I use WEG I just boot to a black screen.

obus
obus
Posted
Posted (edited)

@vandroiy2012

 

please read my message in this thread:

https://www.insanelymac.com/forum/topic/325987-whatevergreen-support-topic/?page=43

 

"Hi all.

I have a Xeon W 2175 processor without internal IGPU running OpenCore latest compile 0.0.4. and everything is working flawlessy. 

For Graphics I use a Sapphire water-cooled RX Vega 64 reference card. I just use Lilu and AppleALC-kext. My problem is that as soon as I use WEG I have the Apple logo and then black screen after progress bar.

Yesterday I've red here: https://www.insanelymac.com/forum/topic/337637-amd-radeon-vii-in-macos-mojave/?page=9 that the pink artefacts when booting in to Mojave 10.14.6 are fixed with new version of Lilu and WEG.

Today I compiled my own Lilu and WEG (embedded) and tested. Could confirm that the artefacts is gone but I am still booting to black screen with injected WEG."

Edited by obus
 Share
Go to topic listing
×
×
  • Create New...