Nvram error getting variable

Nvram error getting variable

• Установка возможна только на ноутбук с процессорами intel core i3/i5/i7
• Убедитесь что у вас графика Intel HD 3000 потому как процессор не поддерживающий данную технологию не запустит систему
• Видеокарта Nvidia работать не будет.
• Картридер не работает (купил не дорогой картридер Firtech FCR-22)
• WiFi адаптер встроенный не работает, нужно менять на BCM43225HM , Atheros AR9285 или из таблицы (Перед заменой модуля обязательно прошить BIOS с отключеной проверкой WiFI из под Windows)

• Для Sierra/High Sierra/Mojave/Catalina в терминал вводим команду: sudo spctl —master-disable
• Для El Capitan нужно поставить галочку напротив пункта «Любые источники» в настройках безопасности.

Сообщение отредактировал WinSSLioN — 21.01.22, 10:57

Важно!

• Установка возможна только на ноутбук с процессорами intel core i3/i5/i7
• Убедитесь что у вас графика Intel HD 3000 потому как процессор не поддерживающий данную технологию не запустит систему
• Видеокарта Nvidia работать не будет.
• Картридер не работает (купил не дорогой картридер Firtech FCR-22)
• WiFi адаптер встроенный не работает, нужно менять на BCM43225HM , Atheros AR9285 или из таблицы (Перед заменой модуля обязательно прошить BIOS с отключеной проверкой WiFI из под Windows)

Для установки нужно:

Источник

Setting a NVRAM variable in normal boot not permitted but allowed in recovery mode

If memory serves me right then in Yosemite it was possible to set the NVRAM variable agc with nvram boot-args even in normal full boot mode.

This seems to have changed in later versions of the OS.

In Sierra this results in an error message:

If I issue this command in recovery mode it is still accepted without error in 10.12.6.

In SingleUser is it is likewise rejected.

Was this changed from 10.10 to 10.12? Why? Why doesn’t it work anymore in normal boot mode but still in recovery?

Any insight on the above is appreciated. But the single question I like to have an answer to is: how can I set this NVRAM variable in either normal boot mode or at least in SingleUser boot mode?

2 Answers 2

It would appear that the change from 10.10 to 10.12 is another step toward including all important security aspects within System Integrity Protection (SIP), meaning that you can’t change these things without first explicitly setting privileges. SIP applies to all users on a Mac, including admins and root .

I’ve just confirmed (because I’m reconfiguring a MacBook Pro with Sierra 10.12.6 just now) that:

Setting boot-args=»-v» in recovery mode will retain the setting in a normal boot mode.

Disabling SIP using csrutil disable in recovery mode will allow you to set boot-args in a normal boot session. WARNING: You should not disable SIP unless you really need to — and you should already know how and why!

Again according to @tubedogg, you can also leave SIP enabled, but allow nvram changes from your normal boot session. This might be more appropriate for your needs. In the Terminal in recovery mode type csrutil enable —without nvram and then restart. I haven’t tried this option personally, as it’s not something I need right now.

I also haven’t tried your agc=0 switch. It’s not something I’ve come across, and it wasn’t in a list of boot arguments I consulted, although I did manage to find a reference that appears to resolve a very specific GPU hardware problem. I see no real reason why you should not be able to set boot-args=»-v agc=0″ in the same scenarios I can set boot-args=»-v» .

Источник

Resetting PRAM through Terminal

For some reason, my Mac won’t let me reset my PRAM in the usual way (by holding the relevant keys down when restarting), simply nothing happens when I try it and my Mac just boots up normally every time.

I’m suspecting this may be due to the fact I’m using a PC keyboard after I broke my Apple one a while back.

I read that I can reset my PRAM through Terminal with the following command:

But all I get is this error:

nvram: Error setting variable — ‘boot-args’: (iokit/common) general error

I’m running High Sierra on a late 2009 iMac if that helps

2 Answers 2

. you must use the nvram command to properly set boot-args NVRAM variable. Starting with macOS Sierra, you must be booted to the recovery partition to run this command.

But now you can clear the NVRAM with

Then restart for the reset to take effect.

I also have a PC keyboard that doesn’t seem able to reset the NVRAM on startup, but I think the real problem is that it’s wireless. But this command is easier and more reliable anyway.

Sounds like a SIP restriction rather than a keyboard issue. Read through the linked article to get an idea of what SIP is, and then try this:

• Ensure you have an up-to-date backup, in case of emergency.
• Power off your Map as normal.
• Hold down Cmd-R and press the Power button. Windows keyboard should be Win-R instead. Keep holding the keys down until the Apple logo appears, then release.
• Wait for macOS to boot into the recovery utilities window.
• From the Utilities menu, choose Terminal. Then: csrutil disable , then exit , then reboot into High Sierra as normal.

I’m not sure where you’re getting -p -r as boot args to reset NVRAM, but sudo nvram -c should do the trick on High Sierra, as Tetsujin states here.

When you’re done, reboot into recovery mode once more, open Terminal and then re-enable SIP with csrutil enable , and reboot into High Sierra.

Источник

Setting a NVRAM variable in normal boot not permitted but allowed in recovery mode

If memory serves me right then in Yosemite it was possible to set the NVRAM variable agc with nvram boot-args even in normal full boot mode.

This seems to have changed in later versions of the OS.

In Sierra this results in an error message:

If I issue this command in recovery mode it is still accepted without error in 10.12.6.

In SingleUser is it is likewise rejected.

Was this changed from 10.10 to 10.12? Why? Why doesn’t it work anymore in normal boot mode but still in recovery?

Any insight on the above is appreciated. But the single question I like to have an answer to is: how can I set this NVRAM variable in either normal boot mode or at least in SingleUser boot mode?

2 Answers 2

It would appear that the change from 10.10 to 10.12 is another step toward including all important security aspects within System Integrity Protection (SIP), meaning that you can’t change these things without first explicitly setting privileges. SIP applies to all users on a Mac, including admins and root .

I’ve just confirmed (because I’m reconfiguring a MacBook Pro with Sierra 10.12.6 just now) that:

Setting boot-args=»-v» in recovery mode will retain the setting in a normal boot mode.

Disabling SIP using csrutil disable in recovery mode will allow you to set boot-args in a normal boot session. WARNING: You should not disable SIP unless you really need to — and you should already know how and why!

Again according to @tubedogg, you can also leave SIP enabled, but allow nvram changes from your normal boot session. This might be more appropriate for your needs. In the Terminal in recovery mode type csrutil enable —without nvram and then restart. I haven’t tried this option personally, as it’s not something I need right now.

I also haven’t tried your agc=0 switch. It’s not something I’ve come across, and it wasn’t in a list of boot arguments I consulted, although I did manage to find a reference that appears to resolve a very specific GPU hardware problem. I see no real reason why you should not be able to set boot-args=»-v agc=0″ in the same scenarios I can set boot-args=»-v» .

Источник

Logouthook does not save created variable #459

TestVar exists in nvram:

Running the LogoutHook gives me some errors, are these errors normal?

TestVar exists in /Volumes/EFI/nvram.plist:

When I reboot, the LogoutHook seems to remove the TestVar. Because its not present anymore.

The LogoutHook is present

The text was updated successfully, but these errors were encountered:

The messages mentioned in the log are normal. I don’t know why the variables are not saved for you, however. Worked fine for us last time we tried.

Guess you need to add TestVar to LegacySchema to allow OC to load this key?

@cattyhouse so ur saying is that create a nvram variable won’t work? Unless you add the variable the the schema?

According to the Configuration.pdf, yes, that’s how it works.

it’s working from OC 0.0.4 util the mid of July version. but OC 0.0.5 doesn’t work after reboot.
would you be able to test with Reset or Clear NVRAM for us please? @vit9696

Is DisableVariableWrite property and VariableRuntimeDxe.efi presence relevant to the issue? I.e. did it break with enabling DisableVariableWrite and removing VariableRuntimeDxe.efi ? If so, does it get fixed with DisableVariableWrite setting to NO and installing VariableRuntimeDxe.efi ?

Also, TestVar should still be present in nvram.plist on EFI partition after reboot (this is not what happens for @yooouuri), but it indeed will not be in nvram -p unless listed in config.plist, this is correct.

DisableVariableWrite is set to true, VariableRuntimeDxe.efi is not presence. I’ll report back with DisableVariableWrite set to false and installed VariableRuntimeDxe.efi

Without DisableVariableWrite and VariableRuntimeDxe.efi I need to disable my iGPU because of the Allocated errors.

1/4 reboots boots with VariableRuntimeDxe.efi loaded.
4/4 reboots boots with VariableRuntimeDxe.efi not loaded.

So VariableRuntimeDxe.efi makes it worse for me.

Also weird thing:

When I change my iGPU DVMT pre-Allocated to 64MB, boot hangs at:

Change it back to 32MB and it boots.

You were not asked to provide your experience with this configuration. You were asked a direct question whether emulated NVRAM is back to normal in this case.

In both cases, TestVar is not present in my nvram.plist

We verified and can confirm that the tool works fine on our systems.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

To obtain the current OpenCore version, we can use the following command:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

But sometimes Opencore version (even Opencore itself) cannot be detected and the request for this variable returns an error whose appearance is different depending on the method used for this task.

From Terminal:

nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version': (iokit/common) data was not found

From Hackintool:

OpenCore version x.x.x is available - you have 0.0.0. Would you like to download a newer version?

From OpenCore Configurator (even with working NVRAM):

The bootloader looks like it is not installed or your NVRAM isn't native.

The key that handles the exposure of UEFI variables to the operating system by OpenCore is Misc -> Security -> ExposeSensitiveData
By default, OpenCore does not announce its presence to the operating system. If ExposeSensitiveData is set to zero, this is the normal behaviour.
Note: this is the reason why the EFI partition that contains the current booting OpenCore is not visible in the picker, and instead EFI partitions with other OpenCore installations can be displayed.

ExposeSensitiveData (Number)

From Configuration.pdf file:

Description: Sensitive data exposure bitmask (sum) to operating system.
0x01 — Expose the printable booter path as an UEFI variable.
0x02 — Expose the OpenCore version as an UEFI variable.
0x04 — Expose the OpenCore version in the OpenCore picker menu title.
0x08 — Expose OEM information as a set of UEFI variables.

Values that ExposeSensitiveData can have and what they mean:

• ExposeSensitiveData=0 -> OpenCore related UEFI variables are not exposed to macOS
• ExposeSensitiveData=1 -> Expose booter path as UEFI variable
• ExposeSensitiveData=3 -> Expose booter path and OpenCore version as UEFI variables
• ExposeSensitiveData=6 -> Expose OpenCore version as UEFI variable and OpenCore version in the picker
• ExposeSensitiveData=7 -> Expose booter path and OpenCore version as UEFI variables and OpenCore version in the picker
• ExposeSensitiveData=15 -> Expose booter path and OpenCore version as UEFI variables, OpenCore version in the picker and OEM information as a set of UEFI variables.

Native NVRAM

In the current version of OpenCore (assuming we have native NVRAM that works fine) the OpenCore not detected (or the OpenCore version not detected) error is usually related to ExposeSensitiveData=0.
With values 3, 6, 7 or 15 in ExposeSensitiveData this error should not happen.

Emulated NVRAM

For emulated NVRAM to work, in addition to the value assigned to ExposeSensitiveData you have to act on 3 keys from Misc -> Security:

• LegacyEnable (Boolean)
  Description: Allows for NVRAM to be stored on nvram.plist for systems without working NVRAM. Enables loading a file named nvram.plist (with NVRAM variables) from the EFI volume root.
• LegacyOverwrite (Boolean)
  Description: Permits overwriting firmware variables in the nvram.plist file.
  Note: Only variables accessible from the operating system will be overwritten.
• LegacySchema (Dictionary)
  Description: Allows assigning nvram variables on systems without working NVRAM. These variables are written to the NVRAM.plist file.

You also have to check a key in PlatformInfo:

• WriteFlash (Boolean)Description: Enables writing to flash memory for all added variables. When WriteFlash=False, the variable is written to RAM, not CMOS, and not preserved across the reboots. This is the difference between volatile and non-volatile variables.

Questions

1. If we have Native NVRAM working, we shouldn’t use any values for Emulated NVRAM, right?

Yes, if we have native NVRAM then we must forget the settings of emulated NVRAM.

2. If I want, can I remove these entries at the LegacySchema and its content? 7C436110-AB2A-4BBB-A880-FE41995C9F82 and 8BE4DF61-93CA-11D2-AA0D-00E098032B8C.
 

It is clear that LegacySchema is a set of NVRAM variables and that OpenCore compares these to the variables present in nvram.plist so in theory it would not be necessary when we have native NVRAM.
But in the OpenCore documentation I have not found anything that says that we can delete LegacySchema when there is native NVRAM.
If we have LegacyEnable=False and LegacyOverwrite=False it seems logical to think that LegacySchema is not used by OpenCore. And this is true, at least on my system, which has native NVRAM and boots perfectly without those 2 LegacySchema entries.

Summary: we can delete the 2 LegacySchema entries if we have native NVRAM.

What is always recommended is to have WriteFlash=True.

Note: ResetNVRAM must be done at first boot each time OpenCore is updated to a different version.

Edited June 12, 2021 by miliuco

Hi everyone,

So a couple of weeks ago I decided to build my first pc, and thought if I’m gonna do it, I might just as well try to make it a Hackintosh. Specs are as follows:

I thought why not, let’s give the OpenCore Vanilla Desktop Guide from the sidebar a shot. And to my surprise (I mean, after reading up on it, I thought it would be a huge pain) it worked on the first attempt. Catalina installed, and the system is running as stable as my MacBook Pro from 2013.

However, there are two things that don’t work, and while they don’t bother me that much, maybe some of you guys could help me out:

1. NVRAM. I tried the method from the vanilla oc guide, and there are two issues: nvram -c gives me the following error: nvram: Error clearing firmware variables: (iokit/common) not permitted. As far as I can tell, the issue here is that SIP is enabled, and nvram can also be cleared from the boot menu, so I did that. Still, after placing logoutHook in my user directory and running sudo defaults write com.apple.loginwindow LogoutHook /Users/(your username)/LogoutHook/LogoutHook.command, when I do nvram -p | grep -i myvar it just returns an empty line. I even added myvar to the LegacySchema strings, but it still doesn’t work. When I run LogoutHook.command, i get nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path': (iokit/common) data was not found Fatal error: /Users/(username)/LogoutHook/nvram.mojave does NOT exist! Any ideas?

2. Sidecar. It allows me to pick my iPad from the menu, the display (on the pc) then changes scaling, my iPad shows «connecting…» for a bit and then just shows a black screen (but is on). Could there be an issue with the iGPU? I’m currently running my monitor off the dGPU. When I try changing the iGPU setting in my BIOS (F10) from «auto» to «on», the pc doesn’t boot anymore. I’m using iMac19,1 as a smbios — maybe changing that to something else would help?

Anyway, my config.plist can be found here: link

I would be super grateful if anyone could point me in the right direction or tell me what I did wrong (I mean, I always found it a bit suspicious that the whole install worked the first time around). And btw, this is an amazing community — without you guys I would’ve never been able to get this far.

EDIT: So I finally got sidecar working. Originally, I wasn’t able to set my iGPU to «Enabled» in my bios, I would get the «couldn’t allocate…» error as if I hadn’t set my slide value. So I tried setting my smbios to iMacPro1,1. Which made Netflix work, but not sidecar. But what worked, was the followng:

1. Reset the smbios to iMac19,1

2. Turn off the pc, unplug the PSU

3. Take out the CMOS-Battery, wait for a minute

4. Reload Previous BIOS settings from profile

5. Enable the iGPU in the BIOS (Auto->Enabled)

6. Reboot.

7. Voilà, enjoy working sidecar!

(Sidenote: I’m getting error code s7363-1260-ffffd1c1 when trying to watch Netflix, but I’m not using that anyways.) This can be solved by adding the shikigva=80 boot argument, as explained below. If you have issues with Beats 1 radio, this also solves the problem.