Jump to content

[Guide] Mac OSX 10.12 and 10.13 with X99 Broadwell-E family and Haswell-E family

nmano

By nmano,
in Installation Guides

 Share
1,954 posts in this topic

Recommended Posts

WeBeRiO
WeBeRiO
Posted
Posted

Ur problema es  PMDrvr

 

el kext es alucinante, pero al reiniciar el sistema truco del sueño

Can I remove without problem?

 

I do not know how it got here O_o

post-471348-0-22752700-1496420888_thumb.png

  • Like 1
Link to comment
Share on other sites
MaLd0n
MaLd0n
Posted
Posted

 

Can I remove without problem?

 

I do not know how it got here O_o

 

;)

i have problem with sleep if i inject device PNLF and ALS0, and of course pmdrver.kext too if you are using xcpm.

i'm using iMac smbios, LMU and PNLF patches for iMac not for MacPro, but i tested, no problem, work in MacPro and iMac.

Link to comment
Share on other sites
Regi Yassin
Regi Yassin
Posted
Posted

;)

i'm using iMac smbios, LMU and PNLF patches for iMac not for MacPro, but i tested, no problem, work in MacPro and iMac.

yesterday i did clean install with smbios imac15,1, with smbios 15,1 wont wake with PNLF and ALS0, test with PNLF only, wont wake, with ALS0 only, wont wake, both, wont wake, without both, works.

with macpro  i cant recall about sleep with those devices, 

Link to comment
Share on other sites
alfaSZ
alfaSZ
Posted
Posted

if u have a problem, just remove ;)

Hi, long time lurker here and reasonably knowledgable as a result.. But after spending considerable amounts of time adding mini ssdts to inject properties such as name, AAPL,slot-name and _SUN (and a few others) for most of the devices I cannot locate what exactly it is that makes system profiler unhappy and returns the dreaded "error while gathering pci device information" under PCI devices.

In your experience is there something specific that is required? Is there a rule? Or are people painstakingly injecting properties for everything under the sun until the message goes away?

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites
alfaSZ
alfaSZ
Posted
Posted

Let the compiler work 

put Return (Package () and Buffer (), and compile again

 

Hi - maybe if you have a sec you could take look at my IOReg? I have tried to incorporate pretty much everything mentioned on this thread, you'll see all devices are loading drivers properly and have "model", "device_type" and "AAPL,slot-name" properties...

 

I can't think of anything else I can do in order to fix the cosmetic System Information -> Hardware -> PCI screen work, I keep getting "There was an error while gathering PCI device information"

Mac Pro.ioreg.zip

Link to comment
Share on other sites
Regi Yassin
Regi Yassin
Posted
Posted

Hi - maybe if you have a sec you could take look at my IOReg? I have tried to incorporate pretty much everything mentioned on this thread, you'll see all devices are loading drivers properly and have "model", "device_type" and "AAPL,slot-name" properties...

 

I can't think of anything else I can do in order to fix the cosmetic System Information -> Hardware -> PCI screen work, I keep getting "There was an error while gathering PCI device information"

can u post your acpi/patched folder?

Link to comment
Share on other sites
alfaSZ
alfaSZ
Posted
Posted

try this, if errors still exist, try to drop ssdt-nvme and ssdt-xhci, if error is gone, then we know where the problem is, i see you are not using patch nvme spoof.

 

Thank you very much for the pointer - indeed the SSDT-HDEF was a mis-mash and I was totally missing the graphics cards, once I added two GFX1's (using GFX1 rather than GFX0 so I don't have to patch the AGDP kext that unloads the first GPU) everything worked, at long last ... 

Check, all in DSDT

attachicon.gifalfaSZ.zip

 

need test, the best is ioreg without SSDTs, for check real device names, _ADR...

 

Got you, just managed to sort my mess of files together as posted in the previous post, will definitely look at your much cleaner approach and report back ..

post-1459809-0-49841900-1496499662_thumb.png

  • Like 1
Link to comment
Share on other sites
mfc88
mfc88
Posted
Posted

Thank you very much for the pointer - indeed the SSDT-HDEF was a mis-mash and I was totally missing the graphics cards, once I added two GFX1's (using GFX1 rather than GFX0 so I don't have to patch the AGDP kext that unloads the first GPU) everything worked, at long last ... 

 

Got you, just managed to sort my mess of files together as posted in the previous post, will definitely look at your much cleaner approach and report back ..

If you're going to use SSDTs, then it's best to separate out the devices via SSDT-{old_device_name}.AML. You have a lot of nested devices that make it rather confusing and unnecessary. The idea behind multiple SSDTs is that if one thing breaks/isn't injected/prevents booting, you can simply drop it before loading up the OS and it won't interfere with the other devices. And, these SSDTs will survive BIOS updates (custom DSDTs most likely will not -- tested and confirmed). 

 

You can use my ssdtGenApp as a starting point, then you'll want to add a "_SUN" method for PCI slots. In order to get the PCI devices to show up in the PCI device list, you'll need a "AAPL,slot-name", "name" and "model" device property. With the exception of NVME, if using HackrNVMEFamily, where you'll want to remove the original device and any D0XX/PXSX devices and then replace it with a new name (NVME), otherwise "Slot" will always be "Ethernet". 

 

Clean up the SSDTs.

Link to comment
Share on other sites
k1n4
k1n4
Posted
Posted

here it is

Regi i've the same MOBO, and the same problem with FakeSMC Sensors... they cause random kernel panic on startup "kernel backtrace hang on boot..."

I'll setup soon ssdt's like you but i've very little time for it. Could someone help for this?

Thanks a lot 

Link to comment
Share on other sites
Matthew82
Matthew82
Posted
Posted

Regi i've the same MOBO, and the same problem with FakeSMC Sensors... they cause random kernel panic on startup "kernel backtrace hang on boot..."

I'll setup soon ssdt's like you but i've very little time for it. Could someone help for this?

Thanks a lot 

Use Slice version of FakeSMC. Is more stable for X99 systems  https://sourceforge.net/projects/hwsensors3.hwsensors.p/?source=navbar

Link to comment
Share on other sites
Dmitry R
Dmitry R
Posted
Posted

HI guys, I'm trying to make xcpm or any kind of speedstep work on 10.12.5 running on MSI x99a with xeon E5-2630L v3 and can't make it happen. On 10.11.6 speedstep works just fine with the same clover config. I tried all possible kernel patches, with and without generated ssdt by ssdtPRGen.sh, nothing helps. The speedstep just doesn't work. The output of AppleIntelinfo on 10.12.5 is this:

bash-3.2# cat /tmp/AppleIntelInfo.dat
AppleIntelInfo.kext v2.5 Copyright © 2012-2017 Pike R. Alpha. All rights reserved.

Settings:
------------------------------------------
logMSRs..................................: 1
logIGPU..................................: 0
logCStates...............................: 1
logIPGStyle..............................: 1
InitialTSC...............................: 0x232eadfeb6e (134 MHz)
MWAIT C-States...........................: 8480

Processor Brandstring....................: Genuine Intel(R) CPU @ 1.80GHz

Processor Signature..................... : 0x306F1
------------------------------------------
 - Family............................... : 6
 - Stepping............................. : 1
 - Model................................ : 0x3F (63)

Model Specific Registers (MSRs)
------------------------------------------

MSR_CORE_THREAD_COUNT............(0x35)  : 0x0
------------------------------------------
 - Core Count........................... : 8
 - Thread Count......................... : 16

MSR_PLATFORM_INFO................(0xCE)  : 0x80C33FB811200
------------------------------------------
 - Maximum Non-Turbo Ratio.............. : 0x12 (1800 MHz)
 - Ratio Limit for Turbo Mode........... : 1 (programmable)
 - TDP Limit for Turbo Mode............. : 1 (programmable)
 - Low Power Mode Support............... : 1 (LPM supported)
 - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available)
 - Maximum Efficiency Ratio............. : 12
 - Minimum Operating Ratio.............. : 8

MSR_PMG_CST_CONFIG_CONTROL.......(0xE2)  : 0x8400
------------------------------------------
 - I/O MWAIT Redirection Enable......... : 1 (enabled, IO read of MSR(0xE4) mapped to MWAIT)
 - CFG Lock............................. : 1 (MSR locked until next reset)
 - C3 State Auto Demotion............... : 0 (disabled/unsupported)
 - C1 State Auto Demotion............... : 0 (disabled/unsupported)
 - C3 State Undemotion.................. : 0 (disabled/unsupported)
 - C1 State Undemotion.................. : 0 (disabled/unsupported)
 - Package C-State Auto Demotion........ : 0 (disabled/unsupported)
 - Package C-State Undemotion........... : 0 (disabled/unsupported)

MSR_PMG_IO_CAPTURE_BASE..........(0xE4)  : 0x10414
------------------------------------------
 - LVL_2 Base Address................... : 0x414
 - C-state Range........................ : 1 (C6 is the max C-State to include)

IA32_MPERF.......................(0xE7)  : 0x1228F9D08AE
IA32_APERF.......................(0xE8)  : 0x122838E36CB

MSR_FLEX_RATIO...................(0x194) : 0x0
------------------------------------------

MSR_IA32_PERF_STATUS.............(0x198) : 0x195600001200
------------------------------------------
 - Current Performance State Value...... : 0x1200 (1800 MHz)

MSR_IA32_PERF_CONTROL............(0x199) : 0x1200
------------------------------------------
 - Target performance State Value....... : 0x1200 (1800 MHz)
 - Intel Dynamic Acceleration........... : 0 (IDA engaged)

IA32_CLOCK_MODULATION............(0x19A) : 0x0

IA32_THERM_INTERRUPT.............(0x19B) : 0x0

IA32_THERM_STATUS................(0x19C) : 0x88210000
------------------------------------------
 - Thermal Status....................... : 0
 - Thermal Log.......................... : 0
 - PROCHOT # or FORCEPR# event.......... : 0
 - PROCHOT # or FORCEPR# log............ : 0
 - Critical Temperature Status.......... : 0
 - Critical Temperature log............. : 0
 - Thermal Threshold #1 Status.......... : 0
 - Thermal Threshold #1 log............. : 0
 - Thermal Threshold #2 Status.......... : 0
 - Thermal Threshold #2 log............. : 0
 - Power Limitation Status.............. : 0
 - Power Limitation log................. : 0
 - Current Limit Status................. : 0
 - Current Limit log.................... : 0
 - Cross Domain Limit Status............ : 0
 - Cross Domain Limit log............... : 0
 - Digital Readout...................... : 33
 - Resolution in Degrees Celsius........ : 1
 - Reading Valid........................ : 1 (valid)

MSR_THERM2_CTL...................(0x19D) : 0x0

IA32_MISC_ENABLES................(0x1A0) : 0x850089
------------------------------------------
 - Fast-Strings......................... : 1 (enabled)
 - FOPCODE compatibility mode Enable.... : 0
 - Automatic Thermal Control Circuit.... : 1 (enabled)
 - Split-lock Disable................... : 0
 - Performance Monitoring............... : 1 (available)
 - Bus Lock On Cache Line Splits Disable : 0
 - Hardware prefetch Disable............ : 0
 - Processor Event Based Sampling....... : 0 (PEBS supported)
 - GV1/2 legacy Enable.................. : 0
 - Enhanced Intel SpeedStep Technology.. : 1 (enabled)
 - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported)
 - Adjacent sector prefetch Disable..... : 0
 - CFG Lock............................. : 0 (MSR not locked)
 - xTPR Message Disable................. : 1 (disabled)

MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x5A0A00
------------------------------------------
 - Turbo Attenuation Units.............. : 0 
 - Temperature Target................... : 90
 - TCC Activation Offset................ : 0

MSR_MISC_PWR_MGMT................(0x1AA) : 0x400000
------------------------------------------
 - EIST Hardware Coordination........... : 0 (hardware coordination enabled)
 - Energy/Performance Bias support...... : 1
 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software)
 - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores)

MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x1414141516171819
------------------------------------------
 - Maximum Ratio Limit for C01.......... : 19 (2500 MHz) 
 - Maximum Ratio Limit for C02.......... : 18 (2400 MHz) 
 - Maximum Ratio Limit for C03.......... : 17 (2300 MHz) 
 - Maximum Ratio Limit for C04.......... : 16 (2200 MHz) 
 - Maximum Ratio Limit for C05.......... : 15 (2100 MHz) 
 - Maximum Ratio Limit for C06.......... : 14 (2000 MHz) 
 - Maximum Ratio Limit for C07.......... : 14 (2000 MHz) 
 - Maximum Ratio Limit for C08.......... : 14 (2000 MHz) 

MSR_POWER_CTL....................(0x1FC) : 0x29000059
------------------------------------------
 - Bi-Directional Processor Hot..........: 1 (enabled)
 - C1E Enable............................: 0 (disabled)

MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03
------------------------------------------
 - Power Units.......................... : 3 (1/8 Watt)
 - Energy Status Units.................. : 14 (61 micro-Joules)
 - Time Units .......................... : 10 (976.6 micro-Seconds)

MSR_PKG_POWER_LIMIT..............(0x610) : 0x782A0001D8230
------------------------------------------
 - Package Power Limit #1............... : 70 Watt
 - Enable Power Limit #1................ : 1 (enabled)
 - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1)
 - Time Window for Power Limit #1....... : 14 (40960 milli-Seconds)
 - Package Power Limit #2............... : 84 Watt
 - Enable Power Limit #2................ : 1 (enabled)
 - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2)
 - Time Window for Power Limit #2....... : 3 (20 milli-Seconds)
 - Lock................................. : 0 (MSR not locked)

MSR_PKG_ENERGY_STATUS............(0x611) : 0x19B00E05
------------------------------------------
 - Total Energy Consumed................ : 26304 Joules (Watt = Joules / seconds)

MSR_CONFIG_TDP_NOMINAL...........(0x648) : 0x12
MSR_CONFIG_TDP_LEVEL1............(0x649) : 0xC40460000F0230
MSR_CONFIG_TDP_LEVEL2............(0x64a) : 0xC4046000000000
MSR_CONFIG_TDP_CONTROL...........(0x64b) : 0x0
MSR_TURBO_ACTIVATION_RATIO.......(0x64c) : 0x0
MSR_PKGC3_IRTL...................(0x60a) : 0x0
MSR_PKGC6_IRTL...................(0x60b) : 0x0
MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x0
MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0x0
MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x0
MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x0

IA32_TSC_DEADLINE................(0x6E0) : 0x232EDCB50C2

CPU Ratio Info:
------------------------------------------
Base Clock Frequency (BLCK)............. : 100 MHz
Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz)
Maximum non-Turbo Ratio/Frequency........: 18 (1800 MHz)
Maximum Turbo Ratio/Frequency............: 25 (2500 MHz)
P-State ratio * 100 = Frequency in MHz
------------------------------------------

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff; min-height: 13.0px}
span.s1 {font-variant-ligatures: no-common-ligatures}
CPU P-States [ (18) ]

I also attached my clover config file, generated ssdt and ioreg file.

How to fix this? 

Thank you.

 

10.12.5.ssdtPRGen.ioreg.zip

config.plist.zip

SSDT.aml.zip

Link to comment
Share on other sites
k1n4
k1n4
Posted
Posted

Use Slice version of FakeSMC. Is more stable for X99 systems https://sourceforge.net/projects/hwsensors3.hwsensors.p/?source=navbar

Thanks a lot for your reply.

It's possibile to give the binaries for the "Slice version"?

I prefer to put FakeSMC and all the plugins in clover/kext folder instead that on S/L/E folder.

Thanks again

 

 

Inviato dal mio iPhone utilizzando Tapatalk

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...