Contribute
Register

iMac Pro X299 - Live the Future now with macOS 10.14 Mojave [Successful Build/Extended Guide]

Status
Not open for further replies.
kgp said:
Working USB port limit patches for 10.14.3 and 10.14.4 Beta1

Thanks to @ydeng, there are now working USB port limit patches for 10.14.3

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83FB0F0F 871604 00
Replace  : 83FB3F0F 871604 00
Name     : USB Port Limit Patch 1 ©ydeng

Code: 
kext     : com.apple.driver.usb.AppleUSBXHCI
Find     : 83FB0F0F 838F0400 00
Replace  : 83FB3F0F 838F0400 00
Name     : USB Port Limit Patch 2 ©ydeng

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83E30FD3 E34109DF
Replace  : 83E33FD3 E34109DF
Name     : USB Port Limit Patch 3 ©ydeng

And here are the respective USB port limit patches for 10.14.4 Beta1 provided by @PMHeart

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83FB0F0F 870B0400 00
Replace  : 83FB3F0F 870B0400 00
Name     : USB Port Limit Patch 1 ©PMHeart

Code: 
kext     : com.apple.driver.usb.AppleUSBXHCI
Find     : 4183FF0F 0F839404 0000
Replace  : 4183FF3F 0F839404 0000
Name     : USB Port Limit Patch 2 ©PMHeart

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83E30FD3 E34109DF
Replace  : 83E33FD3 E34109DF
Name     : USB Port Limit Patch 3 ©PMHeart

The port limit patches should be used in line with the fully implemented XHC USB kexts.

View attachment 382031

However, it is still recommended to disable the port limit patches and use truncated 15-port kexts instead. This might avoid buffer overruns and will make your system more vanilla with respect to future macOS updates.

Enjoy and have fun,

View attachment 382029
Click to expand...
kgp said:
Working USB port limit patches for 10.14.3 and 10.14.4 Beta1

Thanks to @ydeng, there are now working USB port limit patches for 10.14.3

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83FB0F0F 871604 00
Replace  : 83FB3F0F 871604 00
Name     : USB Port Limit Patch 1 ©ydeng

Code: 
kext     : com.apple.driver.usb.AppleUSBXHCI
Find     : 83FB0F0F 838F0400 00
Replace  : 83FB3F0F 838F0400 00
Name     : USB Port Limit Patch 2 ©ydeng

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83E30FD3 E34109DF
Replace  : 83E33FD3 E34109DF
Name     : USB Port Limit Patch 3 ©ydeng

And here are the respective USB port limit patches for 10.14.4 Beta1 provided by @PMHeart

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83FB0F0F 870B0400 00
Replace  : 83FB3F0F 870B0400 00
Name     : USB Port Limit Patch 1 ©PMHeart

Code: 
kext     : com.apple.driver.usb.AppleUSBXHCI
Find     : 4183FF0F 0F839404 0000
Replace  : 4183FF3F 0F839404 0000
Name     : USB Port Limit Patch 2 ©PMHeart

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83E30FD3 E34109DF
Replace  : 83E33FD3 E34109DF
Name     : USB Port Limit Patch 3 ©PMHeart

The port limit patches should be used in line with the fully implemented XHC USB kexts.

View attachment 382031

However, it is still recommended to disable the port limit patches and use truncated 15-port kexts instead. This might avoid buffer overruns and will make your system more vanilla with respect to future macOS updates.

Enjoy and have fun,

View attachment 382029
Click to expand...


And again .... Thank you very much :)
Now all USB ports on the maximus apex x299 are Works 100%
 
  • Like
Reactions: kgp
franksanderdo said:
Hi @perfecto245
If you are lucky, in Systemreport the SMART status tells you some thing.
What drive is it?
Following your fault description I would assume it can be connectors, cables or drive.

All teh Best
Frank
Click to expand...

Hi Frank, Thank you for reaching out. I think it was the drive.. it was disconnecting automatically, and I freezing my system whilst trying to access files. I replaced it and everything works normally :) will see if I can salvage the drive.. :)

Cheers
 
kgp said:
Working USB port limit patches for 10.14.3 and 10.14.4 Beta1

Thanks to @ydeng, there are now working USB port limit patches for 10.14.3

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83FB0F0F 871604 00
Replace  : 83FB3F0F 871604 00
Name     : USB Port Limit Patch 1 ©ydeng

Code: 
kext     : com.apple.driver.usb.AppleUSBXHCI
Find     : 83FB0F0F 838F0400 00
Replace  : 83FB3F0F 838F0400 00
Name     : USB Port Limit Patch 2 ©ydeng

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83E30FD3 E34109DF
Replace  : 83E33FD3 E34109DF
Name     : USB Port Limit Patch 3 ©ydeng

And here are the respective USB port limit patches for 10.14.4 Beta1 provided by @PMHeart

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83FB0F0F 870B0400 00
Replace  : 83FB3F0F 870B0400 00
Name     : USB Port Limit Patch 1 ©PMHeart

Code: 
kext     : com.apple.driver.usb.AppleUSBXHCI
Find     : 4183FF0F 0F839404 0000
Replace  : 4183FF3F 0F839404 0000
Name     : USB Port Limit Patch 2 ©PMHeart

Code: 
kext     : com.apple.iokit.IOUSBHostFamily
Find     : 83E30FD3 E34109DF
Replace  : 83E33FD3 E34109DF
Name     : USB Port Limit Patch 3 ©PMHeart

The port limit patches should be used in line with the fully implemented XHC USB kexts.

View attachment 382031

However, it is still recommended to disable the port limit patches and use truncated 15-port kexts instead. This might avoid buffer overruns and will make your system more vanilla with respect to future macOS updates.

Enjoy and have fun,

View attachment 382029
Click to expand...


Kgp mate, where can I find that 15 port usb kext you mentioned of? I didn't see it attached in your guide page..
 
kgp said:
@izo1, my default EFI-Folder implements AptioMemoryFix-64.efi! No need to use emuvariable! And as clearly advised, you should not install the rc scripts at all! AptioMemoryFix-64.efi allows for native NVRAM! And NVRAM reset can be done by pressing F11 in the Clover Boot menu, as friendly advised by @P1LGRIM above.

You do not reach native NVRAM implementation without AptioMemoryFix-64.efi and by using emuvariable instead. As @P1LGRIM also states, that's truly nonsense.

Did you read at all Section C.1)?

I know it seems hard for you to follow and accept respective guidelines (not only with respect to AptioMemoryFix-64.efi or recommended SSDTs) or to use the default EFI-Folder configuration, but frankly, it seems also impossible to help people who do not follow most respective advices.

Good luck in solving your issues anyway,

KGP
Click to expand...

I’m not using rc scripts or emu variable :)

I said I have used it previously and still cannot clear nvram.

Right now efi is as vanilla as your distribution.
 
izo1 said:
I’m not using rc scripts or emu variable :)

I said I have used it previously and still cannot clear nvram.

Right now efi is as vanilla as your distribution.
Click to expand...

:).. I see.. obviously I misunderstood something from the above discussion.

And the NVRAM reset with F11 does not work for you? You should contact the Clover guys on IM in this case.. ;)

There is a dedicated thread for discussing Clover related issues: https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/
 
P1LGRIM said:
This makes no sense.
You say that your motherboard has native NVRAM support but the only way that it can be affected by the disk is if you are emulating it.

If it is on the disk then it will be in nvram.plist which can be in the root of the system disk or the EFI partition.
It is not unknown for it to be hidden but it would be unusual.

What exactly is the problem that you have with your NVRAM ?
Click to expand...

What doesn’t make sense? I am trying to clear the NVRAM and let macOS recreate it automatically.

I switched motherboards and kept the same macOS install and want a fresh NVRAM.

I used to be able to do this, but for some reason says not allowed.
 
izo1 said:
but for some reason says not allowed
Click to expand...
What says not allowed ?
This is the first time that you have mentioned this.
 
Last edited:
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top