Jump to content
About Just Joined group Read more... ×
cosmo1t

FileNVRAM 1.1.3 Released

80 posts in this topic

Recommended Posts

xZenue is proud to present

FileNVRAM.dylib

https://public.xzenue.com/downloads/

version 1.1.3

FileNVRAM Release Notes

 

========= Version 1.1.3 =======

* Fixed an potential issue where boot-args could get mangled.

* Fixed an issue where certain legacy variables were saved incorrectly.

* Fixed an issue where certain nvram variables not write to the file immediately.

 

========= Version 1.1.2 =======

* Fixed a regression in 1.1.1 causing sleep to break.

 

========= Version 1.1.1 =======

* Fixed an issue where non-root users could delete variables

* Fixed a potential issue with sleep

* Fixed a potential issue with 10.8.3

* Fixed an issue where boot-args remain after deleted on the command line.

* Update ROM generation to generate a random value.

 

===================

FileNVRAM.dylib

===================

 

FileNVRAM copyright xZeneu LLC.

FileNVRAM is licensed under the Attribution-NonCommercial 3.0 Unported license.

Please see the license file for details

 

 

===================

Bugs

===================

 

Please report any bugs at https://public.xzenue.com/bugzilla/

 

 

===================

Requirements

===================

 

- Chameleon r2181 or newer

 

===================

Usage

===================

 

- Install the FileNVRAM.dylib to /Extra/modules/

- Reboot

 

Use the nvram command to manipulate variables

Share this post


Link to post
Share on other sites
Advertisement

For anyone with a stuck boot-flag, you can do this;

sudo nvram -d boot-args

 

Or, while at the Chameleon GUI press the TAB key. Then remove any undesired boot args or flags from the command line and press enter to boot normally.

Click here for more information.

 

Also see here (thanks nyolc8).

Share this post


Link to post
Share on other sites

Just adding to what Gringo Vermelho said: or just start typing something at the boot menu, then the stored boot flags will appear and you can just delete them with the backspace key, finally typing the ones you want to use (or none at all, but in this case you'll need to do it every boot). I just learned it's fixed. :)

Share this post


Link to post
Share on other sites

With this version, my autogenerated ROM value is became this: "i%1b(%e0%96%00"

This is nothing related to my MAC address, none of the characters are in my MAC address, and what the hell is that "(" in it? :worried_anim:

 

Bug in the auto ROM value generator?

Share this post


Link to post
Share on other sites

With this version, my autogenerated ROM value is became this: "i%1b(%e0%96%00"

This is nothing related to my MAC address, none of the characters are in my MAC address, and what the hell is that "(" in it? :worried_anim:

 

Bug in the auto ROM value generator?

 

The autogenerated rom has never been your mac address. IT's randomnly generated. If this is causing things to not work for you please file a bug @ the link in post #1

Share this post


Link to post
Share on other sites

It's a random number. If it happens to be equivalent to an ascii printable character, it'll print out as that char (such as the '('). If not it'll print out as hex (%NN)

 

The value is the the same either way, it's just how nvram is printing it for human readability.

Share this post


Link to post
Share on other sites

The value is the the same either way, it's just how nvram is printing it for human readability.

 

Hi, meklort!

 

If it's that way for the sake of aesthetics (because it's not readable either way in the end), i really think printing as a hex string is a better choice.

 

Best regards!

Share this post


Link to post
Share on other sites

Hi, meklort!

 

If it's that way for the sake of aesthetics (because it's not readable either way in the end), i really think printing as a hex string is a better choice.

 

Best regards!

 

Tell apple that, they are the ones who wrote the nvram program

Share this post


Link to post
Share on other sites

Sorry, but i am a bit a "noob" for that nvram usage ;)

 

If i use nvram -p command - without that module installed - to show variables i get :

 

GA_EP35:~ andreasm$ nvram -p

SystemAudioVolume 0

fmm-computer-name GA_EP35

 

If i would use / install that nvram module (with chameleon 2181+) what new variables would exist / what would be changed / what things may work better?

Or, if no new nvram variables are automaticly created by the module, which variables maybe usefull to create + use?

Share this post


Link to post
Share on other sites

A little feedback:

 

Something is wrong. My Wifi no longer connects to a wifi network when it hits the desktop (it connects a few seconds after hitting the desktop). Not only this I have to wait between 45 seconds to a minute for my bluetooth dongle to work when I hit the desktop.

Share this post


Link to post
Share on other sites

A little feedback:

 

Something is wrong. My Wifi no longer connects to a wifi network when it hits the desktop (it connects a few seconds after hitting the desktop). Not only this I have to wait between 45 seconds to a minute for my bluetooth dongle to work when I hit the desktop.

if you have a bug to file please file it @ the link in post #1.

 

Try dleeting al the nvram variables that are related to wifi/bluetooth.

 

or boot -s, and dleete the nvram.{censored}.plist and reboot

Share this post


Link to post
Share on other sites

if you have a bug to file please file it @ the link in post #1.

 

Try dleeting al the nvram variables that are related to wifi/bluetooth.

 

or boot -s, and dleete the nvram.{censored}.plist and reboot

 

Disregard my bluetooth and wifi woes.

 

It was a hardware problem that has been taken care of

Share this post


Link to post
Share on other sites

Sorry, but i am a bit a "noob" for that nvram usage ;)

 

If i would use / install that nvram module (with chameleon 2181+) what new variables would exist / what would be changed / what things may work better?

Or, if no new nvram variables are automaticly created by the module, which variables maybe usefull to create + use?

 

Here's how I understand that (If I'm wrong please correct me):

OS X saves some settings in NVRAM (Non-Volatile RAM). PC doesn't have that. So every boot these settings are restored to default values. This module writes and restores them from a file created in /Extra directory. So for example, after reboot it will remember your volume settings, brightness value (on a laptop), etc. It can fix iMessage issues, probably also Find My Mac.

Share this post


Link to post
Share on other sites

Any chance the module will ever be able to detect when the boot-args stored in the plist differ from those in org.chameleon.boot.plist and give precedence to the boot.plist?

Share this post


Link to post
Share on other sites

The boot-args are in addition to whatever is in the plist. If you don't want one, just set it using nvram boot-args="-v other flags" or delete it with nvram -d boot-args. Alternatively you can update the boot args in chameleon by updating the command line.

Share this post


Link to post
Share on other sites
The boot-args are in addition to whatever is in the plist. If you don't want one, just set it using nvram boot-args="-v other flags" or delete it with nvram -d boot-args. Alternatively you can update the boot args in chameleon by updating the command line.

 

I get what you're saying but most people are used to updating boot args by editing org.chameleon.boot.plist. This module changes that process and it would be good if the module obeyed what has always been the way to set boot parameters instead of forcing users to learn a new way.

 

If its technically not possible based on the chameleon module architecture then that's one thing but if possible, it would be good to have the option. You could always open source the module and let other developers add that capability ;-)

 

Share this post


Link to post
Share on other sites

We do plan on eventualy releasing source for the module, however those plans are not for the immediate future.

 

In any case, enough information is distributed with the module to modify and extend it's behavior. We include the FileNVRAM.h header in the distribution to allow for any developer to create a module that extends this one. Three API function are defined, get, set, and delete NVRAM variable. Using these functions you can do things such as check if the machine has been locked by FMM, check the default partition that was set by the Startup Disk utility in os x, or anything else that you can think of.

 

In the case of boot-args, the FileNVRAM module registers for a notification to the BootOptions hook. If you wish boot-args to not be set (or to be set to a specific value), you can pose as the original caller of that hook and inject your own data.

Share this post


Link to post
Share on other sites

hello

 

off topic

 

@cosmo1t and @meklort

 

are the chameleon boot loader project dead ?

 

chameleon is a significant tool for hacking mac os x..

 

thanks

Share this post


Link to post
Share on other sites

i got this plist in the extra folder nvram.ffffffff-ffff-ffff-ffff-001xxxxxxx.plist. what does these ffff meaning?

Edited by nai22

Share this post


Link to post
Share on other sites

are the chameleon boot loader project dead ?

cosmo1t and I do not have much time to work on chameleon and took ourselves off of the project. There are still users with commit access who can develop it as needed, however commit activity is very low.

 

 

i got this plist in the extra folder nvram.ffffffff-ffff-ffff-ffff-001xxxxxxx.plist. what does these ffff meaning?

The UUID was read directly out of the machine's SMBIOS, it's whatever your computer's manufacturer set it to be.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By miliuco
      I have Big Sur beta 10 on my system. I also have native NVRAM thanks to SSDT-PMC.aml file.
      I have seen that a nvram.plist file occasionally appears in /System/Volumes/Update volume root folder.

      This file has many entries, some of them from past and not current settings (very different of keys founded in Hackintool or with nvram -p command).
      If I delete it, everything seems to work fine. It is not created again at next boot but after an indefinite number of boots, it can be 2 or 3 or more than 20.
      It happens to someone else? Is it something new in Big Sur? Does it mean that maybe I don't have native NVRAM although I think I do?
    • By miliuco
      macOS Catalina on: Gigabyte Z390 Aorus Elite motherboard + i3 9100 Coffee Lake processor + AMD Radeon RX 580 graphics card + fenvi FV-T919 WIFI and Bluetooth card + Clover r5121 + AppleALC, Lilu, VirtualSMC, XHCI-unsupported, IntelMausiEthernet, USBPorts and WhateverGreen.

      Hardware
       
      Gigabyte Z390 Aorus Elite motherboard: support for Intel 8 and 9 generation processors, Realtek ALC1220 audio, Intel I219V Ethernet, 4 PCI-E slots, 2, 3 and 3.1 USB ports, Intel Graphics 630 integrated graphics card 9th generation Intel i3 9100 processor Nox Hummer H-212 120mm CPU Fan Corsair Vengeance LPX 3200 MHz 16 GB RAM (2 x 8) AMD Radeon RX 580 8GB graphics card Wifi and Bluetooth Card Fenvi FV-T919 Mars Gaming MPII850 Power Supply (850W) Samsung EVO 860 SSD disk.
        What works well?

      Pretty much everything I've tried:
      Radeon RX 580: 3 DP ports and 1 HDMI port, output to 2 displays simultaneously Shutdown, reboot and sleep Integrated sound and HDMI sound output USB ports (2, 3 and 3.1) Enable TRIM for SSD drive AirDrop, Sidecar, etc.
        What is not working well?

      Integrated Intel UHD Graphics 630 card: see below.

      BIOS settings (version F9)

      I only write down the significant options, there are many other options that do not influence macOS and that you can configure to your liking (for example the LEDs on the board, etc.).
      XMP Profile: Auto / Profile 1 / Enabled (eXtreme Memory Profile, I use 3200 MHz memory and without this profile it works at 2600) Platform Power Management: Disabled VT-d: Disabled XHCI Hand-Off: Enabled Legacy USB Support: Enabled Network Stack: Disabled CSM: Disabled Secure Boot: Disabled Fast Boot: Disabled OS Type: Other OS Wake on LAN: Disabled Integrated Graphics: Auto Initial Display Output: PCIe 1 Slot DVMT Pre-Allocated: 256M or higher.
        EFI folder for Clover (installation USB stick / SSD disk with Catalina)

      SSDT

      Some SSDT.aml files in EFI/CLOVER/ACPI/patched.

      SSDT-DTPG.aml (helper module for SSDT)
      SSDT-EC.aml (USB power charge)
      SSDT-UIAC.aml (USB port mapping)
      SSDT-USBX.aml (USB port mapping)
      SSDT-PMC.aml got from OpenCore to have native NVRAM on Z390 mother boards
      SSDT-Z390-RP21-SLOT4-TB3HP.aml (Thunderbolt devices hot plug) it can be skipped.

      Drivers in EFI/CLOVER/drivers/UEFI

      ApfsDriverLoader.efi
      AudioDxe.efi
      DataHubDxe.efi
      FSInject.efi
      VBoxHfs.efi
      SMCHelper.efi
      OcQuirks.efi *
      OpenRuntime.efi *
      OcQuirks.plist *.

      * see OC Quirks below.

      Extensions in EFI / CLOVER / kexts / Other

      AppleALC.kext
      IntelMausi.kext
      Lilu.kext
      USBPorts.kext
      VirtualSMC.kext
      WhateverGreen.kext
      XHCI-unsupported.kext.

      NOTE 1: The USBPorts.kext extension along with 3 aml files included in patched folder (SSDT-EC.aml, SSDT-UIAC.aml y SSDT-USBX.aml) were generated by joanserramiret with the configuration of USB ports for this motherboard so that the limit defined by macOS of 15 ports is not exceeded. Leaves the system configured in this way:
      Enabled all USB2 ports that are not part of a USB3 port (1 internal for BT + 4 rear that are together + 2 on the front) Enabled the USB2 ports that are part of the 2 rear red USB3.1 ports Disabled the USB2 ports that are part of the 4 rear blue USB3 ports Enabled all USB3 ports except the internal one for USB type C connection. Summary: Rear blue ports do not recognize USB2 devices.

      NOTE 2: XHCI-unsupported.kext is required for XHC chipsets whose Device ID is not included in macOS. Depending on the USB driver of your board, it may be necessary to install some additional extension:
      8086: 8CB1 on macOS 10.11.1 or lower: XHCI-9-series.kext 8086: 8D31, 8086: A2AF, 8086: A36D, 8086: 9DED: XHCI-unsupported.kext 8086: 1E31, 8086: 8C31, 8086: 8CB1, 8086: 8D31, 8086: 9C31, 8086: 9CB1: FakePCIID.kext + FakePCIID_XHCIMux.kext. This board (generally Z390 chipset boards) carries the USB 3.1 controller with device ID A36D so the XHCI-unsupported kext is required. You can check your device ID at
      /System/Library/Extensions/IOUSBHostFamily.kext/Contents/Plugins/AppleUSBXHCIPCI.kext/Contents/Info.plist Config.plist file

      The differential options are:

      Acpi> DSDT: change HECI to IMEI / change SAT0 to SATA
      Acpi> Fixes: FixShutdown
      Acpi> Drop OEM_DSM
      Acpi> Drop Tables> DMAR / MATS
      Acpi> SSDT> PluginType selected (Plugin Type number blank)
      Acpi> Halt Enabler / FixHeaders

      Boot> Boot Arguments> slide = 0 / darkwake = 8

      Devices> USB> Inject / FixOwnership / HighCurrent
      Devices> Audio> Inject 11

      Kernel and Kext Patches> Apple RTC and KernelXCPM selected
      Kernel and Kext Patches> KextsToPatch> Name: com.apple.driver.AppleAHCIPort / Find: 40600200 / Replace: 00000000 / Comment: SATA hot plug
      Kernel and Kext Patches> KextsToPatch> Name: com.apple.driver.AppleAHCIPort / Find: 45787465 726E616C / Replace: 496E7465 726E616C / SATA orange icons

      SMBIOS> iMac19.1

      System Parameters> Inject Kexts: Yes / Inject System ID: selected.

      Quirks > select AvoidRuntimeDefrag – DevirtualiseMmio – EnableSafeModeSlide – ForceExitBootServices – ProtectUefiServices – ProvideConsoleGopEnable – ProvideCustomSlide – SetupVirtualMap – SyncRuntimePermissions and set ProvideMaxSlide = 0. *

      Set true DevirtualiseMmio and ProtectUefiServices in OcQuirks.plist file (recommended on Z390 mother boards).

      * see OC Quirks below.

      macOS Catalina install

      There are many publications with instructions so I will only comment on a few specific details.
      The installation USB memory must have a GUID partition scheme so that the board's UEFI can boot from it. I have prepared the USB with the createinstallmedia method + the application "Install macOS Catalina" in the Applications folder The device is USB 3 and, connected to the front USB 3 port, it performs the task quite quickly I have used Clover r5121 which is currently the latest version. The EFI folder of the installation USB can be the same as that of the hard disk with 2 differences: Acpi> SSDT> PluginType deselected and Acpi> Boot leave Default Boot Volume blank and Timeout -1 (so that no volume will boot automatically from the Clover menu). To mount the EFI partition (of the disk or the USB device) I have used Clover Configurator which makes this task very simple or the command line (diskutil), first finding out what disk and partition number is the EFI (diskutil list) and showing it later (mountdisk):
      sudo diskutil list
      sudo diskutil mountdisk / dev / disk2s3  
      RX 580

      Although my RX 580 card is a model from the XFX brand, known for using custom VBios and giving problems in macOS, in my case it seems to work well with Lilu and WhatEverGreen. Booting the operating system it does not show artifacts, the 3 DP ports and the only HDMI port work, you can send the image simultaneously to 2 screens (I have not tried more) with the usual duplication options, yo can send sound in addition to image to one TV by HDMI, during the installation of the operating system it works correctly provided that Lilu and WhatEverGreen are in the USB device, etc. GeekBench 5 Scores: Metal 50100 / OpenCL 44100. As a comparison, the integrated card does not reach 4800 in Metal.
      Regarding the hardware decoding of H264 and HEVC videos, the Hackintool tool and the VideoProc application report that it is not supported although the playback of files of both types with rates of up to 20 mbps is correct so I suspect that it actually encodes well. In order for hardware decoding to appear as supported in the commented applications, the integrated Intel Graphics 630 card must be enabled even if it is disconnected in headless mode (using the RX 580 card as primary sending image to the screen).
       


      Sound

      This board incorporates the Realtek ALC1220 chip that needs the AppleALC extension to work. AppleALC is a Lilu plugin so both must be properly installed.
      Note: Clover > Devices > Audio > Inject 11 or 13 or 15. I’ve tried several layouts and this are the only valid at least in my case.
      Some users have commented that the system does not load AppleALC and they have no sound despite having the extensions in EFI / CLOVER / kexts / Other. In these cases it can be successful to install AppleALC and Lilu in / Library / Extensions and rebuild the extensions cache with Hackintool (a very convenient way to do it) or with this Terminal command:
      sudo spctl --master-disable; sudo mount -uw /; killall Finder; sudo chown -v -R root: wheel / System / Library / Extensions; sudo touch / System / Library / Extensions; sudo chmod -v -R 755 / Library / Extensions; sudo chown -v -R root: wheel / Library / Extensions; sudo touch / Library / Extensions; sudo kextcache -i /  
      What this command does is disable Gatekeeper, mount the system disk in read / write mode, repair permissions on the extensions folders and rebuild the cache. But all of that is done by Hackintool with less work on our part.

      Ethernet

      This board carries the Intel I219V chip that works well with the IntelMausiEthernet extension.

      Wifi & Bluetooth

      I use a Fenvi FV T-919 mini PCI-E card that carries both wifi and bluetooth chips. This card works perfectly in macOS without needing anything other than placing it on the board because it is recognized as Airport Extreme and Bluetooth Apple. Has its own article on perez987.

      Disks

      Samsung EVO 860 SSD. It is a solid state disk with references to work well in Mac. In my case it works well, with a read speed of 430 and a write speed of 250. I have tried faster SSDs but they have given problems to install Catalina, instead with the EVO 860 everything has worked perfectly.

      Integrated graphics

      Integrated Intel Graphics 630 card: we can to make it work correctly by adding some properties in Clover's Devices tab. For it to work you have to:

      - enable it on the board as primary graphics: Initial Display Output IGFX instead of PCIe 1 Slot (actually this is the final step after modifying config.plist)
      - add in config.plist: Boot> Boot Arguments> igfxonln = 1
      - apply a patch (video and audio) in config.plist: Devices> Properties. It is easier to do it from the config.plist file in text mode than from Clover Configurator. With the file open as text find the lines
      <key>Audio</key> <dict> <key>ResetHDA</key> <false/> <key>Inject</key> <integer>11</integer> </dict>  
      Immediately above of them paste this text:
      <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x1F,0x3)</key> <dict> <key>layout-id</key> <data>CwAAAA==</data> <key>model</key> <string>Cannon Lake HDMI</string> <key>hda-gfx</key> <string>onboard-2</string> <key>AAPL,slot-name</key> <string>Internal@0,31,3</string> <key>device_type</key> <string>Audio device</string> </dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>framebuffer-con0-busid</key> <data>AAAAAA==</data> <key>framebuffer-con0-type</key> <data>AAgAAA==</data> <key>framebuffer-con2-flags</key> <data>xwMAAA==</data> <key>model</key> <string>Intel UHD Graphics 630</string> <key>framebuffer-con1-busid</key> <data>AAAAAA==</data> <key>device-id</key> <data>kT4AAA==</data> <key>framebuffer-con2-type</key> <data>AAgAAA==</data> <key>framebuffer-con2-busid</key> <data>BAAAAA==</data> <key>device_type</key> <string>Display controller</string> <key>hda-gfx</key> <string>onboard-1</string> <key>framebuffer-patch-enable</key> <data>AQAAAA==</data> <key>framebuffer-con1-type</key> <data>AAgAAA==</data> <key>AAPL,slot-name</key> <string>Internal@0,2,0</string> <key>AAPL,ig-platform-id</key> <data>BwCbPg==</data> <key>framebuffer-con2-enable</key> <data>AQAAAA==</data> <key>framebuffer-con1-enable</key> <data>AQAAAA==</data> <key>framebuffer-con0-enable</key> <data>AQAAAA==</data> </dict> </dict> But the system crashes when comes out of sleep mode (the PC restarts after a few seconds of leaving sleep mode). This behavior occurs if the cable that comes out from the HDMI port on the motherboard (the only existing connector on this Mobo) plugs in a DisplayPort port on the monitor; if it plugs directly into another HDMI port (monitor or TV) the bug does not occurs and the PC goes in and out of sleep normally.

      Currently the only way to have the graphics card connected to a port other than HDMI without this crash is by replacing the "hda-gfx" property with "no-hda-gfx" in the above code of config.plist. The 2 lines
      <key>hda-gfx</key> <string>onboard-2</string> must be replaced by
      <key>No-hda-gfx</key> <data>AAAAAAAAAAA=</data> After adding this property, you will no longer have sound over HDMI / DP but sleep works very well.

      In summary:
      - Intel HDMI to DisplayPort monitor> has HDMI audio output but has kernel panic when coming from sleep
      - Intel HDMI to HDMI TV> has HDMI audio output and sleep works fine
      - Intel HDMI to DisplayPort monitor with "no-hda-gfx"> sleep works fine but HDMI audio output is lost.

      (based on the post "[GUIDE] General Framebuffer Patching Guide (HDMI Black Screen Problem)" by CaseySJ; thanks also to deeveedee for his help).

      This card can be left activated without connection to the monitor (headless mode) and apparently does not show any interference with the rest of the system.

      With the integrated card as the main card, the system shows enabled both graphics cards and allows to have a screen connected to the Intel 630 via HDMI and a different screen connected to the RX 580 via DP or HDMI, in this case the primary screen is that from the Intel and the other only works when the graphics driver is loaded but, once the system is up and running, the screens allow duplication options as if they depend on a single card.
       
       
       
       
       
      Evolution to Oc Quirks

      OC Quirks is an EFI driver for Clover that replaces AptioMemoryFix and all OsxAptioFix variants. It supports the OpenCore quirks model. AptioMemoryFix has evolved little in the most recent stage and is in a way becoming obsolete. Next versions of Clover will probably stop installing AptioMemoryFix and switch to OC Quirks which is evolving and receiving frequent improvements. You can read about this on the working group website: ReddestDream.

      Migrating our installation from AptioMemoryFix to OC Quirks is relatively simple:
      download the latest version of OC Quirks (search Releases, current version is 23) have a USB device that boots up properly to use in case of failure mount the disk's EFI partition delete AptioMemoryFix and any other OsxAptioFix variant add OcQuirks.efi, OpenRuntime.efi and OcQuirks.plist to Clover's drivers/UEFI folder change to true DevirtualiseMmio and ProtectUefiServices in the file OcQuirks.plist (recommended on boards with Z390 chipset) in Clover> Quirks config.plist file, check the boxes AvoidRuntimeDefrag - DevirtualiseMmio - EnableSafeModeSlide - ForceExitBootServices - ProtectUefiServices - ProvideConsoleGopEnable - ProvideCustomSlide - SetupVirtualMap - SyncRuntimePermissions and assign the value 0 to ProvideMaxSlide Restart the PC.  
      Kernel Panic with BIOS F10c if integrated graphics is enabled

      The Z390 Aorus Elite board comes with BIOS F9 with which the text of this post has been written.

      A few days ago I updated to the current version which is F10c and, since then, I have suffered a kernel panic with the forbidden symbol when going from the Clover menu to the macOS boot screen if the integrated card was enabled in BIOS. This happened regardless of whether the Intel UHD Graphics 630 card was set to Clover (fully for monitor output or headless mode for encoding) or not.

      Returning to BIOS F9 the system has returned to working as before and the kernel panic has disappeared. I can have the card enabled or disabled again in BIOS without problems.
       
      efi-quirks.zip
    • By Forzenny
      Hi there,
       
      I managed to install Mojave on my MSI GP62-6QE laptop with somewhat success. The only annoying thing left is that everytime I shut it down it seemingly kernel panics and I get the "Your computer has restarted because of a problem" at startup.
       
      I tried many different things such as removing emuvariablesuefi64, checking FixShutdown in CloverConfig but it seems the NVRAM is causing this issue.
       
      I have deleted the nvram file from the EFI partition but it seems stuck somewhere else, I can't clear out the nvram from the terminal or in single user mode as it returns a "Not permitted" error.
      Clearing out the nvram by pressing F11 at the boot menu screen works however.
      crashlog.rtf
    • By blackosx
      Do you want to quickly find your boot log, or ever wanted to know which version of bootloader is installed on your disk(s), had the need to dump your BIOS from OS X, just curious about your own system setup or been asked to provide your setup information to others when asking for assistance?
       
      DarwinDumper is a useful collection of readily available tools, and scripts wrapped in an application framework giving you a convenient method to quickly gather a system overview of your hack or Mac. And rest assured that enabling the privacy option will mask sensitive data like the IOPlatformSerialNumber, IOPlatformUUID, IOMACAddress(s), USB Serial Number(s), SystemSerialNumber, serial-number, fmm-mobileme-token-FMM, MLB and ROM efi vars and CustomUUID in the dumped files and report.

      Current Release Version: 3.1.1



      The system dumps are saved to a folder or your choice, but defaulting to the same directory as the main application. You can choose to setup a symlink to make it simple to run DarwinDumper from the Terminal.
       
      There is an option to create an html report showing a complete overview of the dumps. This report will mostly just contain the text dumps as you'll find in the main dump directory, but for some dumps there is extra processing to try to present the information in a better way. For example, the Disk Partitions and Unique ID's dump will show a visual map of the disk layout, and the DMI Tables (SMBIOS) dump will show the data split by table type.
       

       
      Note: The html report does not contain all files from a complete dump so if seeking assistance for a problem and you wish to send someone a DarwinDump then you will want to send the complete dump directory and not just the .html report file.
       
      The following can be read and dumped by DarwinDumper:
      - ACPI tables.
      - Audio codec and further info.
      - Boot loaders and configuration files.
      - CPU info.
      - Device-properties.
      - Disk partition structure / info.
      - Disk sectors (hex).
      - DMI (SMBIOS).
      - EDID.
      - I/O Kit Registry.
      - EFI Memory Map.
      - EFI vars (some).
      - Kernel information
      - Kexts - (list of currently loaded kexts).
      - Memory.
      - NVRAM (both Apple specific and UEFI firmware variables).
      - SMC Keys.
      - LSPCI (PCI vendor & device codes) dumps.
      - Power (Sleep/Hibernate) settings.
      - RTC.
      - System Profiler.
      - System BIOS.
      - System Log(s).
      - Video BIOS.
       
      License:
      DarwinDumper is licensed under GNU General Public License, version 3.0 (GPLv3).
       
      Tools included:
      AnalyseVBIOS
      Copyright: Not Known. License: Not known Source: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/ Alt Link: https://www.dropbox.com/s/dnp903x2z9pqf8k/AnalyseVBIOS.zip?dl=0   AppleIntelInfo Copyright: © 2012-2017 Pike R. Alpha. All rights reserved. License: Creative Commons Attribution-NonCommercial Source: https://github.com/Piker-Alpha/AppleIntelInfo   atomdis Copyright: Michael Larabel @ Phoronix.com License: GPL Version 2 Source: http://www.phoronix.com/scan.php?page=article&item=amd_atombios_dumper   bgrep Copyright 2009 Felix Domke <tmbinc@elitedvb.net>. All rights reserved.   Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:      1. Redistributions of source code must retain the above copyright notice, this list of       conditions and the following disclaimer.      2. Redistributions in binary form must reproduce the above copyright notice, this list       of conditions and the following disclaimer in the documentation and/or other materials       provided with the distribution.   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.   The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the copyright holder.   Source: https://github.com/tmbinc/bgrep   bdmesg Copyright 2010 by Islam M. Ahmed Zaid. All rights reserved. License: GPL Version 2 Source: http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/util/bdmesg.c Alt Link: https://sourceforge.net/p/cloverefiboot/code/1905/tree/CloverPackage/utils/bdmesg/bdmesg.c   cmosDumperForOsx Created by rafirafi, revised extensively by STLVNUB License: Information not available Source: https://www.dropbox.com/s/bg1q0yho6g7u3xn/cmosDumperForOsxV0.1.zip?dl=0   csrstat Created by Piker-Alpha Copyright: © 2015-2017) by Pike R. Alpha License: Information not available Source: https://github.com/Piker-Alpha/csrstat   dmidecode Original nongnu.org
      License: GPL Version 2
      Now updated and hosted by acidanthera Source: https://github.com/acidanthera/dmidecode   dumpACPI Created by blackosx. Idea taken from PHPdev32's MacIASL. Source: https://bitbucket.org/blackosx/dumpacpi   edid-decode Created by Adam Jackson, revised by Andy Vandijck License: Information not available Original Source: http://cgit.freedesktop.org/xorg/app/edid-decode Revised Source: https://www.dropbox.com/s/l0htffnqzs9e1vg/edid-decode.zip?dl=0   fdisk440 Apple Computer, Inc. License: APSL v2.0 Original Source: http://www.opensource.apple.com/source/diskdev_cmds/diskdev_cmds-491/fdisk.tproj/mbr.h Modified by Zef Source: http://forge.voodooprojects.org/p/chameleonApplications/source/tree/HEAD/trunk/fdisk.tproj Alternate Link: https://www.dropbox.com/s/odl9kp38j3flla5/fdisk440.zip?dl=0   FirmwareMemoryMap script Amit Singh (showbootermemorymap) Further development by bcc9 and dmazar License: Information not available   flashrom http://flashrom.org/Flashrom License: GPL Version 2 Source: https://www.dropbox.com/s/gfmqx2t7lvofs1v/flashrom.zip?dl=0   getcodecid Copyright © 2012 AnV Software. All rights reserved. License: Information not available Source: https://github.com/Gengik84/getcodecid   getdump Created by fassl?, modifications by Slice and AutumnRain? License: Information not available Source: https://sourceforge.net/projects/voodoohda/files/   gfxutil Copyright 2008 mcmatrix. All rights reserved. License: Information not available Historic detail can be found at forum.netkas.org Source: https://github.com/acidanthera/gfxutil   iasl Copyright © 2000 – 2014 Intel Corporation. License: Information not available Source for v20200110: https://www.acpica.org/node/176   ioregwv Apple Computer, Inc. License: APSL v2.0 Original Source: https://opensource.apple.com/source/IOKitTools/IOKitTools-86/ Modified by blackosx Source: https://bitbucket.org/blackosx/ioregwv   lzma Copyright © 2013 Igor Pavlov. License: GNU Lesser General Public License Source: http://www.7-zip.org/sdk.html This build by Slice at insanelymac.com: https://www.insanelymac.com/forum/topic/311786-updated-lzma-utility-v1514/   lzvn Copyright: © 2014 Apple Computer, Inc. All rights reserved. License: APSL Credit: Piker-Alpha, Andy Vandijck, MinusZwei. https://github.com/Piker-Alpha/LZVN   MacGap2 Created by Tim Debo. All rights reserved. License: MIT Source: https://github.com/MacGapProject/MacGap2   Macpmem driver (Macpmem.kext) Copyright © 2007-2011 Volatile Systems. Copyright 2013-2014 Google Inc. All Rights Reserved. License: GPL Version 2 Source Code: https://github.com/google/rekall/tree/master/tools/osx/MacPmem]https://github.com/google/rekall/tree/master/tools/osx/MacPmem   nvram Apple Computer, Inc. License: APSL v2.0 Modified by blackosx Source: https://bitbucket.org/blackosx/nvram   oclinfo Copyright © 2009 cmf License: GPL Version 2 Source: http://www.insanelymac.com/forum/topic/170796-opencl-info/   pciutils driver (DirectHW.kext) DirectHW is Copyright © 2008-2010 coresystems GmbH License: GPL Version 2 Source: https://github.com/CloverHackyColor/directhw Kext: Pre-built (Signed) Kext   pciutils lspci Copyright © 1997--2008 Martin Mares License: GPL Version 2 Source Code: https://git.kernel.org/pub/scm/utils/pciutils/pciutils.git
      RadeonDump Created by Dong Luo. Copyright 2008. All rights reserved. Modified by Andy Vandijck License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068 Alt Link: https://www.dropbox.com/s/5drpckxlmaot732/RadeonPCI.zip?dl=0   radeon_bios_decode Created by Dong Luo. Copyright 2008. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068   SMC_util_FansOnly Copyright © 2006 devnull  License: GPL Version 2 Source: https://www.dropbox.com/s/ra9h6gbjj6yhgol/SMC_util_FansOnly.zip?dl=0   smcutil Copyright © 2006 devnull  License: GPL Version 2 Source: https://www.dropbox.com/s/0dgvexijx4oewfr/smcutil.zip?dl=0   VoodooHDA.kext Created by fassl?, modifications by Slice and AutumnRain? License: https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h]https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h Source: https://sourceforge.net/p/voodoohda/code/HEAD/tree/]https://sourceforge.net/p/voodoohda/code/HEAD/tree/   x86info Written to succeed CPUID by Phil Karn (KA9Q). Contributed to by various people. OS X compatability by Slice License: GPL Version 2 Original Source: https://github.com/kernelslacker/x86info Revised Source: https://github.com/CloverHackyColor/x86info  
       
      Running DarwinDumper from the command line:
      From Terminal, you can initiate DarwinDumper by running the following script directly.
      /DarwinDumper.app/Contents/Resources/public/bash/script.sh To help with this, the UI has a Symlink option which you can click to create a symbolic link which points to the above script. DarwinDumper can then be subsequently run from the command-line by loading a new Terminal window and typing darwindumper followed by return.
      $ darwindumper usage: [-a zip,lzma,none] [-d acpi,appleintelinfo,audio,biosSystem,biosVideo,codecid,cpuinfo,devprop,diskLoaderConfigs,bootLoaderBootSectors,diskPartitionInfo,dmi,edid,bootlogF,bootlogK,firmmemmap,memory,ioreg,kernelinfo,kexts,lspci,rcscripts,nvram,opencl,power,rtc,sip,smc,sysprof] [-h] [-l] [-o html,private] [-p 1,2,3,4,5,6,7,8] [-v] Example:
      $ darwindumper -l Will re-run the last dump used options.

      Credits (in alphabetical order):
      acidanthera team, Adam Jackson, Amit Singh, Andy Vandijck, Apple Inc., arsradu, bcc9, blackosx, cmf, DieBuche, dmazar, Dong Luo, droplets, ErmaC, Felix Domke, Google Inc., Intel Corporation, InsanelyDeepak, JrCs, Kabyl, Kynnder, Martin Mareš, mcmatrix, Michael Larabel, Mickey1979, phcoder, Phil Karn, Piker-Alpha, rafirafi, гык-sse2, Slice ,sonotone, STLVNUB, THe KiNG, Trauma, Volatile Systems, xsmile, !Xabbu.
       
      DarwinDumper was originally inspired as an open project by Trauma, it has remained an open project and please keep it an open project, so if you make any changes or additions to it then please share your work here.
       
      Please report any feedback, requests or bugs.
       
      Known issues: v3.1.0
      1 - When SIP File Protection is enabled, dumping disk partition info of non-APFS containers and disks which are not APFS physical stores may fail when running from DarwinDumper via the graphical interface. However, it's been known to succeed when using DarwinDumper from the command line. Something to do with osascript.
      2 - lzma archive option has been known to fail on macOS 10.15 when running dumps requiring root privileges.
       
      macOS Version support:
      - v2.9.9.2 is for older macOS versions
      - v3.0.4 requires OS X 10.9 and newer to run in the Finder, though it should work from the command line okay on older OS versions.
      - v3.1.0 was updated for newer macOS versions and has been tested on 10.13 and 10.15.

      DarwinDumper Download
×