Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

CaseySJ said:
Build 1:
I believe the original DSM2 SSDT injects ThunderboltDROM, right?

Build 3:
No error here because the ThunderboltDROM used inside the SSDT is fully valid.
Click to expand...

I have attached it. I don't see an DROM setting in there.
 

Attachments

  • DSM2 SSDT-TBOLT3-RP12.aml
    1.4 KB · Views: 87
CaseySJ said:
That one contains a valid ThunderboltDROM -- or maybe that's what we thought? Do you have a screenshot of the error in Hackintool?
Click to expand...

Perhaps my adjustment to it made it invalid?
71 changed to 11 (from my firmwares DROM section). Then, as requested by the second error 0x11 = 0x24 <---correct value

Here's a copy/paste of the first error. I might need to go back and try to recreate everything.

Failed CRC32 Verification: 0xbd01ea2d != 0xcb96b939
 
qthegaijin said:
@CaseySJ
Hackintool DROM Search Result:
Code: 
2020-03-16 15:32:25.320972-0700  localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe00002be)
Click to expand...

@CaseySJ also this error went away after CRC32 and CRC8 were taken care of.

Is 0xe00002be the same error that causes the TBpatch method to brick? Does this resolve...that?
 
NorthAmTransAm said:
@CaseySJ also this error went away after CRC32 and CRC8 were taken care of.
Click to expand...
It would be helpful to grab a few additional log lines before and after that one line.
Is 0xe00002be the same error that causes the TBpatch method to brick? Does this resolve...that?
Click to expand...
Wow!!! You may have found something there! That is the same link error we were getting before we decided to flash the firmware. Let me see what happens when I use a valid DROM... Will do that on my unflashed Designare in the morning. It’s been a long day. :)

I still need to determine why my system (and others) just don’t contain these logs...
 
Last edited:
CaseySJ said:
​
Do you see any log entries like this?

View attachment 455225
Click to expand...

I am not sure what SSDT I was using but I did see that once I assumed that it was to do with that specific ssdt and I stopped using it. How can I look for logs for like the last 4 days.
 
Build 1 Titan Ridge TB3
Z370 AORUS Gaming 5 |  i9 9900K |  RX 6900 XT (16 GB)
CaseySJ said:
It would be helpful to grab a few additional log lines before and after that one line.

Wow!!! You may have found something there! That is the same link error we were getting before we decided to flash the firmware. Let me see what happens when I use a valid DROM... Will do that on my unflashed Designare in the morning. It’s been a long day. :)
Click to expand...
Sweet! Ok, it took me a minute to retrace my steps.

Also just to keep em honest for anyone tuning in the. The Hackintool method came from a few pages back via @Elias64Fr.

Changes to Thunderbolt DROM

First 22 bytes changed to my cards DROM​
UID changed to 01​
Fixed or pre-defined values for each Mac model was changed to iMac 19,1​
TBSwitch7 -- changed to 02 87​


Full TDROM used
/* 0000 */ 0x11, 0x01, 0x65, 0xBA, 0x7C, 0x7F, 0x59, 0x00,


/* 0008 */ 0x00, 0x2D, 0xEA, 0x01, 0xBD, 0x01, 0x58, 0x00,


/* 0010 */ 0x01, 0x00, 0x0D, 0x00, 0x01, 0x00, 0x08, 0x81,


/* 0018 */ 0x82, 0x02, 0x82, 0x00, 0x00, 0x00, 0x08, 0x82,


/* 0020 */ 0x92, 0x01, 0x82, 0x00, 0x00, 0x00,0x08, 0x83,


/* 0028 */ 0x82, 0x04, 0x82, 0x01, 0x00, 0x00, 0x08, 0x84,


/* 0030 */ 0x92, 0x03, 0x82, 0x01, 0x00, 0x00, 0x05, 0x85,


/* 0038 */ 0x09, 0x01, 0x00, 0x05, 0x86, 0x09, 0x01, 0x00,


/* 0040 */ 0x02, 0x87, 0x03, 0x88, 0x20, 0x03, 0x89, 0x80,


/* 0048 */ 0x02, 0xCA, 0x02, 0xCB, 0x01, 0x41, 0x70, 0x70,


/* 0050 */ 0x6C, 0x65, 0x20, 0x49, 0x6E, 0x63, 0x2E, 0x00,


/* 0058 */ 0x0C, 0x4E, 0x41, 0x46, 0x45,0x50, 0x72, 0x69,


/* 0060 */ 0x6e, 0x74, 0x73

Error 1 (0xe00002be 0xe0000001 error beneath it)
2020-03-17 21:30:02.955895-0500 localhost kernel[0]: rooting via boot-uuid from /chosen: B125B699-503B-44EA-9EBE-E2D152F5966C


2020-03-17 21:30:02.955913-0500 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>


2020-03-17 21:30:02.956738-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:30:02.956864-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:30:02.961296-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1303: Starting ThreadPool


2020-03-17 21:30:02.961299-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1325: 4 threads would be used for the ThreadPool


2020-03-17 21:30:02.961315-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961317-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961323-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961332-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961469-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk0s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:30:02.961469-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk1s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:30:02.961473-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk0s2: device_handle block size 4096 block count 249999948 features 0 internal


2020-03-17 21:30:02.961474-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk1s2: device_handle block size 4096 block count 122019835 features 0 internal


2020-03-17 21:30:02.961537-0500 localhost kernel[0]: (apfs) <apfs`log_info> fletcher64_init:106: Selecting AVX2 implementation of fletcher64


2020-03-17 21:30:02.961542-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk0s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:30:02.961564-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk1s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:30:02.967671-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::parseDROMData()> IOThunderboltEEPROM::parseDROMData - Failed CRC8 Verification: 0x11 != 0x24


2020-03-17 21:30:02.967673-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe0000001)


2020-03-17 21:30:02.968661-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk0s2: checkpoint search: largest xid 185669, best xid 185669 @ 57


2020-03-17 21:30:02.968663-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk1s2: checkpoint search: largest xid 495966, best xid 495966 @ 205


2020-03-17 21:30:02.968950-0500 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_sysctl_register:973: done registering sysctls.


2020-03-17 21:30:02.969674-0500 localhost kernel[0]: BSD root: disk3s1


2020-03-17 21:30:02.969675-0500 localhost kernel[0]: , major 1, minor 11

Error 2 (0xe00002be 0xe0000001 Error is gone)
2020-03-17 21:35:59.964385-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:35:59.967477-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1303: Starting ThreadPool


2020-03-17 21:35:59.967480-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1325: 4 threads would be used for the ThreadPool


2020-03-17 21:35:59.967491-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967498-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967503-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967510-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967586-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk0s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:35:59.967590-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk0s2: device_handle block size 4096 block count 249999948 features 0 internal


2020-03-17 21:35:59.967652-0500 localhost kernel[0]: (apfs) <apfs`log_info> fletcher64_init:106: Selecting AVX2 implementation of fletcher64


2020-03-17 21:35:59.967658-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk0s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:35:59.974626-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk0s2: checkpoint search: largest xid 185679, best xid 185679 @ 77


2020-03-17 21:35:59.974819-0500 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_sysctl_register:973: done registering sysctls.


2020-03-17 21:35:59.978326-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::parseDROMData()> IOThunderboltEEPROM::parseDROMData - Failed CRC32 Verification: 0xbd01ea2d != 0xcb96b939


2020-03-17 21:35:59.978328-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe0000001)


2020-03-17 21:35:59.978639-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:35:59.982589-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk2s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:35:59.982593-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk2s2: device_handle block size 4096 block count 122019835 features 0 internal


2020-03-17 21:35:59.982679-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk2s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:35:59.989222-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk2s2: checkpoint search: largest xid 496214, best xid 496214 @ 141


2020-03-17 21:35:59.989770-0500 localhost kernel[0]: BSD root: disk4s1


2020-03-17 21:35:59.989771-0500 localhost kernel[0]: , major 1, minor 12


2020-03-17 21:35:59.989908-0500 localhost kernel[0]: (IOStorageFamily) <IOStorageFamily`dkreadwritecompletion(void*, void*, int, unsigned long long)> disk4s1: device is not readable.


2020-03-17 21:35:59.989911-0500 localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs_mountfs: buf_meta_bread failed with 13


2020-03-17 21:35:59.989913-0500 localhost kernel[0]: (HFS) <HFS`hfs_mount> hfs_mount: hfs_mountfs returned error=13 for device unknown-dev


2020-03-17 21:35:59.989915-0500 localhost kernel[0]: hfs_mountroot failed: 13


2020-03-17 21:35:59.989917-0500 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mountroot:1549: apfs: mountroot called!


2020-03-17 21:35:59.990011-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: /dev/disk4: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:35:59.990014-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: /dev/disk4: device_handle block size 4096 block count 122019835 features 16 internal solidstate
 

Attachments

  • SSDT-TBOLT3-RP21-GC-TITAN-RIDGE .aml
    2.2 KB · Views: 100
Last edited:
Elias64Fr said:
Secret sauce is that we don't need all of previous decoding work :lol::lol:
  1. Just make required modifications of DROM
  2. Use a dummy CRC8 and CRC32
  3. After reboot, use hackintool (or terminal command) to see ALL of System log (sometimes "Contains" is buggy)
  4. Search for "DROM" text
  5. If you find a log about DROM error ... It show false CRC8 and then indicates the right CRC8 :lol::lol:
  6. Correct the CRC
  7. Reboot
  8. Do the same thing with CRC32
  9. Replay line 3 and 4 until you don't find anything about DROM
That's all !

UPDATE: Some illustration
Click to expand...

Sucess!!:mrgreen:

Got the IOThunderbolPort@7 as per @Elias64Fr previous post #2086153 on a MacPro 7.1 SMBIOS & Gigabyte Aorus Xtreme!

Captura de ecrã 2020-03-18, às 08.08.33.png

Used dummy UID 0x11 0x22 0x33 0x44 0x55 for this example (will later change to my real UID), dummy CRC32 0x77 0x77 0x77 0x77 and dummy CRC8 0x03, where Hackintool search for DROM showed "corrected" CRC8 0x4f:
Captura de ecrã 2020-03-18, às 07.37.41.png

Then used "corrected" CRC8 0x4f and rebooted, where Hackintool search for DROM again showed "corrected" CRC32 0xbd01ea2d (needs inverting when adding to SSDT):
Captura de ecrã 2020-03-18, às 07.54.15.png

Quite happy and hope this helps others!

Final SSDT attached for reference (with dummy UID).
 

Attachments

  • SSDT-TBOLT3-RP01-V3.aml
    2 KB · Views: 136
Last edited:
NorthAmTransAm said:
Sweet! Ok, it took me a minute to retrace my steps.

Also just to keep em honest for anyone tuning in the. The Hackintool method came from a few pages back via @Elias64Fr.

Changes to Thunderbolt DROM

First 22 bytes changed to my cards DROM​
UID changed to 01​
Fixed or pre-defined values for each Mac model was changed to iMac 19,1​
TBSwitch7 -- changed to 02 87​


Full TDROM used
/* 0000 */ 0x11, 0x01, 0x65, 0xBA, 0x7C, 0x7F, 0x59, 0x00,


/* 0008 */ 0x00, 0x2D, 0xEA, 0x01, 0xBD, 0x01, 0x58, 0x00,


/* 0010 */ 0x01, 0x00, 0x0D, 0x00, 0x01, 0x00, 0x08, 0x81,


/* 0018 */ 0x82, 0x02, 0x82, 0x00, 0x00, 0x00, 0x08, 0x82,


/* 0020 */ 0x92, 0x01, 0x82, 0x00, 0x00, 0x00,0x08, 0x83,


/* 0028 */ 0x82, 0x04, 0x82, 0x01, 0x00, 0x00, 0x08, 0x84,


/* 0030 */ 0x92, 0x03, 0x82, 0x01, 0x00, 0x00, 0x05, 0x85,


/* 0038 */ 0x09, 0x01, 0x00, 0x05, 0x86, 0x09, 0x01, 0x00,


/* 0040 */ 0x02, 0x87, 0x03, 0x88, 0x20, 0x03, 0x89, 0x80,


/* 0048 */ 0x02, 0xCA, 0x02, 0xCB, 0x01, 0x41, 0x70, 0x70,


/* 0050 */ 0x6C, 0x65, 0x20, 0x49, 0x6E, 0x63, 0x2E, 0x00,


/* 0058 */ 0x0C, 0x4E, 0x41, 0x46, 0x45,0x50, 0x72, 0x69,


/* 0060 */ 0x6e, 0x74, 0x73

Error 1 (0xe00002be error beneath it)
2020-03-17 21:30:02.955895-0500 localhost kernel[0]: rooting via boot-uuid from /chosen: B125B699-503B-44EA-9EBE-E2D152F5966C


2020-03-17 21:30:02.955913-0500 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>


2020-03-17 21:30:02.956738-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:30:02.956864-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:30:02.961296-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1303: Starting ThreadPool


2020-03-17 21:30:02.961299-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1325: 4 threads would be used for the ThreadPool


2020-03-17 21:30:02.961315-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961317-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961323-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961332-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:30:02.961469-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk0s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:30:02.961469-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk1s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:30:02.961473-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk0s2: device_handle block size 4096 block count 249999948 features 0 internal


2020-03-17 21:30:02.961474-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk1s2: device_handle block size 4096 block count 122019835 features 0 internal


2020-03-17 21:30:02.961537-0500 localhost kernel[0]: (apfs) <apfs`log_info> fletcher64_init:106: Selecting AVX2 implementation of fletcher64


2020-03-17 21:30:02.961542-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk0s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:30:02.961564-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk1s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:30:02.967671-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::parseDROMData()> IOThunderboltEEPROM::parseDROMData - Failed CRC8 Verification: 0x11 != 0x24


2020-03-17 21:30:02.967673-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe0000001)


2020-03-17 21:30:02.968661-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk0s2: checkpoint search: largest xid 185669, best xid 185669 @ 57


2020-03-17 21:30:02.968663-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk1s2: checkpoint search: largest xid 495966, best xid 495966 @ 205


2020-03-17 21:30:02.968950-0500 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_sysctl_register:973: done registering sysctls.


2020-03-17 21:30:02.969674-0500 localhost kernel[0]: BSD root: disk3s1


2020-03-17 21:30:02.969675-0500 localhost kernel[0]: , major 1, minor 11

Error 2 (0xe00002be Error is gone)
2020-03-17 21:35:59.964385-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:35:59.967477-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1303: Starting ThreadPool


2020-03-17 21:35:59.967480-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_init:1325: 4 threads would be used for the ThreadPool


2020-03-17 21:35:59.967491-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967498-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967503-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967510-0500 localhost kernel[0]: (apfs) <apfs`log_debug> swcrypto_threadpool_worker_thread:1249: ThreadPool worker thread started


2020-03-17 21:35:59.967586-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk0s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:35:59.967590-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk0s2: device_handle block size 4096 block count 249999948 features 0 internal


2020-03-17 21:35:59.967652-0500 localhost kernel[0]: (apfs) <apfs`log_info> fletcher64_init:106: Selecting AVX2 implementation of fletcher64


2020-03-17 21:35:59.967658-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk0s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:35:59.974626-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk0s2: checkpoint search: largest xid 185679, best xid 185679 @ 77


2020-03-17 21:35:59.974819-0500 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_sysctl_register:973: done registering sysctls.


2020-03-17 21:35:59.978326-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::parseDROMData()> IOThunderboltEEPROM::parseDROMData - Failed CRC32 Verification: 0xbd01ea2d != 0xcb96b939


2020-03-17 21:35:59.978328-0500 localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe0000001)


2020-03-17 21:35:59.978639-0500 localhost kernel[0]: (apfs) <apfs`log_debug> cryptoAlloc:662: Using 64 buffers with size 16384, 512 buffers size 65536


2020-03-17 21:35:59.982589-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: disk2s2: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:35:59.982593-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: disk2s2: device_handle block size 4096 block count 122019835 features 0 internal


2020-03-17 21:35:59.982679-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1222: disk2s2: initializing cache w/hash_size 8192 and cache size 32768


2020-03-17 21:35:59.989222-0500 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1473: disk2s2: checkpoint search: largest xid 496214, best xid 496214 @ 141


2020-03-17 21:35:59.989770-0500 localhost kernel[0]: BSD root: disk4s1


2020-03-17 21:35:59.989771-0500 localhost kernel[0]: , major 1, minor 12


2020-03-17 21:35:59.989908-0500 localhost kernel[0]: (IOStorageFamily) <IOStorageFamily`dkreadwritecompletion(void*, void*, int, unsigned long long)> disk4s1: device is not readable.


2020-03-17 21:35:59.989911-0500 localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs_mountfs: buf_meta_bread failed with 13


2020-03-17 21:35:59.989913-0500 localhost kernel[0]: (HFS) <HFS`hfs_mount> hfs_mount: hfs_mountfs returned error=13 for device unknown-dev


2020-03-17 21:35:59.989915-0500 localhost kernel[0]: hfs_mountroot failed: 13


2020-03-17 21:35:59.989917-0500 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mountroot:1549: apfs: mountroot called!


2020-03-17 21:35:59.990011-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:285: /dev/disk4: device accelerated crypto: 0 (compiled @ Aug 20 2019 17:32:55)


2020-03-17 21:35:59.990014-0500 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:288: /dev/disk4: device_handle block size 4096 block count 122019835 features 16 internal solidstate
Click to expand...
@NorthAmTransAm @CaseySJ
On your log, I can see that you don't have our damn error 0xe00002be but like on my previous screenshot :

IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe0000001)
​
Same error description BUT different error code :confused:
 
augustopaulo said:
Sucess!!:mrgreen:

Got the IOThunderbolPort@7 as per @Elias64Fr previous post #2086153 on a MacPro 7.1 & Gigabyte Aorus Xtreme!

View attachment 455250

Used dummy UID 0x11 0x22 0x33 0x44 0x55 for this example (will later change to my real UID), dummy CRC32 0x77 0x77 0x77 0x77 and dummy CRC8 0x03, where Hackintool search for DROM showed "corrected" CRC8 0x4f:
View attachment 455251

Then used "corrected" CRC8 0x4f and rebooted, where Hackintool search for DROM again showed "corrected" CRC32 0xbd01ea2d (needs inverting when adding to SSDT):
View attachment 455252

Quite happy and hope this helps others!

Final SSDT attached for reference (with dummy UID).
Click to expand...
When connecting my MBP with this system via a TB2->TB3 cable adapter in thunderbolt networking mode, the following is activated:
Captura de ecrã 2020-03-18, às 08.36.30.png
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top