Opções binárias Mauá: 0x11 In Binary Option

Cant passthrough RX 5700 XT

I was trying to passtrough my only gpu but there seems to be a problem with vfio.
CPU: Ryzen 1700X
GPU: Sapphire pulse rx 5700 xt
Mobo: Asus Rog strix X370-F
Bios options: SVM : Enabled, SR-IOV : Disabled
OS: arch , kernel 5.2.11-arch1-1-ARCH
Kernel parameters: "amd_iommu=on iommu=pt loglevel=3 quiet"

mkinitcpio.conf (comments are ommited)
MODULES=(vfio_pci vfio vfio_iommu_type1 vfio_virqfd) BINARIES=() FILES=() HOOKS=(base udev autodetect modconf block filesystems keyboard fsck) 
/etc/modprobe.d/vfio.conf
options vfio_pci ids=1002:731f,1002:ab38 
iommu groups
IOMMU Group 0: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU Group 1: 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU Group 10: 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] IOMMU Group 11: 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) IOMMU Group 12: 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467] IOMMU Group 13: 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] IOMMU Group 14: 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02) 02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller [1022:43b5] (rev 02) 02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port [1022:43b0] (rev 02) 03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 03:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) 04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] 05:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU Group 15: 0a:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1478] (rev c1) IOMMU Group 16: 0b:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1479] IOMMU Group 17: 0c:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5700 / 5700 XT] [1002:731f] (rev c1) IOMMU Group 18: 0c:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38] IOMMU Group 19: 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] IOMMU Group 2: 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU Group 20: 0d:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456] IOMMU Group 21: 0d:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller [1022:145c] IOMMU Group 22: 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455] IOMMU Group 23: 0e:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 24: 0e:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457] IOMMU Group 3: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU Group 4: 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU Group 5: 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] IOMMU Group 6: 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU Group 7: 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] IOMMU Group 8: 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] IOMMU Group 9: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] 
xml
 win10 facb7abd-ac3e-4a04-8e86-d6944b62d723      8388608 8388608 16  hvm /usshare/ovmf/x64/OVMF_CODE.fd /valib/libvirt/qemu/nvram/win10_VARS.fd                      destroy restart destroy      /usbin/qemu-system-x86_64     
Output of "dmesg | grep vfio" before starting vm
[ 1.279191] vfio-pci 0000:0c:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.293682] vfio_pci: add [1002:731f[ffffffff:ffffffff]] class 0x000000/00000000 [ 1.310411] vfio_pci: add [1002:ab38[ffffffff:ffffffff]] class 0x000000/00000000 
full output: https://pastebin.com/UVaxAWWU

Output of "dmesg | grep vfio" after starting vm
[ 1.279191] vfio-pci 0000:0c:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.293682] vfio_pci: add [1002:731f[ffffffff:ffffffff]] class 0x000000/00000000 [ 1.310411] vfio_pci: add [1002:ab38[ffffffff:ffffffff]] class 0x000000/00000000 [ 358.866916] vfio-pci 0000:0c:00.0: vfio_ecap_init: hiding ecap [email protected] [ 358.866927] vfio-pci 0000:0c:00.0: vfio_ecap_init: hiding ecap [email protected] [ 358.866930] vfio-pci 0000:0c:00.0: vfio_ecap_init: hiding ecap [email protected] [ 358.866931] vfio-pci 0000:0c:00.0: vfio_ecap_init: hiding ecap [email protected] [ 358.866933] vfio-pci 0000:0c:00.0: vfio_ecap_init: hiding ecap [email protected] [ 358.867808] vfio-pci 0000:0c:00.0: BAR 0: can't reserve [mem 0xe0000000-0xefffffff 64bit pref] [ 361.571367] vfio-pci 0000:0c:00.0: No more image in the PCI ROM [ 361.571388] vfio-pci 0000:0c:00.0: No more image in the PCI ROM 
full output: https://pastebin.com/VyxF9Y88

Since I only have one gpu I am forwarding X11 to a laptop and running virt-manager from there, windows starts and works fine but on my main display I only get a blinking cursor after starting the vm.

Edit: Thanks to u/cybervseas and this post https://www.reddit.com/VFIO/comments/7kpw33/cant_passthrough_boot_gpu_did_i_miss_something/ I got the vm working.
I added a line to the xml file that points to the rom file to be used. You can get that file from https://www.techpowerup.com/vgabios/ , download gpu-z and dump it or any other way to get the rom of your gpu.
    
The last thing was changing some settings in grub. I added the kernel parameter 'nofb' and changed GRUB_GFXPAYLOAD from 'keep' to 'text' in the file at /etc/default/grub.
Everything seems to work now I am writing this from inside the vm and I had no problems with the driver installation it works the same way as if windows was the host os.
submitted by diogo464 to VFIO [link] [comments]

Game NCCH and CDN Encryption (an explanation)

Game and CDN Encryption

Overview

There's been a lot of misinformation going around since the Sun/Moon demo's been announced, and I've come to realize people really don't understand how game encryption works on the 3DS.
I'd like to try to correct that.
Please note that the earlier parts of this post have been plagiarized liberally from topkeknosnek's wonderful explanation of the eShop and CDN's encryption.
The parts past CDN encryption are less plagiarized.
(To skip the bits that aren't relevant for physical game cartridges, jump to step 4.)

Overview

Very abstractly spoken, this is what happens when you purchase and download a game from the eShop:
  1. The game is purchased via eShop.
  2. eShop causes the download and installation of the ticket for the title.
  3. 3DS downloads the tmd and CDN contents.
  4. (3a) 3DS decrypts and installs the CDN contents.
  5. (3b) 3DS verifies the SHA-256 hash of the decrypted CDN contents.
You probably barely got any of that, so let's break it down.

Step 1: eShop Title Purchase

First, the game to download needs to be purchased.
Some terminology: eShop games are called "titles". The term "titles" is broader than that, however, and includes every part of the system firmware, such as NATIVE_FIRM or the HOME Menu.
The eShop application on the 3DS ("tiger") sends a request to the eShop server called ninja -- there are multiple eShop servers, but ninja is the relevant one for purchase-related things. In that request, tiger asks for purchase of a certain title.
ninja then verifies whether tiger is actually authenticated and if the associated account has the required balance. If not, an error is returned to tiger. If yes, the purchase is processed and tiger is notified about that. From then on, the respective title is associated with its respective NNID.

Step 2: Ticket Download

Once the eShop has been notified of the successful purchase, it calls the nim system module to download and install the ticket for the purchased title. The nim service is a service in the 3DS's firmware that handles downloading and installing CDN contents, including the firmware itself.

Tickets

A ticket describes a digital entitlement to a certain CDN content. A ticket can be either unique, in which case it contains a console ID and an eShop account ID. Or it can be a cetk (Common E-Ticket), which is valid for all consoles.
Of particular interest in a ticket is the titlekey. The titlekey is an encryption key that is used to decrypt the CDN contents. Guessing it blindly (brute forcing it) is currently considered computationally infeasible.
Furthermore, a ticket contains the amount of times a title can be launched. This is effectively only used for demos. The current amount of times the title can be launched, however, is kept track of by the HOME Menu. For this reason, HANS, regionthree and similar launchers can bypass the demo launch limit.
Tickets are always signed by Nintendo (RSA-2048 over a SHA-256 hash with PKCS#1 padding), meaning they cannot be forged. This signature is also checked every time the title is launched. Finding the private key to the public key is currently considered computationally infeasible.

Step 3: TMDs and Contents

Once the ticket has been installed, nim will then download and install the title. This is done in two steps: Downloading and verifying the TMD, then downloading and verifying the CDN contents.

Step 3a: TMD

First, nim downloads the TMD for a given title.
A TMD (title metadata) contains information about the contents themselves: The number of contents and their respective SHA-256 hashes.
TMDs are always signed by Nintendo (RSA-2048 over a SHA-256 hash with PKCS#1 padding), meaning they cannot be forged.

Step 3b: Contents

Once the TMD has been obtained, nim proceeds to download the contents described in the TMD.
All contents on the CDN have a layer of encryption around them (AES-128-CBC; the IV is the content index as described by the TMD, then 14 bytes of zeroes are appended). This is sometimes called the "outer" encryption because contents themselves can have encryption inside as well.
A content is just an NCCH after decryption. An NCCH is, simply put, something the 3DS can work with: A bundle of resources (CFA, CTR File Archive, such as the digital manuals) or an executable (CXI, CTR eXecutable Image).
While nim downloads, decrypts and installs the contents, it also hashes the contents (SHA-256). Hashing is the process of taking an input of arbitrary length and getting a fixed-length (hopefully unique) number. Finding the file that belongs to a hash, or a different file that has the same hash, is -- for a good hash function -- computationally infeasible. Spoiler: SHA-256 is a good hash function.
If the SHA-256 of any one of the decrypted contents mismatches the hash in the TMD (which is signed), nim fails the installation and removes the partially installed title.

Step 4: NCCH Decryption

As mentioned before, a game consists of one or more NCCH archives, where an NCCH is a special type of archive that the console knows how to work with.
Game decryption consists of validating the NCCH's signatures, and then decrypting its various partitions.
An NCCH generally consists of the following partitions:
The encrypted partitions can, optionally, be stored decrypted instead, but no commercial title would ever elect to make use of that option (for obvious reasons), so I will be assuming NCCHs are always encrypted for the remainder of this post.
It's also worth nothing that the three additional partitions are all optional -- manuals have no Extended Header or ExeFS, for example.

Step 4a: NCCH signature verification

The first 256 bytes of any NCCH consists of an RSA-2048 signature over the SHA-256 hash of the remaining 256-bytes of the header. This signature, as with all RSA-2048 signatures, is computationally infeasible to break, and so verifies the validity of the following header metadata.
Once the NCCH's header has been verified, the system will proceed to read the metadata for the other partitions, and decrypt them to verify their SHA-256 hashes, which are stored in the header.

Step 4b: NCCH partition decryption

NCCH partitions are encrypted with one of (as of October 9th, 2016) five (really six) possible key derivation schemes. Sound confusing? It is. The system originally only had two schemes, but as they were cracked and the system began to be penetrated by homebrew users, Nintendo cooked up new and more complex schemes to prevent unauthorized users from decrypting NCCH contents.
Once the key has been derived, though, NCCH decryption is relatively simple -- each partition is protected by AES-CTR encryption, using the Title ID and Partition type (Extended Header, ExeFS, or RomFS) as a CTInitialization Vector. As such, I'll mostly be focused on explaining the various key derivation schemes, as they're the meat of how NCCH files are protected.

Scheme 0: Fixed-key encryption

The first, and simplest key derivation scheme. Used presumably for testing in the early stages of the 3DS's development and for legacy support, partitions are protected using a key that consists entirely of zeros. This is not very secure, obviously, and so titles that use this encryption method can be easily decrypted on a PC. This isn't really used by anything, but it merits mentioning because it's the key scheme Gateway allowed users to use when they began to allow users to run homebrew from their red cart, way back in the early days of the scene. Scheme 0 is also the type of encryption used by the SDK for testing games on dev units.

Scheme 1: Secure1 encryption

The second key derivation scheme, and the simplest of the ones that do real key derivation. Before I can explain how it works, one should know that the 3DS has a hardware engine devoted to doing AES encryption and decryption which also serves a second purpose as a "Keyscrambler". The keyscrambler, originally introduced with the DSi, allows Nintendo to "mix" two keys together to calculate a third key. The keyscrambler is write-only -- which means that even though you can use the secret keys made by scrambling together two input keys, you can't read them or learn what they are. The hardware engine also has some number of keyslots, each of which is devoted to a particular kind of encryption, so that it can keep track of many mixed-together secret keys without removing access to the others.
Some terminology:
With that out of the way, Secure1 uses a fairly basic method to derive the secret encryption key. The bootrom (the unchangable code that runs early in the console's boot, which locks access to itself away as soon as it's done executing) initializes the 44th (0x2C) keyslot by writing secret data to the KeyX. When an NCCH using Secure1 needs to decrypt one of its partitions, it writes the first 16 bytes from the header's signature to the KeyY, and uses the resulting secret key to decrypt the partition's contents. This is clever, because using part of the signature to calculate the secret key discourages an attacker from trying to modify the signature -- doing so would make the partitions decrypt incorrectly!
Secure1 is a good scheme. That said, when the system was first compromised at the Kernel9 level, Nintendo realized people could decrypt titles and worked to create a new scheme that would keep content safe even with the system itself compromised.

Scheme 2: Secure2 encryption

The third key derivation scheme, introduced with firmware 7.0. Having realized that Secure1 had been compromised due to the 4.5 ARM9 exploits, Nintendo implemented this scheme to prevent content decryption without a new ARM9 exploit on higher firmwares. They accomplished this fairly ingeniously: the bootrom, in addition to initializing the hardware keyslots, initializes some RSA data that went unused, and got overwritten later on during the firmware's bootup process. Nintendo added code that runs early on in the firmware boot that checks whether this RSA data is still present. If so, firmware will perform RSA encryption on some static data, then hash the resulting encrypted data with SHA-256. The second 16 bytes of this SHA-256 hash is then used to initialize the 37th (0x25) keyslot's KeyX, and firmware will overwrite the RSA data to prevent its being used after the system is fully booted up.
Secure2 decryption proceeds much the same way as Secure1, afterwards. The Extended header and ExeFS still largely use keyslot 0x2C for encryption using the Secure1 secret key methodology. However, the ExeFS's code binary and RomFS get special treatment -- they use keyslot 0x25 instead of keyslot 0x2C.
That scheme was, for a while, secure -- the data is already overwritten by the time attackers got ARM9 code execution on 4.0. Since the Extended header, and title's 3D banneicon still use the old form of encryption, to an older system the title will display correctly in the home menu, but when it comes time for the title to launch the game's code and RomFS will fail to decrypt correctly -- and thus Nintendo achieved backwards compatibility while keeping the important bits of a title's content secure and out of the hands of unauthorized users.
However, Gateway got a hold of the data used to initialize keyslot 0x25 somehow. Nobody's actually sure how this happened! Gateway's obtaining the key meant, though, that they included it in their exploit, and it was eventually extracted and leaked to the public by an anonymous user known as "K" on October 25th, 2014. Nintendo's sytem was thus once more insecure -- and so they needed to fix that.

Scheme 3: Secure3 encryption

With the release of the N3DS, Nintendo added a new, N3DS-exclusive encryption method in Secure3. The N3DS, as anyone who uses A9LH will know, added a new 512-byte sector of encrypted secret data to the console's NAND, and a new loader to firmware. This loader decrypted the first 16-bytes of the secret sector using the SHA-256 hash of first 144 bytes from the console's OTP data, initializes a temporary (0x11) keyslot with those first 16-bytes, then locks out access to the OTP. It then verifies the key it read from NAND, uses the temporary keyslot to decrypt some static data to initialize the 21st (0x15) keyslot and other static data to initialize the 24th (0x18) through the 31st (0x1F) keyslots, then uses keyslot 0x15 to decrypt the rest of the N3DS's firmware.
Secure3 encryption works exactly the same as Secure2 encryption, except where Secure2 would use keyslot 0x25, Secure3 uses keyslot 0x18.
This scheme was, once more, seemingly secure -- as far as Nintendo knew, nobody could access the OTP, and thus nobody could decrypt the secret data in NAND to get the new NCCH key. However, Nintendo made a mistake -- the close reader will notice they forgot to clear their temporary keyslot 0x11 after using it, and so once people gained ARM9 code execution on a New 3DS, they could use keyslot 0x11 to decrypt firmware and regenerate the missing keys, once more breaking nintendo's scheme. Nintendo fixed this in their 9.6 update, introducing their next two schemes.

Scheme 4: Secure4 encryption

Introduced in Firmware 9.6.0, Nintendo sought to fix their mistake in Secure3 by using a different set of 16 bytes from the encrypted secret data in NAND to decrypt firmware and calculate further encryption keys. They did this by initializing their temporary keyslot 0x11 with the second 16-bytes from the secret sector the same way they did with the first 16, then lock out the OTP. They then use the temporary keyslot to decrypt some static data to initialize the 22nd (0x16) keyslot and other static data to initialize the 25th (0x19) through the 31st (0x1F) keyslots, then uses keyslot 0x16 to decrypt the rest of the N3DS's firmware (They leave the 24th keyslot initialized the same way as before, to retain compatibility with Secure3-protected titles). They also properly clear their temporary keyslot (0x11) when done.
Secure4 encryption works as Secure3 and Secure2 do, except using keyslot 0x1B in place of 0x18/0x25.
This scheme was secure for a long while. However, people eventually noticed that Nintendo made a fatal flaw in their implementation -- they forgot to verify keyslot 0x16 before using it to decrypt firmware. The secret sector was leaked on pastebin by an anonymous user known as "K" on January 12th, 2016, and, thus, by random brute force or by obtaining OTP, one can replace the key in NAND with a calculated one to gain pre-kernel code access on N3DS or O3DS known usually as "arm9loaderhax", sometimes "kernel9loaderhax", and occasionally to the very stupid as "Gateway Fast-Boot". Arm9loaderhax breaks Secure4 entirely -- and prevents Nintendo from ever using the secret sector again for additional encryption schemes, and from using other miscellaneous bootrom-initialized data. It also enables the user to calculate the key used for Secure2 encryption, though as it was leaked there's not much point to doing this. It also enables some other cool stuff with custom firmware, but from an encryption perspective that's relatively uninteresting and outside of the scope of this post.

Scheme 5: Seed encryption

Introduced alongside Secure4, Seed encryption isn't actually separate from the other schemes! It can be used alongside Secure2, Secure3, or Secure4, as an additional protection layer for certain titles. The motivation behind Seed encryption was that Nintendo wanted to allow users to purchase titles and download them in advance of their release date, but not let users play them before release date arrived. The old encryption methods had no way to support this -- purchasing a title gives its titlekey, which enables decryption, and once a title has been decrypted none of the schemes had any concept of release date protection -- they just use the first 16 bytes NCCH signature mixed with some other secret data (varying by Secure# scheme) to derive the secret key.
Seed encryption fixes this problem. Nintendo added a new server ("kagiya") to their CDN which stores 16-byte "external seeds", also known as "content lock seeds", "ext seeds", "ext keys", and any number of other names. These seeds are unique to each title that uses the encryption scheme. If a title uses seed encryption, then whenever it is launched Nintendo will attempt to retrieve the title's seed from SEEDDB. Failing that, the user will be prompted to download a "small update" from the eShop, which consists of the console trying to retrieve the seed from kagiya, and storing the seed in SEEDDB for future easy access.
Supposing the console succeeds in retrieving the seed from SEEDDB, it will then calculate the SHA256 hash of the first 16 bytes of the NCCH's signature and the 16 byte external seed. If the partition being decrypted would use Secure1's keyslot 0x2C, decryption proceeds per normal. However, if the partition is code or the title's RomFS, the system will instead use this SHA256 hash as the KeyY for whatever keyslot the secondary encryption scheme would use (0x25 for Secure2, 0x18 for Secure3, and 0x1B for Secure4).
This scheme adds no security after a title's release date, but it enables exactly the pre-purchasing behavior Nintendo wanted -- Nintendo can hold off on releasing the external seed for a title until its release date, while allowing users to purchase the title beforehand. Purchasing the title will let users download the title to their console and decrypt the CDN contents with the titlekey -- users can also preview the icon and 3d banner, as they will use the old 0x2C Secure1 encryption. However, because code and RomFS partitions will use a secret key that requires the content seed to calculate, they cannot be accessed prior to release date when Nintendo publishes the title's seed to their Kagiya server.

Practical Impact

All Secure# methods have been broken, at this point. Anyone with a console and arm9loaderhax can make use of the 3ds's hardware AES engine to decrypt content using any of the Secure1/2/3/4 schemes. Further, Nintendo cannot introduce new schemes, as there is no bootrom-initialized data that a future kernel9loader could access that vulnerable versions can't similarly access. Introducing a new scheme would require a new hardware revision, and with the NX on the horizon that seems unlikely to happen.
However, you may notice that Secure2/3/4 use calculated data for their KeyX, whereas Secure1 uses bootrom-initialized data. This means, in practice, that since the 3DS's keyscrambler algorithm was broken at 32c3 by yellows8 and plutoo, we can calculate the scrambled secret keys for those schemes on our PCs without any need for a console. Ironically, this means Secure1 is actually more secure than Secure2/Secure3/Secure4 -- any titles making use of later schemes can have their code and RomFSs be decrypted on PC, but Secure1 can only be decrypted by making use of a hacked 3DS console. Nintendo would actually be better off by no longer using Secure2/3/4, and by switching back exclusively to Secure1, which will remain permanently secure unless the 3DS's bootrom somehow gets dumped.
Further, seed encryption prevents titles from being played ahead of their release dates even if their titlekys are public knowledge. This means that when, for example, Pokemon Sun and Moon become available for prepurchase in the next month, even though their titlekeys will be public and usable with piracy tools the games won't be playable or capable of being decrypted before the official release date.
It is worth nothing, however, seed encryption is for downloadable eShop titles only -- no physical cartridge will ever make use of it.

And a bit of trivia

Even though content lock seeds should never be published ahead of time, Nintendo can be a bit careless with them -- they're fairly often released when they shouldn't be, enabling pre-release date access to some games. The Legend of Zelda: Triforce Heroes, for example, had its content lock seed published a month before its release date, despite being pre-purchasable. This meant that anyone who was paying attention could have been playing that game several weeks in advance, though I don't know that anyone publically exploited this.
submitted by SciresM to 3dshacks [link] [comments]

SMBIOS erros in boot.log

I'm having problems with my audio lagging behind my video, both with the internal motherboard Realtec 1155 card but also with my RME Firewire 400. Toledo on Tonymac86 mentioned the following error in my boot.log as a cause, but hasn't really given me any leads as to fix?
I've googled and trawled both of the large hack websites but can't seem to find a fix, i'd be happy to just get my fireface400 working at this points i want to use the hack for music production.
Gigabyte X99P-SLi motherboard Intel 6800k CPU Latest clover
0:100 0:100 MemLog inited, TSC freq: 3400001489 0:100 0:000 0:100 0:000 Now is 27.8.2016, 6:5:11 (GMT) 0:100 0:000 Starting Clover rev 3625 on American Megatrends EFI 0:100 0:000 Build with: [Args: ./ebuild.sh -D NO_GRUB_DRIVERS_EMBEDDED | Command: build -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -p CloveClover.dsc -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.11.6 | XCODE: 7.3.1] 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,9B252EA9-F7E0-4271-AE43-CE40F53C2F6D,0x28,0x64000) @B20D2698 0:100 0:000 SelfDirPath = \EFI\BOOT 0:100 0:000 Total Memory Slots Count = 8 0:100 0:000 Type 17 Index = 0 0:100 0:000 SmbiosTable.Type17->Speed = 2133MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A1 0:100 0:000 SmbiosTable.Type17->Vendor = Undefined 0:100 0:000 SmbiosTable.Type17->SerialNumber = 00000000 0:100 0:000 SmbiosTable.Type17->PartNumber = F4-3200C16-8GTZSW 0:100 0:000 Type 17 Index = 1 0:100 0:000 Ignoring insane frequency value 0MHz 0:100 0:000 SmbiosTable.Type17->Speed = 0MHz 0:100 0:000 SmbiosTable.Type17->Size = 0MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A2 0:100 0:000 SmbiosTable.Type17->Vendor = 0:100 0:000 SmbiosTable.Type17->SerialNumber = 0:100 0:000 SmbiosTable.Type17->PartNumber = 0:100 0:000 Type 17 Index = 2 0:100 0:000 SmbiosTable.Type17->Speed = 2133MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B1 0:100 0:000 SmbiosTable.Type17->Vendor = Undefined 0:100 0:000 SmbiosTable.Type17->SerialNumber = 00000000 0:100 0:000 SmbiosTable.Type17->PartNumber = F4-3200C16-8GTZSW 0:100 0:000 Type 17 Index = 3 0:100 0:000 Ignoring insane frequency value 0MHz 0:100 0:000 SmbiosTable.Type17->Speed = 0MHz 0:100 0:000 SmbiosTable.Type17->Size = 0MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B2 0:100 0:000 SmbiosTable.Type17->Vendor = 0:100 0:000 SmbiosTable.Type17->SerialNumber = 0:100 0:000 SmbiosTable.Type17->PartNumber = 0:100 0:000 Type 17 Index = 4 0:100 0:000 SmbiosTable.Type17->Speed = 2133MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_C1 0:100 0:000 SmbiosTable.Type17->Vendor = Undefined 0:100 0:000 SmbiosTable.Type17->SerialNumber = 00000000 0:100 0:000 SmbiosTable.Type17->PartNumber = F4-3200C16-8GTZSW 0:100 0:000 Type 17 Index = 5 0:100 0:000 Ignoring insane frequency value 0MHz 0:100 0:000 SmbiosTable.Type17->Speed = 0MHz 0:100 0:000 SmbiosTable.Type17->Size = 0MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_C2 0:100 0:000 SmbiosTable.Type17->Vendor = 0:100 0:000 SmbiosTable.Type17->SerialNumber = 0:100 0:000 SmbiosTable.Type17->PartNumber = 0:100 0:000 Type 17 Index = 6 0:100 0:000 SmbiosTable.Type17->Speed = 2133MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_D1 0:100 0:000 SmbiosTable.Type17->Vendor = Undefined 0:100 0:000 SmbiosTable.Type17->SerialNumber = 00000000 0:100 0:000 SmbiosTable.Type17->PartNumber = F4-3200C16-8GTZSW 0:100 0:000 Type 17 Index = 7 0:100 0:000 Ignoring insane frequency value 0MHz 0:100 0:000 SmbiosTable.Type17->Speed = 0MHz 0:100 0:000 SmbiosTable.Type17->Size = 0MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_D2 0:100 0:000 SmbiosTable.Type17->Vendor = 0:100 0:000 SmbiosTable.Type17->SerialNumber = 0:100 0:000 SmbiosTable.Type17->PartNumber = 0:100 0:000 Boot status=0 0:100 0:000 Clover revision: 3625 running on Default string 0:100 0:000 ... with board X99P-SLI-CF 0:100 0:000 CPU Vendor = 756E6547 Model=406F1 0:100 0:000 got cores from CPUID_1 = 0 0:100 0:000 The CPU supported turbo 0:100 0:000 BrandString = Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz 0:100 0:000 FSBFrequency=100MHz DMIvalue=100000kHz 0:100 0:000 Corrected FSBFrequency=100MHz 0:100 0:000 VendoModel/Stepping: 0x756E6547/0x4F/0x1 0:100 0:000 Family/ExtFamily: 0x6/0x0 0:100 0:000 MaxDiv/MinDiv: 38.0/6 0:100 0:000 Turbo: 0/0/0/0 0:100 0:000 Features: 0xBFEBFBFF 0:100 0:000 Threads: 12 0:100 0:000 Cores: 6 0:100 0:000 FSB: 100 MHz 0:100 0:000 CPU: 3800 MHz 0:100 0:000 TSC: 3800 MHz 0:100 0:000 PIS: 400 MHz 0:100 0:000 PCI (00|00:00.00) : 8086 6F00 class=060000 0:100 0:000 PCI (00|00:01.00) : 8086 6F02 class=060400 0:100 0:000 PCI (00|00:01.01) : 8086 6F03 class=060400 0:100 0:000 PCI (00|00:03.00) : 8086 6F08 class=060400 0:100 0:000 PCI (00|4B:00.00) : 10DE 128B class=030000 0:100 0:000 Found NVidia model=Unknown family 106 0:100 0:000 PCI (00|4B:00.01) : 10DE 0E0F class=040300 0:100 0:000 PCI (00|00:05.00) : 8086 6F28 class=088000 0:100 0:000 PCI (00|00:05.01) : 8086 6F29 class=088000 0:100 0:000 PCI (00|00:05.02) : 8086 6F2A class=088000 0:100 0:000 PCI (00|00:05.06) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.00) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.01) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.02) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.03) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.04) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.05) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.06) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:06.07) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:07.00) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:07.01) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:07.02) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:07.03) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:07.04) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:11.00) : 8086 8D7C class=FF0000 0:100 0:000 PCI (00|00:14.00) : 8086 8D31 class=0C0330 0:100 0:000 PCI (00|00:16.00) : 8086 8D3A class=078000 0:100 0:000 PCI (00|00:16.01) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:16.02) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:16.03) : FFFF FFFF class=FFFFFF 0:100 0:000 PCI (00|00:19.00) : 8086 15A1 class=020000 0:100 0:000 LAN 0, Vendor=8086, MMIO=DF400000 0:100 0:000 PCI (00|00:1A.00) : 8086 8D2D class=0C0320 0:100 0:000 PCI (00|00:1B.00) : 8086 8D20 class=040300 0:100 0:000 PCI (00|00:1C.00) : 8086 8D10 class=060400 0:100 0:000 PCI (00|00:1C.03) : 8086 8D16 class=060400 0:100 0:000 PCI (00|4D:00.00) : 104C 823E class=060400 0:100 0:000 PCI (00|4E:00.00) : 104C 823F class=0C0010 0:100 0:000 PCI (00|00:1C.04) : 8086 8D18 class=060400 0:100 0:000 PCI (00|4F:00.00) : 144D A802 class=010802 0:100 0:000 PCI (00|00:1D.00) : 8086 8D26 class=0C0320 0:100 0:000 PCI (00|00:1F.00) : 8086 8D47 class=060100 0:100 0:000 PCI (00|00:1F.02) : 8086 8D02 class=010601 0:100 0:000 PCI (00|00:1F.03) : 8086 8D22 class=0C0500 0:100 0:000 PCI (00|00:1F.06) : FFFF FFFF class=FFFFFF 0:100 0:000 Clover load options size = 0 bytes 0:104 0:003 Using OEM config.plist at path: EFI\CLOVER\config.plist 0:104 0:000 EFI\CLOVER\config.plist loaded: Success 0:105 0:001 Found theme directory: embedded 0:106 0:001 Found theme directory: random 0:107 0:001 Loading early settings 0:107 0:000 timeout set to 20 0:107 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 0:107 0:000 Config set FakeCPUID=306A0 0:107 0:000 ForceKextsToLoad: 1 requested 0:107 0:000 ForceKextsToLoad 0: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext 0:107 0:000 KextsToPatch: 4 requested 0:107 0:000 KextsToPatch 0: AppleUSBXHCIPCI (Change 15 Port Limit To 30 in XHCI 10.11 (99-series)) :: Kext bin patch, data len: 8 0:107 0:000 KextsToPatch 1: AirPortBrcm4360 (5GHz Patch) :: Kext bin patch, data len: 7 0:107 0:000 KextsToPatch 2: AppleGraphicsDevicePolicy (AppleGraphicsDevicePolicy (board-id) Patch (c) Pike R. Alpha) :: Kext bin patch, data len: 8 0:107 0:000 KextsToPatch 3: IOPCIFamily (5960XPatch by Brumbaer) :: Kext bin patch, data len: 7 0:107 0:000 Default theme: El Capitan 0:107 0:000 Hiding entries with string Windows 0:107 0:000 Hiding entries with string BOOTX64.EFI 0:107 0:000 LoadDrivers() start 0:107 0:000 Loading FSInject-64.efi status=Success 0:107 0:000 Loading OsxAptioFix2Drv-64.efi status=Success 0:108 0:000 Loading OsxFatBinaryDrv-64.efi status=Success 0:108 0:000 Loading Test2.efi status=Success 0:108 0:000 Loading NvmExpressDxe-64.efi status=Success 0:109 0:001 - driver needs connecting 0:109 0:000 Loading HFSPlus.efi status=Success 0:111 0:001 - driver needs connecting 0:111 0:000 2 drivers needs connecting ... 0:111 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 0:111 0:000 HFS+ driver loaded 0:111 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 0:205 0:094 LoadDrivers() end 0:205 0:000 Dump SMC keys from NVRAM: 0:209 0:003 SetMaxResolution: found best mode 5: 1920x1200 0:596 0:386 Video mode change to mode #5: Success 0:596 0:000 - set 0:596 0:000 Console modes reported: 5, available modes: 0:596 0:000 Mode 1: 80x25 (current mode) 0:596 0:000 Mode 2: 80x50 0:596 0:000 Mode 3: 100x31 0:596 0:000 Mode 4: 127x33 0:596 0:000 Mode 5: 100x60 0:596 0:000 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,9B252EA9-F7E0-4271-AE43-CE40F53C2F6D,0x28,0x64000) 1:536 0:940 MAC address of LAN #0= 40:8D:5C:B8:E3:6D: 1:536 0:000 ScanSPD() start 1:536 0:000 SMBus device : 8086 8D22 class=0C0500 status=Success 1:536 0:000 SMBus CmdReg: 0x1 1:536 0:000 Scanning SMBus [8086:8D22], mmio: 0xDF435004, ioport: 0x580, hostc: 0x11 1:536 0:000 Slots to scan [8]... 1:537 0:001 ScanSPD() end 1:537 0:000 Get Acpi Tables List from RSDT: 1:537 0:000 Found table: FACP A M I len=132 1:537 0:000 Found table: APIC A M I len=244 1:537 0:000 Found table: FPDT A M I len=68 1:537 0:000 Found table: FIDT A M I len=156 1:537 0:000 Found table: MCFG A M I len=60 1:537 0:000 Found table: SSDT SataTabl len=877 1:537 0:000 Found table: UEFI A M I len=66 1:537 0:000 Found table: HPET A M I len=56 1:537 0:000 Found table: MSCT A M I len=144 1:537 0:000 Found table: SLIT A M I len=45 1:537 0:000 Found table: SRAT A M I len=4440 1:537 0:000 Found table: WDDT A M I len=64 1:537 0:000 Found table: SSDT PmMgt len=67162 1:537 0:000 Found table: NITR A M I len=113 1:537 0:000 Found table: BGRT ALASKAA len=56 1:537 0:000 Found table: ASF! HCG len=160 1:537 0:000 Calibrated TSC frequency =3400001489 =3400MHz 1:538 0:000 Loading main settings 1:538 0:000 Dropping 2 tables 1:538 0:000 Drop table 0 signature="DMAR" (52414D44) 1:538 0:000 set table: 52414D44, 0 to drop: 1:538 0:000 Drop table 1 signature="SSDT" (54445353) table-id="PmMgt" (00000074674D6D50) 1:538 0:000 set table: 54445353, 74674D6D50 to drop: true 1:538 0:000 1:538 0:000 Config set ChassisType=0x6 1:540 0:002 found 8 volumes with blockIO 1:540 0:000 0. Volume: 1:540 0:000 PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,43-19-B0-61-56-38-25-00) 1:541 0:001 1. Volume: 1:541 0:000 PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,43-19-B0-61-56-38-25-00)\HD(1,GPT,52395F77-6E59-4EDC-91E4-56124BF7316A,0x28,0x64000) 1:542 0:001 Result of bootcode detection: bootable unknown (legacy) 1:546 0:004 2. Volume: 1:546 0:000 PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,43-19-B0-61-56-38-25-00)\HD(2,GPT,656B3604-7829-4A56-9632-D235CE4A5AAC,0x64028,0x3B807340) 1:547 0:001 3. Volume: 1:548 0:000 PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,43-19-B0-61-56-38-25-00)\HD(3,GPT,D7444DF5-424F-46FA-B564-7F8CE0EA5B18,0x3B8AB368,0x135F20) 1:549 0:001 4. Volume: 1:549 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0) 1:549 0:000 5. Volume: 1:549 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,9B252EA9-F7E0-4271-AE43-CE40F53C2F6D,0x28,0x64000) 1:550 0:000 Result of bootcode detection: bootable unknown (legacy) 1:550 0:000 This is SelfVolume !! 1:550 0:000 6. Volume: 1:550 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7012107D-62C0-46F8-AA9D-A38AA91BA894,0x64028,0x3A1EC0C0) 1:551 0:000 7. Volume: 1:551 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,F9C197E1-B014-4774-93EF-F9FACBF2D964,0x3A2500E8,0x135F20) 1:551 0:000 GlobalConfig: theme.plist not found, get random theme random 1:552 0:001 Using theme 'random' (EFI\CLOVER\themes\random) 1:552 0:000 Choosing theme random 1:552 0:000 Custom entries start 1:552 0:000 Custom entries finish 1:552 0:000 Scanning loaders... 1:552 0:000 0: 'Whole Disc Boot' no file system 1:552 0:000 1: 'NVMEFI' 1:568 0:016 2: 'NVME' 1:575 0:006 AddLoaderEntry for Volume Name=NVME 1:580 0:005 Check if volume Is Hibernated: 1:580 0:000 Check sleep image 'by signature': 1:584 0:004 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Not Found 1:584 0:000 using default sleep image name = \private\var\vm\sleepimage 1:588 0:004 sleepimage not found -> Not Found 1:588 0:000 hibernated: no - sign 1:589 0:000 Icon 17 (icons\vol_internal_hfs.icns) not found 1:589 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:590 0:001 3: 'Recovery HD' 1:591 0:001 AddLoaderEntry for Volume Name=Recovery HD 1:593 0:002 Icon 20 (icons\vol_recovery.icns) not found 1:593 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:594 0:000 4: 'Whole Disc Boot' no file system 1:594 0:000 5: 'OSEFI' 1:594 0:000 6: 'El Capitan' 1:596 0:001 AddLoaderEntry for Volume Name=El Capitan 1:599 0:002 Check if volume Is Hibernated: 1:599 0:000 Check sleep image 'by signature': 1:601 0:002 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Not Found 1:601 0:000 using default sleep image name = \private\var\vm\sleepimage 1:603 0:002 sleepimage not found -> Not Found 1:603 0:000 hibernated: no - sign 1:604 0:000 7: 'Recovery HD' 1:604 0:000 AddLoaderEntry for Volume Name=Recovery HD 1:605 0:000 Custom legacy start 1:605 0:000 Custom legacy end 1:605 0:000 Custom tool start 1:605 0:000 Custom tool end 1:605 0:000 Icon 8 (icons\tool_shell.png) not found 1:605 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:606 0:000 found tool \EFI\CLOVER\tools\Shell64U.efi 1:606 0:000 Checking EFI partition Volume 1 for Clover 1:612 0:006 Found Clover 1:612 0:000 Icon 2 (icons\func_clover.png) not found 1:612 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:612 0:000 Checking EFI partition Volume 5 for Clover 1:612 0:000 Found Clover 1:612 0:000 Icon 1 (icons\func_options.png) not found 1:612 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:612 0:000 Icon 0 (icons\func_about.png) not found 1:612 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:612 0:000 Icon 5 (icons\func_reset.png) not found 1:612 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:612 0:000 Icon 6 (icons\func_shutdown.png) not found 1:612 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:612 0:000 GetEfiBootDeviceFromNvram: efi-boot-device-data not found 1:612 0:000 EfiBootVolume not found 1:612 0:000 found entry 2. 'Boot Mac OS X from El Capitan', Volume 'El Capitan', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7012107D-62C0-46F8-AA9D-A38AA91BA894,0x64028,0x3A1EC0C0)\System\Library\CoreServices\boot.efi' 1:612 0:000 DefaultIndex=2 and MainMenu.EntryCount=11 1:612 0:000 banner file not read 1:700 0:088 InitScroll: MaxIndex=10, FirstVisible=0, MaxVisible=3, MaxFirstVisible=0 1:700 0:000 Icon 22 () not found 1:700 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:701 0:000 Icon 23 () not found 1:701 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:701 0:000 UpdateScroll on 6 1:709 0:007 Found Mouse device: 1:709 0:000 Icon 11 (icons\pointer.png) not found 1:709 0:000 Theme path EFI\CLOVER\themes\random, ThemeDir=B2ED7F20 1:711 0:001 GUI ready 3:552 1:841 Boot option Boot0000 not found 3:552 0:000 StartLoader() start 3:552 0:000 Finally: Bus=89473kHz CPU=3400MHz 3:552 0:000 Loading boot.efi status=Success 3:641 0:089 GetOSVersion: 10.11.6 3:641 0:000 Filtering KextPatches: 3:641 0:000 - Patch [0] "AppleUSBXHCIPCI" :: KextPatch :: [OS: 10.11.6 | MatchOS: undefined] ==> allowed 3:641 0:000 - Patch [1] "AirPortBrcm4360" :: KextPatch :: [OS: 10.11.6 | MatchOS: undefined] ==> allowed 3:641 0:000 - Patch [2] "AppleGraphicsDevicePolicy" :: KextPatch :: [OS: 10.11.6 | MatchOS: undefined] ==> allowed 3:641 0:000 - Patch [3] "IOPCIFamily" :: KextPatch :: [OS: 10.11.6 | MatchOS: undefined] ==> allowed 3:641 0:000 insert table 9 for dev 0:0 3:641 0:000 insert table 9 for dev 0:1 3:641 0:000 insert table 9 for dev 19:0 3:641 0:000 insert table 9 for dev 0:0 3:642 0:000 Injecting user memory modules to SMBIOS 3:642 0:000 Channels: 4 3:642 0:000 Interleave: 0 2 4 6 1 3 5 7 8 10 12 14 9 11 13 15 16 18 20 22 17 19 21 23 3:642 0:000 DIMM1 3200MHz 8192MB 3:642 0:000 DIMM2 EMPTY 3:642 0:000 DIMM3 3200MHz 8192MB 3:642 0:000 DIMM4 EMPTY 3:642 0:000 DIMM5 3200MHz 8192MB 3:642 0:000 DIMM6 EMPTY 3:642 0:000 DIMM7 3200MHz 8192MB 3:642 0:000 DIMM8 EMPTY 3:642 0:000 mTotalSystemMemory = 32768 3:642 0:000 NumberOfMemoryDevices = 8 3:642 0:000 Type20[0]->End = 0x7FFFFF, Type17[0] = 0x2000 3:642 0:000 Type20[1]->End = 0xFFFFFF, Type17[2] = 0x6000 3:642 0:000 Type20[2]->End = 0x17FFFFF, Type17[4] = 0xC000 3:642 0:000 Type20[3]->End = 0x1FFFFFF, Type17[6] = 0x14000 3:642 0:000 Table 131 is present, CPUType=10 3:642 0:000 Change to: 402 3:642 0:000 RSDT 0xB6383028 3:642 0:000 FADT from RSDT: 0xB6383148 3:642 0:000 XSDT 0xB6383090 3:642 0:000 FADT from XSDT: 0xB63B8050 3:642 0:000 Xsdt reallocation done 3:642 0:000 old FADT length=10C 3:642 0:000 Apply DsdtFixMask=0x00000000 old way 3:642 0:000 drop _DSM mask=0x0000 3:642 0:000 ========= Auto patch DSDT Starting ======== 3:642 0:000 VideoCard devID=0x128B10DE 3:642 0:000 DisplayADR1[0] = 0x30000, DisplayADR2[0] = 0x0 3:642 0:000 USBADR[0] = 0x140000 and PCIe = 0xFFFE 3:642 0:000 USBADR[1] = 0x1A0000 and PCIe = 0xFFFE 3:686 0:044 Audio HDA (addr:0x1B0000) setting specified layout-id=1 (0x1) 3:686 0:000 USBADR[2] = 0x1D0000 and PCIe = 0xFFFE 3:686 0:000 first CPU found at 2C25 offset 2C29 3:686 0:000 device candidate at 2B8C 3:686 0:000 device inserted in acpi_cpu_score SCK0 3:686 0:000 score candidate at 29A0 3:686 0:000 score inserted in acpi_cpu_score _SB_SCK0 3:686 0:000 Found ACPI CPU: CP00 And CP01 And CP02 And CP03 And CP04 And CP05 And CP06 And CP07 And CP08 And CP09 And CP0A And CP0B And CP0C And CP0D And CP0E And CP0F And CP10 And CP11 And CP12 And CP13 And CP14 And CP15 And CP16 And CP17 And CP18 And CP19 And CP1A And CP1B And CP1C And CP1D And CP1E And CP1F within the score: _SB_SCK0 3:686 0:000 Found PCIROOTUID = 0 3:686 0:000 ========= Auto patch DSDT Finished ======== 3:686 0:000 Drop tables from Xsdt, SIGN=SSDT TableID=PmMgt Length=67162 3:686 0:000 Xsdt has tables count=16 3:686 0:000 Table: SSDT PmMgt 67162 dropped 3:686 0:000 corrected XSDT length=156 3:686 0:000 Patch table: SSDT SataTabl 3:686 0:000 SSDT len = 0x36D 3:687 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0 3:687 0:000 Xsdt has tables count=15 3:687 0:000 corrected XSDT length=156 3:687 0:000 Start: Processing Patched AML(s): Unsorted 3:687 0:000 Inserting SSDT-HDEF-ALZA-2.aml from EFI\CLOVER\ACPI\patched ... Success 3:689 0:002 Inserting SSDT-NVME-1.aml from EFI\CLOVER\ACPI\patched ... Success 3:690 0:001 Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success 3:691 0:001 End: Processing Patched AML(s) 3:691 0:000 CPUBase=0 and ApicCPUBase=0 ApicCPUNum=12 3:691 0:000 Unsupported CPU (0x6): P-States not generated !!! 3:691 0:000 GeneratePStates failed: Status=Not Found 3:691 0:000 SSDT with CPU C-States generated successfully 3:691 0:000 EdidDiscovered size=128 3:691 0:000 00 | 00 FF FF FF FF FF FF 00 10 AC 15 F0 4C 4E 33 30 3:691 0:000 16 | 32 14 01 03 80 34 20 78 EE 1E C5 AE 4F 34 B1 26 3:691 0:000 32 | 0E 50 54 A5 4B 00 81 80 A9 40 D1 00 71 4F 01 01 3:691 0:000 48 | 01 01 01 01 01 01 28 3C 80 A0 70 B0 23 40 30 20 3:691 0:000 64 | 36 00 06 44 21 00 00 1A 00 00 00 FF 00 48 33 39 3:691 0:000 80 | 30 4D 30 43 38 30 33 4E 4C 0A 00 00 00 FC 00 44 3:691 0:000 96 | 45 4C 4C 20 55 32 34 31 30 0A 20 20 00 00 00 FD 3:691 0:000 112 | 00 38 4C 1E 51 11 00 0A 20 20 20 20 20 20 00 52 3:691 0:000 NVidia GFX injection not set 3:691 0:000 USB Controller [8086:8D31] :: PciRoot(0x0)\Pci(0x14,0x0) 3:691 0:000 LAN Controller [8086:15A1] :: PciRoot(0x0)\Pci(0x19,0x0) 3:691 0:000 USB Controller [8086:8D2D] :: PciRoot(0x0)\Pci(0x1A,0x0) 3:691 0:000 HDA Controller [8086:8D20] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1) 3:691 0:000 USB Controller [8086:8D26] :: PciRoot(0x0)\Pci(0x1D,0x0) 3:691 0:000 RCBA access disabled; trying to enable 3:691 0:000 stringlength = 2046 3:691 0:000 CurrentMode: Width=1920 Height=1200 3:691 0:000 Beginning FSInjection FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B20D2418 FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B20D2418 3:693 0:002 Force kext: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext 3:693 0:000 Failed to load extra kext (Info.plist not found): /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext 3:693 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 3:694 0:001 Extra kext: EFI\CLOVER\kexts\Other\AppleALC.kext 3:700 0:005 Extra PlugIn kext: EFI\CLOVER\kexts\Other\AppleALC.kext\Contents\PlugIns\PinConfigs.kext 3:701 0:001 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext 3:704 0:002 Extra kext: EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext 3:705 0:001 Extra kext: EFI\CLOVER\kexts\Other\NullCPUPowerManagement.kext 3:706 0:001 Extra kext: EFI\CLOVER\kexts\Other\USBInjectAll.kext 3:712 0:005 Extra kext: EFI\CLOVER\kexts\Other\VoodooTSCSync.kext 3:713 0:001 Extra kext: EFI\CLOVER\kexts\Other\HackrNVMeFamily-10_11_6.kext 3:718 0:004 Removed efi-boot-device-data variable: Not Found 3:718 0:000 Custom boot is disabled
submitted by ekwipt to hackintosh [link] [comments]

[Hacking Tutorial] Modifying Existing Weapons

It's been a while since I had one of these, but we're going to go through modifying weapons and adding custom ones. There's some new concepts in here for adding new items, so we're going to start simple with modifying existing weapons.
Things you'll need:
With that, let's get started. The first thing we're going to do is simple: modify stats of existing weapons.
  1. Open up Nightmare and open up the ROM and load up the Item Editor for your game (I assume you went through the other tutorials, so I won't have too many pictures for things covered earlier). You should see something like this for FE6.
  2. Things should be looking pretty obvious right now, so let's choose a weapon to modify. Let's just do Iron Lance, since that's easy to test. So go ahead and find Iron Lance in the list.
  3. Once you select it, all of the fields below will update with data for that item. Most things should be pretty straightforward, and modifying them should be pretty straightforward as well, but let's just go over them really quick.
  1. Whew, so let's just modify our Iron Lance already. We're going to modify it so that it looks like this. Yeah, it's OP.
  2. So let's check it out in game. Pssh. Yeah, "ordinary spear" my ass. Let's try it out, shall we?. I'm not sure I would have expected any different. Also, I'm pretty sure that's the Divinestone buff.
  3. So, there you go. How to break Fire Emblem 6 over your knee with an ordinary spear.
So I did mention you could do all of this without Nightmare as well. You should stop reading here if you want to keep your brain intact. I take no responsibility for massive confusion if you read on.
Here's your cheat sheet for doing it without Nightmare. You have to know where the weapon data lives in the ROM. You see, that nightmare module (nmm file) is actually human readable if you open it in a text editor. If you open up FE6's item editor, you'll find this:
FE6 Item Editor by SpyroDi, modified by Arch
0x60B648
128
32
FE6 Item Editor.txt
NULL
You can take a guess what that address I bolded there is. If you jump to that address in the hex, you'll find the start of weapon data. Each block for an item is 0x20 bytes (32 bytes, which corresponds to the other info in the module). Remember Iron Lance's ID? It was 0x10. That means it's the 16th item in the block. so if you do 16 x 32, you'll get 512, which is 0x200. If you jump to 0x60B648 + 0x200 (which is 0x60B848), you'll find your Iron Lance. So let's jump to it in our modified file.
What you'll see at that offset and the next 32 bytes for it is:
39 07 BE 05 00 00 10 01 21 01 00 00 B0 27 66 08 00 00 00 00 63 19 64 01 23 11 08 00 01 0F 00 00
Sweet jesus, what the fuck is this? Well, if you look closely and look at what we found earlier for Iron Lance, all of those values do actually match up. Remember the item name? The value there was 0739 in Nightmare. Remembering that GBA uses little endian, that corresponds to the first 2 bytes. The next two are the item description (which was 05BE in nightmare). The next two are the item description, which was blank (0000). Followed by the ID (0x10), weapon type (1 for spear), weapon ability 1 (0x20 is the brave effect, and 0x01 is the weapon trait, combine them together for 0x21), weapon ability 2 (0x01 is Reversing weapon triangle), 2 blank bytes (you'll see how we get this later), stat bonuses pointer (again, written in little endian order (we typed in 86627B0 earlier)), effectiveness pointer (which was nil, so 00000000), then durability (which was 99, or 0x63 in hex) and so on. Note that cost per use in this case is 2 bytes (since it could exceed 255, theoretically).
Note that this format is different across games, so you may have to figure out what you're modifying, but the general order is roughly the same. In fact, the nightmare module also tells you this information of what the bytes mean (including blank bytes from above) if you parse through it. Here's a sample from FE7's item editor nightmare module:
FE7 Item Editor by SpyroDi, updated by Nintenlord
0xBE222c Where the item data starts
159 How many items we have
36 The size of each item
FE7 Item Editor.txt
NULL
Item Name Pointer
0 The offset for the item name (i.e. how many bytes to skip from the beginning)
2 The number of bytes taken up by this field (i.e. how many bytes to read)
NEHU
NULL
The bold bits are mine.
Finally, what if you don't know the ID? Alongside the nightmare module for the item editor is also an Item List.txt file that holds the list of all IDs for all items. You can look it up there as well.
Just to prove this works, we're going to modify our weapon back to more reasonable levels. We'll remove the Divinestone buff and bring it down to more reasonable levels. The changes I made look like this in HxD, and you should be able to decipher what my values are going to be.
I changed the Iron Lance to this string of hex:
39 07 BE 05 00 00 10 01 21 01 00 00 00 00 00 00 00 00 00 00 3C 04 64 08 0A 11 08 00 01 0F 00 00
Take a moment and see if you can figure out what I changed it to. I bolded the changes. See if you're right here. It still breaks the game, but at least it breaks it more reasonably.
Believe it or not, this is the easy stuff. Making your own weapons? That shit is a lot more complicated, but if you know this, it'll make things a lot easier.
submitted by OtakuReborn to fireemblem [link] [comments]

Only one resolution available(1024x768) on 10.11.3

I disabled the internal graphic hd4600 Instead, I use the GALAX GT 610 as my graphic card. However it only shows the 1024x768 to me.
Here's my system info
Here's my config.list
https://gist.github.com/poc7667/c719d74e91f19d16ba5a
![inline](https://i.imgur.com/lHGIGCy.png =300x "Title")
![inline](https://i.imgur.com/oIkc46b.png =300x "Title")
![inline](https://i.imgur.com/o4w5X0C.png =300x "Title")
![inline](https://i.imgur.com/A4F4cVn.png =300x "Title")
![inline](https://i.imgur.com/6yHGxQ9.png =300x "Title")
This is my boot log
0:100 0:100 MemLog inited, TSC freq: 3200003850 0:100 0:000 0:100 0:000 Now is 28.1.2016, 0:38:33 (GMT+2047) 0:100 0:000 Starting Clover rev 3333 on American Megatrends EFI 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,1F52ECF2-39A5-4A6B-A149-760935D9EDD1,0x28,0x64000) @9F507518 0:100 0:000 SelfDirPath = \EFI\BOOT 0:100 0:000 Total Memory Slots Count = 4 0:100 0:000 Type 17 Index = 0 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0 0:100 0:000 Type 17 Index = 1 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1 0:100 0:000 Type 17 Index = 2 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 ChannelB-DIMM0 0:100 0:000 Type 17 Index = 3 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1 0:100 0:000 Boot status=0 0:100 0:000 Clover revision: 3333 running on Z97-D3H 0:100 0:000 ... with board Z97-D3H-CF 0:100 0:000 CPU Vendor = 756E6547 Model=306C3 0:100 0:000 The CPU supported turbo 0:100 0:000 BrandString = Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz 0:100 0:000 MSR 0xE2 before patch 1E000404 0:100 0:000 MSR 0xE4 00021814 0:100 0:000 MSR 0xCE 00080838F3012000 0:100 0:000 non-usable FLEX_RATIO = 10000 0:100 0:000 corrected FLEX_RATIO = 0 0:100 0:000 FSBFrequency=100MHz DMIvalue=100000kHz 0:100 0:000 Corrected FSBFrequency=100MHz 0:100 0:000 VendoModel/Stepping: 0x756E6547/0x3C/0x3 0:100 0:000 Family/ExtFamily: 0x6/0x0 0:100 0:000 MaxDiv/MinDiv: 32.0/8 0:100 0:000 Turbo: 32/33/34/34 0:100 0:000 Features: 0xBFEBFBFF 0:100 0:000 Threads: 4 0:100 0:000 Cores: 4 0:100 0:000 FSB: 100 MHz 0:100 0:000 CPU: 3200 MHz 0:100 0:000 TSC: 3200 MHz 0:100 0:000 PIS: 400 MHz 0:100 0:000 PCI (00|00:00.00) : 8086 0C00 class=060000 0:100 0:000 PCI (00|00:01.00) : 8086 0C01 class=060400 0:100 0:000 PCI (00|01:00.00) : 10DE 104A class=030000 0:100 0:000 Found NVidia model=nVidia GeForce GT 610 0:100 0:000 PCI (00|01:00.01) : 10DE 0E08 class=040300 0:100 0:000 PCI (00|00:02.00) : 8086 0412 class=030000 0:100 0:000 Found GFX model=Intel HD Graphics 4600 0:100 0:000 PCI (00|00:03.00) : 8086 0C0C class=040300 0:100 0:000 PCI (00|00:14.00) : 8086 8CB1 class=0C0330 0:100 0:000 PCI (00|00:16.00) : 8086 8CBA class=078000 0:100 0:000 PCI (00|00:19.00) : 8086 153B class=020000 0:100 0:000 LAN 0, Vendor=8086, MMIO=F7800000 0:100 0:000 PCI (00|00:1B.00) : 8086 8CA0 class=040300 0:100 0:000 PCI (00|00:1C.00) : 8086 8C90 class=060400 0:100 0:000 PCI (00|00:1C.03) : 8086 8C96 class=060400 0:100 0:000 PCI (00|03:00.00) : 8086 244E class=060401 0:100 0:000 PCI (00|00:1F.00) : 8086 8CC4 class=060100 0:100 0:000 PCI (00|00:1F.02) : 8086 8C82 class=010601 0:100 0:000 PCI (00|00:1F.03) : 8086 8CA2 class=0C0500 0:100 0:000 Clover load options size = 0 bytes 0:105 0:005 Using OEM config.plist at path: EFI\CLOVER\config.plist 0:105 0:000 EFI\CLOVER\config.plist loaded: Success 0:107 0:002 Found theme directory: applestyle 0:110 0:003 Found theme directory: EMBEDDED 0:111 0:001 Found theme directory: RANDOM 0:112 0:001 Loading early settings 0:112 0:000 timeout set to 1 0:112 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 0:112 0:000 KextsToPatch: 2 requested 0:112 0:000 KextsToPatch 0: AppleHDA (Audio patch) Kext bin patch, data len: 4 0:112 0:000 KextsToPatch 1: AppleAHCIPort (External icons patch) Kext bin patch, data len: 8 0:112 0:000 Default theme: embedded 0:112 0:000 Hiding entries with string VolumeName_NOT_SHOWN 0:112 0:000 Hiding entries with string EntryPath_NOT_SHOWN 0:112 0:000 Hiding entries with string VolumeUUID_NOT_SHOWN 0:112 0:000 CustomEDID ok 0:112 0:000 LoadDrivers() start 0:114 0:002 Loading FSInject-64.efi status=Success 0:116 0:001 Loading OsxAptioFix2Drv-64.efi status=Success 0:117 0:001 Loading OsxFatBinaryDrv-64.efi status=Success 0:118 0:001 Loading VBoxHfs-64.efi status=Success 0:119 0:001 - driver needs connecting 0:119 0:000 1 drivers needs connecting ... 0:119 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 0:119 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 0:312 0:192 LoadDrivers() end 0:312 0:000 Dump SMC keys from NVRAM: 0:353 0:041 SetMaxResolution: found best mode 4: 1920x1080 1:190 0:836 Video mode change to mode #4: Success 1:190 0:000 - set 1:190 0:000 Console modes reported: 6, available modes: 1:190 0:000 Mode 1: 80x25 (current mode) 1:190 0:000 Mode 2: 80x50 1:190 0:000 Mode 3: 100x31 1:190 0:000 Mode 4: 128x30 1:190 0:000 Mode 6: 120x50 1:190 0:000 SetScreenResolution: 1920x1080 - already set 1:190 0:000 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,1F52ECF2-39A5-4A6B-A149-760935D9EDD1,0x28,0x64000) 2:513 1:322 MAC address of LAN #0= FC:AA:14:C8:87:92: 2:513 0:000 ScanSPD() start 2:513 0:000 SMBus CmdReg: 0x1 2:513 0:000 Scanning SMBus [8086:8CA2], mmio: 0xF7838004, ioport: 0xF040, hostc: 0x11 2:513 0:000 Slots to scan [8]... 2:527 0:014 SPD[0]: Type 11 @0x50 2:536 0:008 DDR speed 1777MHz 2:536 0:000 Slot: 0 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=060C010805030906 2:550 0:014 SPD[1]: Type 11 @0x51 2:558 0:008 DDR speed 1777MHz 2:558 0:000 Slot: 1 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=070701080203020E 2:573 0:014 SPD[2]: Type 11 @0x52 2:581 0:008 DDR speed 1777MHz 2:581 0:000 Slot: 2 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=07040108060F020E 2:595 0:014 SPD[3]: Type 11 @0x53 2:604 0:008 DDR speed 1777MHz 2:604 0:000 Slot: 3 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=07050108060A020E 2:628 0:024 ScanSPD() end 2:628 0:000 Get Acpi Tables List from RSDT: 2:628 0:000 Found table: FACP A M I len=132 2:628 0:000 Found table: APIC A M I len=114 2:628 0:000 Found table: FPDT A M I len=68 2:628 0:000 Found table: SSDT Ther_Rvp len=3054 2:628 0:000 Found table: SSDT Cpu0Ist len=1337 2:628 0:000 Found table: SSDT CpuSsdt len=2932 2:628 0:000 Found table: MCFG A M I len=60 2:628 0:000 Found table: HPET A M I len=56 2:628 0:000 Found table: SSDT SataTabl len=877 2:628 0:000 Found table: SSDT SaSsdt len=23390 2:628 0:000 Calibrated TSC frequency =3200003850 =3200MHz 2:628 0:000 Loading main settings 2:628 0:000 Read NVCAP:0000000000000000000000000000000000000000 2:628 0:000 USB FixOwnership: true 2:628 0:000 Config set ResetAddr=0x0 2:628 0:000 Config calc ResetVal=0x0 2:628 0:000 Config set ResetVal=0x0 2:628 0:000 Config set ChassisType=0x6 2:628 0:000 Config set QPI=65535MHz 2:628 0:000 Config set CpuFreq=3199MHz 2:628 0:000 Config set CpuType=605 2:628 0:000 Config set BusSpeed=99999kHz 2:628 0:000 Error: invalid CustomUUID '' - should be in the format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX 2:628 0:000 found 4 volumes with blockIO 2:628 0:000 0. Volume: 2:628 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0) 2:629 0:000 Result of bootcode detection: bootable unknown (legacy) 2:629 0:000 1. Volume: 2:629 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,1F52ECF2-39A5-4A6B-A149-760935D9EDD1,0x28,0x64000) 2:629 0:000 Result of bootcode detection: bootable Clover (clover) 2:635 0:005 This is SelfVolume !! 2:635 0:000 2. Volume: 2:635 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,7BB0DBB6-3FB6-4FCF-9508-35C31C06D230,0x64028,0x1BD8A540) 2:636 0:000 3. Volume: 2:636 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(3,GPT,99455448-8CE7-426E-8E5C-D7A16F77F418,0x1BDEE568,0x135F20) 2:636 0:000 using embedded theme 2:636 0:000 Choosing theme 2:637 0:000 Custom entries start 2:637 0:000 Custom entries finish 2:637 0:000 Scanning loaders... 2:637 0:000 0: 'Whole Disc Boot' no file system 2:637 0:000 1: 'EFI' 3:545 0:908 2: 'capitan' 3:554 0:008 AddLoaderEntry for Volume Name=capitan 3:559 0:004 Check if volume Is Hibernated: 3:559 0:000 Check sleep image 'by signature': 3:565 0:006 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success 3:565 0:000 SleepImage name from pref: ImageVolume = 'capitan', ImageName = '\private\var\vm\sleepimage' 3:570 0:004 Reading first 512 bytes of sleepimage ... 3:570 0:000 OurBlockIoRead: Lba=173E5828, Offset=2E7CB05000 (BlockSize=512) 3:570 0:000 sig lion: 1010004 3:570 0:000 sig snow: 42601 3:570 0:000 no valid sleep image offset was found 3:570 0:000 Reading completed -> Success 3:570 0:000 sleepimage offset could not be acquired 3:570 0:000 hibernated: no - sign 3:573 0:003 3: 'Recovery HD' 3:574 0:001 AddLoaderEntry for Volume Name=Recovery HD 3:576 0:001 Custom legacy start 3:576 0:000 Custom legacy end 3:576 0:000 Scanning legacy ... 3:576 0:000 0: 'Whole Disc Boot' (legacy) not legacy 3:576 0:000 1: 'EFI' (clover) add legacy 3:576 0:000 added 'Boot Clover from EFI' OSType=3 Icon=clover 3:576 0:000 2: 'capitan' (legacy) not legacy 3:576 0:000 3: 'Recovery HD' (legacy) not legacy 3:576 0:000 Custom tool start 3:576 0:000 Custom tool end 3:578 0:001 found tool \EFI\CLOVER\tools\Shell64U.efi 3:578 0:000 Checking EFI partition Volume 1 for Clover 3:578 0:000 Found Clover 3:579 0:000 GetEfiBootDeviceFromNvram: efi-boot-device-data not found 3:579 0:000 EfiBootVolume not found 3:579 0:000 found entry 0. 'Boot Mac OS X from capitan', Volume 'capitan', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,7BB0DBB6-3FB6-4FCF-9508-35C31C06D230,0x64028,0x1BD8A540)\System\Library\CoreServices\boot.efi' 3:579 0:000 DefaultIndex=0 and MainMenu.EntryCount=9 3:647 0:067 Found Mouse device: 3:648 0:000 GUI ready 5:648 2:000 StartLoader() start 5:648 0:000 Entry->Settings: 5:648 0:000 Finally: Bus=99999kHz CPU=3199MHz 5:648 0:000 Kernel and Kext Patches at 90FE82B0: 5:648 0:000 Allowed: y 5:648 0:000 Debug: n 5:648 0:000 KernelCpu: n 5:648 0:000 Lapic: n 5:648 0:000 Haswell-E: n 5:648 0:000 AICPUPM: y 5:648 0:000 AppleRTC: y 5:648 0:000 KernelPm: y 5:648 0:000 FakeCPUID: 0x0 5:648 0:000 ATIController: null 5:648 0:000 ATIDataLength: 0 5:648 0:000 0 Kexts to load 5:648 0:000 2 Kexts to patch 5:648 0:000 KextPatch[0]: 4 bytes, AppleHDA 5:648 0:000 KextPatch[1]: 8 bytes, AppleAHCIPort 5:648 0:000 Loading boot.efi status=Success 5:861 0:213 GetOSVersion: : 10.11.3 5:862 0:000 insert table 9 for dev 0:0 5:862 0:000 insert table 9 for dev 0:1 5:862 0:000 insert table 9 for dev 19:0 5:862 0:000 Channels: 2 5:862 0:000 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23 5:862 0:000 SMBIOS Type 17 Index = 0 => 0 0: 5:862 0:000 DIMM1 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 8192 5:862 0:000 SMBIOS Type 17 Index = 1 => 2 2: 5:862 0:000 DIMM2 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 16384 5:862 0:000 SMBIOS Type 17 Index = 2 => 1 1: 5:862 0:000 DIMM3 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 24576 5:862 0:000 SMBIOS Type 17 Index = 3 => 3 3: 5:862 0:000 DIMM4 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 32768 5:862 0:000 NumberOfMemoryDevices = 4 5:862 0:000 Type20[0]->End = 0x7FFFFF, Type17[0] = 0x2000 5:862 0:000 Type20[1]->End = 0x17FFFFF, Type17[2] = 0x8000 5:862 0:000 Type20[2]->End = 0xFFFFFF, Type17[1] = 0xC000 5:862 0:000 Type20[3]->End = 0x1FFFFFF, Type17[3] = 0x14000 5:862 0:000 Table 131 is present, CPUType=31 5:862 0:000 Change to: 605 5:862 0:000 RSDT 0xABDC5028 5:862 0:000 FADT from RSDT: 0xABDC5100 5:862 0:000 XSDT 0xABDC5078 5:862 0:000 FADT from XSDT: 0xABDD5AD8 5:862 0:000 Xsdt reallocation done 5:862 0:000 old FADT length=10C 5:862 0:000 Found OperationRegion(GNVS, SystemMemory, ABDFCA98, ...) 5:862 0:000 Found OperationRegion(PNVA, SystemMemory, ABDFDD98, ...) 5:862 0:000 Found OperationRegion(CPSB, SystemMemory, ABC5AE98, ...) 5:862 0:000 Found OperationRegion(TMMB, SystemMemory, FED40000, ...) 5:864 0:001 Apply DsdtFixMask=0x00000000 old way 5:864 0:000 drop _DSM mask=0x0000 5:864 0:000 ========= Auto patch DSDT Starting ======== 5:864 0:000 VideoCard devID=0x104A10DE 5:864 0:000 DisplayADR1[0] = 0x10000, DisplayADR2[0] = 0x0 5:864 0:000 VideoCard devID=0x4128086 5:864 0:000 DisplayADR1[1] = 0x20000, DisplayADR2[1] = 0xFFFE 5:864 0:000 USBADR[0] = 0x140000 and PCIe = 0xFFFE 5:973 0:109 Audio HDA (addr:0x1B0000) setting specified layout-id=1 (0x1) 5:973 0:000 first CPU found at B7FC offset B7FF 5:973 0:000 score candidate at B7F8 5:973 0:000 score inserted in acpi_cpu_score _PR 5:973 0:000 Found ACPI CPU: CPU0 And CPU1 And CPU2 And CPU3 And CPU4 And CPU5 And CPU6 And CPU7 within the score: PR 5:974 0:000 Found PCIROOTUID = 0 5:974 0:000 ========= Auto patch DSDT Finished ======== 5:974 0:000 Patch table: SSDT Ther_Rvp 5:974 0:000 SSDT len = 0xBEE 5:974 0:000 Patch table: SSDT Cpu0Ist 5:974 0:000 SSDT len = 0x539 5:974 0:000 Patch table: SSDT CpuSsdt 5:974 0:000 SSDT len = 0xB74 5:974 0:000 Patch table: SSDT SataTabl 5:974 0:000 SSDT len = 0x36D 5:974 0:000 Patch table: SSDT SaSsdt 5:974 0:000 SSDT len = 0x5B5E 5:974 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0 5:974 0:000 Xsdt has tables count=10 5:974 0:000 corrected XSDT length=116 5:974 0:000 Inserting SSDT-SB-OC.aml from EFI\CLOVER\ACPI\patched ... Success 5:975 0:001 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=4 5:975 0:000 EdidDiscovered size=128 5:975 0:000 00 | 00 FF FF FF FF FF FF 00 15 C3 31 25 01 01 01 01 5:975 0:000 16 | 2F 18 01 03 80 35 1E 78 EA 7E 75 A7 55 52 9C 27 5:975 0:000 32 | 0F 50 54 A1 08 00 81 80 B3 00 A9 C0 81 C0 81 00 5:975 0:000 48 | 01 01 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C 5:975 0:000 64 | 45 00 10 29 21 00 00 1E 00 00 00 FF 00 33 36 30 5:975 0:000 80 | 34 31 31 31 34 0A 20 20 20 20 00 00 00 FD 00 31 5:975 0:000 96 | 3D 0F 44 0F 00 0A 20 20 20 20 20 20 00 00 00 FC 5:975 0:000 112 | 00 45 56 32 34 35 30 0A 20 20 20 20 20 20 01 03 5:975 0:000 NVidia GFX injection not set 5:975 0:000 Intel GFX injection not set 5:975 0:000 HDA Controller [8086:0C0C] :: PciRoot(0x0)\Pci(0x3,0x0) => setting specified layout-id=1 (0x1) 5:975 0:000 USB Controller [8086:8CB1] :: PciRoot(0x0)\Pci(0x14,0x0) 5:975 0:000 LAN Controller [8086:153B] :: PciRoot(0x0)\Pci(0x19,0x0) 5:975 0:000 HDA Controller [8086:8CA0] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1) 5:975 0:000 RCBA access disabled; trying to enable 5:975 0:000 stringlength = 1362 5:975 0:000 CurrentMode: Width=1920 Height=1080 5:975 0:000 Beginning FSInjection FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 9F507218 FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 9F507218 5:980 0:005 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 5:981 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.11 5:983 0:002 Extra kext: EFI\CLOVER\kexts\10.11\AppleACPIPS2Nub.kext 5:986 0:003 Extra kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext 5:993 0:006 Extra PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext\Contents\PlugIns\ApplePS2Keyboard.kext 5:997 0:004 Extra PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext\Contents\PlugIns\ApplePS2Mouse.kext 6:000 0:003 Extra PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext\Contents\PlugIns\ApplePS2Trackpad.kext 6:004 0:004 Extra kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext 6:008 0:004 Extra kext: EFI\CLOVER\kexts\10.11\NullCPUPowerManagement.kext 6:014 0:005 Removed efi-boot-device-data variable: Not Found 6:014 0:000 Custom boot screen not used because entry has unset use graphics 6:014 0:000 Closing log
submitted by poc7667 to hackintosh [link] [comments]

Adafruit Space Invader pendant. Want to convert to using a bicolor 1.2 led matrix. How would the code change?

 // Trinket/Gemma + LED matrix backpack jewelry. Plays animated // sequence on LED matrix. Press reset button to display again, // or add optional momentary button between pin #1 and +V. // THERE IS NO ANIMATION DATA IN THIS SOURCE FILE, you should // rarely need to change anything here. EDIT anim.h INSTEAD. #define BRIGHTNESS 14 // 0=min, 15=max #define I2C_ADDR 0x70 // Edit if backpack A0/A1 jumpers set #include  #include  #include  #include "anim2.h" // Animation data is located here #include "anim3.h" // Animation data is located here #include "anim4.h" // Animation data is located here static const uint8_t PROGMEM reorder[] = { // Column-reordering table 0x00,0x40,0x20,0x60,0x10,0x50,0x30,0x70,0x08,0x48,0x28,0x68,0x18,0x58,0x38,0x78, 0x04,0x44,0x24,0x64,0x14,0x54,0x34,0x74,0x0c,0x4c,0x2c,0x6c,0x1c,0x5c,0x3c,0x7c, 0x02,0x42,0x22,0x62,0x12,0x52,0x32,0x72,0x0a,0x4a,0x2a,0x6a,0x1a,0x5a,0x3a,0x7a, 0x06,0x46,0x26,0x66,0x16,0x56,0x36,0x76,0x0e,0x4e,0x2e,0x6e,0x1e,0x5e,0x3e,0x7e, 0x01,0x41,0x21,0x61,0x11,0x51,0x31,0x71,0x09,0x49,0x29,0x69,0x19,0x59,0x39,0x79, 0x05,0x45,0x25,0x65,0x15,0x55,0x35,0x75,0x0d,0x4d,0x2d,0x6d,0x1d,0x5d,0x3d,0x7d, 0x03,0x43,0x23,0x63,0x13,0x53,0x33,0x73,0x0b,0x4b,0x2b,0x6b,0x1b,0x5b,0x3b,0x7b, 0x07,0x47,0x27,0x67,0x17,0x57,0x37,0x77,0x0f,0x4f,0x2f,0x6f,0x1f,0x5f,0x3f,0x7f, 0x80,0xc0,0xa0,0xe0,0x90,0xd0,0xb0,0xf0,0x88,0xc8,0xa8,0xe8,0x98,0xd8,0xb8,0xf8, 0x84,0xc4,0xa4,0xe4,0x94,0xd4,0xb4,0xf4,0x8c,0xcc,0xac,0xec,0x9c,0xdc,0xbc,0xfc, 0x82,0xc2,0xa2,0xe2,0x92,0xd2,0xb2,0xf2,0x8a,0xca,0xaa,0xea,0x9a,0xda,0xba,0xfa, 0x86,0xc6,0xa6,0xe6,0x96,0xd6,0xb6,0xf6,0x8e,0xce,0xae,0xee,0x9e,0xde,0xbe,0xfe, 0x81,0xc1,0xa1,0xe1,0x91,0xd1,0xb1,0xf1,0x89,0xc9,0xa9,0xe9,0x99,0xd9,0xb9,0xf9, 0x85,0xc5,0xa5,0xe5,0x95,0xd5,0xb5,0xf5,0x8d,0xcd,0xad,0xed,0x9d,0xdd,0xbd,0xfd, 0x83,0xc3,0xa3,0xe3,0x93,0xd3,0xb3,0xf3,0x8b,0xcb,0xab,0xeb,0x9b,0xdb,0xbb,0xfb, 0x87,0xc7,0xa7,0xe7,0x97,0xd7,0xb7,0xf7,0x8f,0xcf,0xaf,0xef,0x9f,0xdf,0xbf,0xff }; int animationSection = 0; void ledCmd(uint8_t x) { // Issue command to LED backback driver Wire.beginTransmission(I2C_ADDR); Wire.write(x); Wire.endTransmission(); } void clear(void) { // Clear display buffer Wire.beginTransmission(I2C_ADDR); for(uint8_t i=0; i<17; i++) Wire.write(0); Wire.endTransmission(); } void setup() { power_timer1_disable(); // Disable unused peripherals power_adc_disable(); // to save power PCMSK |= _BV(PCINT1); // Set change mask for pin 1 Wire.begin(); // I2C init clear(); // Blank display ledCmd(0x21); // Turn on oscillator ledCmd(0xE0 | BRIGHTNESS); // Set brightness ledCmd(0x81); // Display on, no blink } uint8_t rep = REPS; void loop() { switch (animationSection) { case 0: for(int i=0; i 10) { animationSection = 0; } if(!--rep) { // If last cycle... ledCmd(0x20); // LED matrix in standby mode // GIMSK = _BV(PCIE); // Enable pin change interrupt // power_all_disable(); // All peripherals off // set_sleep_mode(SLEEP_MODE_PWR_DOWN); // sleep_enable(); // sei(); // Keep interrupts disabled // sleep_mode(); // Power down CPU (pin 1 will wake) // Execution resumes here on wake. // PLD - Simply Sleep for 2 minutes then start again... //delay(100000); //delay(100000); delay(120000); animationSection = 0; GIMSK = 0; // Disable pin change interrupt rep = REPS; // Reset animation counter power_timer0_enable(); // Re-enable timer power_usi_enable(); // Re-enable USI Wire.begin(); // Re-init I2C clear(); // Blank display ledCmd(0x21); // Re-enable matrix } } ISR(PCINT0_vect) {} // Button tap 
This is a section of the anim file. I want to be able to set the various colors in these "frames"
// Animation data for Trinket/Gemma + LED matrix backpack jewelry. // Edit this file to change the animation; it's unlikely you'll need // to edit the source code. #define REPS 10 // Number of times to repeat the animation loop (1-255) const int frameSpeed2 = 3; const uint8_t PROGMEM anim2[] = { // Animation bitmaps. Each frame of animation MUST contain // 8 lines of graphics data (there is no error checking for // length). Each line should be prefixed with the letter 'B', // followed by exactly 8 binary digits (0 or 1), no more, // no less (again, no error checking). '0' represents an // 'off' pixel, '1' an 'on' pixel. End line with a comma. B00000000, B00000000, B00000000, B00000000, B00000000, B00000000, B00000000, B00000000, frameSpeed2, // 0.10 seconds }; 
submitted by pldiguanaman to arduino [link] [comments]

Changed my theme, now autoboot doesn't work.

Hey guys, So I changed my Clover theme using Clover Configurator, and now my autoboot doesn't work. I'm pretty sure it has something to do with the theme altering my NVRAM. I've tried changing the default boot volume to my UUID and that still doesn't work. However, when I select my Macintosh hard drive as a startup disk in preferences, it will autoboot the first time and then fail to autoboot subsequent times. Below is a copy of my boot.log. Any ideas? Thanks.
0:100 0:100 MemLog inited, TSC freq: 3499997738 0:100 0:000 0:100 0:000 Now is 24.11.2015, 6:37:43 (GMT+2047) 0:100 0:000 Starting Clover rev 3320 on American Megatrends EFI 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,20C7F91B-D47C-498B-8E20-A475B63FD533,0x28,0x64000) @49DF2A18 0:100 0:000 SelfDirPath = \EFI\CLOVER 0:100 0:000 Total Memory Slots Count = 4 0:100 0:000 Type 17 Index = 0 0:100 0:000 SmbiosTable.Type17->Speed = 1333MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0 0:100 0:000 Type 17 Index = 1 0:100 0:000 SmbiosTable.Type17->Speed = 1333MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1 0:100 0:000 Type 17 Index = 2 0:100 0:000 SmbiosTable.Type17->Speed = 1333MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 ChannelB-DIMM0 0:100 0:000 Type 17 Index = 3 0:100 0:000 SmbiosTable.Type17->Speed = 1333MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1 0:100 0:000 Boot status=0 0:100 0:000 Clover revision: 3320 running on Z97X-UD7 TH 0:100 0:000 ... with board Z97X-UD7 TH-CF 0:100 0:000 CPU Vendor = 756E6547 Model=306C3 0:100 0:000 The CPU supported turbo 0:100 0:000 BrandString = Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz 0:100 0:000 MSR 0xE2 before patch 1E000404 0:100 0:000 MSR 0xE4 00021814 0:100 0:000 MSR 0xCE 00080838F3012300 0:100 0:000 non-usable FLEX_RATIO = F0000 0:100 0:000 corrected FLEX_RATIO = E0000 0:100 0:000 FSBFrequency=100MHz DMIvalue=100000kHz 0:100 0:000 Corrected FSBFrequency=100MHz 0:100 0:000 VendoModel/Stepping: 0x756E6547/0x3C/0x3 0:100 0:000 Family/ExtFamily: 0x6/0x0 0:100 0:000 MaxDiv/MinDiv: 35.0/8 0:100 0:000 Turbo: 39/39/39/39 0:100 0:000 Features: 0xBFEBFBFF 0:100 0:000 Threads: 4 0:100 0:000 Cores: 4 0:100 0:000 FSB: 100 MHz 0:100 0:000 CPU: 3500 MHz 0:100 0:000 TSC: 3500 MHz 0:100 0:000 PIS: 400 MHz 0:100 0:000 PCI (00|00:00.00) : 8086 0C00 class=060000 0:100 0:000 PCI (00|00:01.00) : 8086 0C01 class=060400 0:100 0:000 PCI (00|01:00.00) : 10DE 0FC8 class=030000 0:100 0:000 Found NVidia model=EVGA GeForce GT 740 0:100 0:000 PCI (00|01:00.01) : 10DE 0E1B class=040300 0:100 0:000 PCI (00|00:14.00) : 8086 8CB1 class=0C0330 0:100 0:000 PCI (00|00:16.00) : 8086 8CBA class=078000 0:100 0:000 PCI (00|00:19.00) : 8086 153B class=020000 0:100 0:000 LAN 0, Vendor=8086, MMIO=DC300000 0:100 0:000 PCI (00|00:1A.00) : 8086 8CAD class=0C0320 0:100 0:000 PCI (00|00:1B.00) : 8086 8CA0 class=040300 0:100 0:000 PCI (00|00:1C.00) : 8086 8C90 class=060400 0:100 0:000 PCI (00|00:1C.02) : 8086 8C94 class=060400 0:100 0:000 PCI (00|03:00.00) : 10B5 8605 class=060400 0:100 0:000 PCI (00|04:01.00) : 10B5 8605 class=060400 0:100 0:000 PCI (00|04:02.00) : 10B5 8605 class=060400 0:100 0:000 PCI (00|04:03.00) : 10B5 8605 class=060400 0:100 0:000 PCI (00|00:1C.03) : 8086 8C96 class=060400 0:100 0:000 PCI (00|08:00.00) : 1B4B 9172 class=010601 0:100 0:000 PCI (00|00:1C.04) : 8086 8C98 class=060400 0:100 0:000 PCI (00|00:1D.00) : 8086 8CA6 class=0C0320 0:100 0:000 PCI (00|00:1F.00) : 8086 8CC4 class=060100 0:100 0:000 PCI (00|00:1F.02) : 8086 8C82 class=010601 0:100 0:000 PCI (00|00:1F.03) : 8086 8CA2 class=0C0500 0:100 0:000 Clover load options size = 40 bytes 0:100 0:000 Clover started with option to boot bootmgfw.efi from EFI 0:102 0:002 Using OEM config.plist at path: EFI\CLOVER\config.plist 0:103 0:000 EFI\CLOVER\config.plist loaded: Success 0:105 0:002 Found theme directory: EMBEDDED 0:106 0:001 Found theme directory: RANDOM 0:108 0:001 Found theme directory: ICLOVER 0:111 0:003 Loading early settings 0:111 0:000 timeout set to 3 0:111 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 0:111 0:000 KextsToPatch: 5 requested 0:111 0:000 KextsToPatch 0: AppleHDA (10.11-AppleHDA/Realtek ALC...) Kext bin patch, data len: 4 0:111 0:000 KextsToPatch 1: AppleHDAController (HD4600_HDMI_Audio-1of2) Kext bin patch, data len: 5 0:111 0:000 KextsToPatch 2: AppleHDAController (HD4600_HDMI_Audio-2of2) Kext bin patch, data len: 5 0:111 0:000 KextsToPatch 3: AppleHDA (10.9-10.11-AppleHDA/Realtek ALC1150) Kext bin patch, data len: 4 0:111 0:000 KextsToPatch 4: AppleHDA (AppleHDA/Resources/xml>zml) Kext bin patch, data len: 6 0:111 0:000 Default theme: iclover 0:111 0:000 LoadDrivers() start 0:112 0:001 Loading FSInject-64.efi status=Success 0:113 0:001 Loading OsxAptioFix2Drv-64.efi status=Success 0:114 0:001 Loading OsxFatBinaryDrv-64.efi status=Success 0:115 0:001 Loading VBoxHfs-64.efi status=Success 0:116 0:001 - driver needs connecting 0:116 0:000 1 drivers needs connecting ... 0:116 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 0:116 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 0:239 0:123 LoadDrivers() end 0:239 0:000 Dump SMC keys from NVRAM: 0:283 0:043 SetScreenResolution: 1920x1080 - setting Mode 4 0:608 0:324 Video mode change to mode #4: Success 0:608 0:000 Console modes reported: 6, available modes: 0:608 0:000 Mode 1: 80x25 (current mode) 0:608 0:000 Mode 2: 80x50 0:608 0:000 Mode 3: 100x31 0:608 0:000 Mode 4: 128x30 0:608 0:000 Mode 6: 120x50 0:608 0:000 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,20C7F91B-D47C-498B-8E20-A475B63FD533,0x28,0x64000) 1:904 1:296 MAC address of LAN #0= 40:8D:5C:11:6B:BB: 1:904 0:000 ScanSPD() start 1:905 0:000 SMBus CmdReg: 0x1 1:905 0:000 Scanning SMBus [8086:8CA2], mmio: 0xDC334004, ioport: 0xF000, hostc: 0x11 1:905 0:000 Slots to scan [8]... 1:919 0:014 SPD[0]: Type 11 @0x50 1:927 0:008 Found module with XMP version 1.3XMP Profile1: 101/8ns 1:927 0:000 Using XMP Profile1 instead of standard frequency 1333MHz 1:927 0:000 DDR speed 1600MHz 1:927 0:000 Slot: 0 Type 24 8192MB 1600MHz Vendor=Crucial Technology PartNo=BLT8G3D1608DT1TX0. SerialNo=0A07000A0D0A030E 1:941 0:014 SPD[1]: Type 11 @0x51 1:950 0:008 Found module with XMP version 1.3XMP Profile1: 101/8ns 1:950 0:000 Using XMP Profile1 instead of standard frequency 1333MHz 1:950 0:000 DDR speed 1600MHz 1:950 0:000 Slot: 1 Type 24 8192MB 1600MHz Vendor=Crucial Technology PartNo=BLT8G3D1608DT1TX0. SerialNo=0A07000A0D0A030D 1:964 0:014 SPD[2]: Type 11 @0x52 1:972 0:008 Found module with XMP version 1.3XMP Profile1: 101/8ns 1:972 0:000 Using XMP Profile1 instead of standard frequency 1333MHz 1:972 0:000 DDR speed 1600MHz 1:972 0:000 Slot: 2 Type 24 8192MB 1600MHz Vendor=Crucial Technology PartNo=BLT8G3D1608DT1TX0. SerialNo=0A0101060A010D04 1:987 0:014 SPD[3]: Type 11 @0x53 1:995 0:008 Found module with XMP version 1.3XMP Profile1: 101/8ns 1:995 0:000 Using XMP Profile1 instead of standard frequency 1333MHz 1:995 0:000 DDR speed 1600MHz 1:995 0:000 Slot: 3 Type 24 8192MB 1600MHz Vendor=Crucial Technology PartNo=BLT8G3D1608DT1TX0. SerialNo=0A0101060A02000C 2:019 0:024 ScanSPD() end 2:019 0:000 Get Acpi Tables List from RSDT: 2:019 0:000 Found table: FACP A M I len=132 2:019 0:000 Found table: APIC A M I len=114 2:019 0:000 Found table: FPDT A M I len=68 2:019 0:000 Found table: SSDT Ther_Rvp len=3054 2:019 0:000 Found table: SSDT Cpu0Ist len=1337 2:019 0:000 Found table: SSDT CpuSsdt len=2932 2:019 0:000 Found table: MCFG A M I len=60 2:019 0:000 Found table: HPET A M I len=56 2:019 0:000 Found table: SSDT SataTabl len=877 2:019 0:000 Found table: SSDT SaSsdt len=23390 2:019 0:000 Found table: BGRT A M I len=56 2:019 0:000 Calibrated TSC frequency =3499997738 =3499MHz 2:019 0:000 Loading main settings 2:019 0:000 Config set ChassisType=0xD 2:019 0:000 found 13 volumes with blockIO 2:019 0:000 0. Volume: 2:019 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0) 2:021 0:002 1. Volume: 2:021 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0) 2:022 0:000 2. Volume: 2:022 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0) 2:025 0:003 3. Volume: 2:025 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0) 2:025 0:000 found optical drive 2:025 0:000 4. Volume: 2:025 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,20C7F91B-D47C-498B-8E20-A475B63FD533,0x28,0x64000) 2:026 0:000 Result of bootcode detection: bootable unknown (legacy) 2:031 0:004 This is SelfVolume !! 2:031 0:000 5. Volume: 2:031 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,DE5DDDF8-DCCC-4EB6-9C3F-66280BDC8184,0x64028,0x1D02BA00) 2:031 0:000 6. Volume: 2:031 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,C1E3C1BD-DB5E-4405-96E5-4CCE9D6EA4DB,0x1D08FA28,0x135F20) 2:032 0:000 7. Volume: 2:032 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,E6565B12-56A7-463D-B8B0-45E8B0427543,0x800,0xE1000) 2:032 0:000 Result of bootcode detection: bootable Windows (vista,win) 2:032 0:000 8. Volume: 2:032 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,2096CC5A-813D-40D7-95EB-B9D8DD36AA74,0xE1800,0x32000) 2:033 0:000 Result of bootcode detection: bootable Windows (vista,win) 2:060 0:027 9. Volume: 2:060 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(3,GPT,679EE6DA-4DAB-43E8-BD06-205CCC567065,0x113800,0x8000) 2:061 0:000 10. Volume: 2:061 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(4,GPT,0EC1B9F7-E828-4A69-88E4-9297B267FC6D,0x11B800,0x745EB000) 2:061 0:000 Result of bootcode detection: bootable Windows (vista,win) 2:061 0:000 11. Volume: 2:061 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,B6C833AC-6424-4AF7-8690-6E71843F1B87,0x28,0x64000) 2:062 0:000 Result of bootcode detection: bootable unknown (legacy) 2:071 0:009 12. Volume: 2:071 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,DA3D8410-9259-4D2C-B305-A2EC39E00417,0x64028,0x74662D60) 2:073 0:002 Using theme 'iclover' (EFI\CLOVER\themes\iclover) 2:073 0:000 theme iclover defined in NVRAM found and theme.plist parsed 2:075 0:001 Choosing theme iclover 2:075 0:000 Custom entries start 2:075 0:000 Custom entry 0 skipped because it is hidden. 2:075 0:000 Custom entries finish 2:075 0:000 Scanning loaders... 2:075 0:000 0: 'Whole Disc Boot' no file system 2:075 0:000 1: 'Whole Disc Boot' no file system 2:075 0:000 2: 'Whole Disc Boot' no file system 2:075 0:000 3: 'Whole Disc Boot' no file system 2:075 0:000 4: 'EFI' 2:090 0:014 5: 'Macintosh' 2:099 0:008 AddLoaderEntry for Volume Name=Macintosh 2:099 0:000 Not match custom entry 0: Volume: not match, VolumeType: match, Type: not match 2:104 0:004 Check if volume Is Hibernated: 2:104 0:000 Check sleep image 'by signature': 2:110 0:006 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success 2:110 0:000 SleepImage name from pref: ImageVolume = 'Macintosh', ImageName = '\private\var\vm\sleepimage' 2:116 0:005 Reading first 512 bytes of sleepimage ... 2:116 0:000 OurBlockIoRead: Lba=45268C8, Offset=8A4D19000 (BlockSize=512) 2:116 0:000 sig lion: DBFF63 2:116 0:000 sig snow: 4D3E6768 2:116 0:000 no valid sleep image offset was found 2:116 0:000 Reading completed -> Success 2:116 0:000 sleepimage offset could not be acquired 2:116 0:000 hibernated: no - sign 2:130 0:014 6: 'Recovery HD' 2:132 0:001 AddLoaderEntry for Volume Name=Recovery HD 2:132 0:000 Skipped because matching custom entry 0! 2:141 0:009 7: 'Legacy HD1' no file system 2:141 0:000 8: 'EFI' 2:142 0:000 AddLoaderEntry for Volume Name=EFI 2:142 0:000 Not match custom entry 0: Volume: not match, VolumeType: match, Type: not match 2:153 0:011 9: 'Legacy HD3' no file system 2:153 0:000 10: 'Legacy HD4' no file system 2:153 0:000 11: 'EFI' 2:163 0:009 12: 'Macintosh Data' 2:180 0:016 Custom legacy start 2:180 0:000 Custom legacy end 2:180 0:000 Custom tool start 2:180 0:000 Custom tool end 2:182 0:001 found tool \EFI\CLOVER\tools\Shell64U.efi 2:182 0:000 Checking EFI partition Volume 4 for Clover 2:182 0:000 Found Clover 2:183 0:000 Checking EFI partition Volume 8 for Clover 2:183 0:000 Checking EFI partition Volume 11 for Clover 2:186 0:002 GetEfiBootDeviceFromNvram: efi-boot-device-data not found 2:187 0:000 EfiBootVolume not found 2:187 0:000 Default boot entry not found 2:187 0:000 DefaultIndex=-1 and MainMenu.EntryCount=8 2:187 0:000 Use anime=iClover_logo frames=4 2:274 0:087 Found Mouse device: 2:275 0:000 GUI ready 19:933 17:658 BootOption of the entry is empty 19:933 0:000 StartLoader() start 19:933 0:000 Entry->Settings: 19:933 0:000 Finally: Bus=99999kHz CPU=3500MHz 19:933 0:000 Kernel and Kext Patches at 3D4800F0: 19:933 0:000 Allowed: y 19:933 0:000 Debug: n 19:933 0:000 KernelCpu: n 19:933 0:000 Lapic: n 19:933 0:000 Haswell-E: n 19:933 0:000 AICPUPM: y 19:933 0:000 AppleRTC: y 19:933 0:000 KernelPm: y 19:933 0:000 FakeCPUID: 0x0 19:933 0:000 ATIController: null 19:933 0:000 ATIDataLength: 0 19:933 0:000 0 Kexts to load 19:933 0:000 5 Kexts to patch 19:933 0:000 KextPatch[0]: 4 bytes, AppleHDA 19:933 0:000 KextPatch[1]: 5 bytes, AppleHDAController 19:933 0:000 KextPatch[2]: 5 bytes, AppleHDAController 19:933 0:000 KextPatch[3]: 4 bytes, AppleHDA 19:933 0:000 KextPatch[4]: 6 bytes, AppleHDA 19:933 0:000 Loading boot.efi status=Success 20:141 0:207 GetOSVersion: : 10.11.1 20:141 0:000 insert table 9 for dev 0:0 20:141 0:000 insert table 9 for dev 0:1 20:141 0:000 insert table 9 for dev 19:0 20:141 0:000 Channels: 2 20:141 0:000 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23 20:141 0:000 SMBIOS Type 17 Index = 0 => 0 0: 20:141 0:000 BANK0 DIMM0 1600MHz 8192MB 20:141 0:000 mTotalSystemMemory = 8192 20:141 0:000 SMBIOS Type 17 Index = 1 => 2 2: 20:141 0:000 BANK1 DIMM0 1600MHz 8192MB 20:141 0:000 mTotalSystemMemory = 16384 20:141 0:000 SMBIOS Type 17 Index = 2 => 1 1: 20:141 0:000 BANK0 DIMM1 1600MHz 8192MB 20:141 0:000 mTotalSystemMemory = 24576 20:141 0:000 SMBIOS Type 17 Index = 3 => 3 3: 20:141 0:000 BANK1 DIMM1 1600MHz 8192MB 20:141 0:000 mTotalSystemMemory = 32768 20:141 0:000 NumberOfMemoryDevices = 4 20:141 0:000 Type20[0]->End = 0x7FFFFF, Type17[0] = 0x2000 20:141 0:000 Type20[1]->End = 0x17FFFFF, Type17[2] = 0x8000 20:141 0:000 Type20[2]->End = 0xFFFFFF, Type17[1] = 0xC000 20:141 0:000 Type20[3]->End = 0x1FFFFFF, Type17[3] = 0x14000 20:141 0:000 Table 131 is present, CPUType=31 20:141 0:000 Change to: 605 20:141 0:000 RSDT 0x581B3028 20:141 0:000 FADT from RSDT: 0x581B3108 20:141 0:000 XSDT 0x581B3080 20:141 0:000 FADT from XSDT: 0x581C5540 20:141 0:000 Xsdt reallocation done 20:141 0:000 old FADT length=10C 20:141 0:000 Found OperationRegion(GNVS, SystemMemory, 581EEA98, ...) 20:141 0:000 Found OperationRegion(PNVA, SystemMemory, 581EFD98, ...) 20:141 0:000 Found OperationRegion(RCRB, SystemMemory, 0, ...) 20:141 0:000 Found OperationRegion(XHCP, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(MCA1, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(PSCA, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(MCA1, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(ICB1, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(ICB1, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(RPAC, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(EPAC, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(CPSB, SystemMemory, 58049E98, ...) 20:142 0:000 Found OperationRegion(MBAR, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(PXVD, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(MMMM, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(RP_X, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(RP_X, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(RP_X, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(PXVD, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(RP_X, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(RP_X, SystemMemory, 0, ...) 20:142 0:000 Found OperationRegion(TMMB, SystemMemory, FED40000, ...) 20:143 0:001 Apply DsdtFixMask=0x00000000 old way 20:143 0:000 drop _DSM mask=0x0000 20:143 0:000 ========= Auto patch DSDT Starting ======== 20:143 0:000 VideoCard devID=0xFC810DE 20:143 0:000 DisplayADR1[0] = 0x10000, DisplayADR2[0] = 0x0 20:143 0:000 USBADR[0] = 0x140000 and PCIe = 0xFFFE 20:143 0:000 USBADR[1] = 0x1A0000 and PCIe = 0xFFFE 20:249 0:105 Audio HDA (addr:0x1B0000) setting specified layout-id=1 (0x1) 20:249 0:000 USBADR[2] = 0x1D0000 and PCIe = 0xFFFE 20:249 0:000 first CPU found at C65E offset C661 20:249 0:000 score candidate at C65A 20:249 0:000 score inserted in acpi_cpu_score _PR 20:249 0:000 Found ACPI CPU: CPU0 And CPU1 And CPU2 And CPU3 And CPU4 And CPU5 And CPU6 And CPU7 within the score: PR 20:249 0:000 Found PCIROOTUID = 0 20:249 0:000 ========= Auto patch DSDT Finished ======== 20:249 0:000 Patch table: SSDT Ther_Rvp 20:249 0:000 SSDT len = 0xBEE 20:249 0:000 Patch table: SSDT Cpu0Ist 20:249 0:000 SSDT len = 0x539 20:249 0:000 Patch table: SSDT CpuSsdt 20:249 0:000 SSDT len = 0xB74 20:249 0:000 Patch table: SSDT SataTabl 20:249 0:000 SSDT len = 0x36D 20:249 0:000 Patch table: SSDT SaSsdt 20:249 0:000 SSDT len = 0x5B5E 20:249 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0 20:249 0:000 Xsdt has tables count=11 20:249 0:000 corrected XSDT length=124 20:249 0:000 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=4 20:250 0:000 EdidDiscovered size=128 20:250 0:000 00 | 00 FF FF FF FF FF FF 00 04 69 F2 23 65 01 00 00 20:250 0:000 16 | 09 14 01 03 80 34 1D 78 2A C7 20 A4 55 49 99 27 20:250 0:000 32 | 13 50 54 BF EF 00 71 4F 81 80 95 00 B3 00 D1 C0 20:250 0:000 48 | 01 01 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C 20:250 0:000 64 | 45 00 09 25 21 00 00 1E 00 00 00 FF 00 41 33 4C 20:250 0:000 80 | 4D 54 46 30 30 30 33 35 37 0A 00 00 00 FD 00 37 20:250 0:000 96 | 4B 1E 55 10 00 0A 20 20 20 20 20 20 00 00 00 FC 20:250 0:000 112 | 00 41 53 55 53 20 56 48 32 33 36 48 0A 20 00 CE 20:250 0:000 NVidia GFX injection not set 20:250 0:000 LAN Controller [8086:153B] :: PciRoot(0x0)\Pci(0x19,0x0) 20:250 0:000 HDA Controller [8086:8CA0] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1) 20:250 0:000 stringlength = 540 20:250 0:000 CurrentMode: Width=1920 Height=1080 20:250 0:000 Beginning FSInjection FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 49DF2718 FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 49DF2718 20:257 0:006 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 20:257 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.11 20:259 0:001 Extra kext: EFI\CLOVER\kexts\10.11\FakePCIID_XHCIMux.kext 20:260 0:001 Extra kext: EFI\CLOVER\kexts\10.11\FakePCIID.kext 20:264 0:003 Extra kext: EFI\CLOVER\kexts\10.11\realtekALC.kext 20:269 0:005 Removed efi-boot-device-data variable: Not Found 20:269 0:000 Custom boot is disabled 20:269 0:000 Closing log
submitted by positiveR8 to hackintosh [link] [comments]

2013 Day2P28 LoB: PLT & Dynamic Linking Exploit Development Student (XDS) Review [eLearnSecurity]

Thursday, 20 July 2017. 0x11 In Biner Pilihan Tuesday, October 18, 2016. 0x11 In Binary Option ASCII Table and ASCII Code ( 0 - 127 ) Decimal Octal Hex Binairy Character ----- ----- ---- ----- ----- 000 000 0x00 00000000 NUL (Null char.) 001 001 0x01 00000001 SOH (Start of Header) 002 002 0x02 00000010 STX (Start of Text) 003 003 0x03 00000011 ETX (End of Text) 004 004 0x04 00000100 EOT (End of Transmission) 005 005 0x05 00000101 ENQ (Enquiry) 006 006 0x06 00000110 ACK (Acknowledgment ... Wednesday, 10 April 2019. 0x11 in binary option Tuesday, 20 December 2016. 0x11 In Binary Option 0x11 In Binary Option . Opções binárias Broker Apesar de opções binárias são uma forma relativamente nova de comércio dentro do mercado de ações e outros mercados financeiros, é uma área em rápido crescimento dos mercados de investimento. Os comerciantes experientes são dabbling com esta técnica e abriu a porta para que muitos comerciantes do principiante investem nos mercados ... VBA is what I do I couldn t leave the page without offering some code The following code will read a Compound Binary File and extract structural details from it It, then, looks for and extracts the stream called dir This stream was chosen for the demonstration simply because it was relevant to the forum posting that triggered the writing of this page Decompression, and interpretation, of the ... Sep. 25. 0x11 In Binary Option In this case, the only allowed fields are: Type= Binary, Offset= 0x0 and option=-ram + instance : ram0 It is used for files loaded in RAM by the programming service, for example to load and execute kernel. Several devices can be mixed in the same FlashLayout file. 2.7 Field6: Offset . The supported values are: boot1: first boot area partition of e• MMC (offset is 0x0) boot2: second boot area ... Compiler Option SD-6 Feature Test; Concepts: N4377: 6-fconcepts __cpp_concepts >= 201507 : Transactional Memory: N4514: 6 (no atomic_cancel)-fgnu-tm __cpp_transactional_memory >= 201505 : Coroutines : N4649: In progress: Modules : N4720: In progress: C++14 Support in GCC. GCC has full support for the previous revision of the C++ standard, which was published in 2014. This mode is the default ...

[index] [20179] [4650] [23759] [1752] [2253] [25446] [16954] [19391] [17220] [2886]

2013 Day2P28 LoB: PLT & Dynamic Linking

The course is dedicated to binary exploitation, and is a great baseline for those trying to learn modern day exploit development and vulnerability research. Loading... *Manipulating linker options to change the structure of binary formats *Reading and understanding PE files with PEView *Using WinDbg to watch the loader resolve imports in an executable

http://binary-optiontrade.choitiotrinigangeb.tk