Yes. It is an optional parameter. Usually it is the same as the number of bytes specified. If Buffer size is larger, then uninitialized bytes are set to 0x00. If it is smaller, then the length of the initialized bytes is used (so I guess Buffer (One) is actually valid but in that case maybe...
The message means the Buffer for ThunderboltDROM has a size that is less than the number of bytes specified. In the case of your dsl and aml examples, the Buffer size was set to One which is definitely not large enough for a DROM. The message does not affect the ability to load the DROM.
I wasn't able to reproduce those errors but I did make a change that might work.
If an error occurs again, please state which shell you are using.
Quotes might be easier to do and read (but ~ must be outside the quotes)
loadfwfile ~"/Downloads/Vision D/Vision-D-FW-1.bin"
The "source" info also shows if the DROM came from the active or inactive part of the firmware (if you have a 1MB firmware which has been updated once before then it will...
Only problem in that DROM is the CRC for the UID.
0x01) UID: 0x0000554433221102
0x0d) Device ROM Revision: 1
0x10) Vendor ID: 0x1
0x12) Device ID: 0x10
0x14) Device Revision: 0x1
0x15) EEPROM Revision: 0
0x16) 1: 820282000000
0x1e) 2: 920182000000
Checksum is correct now. But I guess your new UI will require dynamic recalculation of the checksum.
You could try to find the answer in my script. When any information is changed, the two bytes that store the length is updated (linux source code says the max length value is 0x3FF; add 13 to...
So it just creates an entire SSDT with a random UID?
A couple issues:
1) The pasted text doesn't include indenting. Can you use <pre> instead of <li> for the text (or anything that can preserve indenting)?
2) The length bytes at 0x0E doesn't include the device name string. Change from 0x58 to...
The script has only been tested with zsh. I need to add a !# to the top of the script to force zsh. If you have a Terminal.app that defaults to bash (the default in older macOS versions), then you can probably just type zsh to start a zsh terminal session.
The script does nothing if you run it...
I created a script to load, examine, and edit Thunderbolt DROMs. You can load many, and it will only keep the unique ones but it remembers all the sources for each.
The script is attached. Future updates will go to
It may be useful to have an IO Registry dump when the driver is working and when it is not to compare.
Also, any messages in the system log related to the driver "ProCaptureDriver"? You might need to set log debug level.
sudo log config --mode "level: debug"
Strange thing happened to me today. I haven't been using my hackintosh for a long while. I booted up into Clover and found that my Dell UP2715K was showing 5120x2880 60Hz! I took a screenshot in Clover to confirm (also Clover Info menu and debug log showed 5120x2880 mode). I didn't think dual...
If they were disabled, then they wouldn't have a Location ID? I'm not 100% sure how Hackintool works.
You have enabled ports with the same Location IDs. You are supposed to limit the number of ports to 15 per controller so that Location IDs are unique.
You might have old info showing. Click...
So you're saying the problem you had has gone away without using any kext?
Back to the codeless kext issue. It makes sense to have kexts that have code, and kexts that don't have code that point to other kexts with code. But if you want a kext with no code, then I guess you could use Xcode to...
ProbeScore is now 0x3e8 = 1000 and CFBundleIdentifier is now com.apple.driver.Hack16X50Serial so it looks like our kext loaded but it also looks like the code was executed because some other properties exist that are not in the Info.plist. I don't know why it doesn't hinder the boot process.
Oh right. Your debug files contain the ioreg which I didn't look at. It has all the information. 0x384 is the Probe Score from the info.plist (900 decimal). So a codeless kext would be identical, without all the extra code. Replace Apple16 with Hack16 or some other name. Change probe score to...