Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

Reply to thread

Message

1. CPU PM - You can check this for ssdtPRGen - https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/236 and if it doesn't help, you can create normal Clover USB and tick the checkboxes on Clover Configurator to generate C&P states for your CPU, boot it and dump the tables with F4 i think it was, then you can boot with OC and copy the dumped SSDT from the Clover USB to OC.

2. The LPC Bridge on my motherboard is at specific path (\_SB.PCI0.ISA), so you will need to find it using Hackintool (Look for LPC/LPCB/ISA or google for more examples what this can be called in a DSDT device path). Also mine address as example appears as 3a16 on Windows and 3a18 on macOS, so be careful with that if you use Windows. The rest are probably universal (compare the paths and the addresses), because the SMBus is fake device in this case.

3. Yes, you need to plug USB 1.1 devices into USB 2.0 hub.

4. The DTGP method is called in some SSDTs, so this is why it's included. The MCDP was the one used sometimes before DTGP (i think) and it doesn't do any harm. No DSDT modification is needed, it's only dumped and used as a reference for what needs to be patched via SSDTs.

<blockquote data-quote="np44" data-source="post: 5819" data-attributes="member: 4875">1. CPU PM - You can check this for ssdtPRGen - <a href="https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/236" target="_blank">https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/236</a> and if it doesn&#039;t help, you can create normal Clover USB and tick the checkboxes on Clover Configurator to generate C&amp;P states for your CPU, boot it and dump the tables with F4 i think it was, then you can boot with OC and copy the dumped SSDT from the Clover USB to OC.2. The LPC Bridge on my motherboard is at specific path (\_SB.PCI0.ISA), so you will need to find it using Hackintool (Look for LPC/LPCB/ISA or google for more examples what this can be called in a DSDT device path). Also mine address as example appears as 3a16 on Windows and 3a18 on macOS, so be careful with that if you use Windows. The rest are probably universal (compare the paths and the addresses), because the SMBus is fake device in this case.3. Yes, you need to plug USB 1.1 devices into USB 2.0 hub.4. The DTGP method is called in some SSDTs, so this is why it&#039;s included. The MCDP was the one used sometimes before DTGP (i think) and it doesn&#039;t do any harm. No DSDT modification is needed, it&#039;s only dumped and used as a reference for what needs to be patched via SSDTs.</blockquote>

[QUOTE="np44, post: 5819, member: 4875"] 1. CPU PM - You can check this for ssdtPRGen - [URL]https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/236[/URL] and if it doesn't help, you can create normal Clover USB and tick the checkboxes on Clover Configurator to generate C&P states for your CPU, boot it and dump the tables with F4 i think it was, then you can boot with OC and copy the dumped SSDT from the Clover USB to OC. 2. The LPC Bridge on my motherboard is at specific path (\_SB.PCI0.ISA), so you will need to find it using Hackintool (Look for LPC/LPCB/ISA or google for more examples what this can be called in a DSDT device path). Also mine address as example appears as 3a16 on Windows and 3a18 on macOS, so be careful with that if you use Windows. The rest are probably universal (compare the paths and the addresses), because the SMBus is fake device in this case. 3. Yes, you need to plug USB 1.1 devices into USB 2.0 hub. 4. The DTGP method is called in some SSDTs, so this is why it's included. The MCDP was the one used sometimes before DTGP (i think) and it doesn't do any harm. No DSDT modification is needed, it's only dumped and used as a reference for what needs to be patched via SSDTs. [/QUOTE]

Verification

Top Bottom