Jump to content

5,130 posts in this topic

Recommended Posts

On 10/13/2019 at 9:33 PM, dogansan said:

thanks for help. I deleted FakeSMC and ACS6x.kext from L/E and made off SSDT in config.plist. Now, I see some progress but still no full booting and login. I am using a USB as boot device , it seems my signature is not seen at the bottom, my systems spec are as follows:

Desktop PC : Intel Core i7 3370K  | ASUS Maximus Formula V |ASUS R7 370 | DDR3 (2x8GB) RGB | 82579V Gigabit LAN  | Broadcom BCM43228 802.11a/b/g/n+ Bluetooth | macOS Catalina 10.15.1 Beta 19B68f, Linux , Mojave  and Windows Enterprise 10 Build 1903 (Bootloader : Clover r5080 + OpenCore 0.5.1 not yet)

20191013_211249.jpg

I solved the hanging at apfs boot module start during booting by activating SSDT-EC-USBX.aml abd adding nv_disable=1 to boot args. It now boots ,now I have to activate Radeon R9-270

Share this post


Link to post
Share on other sites
Advertisement

@bittantone sorry, I had two copy+paste mistakes: https://github.com/acidanthera/OcSupportPkg/commit/0c20f3f5cf860d51961d8b0c1bbcaf36eee6e571

but considering the first branch is not even reached, I get the feeling this will not work either. Please report back whether it works, but a different kind of workaround is going to take a bit more time to implement

Share this post


Link to post
Share on other sites
39 minutes ago, Download-Fritz said:

@bittantone sorry, I had two copy+paste mistakes: https://github.com/acidanthera/OcSupportPkg/commit/0c20f3f5cf860d51961d8b0c1bbcaf36eee6e571

but considering the first branch is not even reached, I get the feeling this will not work either. Please report back whether it works, but a different kind of workaround is going to take a bit more time to implement

Ok, now it reaches the OC menu, but it still fails to read the NVME containing macOS

opencore-log.txt

 

@Download-Fritz the part that looks more strange to me is that if I put ScanPolicy to 0 the macOS entry on NVME is correctly detected and everything works fine. Couldn't it be possible that the NVME partition is detected as something different from APFS and HFS+ and for that reason is ignored?

 

(Please note that I've fire vault enabled)

Edited by bittantone

Share this post


Link to post
Share on other sites
1 hour ago, bittantone said:

Ok, now it reaches the OC menu, but it still fails to read the NVME containing macOS

opencore-log.txt

 

@Download-Fritz the part that looks more strange to me is that if I put ScanPolicy to 0 the macOS entry on NVME is correctly detected and everything works fine. Couldn't it be possible that the NVME partition is detected as something different from APFS and HFS+ and for that reason is ignored?

 

(Please note that I've fire vault enabled)

 

My set up is similar: I usually boot from an NVME drive, no NVRAM is used, but I do not have Fire Vault enabled. I use ScanPolicy of 3080963 as mentioned earlier. With this I can boot from NVME or SATA drives (I have no Windows active so cannot comment). And setting the System Preferences/Startup Disk works perfectly in either Mojave or Catalina.

 

When you mentioned difficulty getting into BIOS, I've seen that with corrupted BIOS. Maybe re-flash BIOS.

 

Another possibility is a corrupted config file; are you using XCode for editing?

 

I once had a corrupted EFI drive that gave weird boots (your issue doesn't sound this bad). My only recourse at the time was to reformat and use a backup to restore. 

Share this post


Link to post
Share on other sites
17 minutes ago, iGPU said:

 

My set up is similar: I usually boot from an NVME drive, no NVRAM is used, but I do not have Fire Vault enabled. I use ScanPolicy of 3080963 as mentioned earlier. With this I can boot from NVME or SATA drives (I have no Windows active so cannot comment). And setting the System Preferences/Startup Disk works perfectly in either Mojave or Catalina.

 

When you mentioned difficulty getting into BIOS, I've seen that with corrupted BIOS. Maybe re-flash BIOS.

 

Another possibility is a corrupted config file; are you using XCode for editing?

 

I once had a corrupted EFI drive that gave weird boots (your issue doesn't sound this bad). My only recourse at the time was to reformat and use a backup to restore. 

 

Thank you for your inputs. I've tried with 3080963, but unfortunately it does not find macOS on the NVME :no: I'd be happy to use ScanEntry = 0, which works, but it does find Windows and start it by default, even though I set macOS from Startup Disk panel. 

Are you using LogoutHook + nvram.plist?

 

Concerning BIOS corruption, yeah I think this is the cause, but honestly I don't know whether it is plausible, nor how to fix it. 

 

I'm using Xcode and Plist Editor Pro, but sometimes I also use Meld/Kaleidoscope to compare different config.plists. Btw I don't think this is the problem, since the BIOS is stuck even though I remove the USB drive with OpenCore

Edited by bittantone

Share this post


Link to post
Share on other sites
24 minutes ago, bittantone said:

Concerning BIOS corruption, yeah I think this is the cause, but honestly I don't know whether it is plausible, nor how to fix it.

 

That would be interesting... just perform a FW update and, if there is such a prompt, refuse to carry on previous settings.

Share this post


Link to post
Share on other sites
36 minutes ago, Download-Fritz said:

 

That would be interesting... just perform a FW update and, if there is such a prompt, refuse to carry on previous settings.

As far as I know, to re-flash my BIOS I need to enter BIOS settings, which I cannot access when BIOS gets corrupted. The only workaround is to remove the CMOS battery to reset settings and power on without any SATA/disk inserted...

Share this post


Link to post
Share on other sites

I'm trying to migrate to OpenCore from Clover.  I took my existing install, got rid of the Clover folder, set up the OC folder according to the Vanilla Guide, and also copied over the BOOT folder from the 0.51 zip file.  The only thing (AFAIK) I did different from the Vanilla Guide was keeping my existing DSDT which has generally had no effect since my motherboard is "out of the box" hackintoshable.

 

When I boot into my Mac SSD, it just hangs at the BIOS screen.  No further information, just the POST and then it sits there.  As such, I'm stumped.  I'm running a Gigabyte Z77X-UD5H with an 3570k and RX 580 video card.  I've been using this as a hackintosh for years, so hopefully I can keep doing so!

 

I would really appreciate any help or advice!  What I've done so far:

- turned off my custom SSDT made with powergen.sh way back when

- added the EC SSDT per the vanilla guide

- removed an old Apple folder that was hanging out there

 

I'm pretty well at a loss here because I'm not getting any error messages, so any help would be appreciated!  I'm attaching my EFI folder with my system's serial numbers and UUID scrubbed.  Thanks in advance!

EFI.zip

Edited by birdbird

Share this post


Link to post
Share on other sites
1 hour ago, bittantone said:

As far as I know, to re-flash my BIOS I need to enter BIOS settings, which I cannot access when BIOS gets corrupted. The only workaround is to remove the CMOS battery to reset settings and power on without any SATA/disk inserted...

 

I had same issue of difficulty getting into BIOS (on both ASUS and GB mobos). I kept re-booting while tapping the "Delete" key (entry for ASUS mobos) and eventually I got in. (Removing NVME and SATA drives is okay at this stage.)

 

I'd already prepared a USB flash drive on another computer and had it inserted into the correct USB port (check your manual; there is one port that is correct for flashing BIOS for each mobo).

 

One other thing to consider that can make getting into BIOS difficult is bad memory. So check your DDR4 sticks.

 

When the worse BIOS corruption happened to me, it was compounded by a bad DDR4 stick. My clue was a change in LED colors. All of the DDR4 sticks had LEDs and one displayed colors different than the rest; so I removed that stick along with its mate (keeping correct pairs), and then I easily got into BIOS, and was subsequently able to re-flash it.

Edited by iGPU

Share this post


Link to post
Share on other sites

Am I reading this right?

 

If I set scan policy to 1 (0x00000001) then OC will see only the OS I use? Or would I need to include their devices as well. "1" doesn't seem to work on it's own and my OS is on an M.2 drive. Am ok to presume I need...

 

1, 2, 400, 8000? so a total of 0x00008403 (33,795)?

 

Im doing this mostly to learn but also my logs tell me that a lot of my boot is spent here.

0x00000001 - Known File Systems Only
0x00000002 - Known Device Types.
0x00000200 - HFS File System Scan
0x00000400 - Allow EFI Partition Scan
0x00010000 - Allow Sata Scan
0x00020000 - SAS Scan
0x00040000 - SCSI Scan
0x00080000 - NVMe Scan
0x00100000 - CD/DVD Scan
0x00200000 - USB Drive Scan
0x00400000 - FireWire Scan
0x00800000 - SD/Card Media Scan

 

Share this post


Link to post
Share on other sites
1 hour ago, birdbird said:

I'm trying to migrate to OpenCore from Clover.  I took my existing install, got rid of the Clover folder, set up the OC folder according to the Vanilla Guide, and also copied over the BOOT folder from the 0.51 zip file.  The only thing (AFAIK) I did different from the Vanilla Guide was keeping my existing DSDT which has generally had no effect since my motherboard is "out of the box" hackintoshable.

 

When I boot into my Mac SSD, it just hangs at the BIOS screen.  No further information, just the POST and then it sits there.  As such, I'm stumped.  I'm running a Gigabyte Z77X-UD5H with an 3570k and RX 580 video card.  I've been using this as a hackintosh for years, so hopefully I can keep doing so!

 

I would really appreciate any help or advice!  What I've done so far:

- turned off my custom SSDT made with powergen.sh way back when

- added the EC SSDT per the vanilla guide

- removed an old Apple folder that was hanging out there

 

I'm pretty well at a loss here because I'm not getting any error messages, so any help would be appreciated!  I'm attaching my EFI folder with my system's serial numbers and UUID scrubbed.  Thanks in advance!

EFI.zip

 

You might have some issues with residual Clover files. Maybe try removing them, by running the following from a Terminal window:

sudo rm -rf /etc/rc.boot.d
sudo rm -rf /etc/rc.shutdown.d
sudo rm -rf /Volumes/EFI/nvram.plist
sudo rm -rf /etc/rc.clover.lib
sudo rm -rf etc/rc.boot.d/20.mount_ESP.local
sudo rm -rf /etc/rc.boot.d/70.disable_sleep_proxy_client.local.disabled
sudo rm -rf /etc/rc.boot.d/80.save_nvram_plist.local

lastly, look for and remove this file if present: Library/PreferencePanes/Clover.prefPane

 

***

 

As for your EFI file, you got IntelMausiEthernet.kext in your kext folder but IntelMausi.kext in your Kernel section. (I'm not certain how useful BrcmPatchRAM2.kext is, but it probably isn't keeping you from booting; I think AirportBrcmFixup.kext is more useful.)

 

ExternalDiskIcons, ThirdPartyTrim and XhciPortLimit are usually best "No". In regard to the latter, you're using USBInjectAll.kext, but I don't see a SSDT-UIAC file. So I don't see a proper way you're limiting USB ports (aside from depending on XhciPortLimit, which is best not used). A simple addition when using USBInjectAll would be to add a boot argument (NVRAM section) like this: uia_exclude=HS09;HS10;HS13;SSP3;SSP4;SSP7;SSP8;USR1;USR2 (obviously changing these values to ports you wish to exclude). I prefer not using USBInjectAll (and the above boot arg), and instead use a USBPortsMap kext file to inject the desired USB ports. Hackintool can create this file for you.

 

In your PlatformInfo section, you've removed DataHub, PlatformNVRAM and SMBIOS sections. I kept all and leave Automatic as No. Maybe copy these from the Sample.plist file, and and fill-in with your data. 

 

I don't use any DSDT.aml file and have no issues booting with OC.

 

Finally, the OC docs suggest leaving AvoidHighAlloc as YES for GA-Z77P mobos; maybe this holds true for your GA-Z77X?

Share this post


Link to post
Share on other sites

 

3 hours ago, Carbonimax said:

Hi,

 

I try to boot with OC 0.5.1 but it stuck on this. Anyone can help me? 

IMG_9323.jpg

Here is my EFI Folder.

I would really appreciate any help or advice :)

EFI.zip

Share this post


Link to post
Share on other sites
12 minutes ago, Carbonimax said:

 

Here is my EFI Folder.

I would really appreciate any help or advice :)

 

Most all of your ACPI patches are discouraged per OC docs. I'd turn them off to sort things out first.

 

I've not needed any DSDT.aml files to boot. I'd turn this off for now too.

You've got a lot of DeviceProperties. I'd probably try to boot without most of them and then add them back once things look okay.

 

I'd reduce your boot arguments from:
-v dart=0 alcid=16 slide=0 darkwake=10 debug=0x100 agdpmod=pikera nv_disable=1

 

To:
-v darkwake=10 debug=0x100

(dart=0 not needed since you have DisableIoMapper = YES; slide=0 is discouraged.)

 

You can leave UEFI/Input/PointerSupportMode blank as you're not using an ASUS mobo (I am using one but still leave it blank).

 

Your other settings are similar to what I've used with both Mojave and Catalina.

Share this post


Link to post
Share on other sites

Thank you!

 

I remove DSDT.aml, all patches, all DeviceProperties, reduce boot args and change ScanPolicy to 0 but always same problem, halt on the same line :-/

Edited by Carbonimax

Share this post


Link to post
Share on other sites
2 hours ago, Carbonimax said:

Thank you!

 

I remove DSDT.aml, all patches, all DeviceProperties, reduce boot args and change ScanPolicy to 0 but always same problem, halt on the same line :-/

 

Sorry, it didn't help. I did just notice that you're must be on "Catalina 10.15.1" (your sig says "Mojave 10.15.1", but Mojave = 10.14.x), and I only saw the Mojave.

 

So, while it may not affect your boot, Catalina 10.15.1 beta (2) seem to need boot/arg agdpmod=pikera (which I'd told you to remove), and no need for WEG with a navi GPU, like RX5700. I don't know about Vega 64 (also in your sig) since not navi. (I'm not running beta OS and don't have a navi GPU, just a Vega 56, so I'm out of that loop.)

Edited by iGPU

Share this post


Link to post
Share on other sites

Seem to have an issue with OC and Catalina 10.15.1b2. I updated the os and booted from OC 0.5.2 ok. If I restart I get "Unable to load kernel cache". I can still boot from clover 5096 with no problems, I can use OC to boot mohave no problems. It will even boot Windows just fine. Will not boot into catalina again from OC. Please help and thank you.

 

EFI.zip

Share this post


Link to post
Share on other sites
10 hours ago, iGPU said:

 

Sorry, it didn't help. I did just notice that you're must be on "Catalina 10.15.1" (your sig says "Mojave 10.15.1", but Mojave = 10.14.x), and I only saw the Mojave.

 

So, while it may not affect your boot, Catalina 10.15.1 beta (2) seem to need boot/arg agdpmod=pikera (which I'd told you to remove), and no need for WEG with a navi GPU, like RX5700. I don't know about Vega 64 (also in your sig) since not navi. (I'm not running beta OS and don't have a navi GPU, just a Vega 56, so I'm out of that loop.)

Correct, it is Catalina! Fix.

 

In Clover, I have to put `agdpmod=pikera`, otherwise I have a black screen... I don't know why.

When I replace `pikera` by `vit9696` or without WEG, it doesn't work.

 

With ou without this boot args, OC crash, so I think it is not the problem.

Share this post


Link to post
Share on other sites
19 hours ago, NorthAmTrans said:

Am I reading this right?

 

If I set scan policy to 1 (0x00000001) then OC will see only the OS I use? Or would I need to include their devices as well. "1" doesn't seem to work on it's own and my OS is on an M.2 drive. Am ok to presume I need...

 

1, 2, 400, 8000? so a total of 0x00008403 (33,795)?

 

Im doing this mostly to learn but also my logs tell me that a lot of my boot is spent here.


0x00000001 - Known File Systems Only
0x00000002 - Known Device Types.
0x00000200 - HFS File System Scan
0x00000400 - Allow EFI Partition Scan
0x00010000 - Allow Sata Scan
0x00020000 - SAS Scan
0x00040000 - SCSI Scan
0x00080000 - NVMe Scan
0x00100000 - CD/DVD Scan
0x00200000 - USB Drive Scan
0x00400000 - FireWire Scan
0x00800000 - SD/Card Media Scan

 

 

this information is wrong. correct one is: 

 

0x00000001 (bit 0) — OC_SCAN_FILE_SYSTEM_LOCK,

0x00000002 (bit 1) — OC_SCAN_DEVICE_LOCK,

.....

 

RTFOM: READ THE {censored} ORIGINAL MANUAL

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

Share this post


Link to post
Share on other sites
56 minutes ago, justin said:

 

this information is wrong. correct one is: 

 

0x00000001 (bit 0) — OC_SCAN_FILE_SYSTEM_LOCK,

0x00000002 (bit 1) — OC_SCAN_DEVICE_LOCK,

.....

 

RTFOM: READ THE {censored} ORIGINAL MANUAL

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

Delightfully hostile. Will disregard other manuals, I've read em all but just wanted something to copy and paste.

 

Can you help me come up with a value or teach me how you do that will scan only my M.2 drive?

Share this post


Link to post
Share on other sites
1 hour ago, NorthAmTrans said:

Delightfully hostile. Will disregard other manuals, I've read em all but just wanted something to copy and paste.

 

Can you help me come up with a value or teach me how you do that will scan only my M.2 drive?

 

to scan only M.2 (NVME+APFS), you need:

 

0x00000001 (bit 0) — OC_SCAN_FILE_SYSTEM_LOCK

0x00000002 (bit 1) — OC_SCAN_DEVICE_LOCK

0x00000100 (bit 8) — OC_SCAN_ALLOW_FS_APFS

0x00080000 (bit 19) — OC_SCAN_ALLOW_DEVICE_NVME,

 

that's bit 0+1+8+19, hex 0x80103, decimal 524547

(open Calculator.app, View-Programmer, click bit 0 1 8 19 to set them "1", then click 16 and 10, you will get the hex and decimal value)

so put ScanPolicy=524547 in there.

 

Screen Shot 2019-10-21 at 02.41.21.png

Edited by justin

Share this post


Link to post
Share on other sites

 

Hi @justin

I have now  0xB0503. Converted that will be 722179.

This combination reads as:

OC_SCAN_FILE_SYSTEM_LOCK 

OC_SCAN_DEVICE_LOCK
OC_SCAN_ALLOW_FS_APFS
OC_SCAN_ALLOW_DEVICE_SATA 

OC_SCAN_ALLOW_DEVICE_SASEX 

OC_SCAN_ALLOW_FS_ESP

OC_SCAN_ALLOW_DEVICE_NVME

 

OC_SCAN_ALLOW_FS_ESP allows to scan EFI System partition wich means that my EFI partition-map will show up as a separate boot option in Boot menu together with my Windows boot option.

Is there a way to hide only the EFI boot option in Boot menu and keep just the Windows boot option in Boot menu?

I have Windows on a separate disk.

Edited by obus

Share this post


Link to post
Share on other sites

Hello, OpenCore is giving me this error "Found legacy AptioMemoryFix driver!" but I'm using the one bundled in the latest package (v0.5.1). Anybody kn ows how to help me? Thanks a lot.

EFI.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
      Anyone who likes the program, please support its Community Score.
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By STLVNUB
      Script file to clone and help build Clover, Opencore (official and unofficial) repos
      Script will create link to itself in /usr/local/bin/bob
      Wouldn't hurt to check there are no "Bob"'s there, i "Hope" there isn't.
       
      Then you only need to type bob. and a parameter
      "n" for NDK repo, unofficial
      "a" for ACID repo, official
      "c" for CLOVER
      It also takes "all" for ALL, if your game
      Currently NDK Repo has problems so "all" and "n" DON'T WORK
       
      Easier typing bob than.....usual stuff
      Enjoy
       
    • By cvad
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
      Anyone who likes the program, please support its Community Score.
       
       
      Feel free to "Rate File"
    • 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.0.4, though latest beta DarwinDumper_v3.1.0b6



      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/   AppleIntelInfo Copyright: © 2012-2017 Pike R. Alpha. All rights reserved. License: Creative Commons Attribution-NonCommercial 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   cmosDumperForOsx Created by rafirafi, revised extensively by STLVNUB License: Information not available Source: http://www.projectosx.com/forum/index.php?showtopic=2432&st=0&p=21522&&do=findComment&comment=21522   csrstat Created by Piker-Alpha Copyright: © 2015-2017) by Pike R. Alpha License: Information not available Source: https://github.com/Piker-Alpha/csrstat   dmidecode http://www.nongnu.org/dmidecode/ License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2488   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: http://bit.ly/1qAzqxb   fdisk440 Apple Computer, Inc. License: APSL v2.0 Source: http://forge.voodooprojects.org/p/chameleonApplications/source/tree/HEAD/trunk/fdisk.tproj   FirmwareMemoryMap script Amit Singh (showbootermemorymap) License: Information not available Source: http://www.projectosx.com/forum/index.php?showtopic=2447&st=120&p=19329&&do=findComment&comment=19329   flashrom http://flashrom.org/Flashrom License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2485&view=findpost&p=40285   getcodecid Copyright © 2012 AnV Software. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/285277-getcodecid-command-line-tool-to-detect-codec-id/   getdump Created by fassl?, modifications by Slice and AutumnRain? License: Information not available Source: https://svn.code.sf.net/p/voodoohda/code/tranc/getdump.c   gfxutil Copyright 2008 mcmatrix. All rights reserved. License: Information not available http://forum.netkas.org/index.php?PHPSESSID=q2isd338ihjjpcgbng7tne08pdv7tr4f&topic=64.0 Source: https://dl.dropbox.com/u/222155/gfxutil_source.zip   iasl Copyright © 2000 – 2014 Intel Corporation. License: Information not available Source: https://github.com/acpica/acpica   ioregwv Apple Computer, Inc. License: APSL v2.0 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   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   nvram Apple Computer, Inc. License: APSL v2.0 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: http://www.projectosx.com/forum/index.php?showtopic=2480   pciutils lspci Copyright © 1997--2008 Martin Mares License: GPL Version 2 Source Code: https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils.git/+/master   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   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   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   smbios-reader http://www.nongnu.org/dmidecode/ License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2208   SMC_util3 Copyright © 2006 devnull  License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=23230   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: http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=41134  
       
      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.

      Credits (in alphabetical order):
      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.
       
      Please note:
      DarwinDumper v3 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.

      The following link retains the download for v2.9.9.2 for older OS versions.

      DarwinDumper Download
×