Jump to content

ssdtGen - custom generated SSDTs (x99/z170/z97/h97 systems)


mfc88
 Share

203 posts in this topic

Recommended Posts

Not sure if this will work, but see if you can run it in 10.11.6...

 

Thank you !!

Sure it does work. but not as i was expecting :)

 

 

My bad and sorry for having misread your first post. I should have paid better attention,

post-80278-0-56826100-1494261328_thumb.png

Link to comment
Share on other sites

Thank you !!

Sure it does work. but not as i was expecting :)

 

 

My bad and sorry for having misread your first post. I should have paid better attention,

I might be able to add support for your board, but it may take some trial and error.

 

Up to you. If so, send me your current Clover folder and a IORegistry dump.

  • Like 1
Link to comment
Share on other sites

I might be able to add support for your board, but it may take some trial and error.

 

Up to you. If so, send me your current Clover folder and a IORegistry dump.

 

Here it is

 

I guess since the time i've been around, trials and errors have become our daily companions :)

 

Thanks

 

 

Thanks

going to give a look

Link to comment
Share on other sites

Here it is

 

I guess since the time i've been around, trials and errors have become our daily companions :)

 

Thanks

1. You'll need to remove the DSDT.aml from CLOVER->ACPI->patched.

2.) Since you're using Clover for CPU PM (generate C/P states) you'll want to remove the RampageDev "SSDT.aml" from CLOVER->ACPI->patched. As is, it'll conflict with the custom SSDTs.

3.) You'll need to edit your config.plist:

3a.) Acpi->Fixes ==> Unselect: addDTGP, addMCHC (does nothing for you), fixSBUS, fixSATA, fixUSB, and fixHDA.

3b.) Under Boot, uncheck nvda_drv=1 and instead select/check "nv_disable=1". Under Graphics, select/check "Inject NVidia".

3c.) Under KextsToPatch, disable all AppleGraphicsDevicePolicy patches (click the "Disable" checkbox)

4.) Reboot

5.) Download and run this version of  ssdtGen_0.2.2b(v2).zip, select "Build All"

6a.) If you get any SSDT errors, run in Debug mode, and attach/post debug.output.txt. Revert back to your original CLOVER folder.

or

6b.) If no errors, take the SSDTs, drop them in CLOVER->ACPI->patched.

6b1.) Edit your config.plist, under Boot, check nvda_drv=1, and unselect "nv_disable=1". Under Graphics, unselect "Inject Nvidia".

6b2.) Reboot

6b3.) Assuming you don't get a black screen on boot (if you do, revert back to step 3b) attach an IORegistry dump.

  • Like 1
Link to comment
Share on other sites

i will try and post results

Thanks 

 

 

Did exactly as you suggested

no errors at all, everything went smooth.

 

So please accept my Thanks again for your time, patience and great help!

 

I suppose this are the possible file generated for my mobo is it?

post-80278-0-01582300-1494510105.png

Edited by LAbyOne
Link to comment
Share on other sites

i will try and post results

Thanks 

 

 

Did exactly as you suggested

no errors at all, everything went smooth.

 

So please accept my Thanks again for your time, patience and great help!

 

I suppose this are the possible file generated for my mobo is it?

Missing GLAN and HDAS. Run "Build GLAN" and "Build HDAS" and check for errors.

Link to comment
Share on other sites

Missing GLAN and HDAS 

Yeah i noticed that too

and when trying to make it i get this

 

Creating: SSDT-GLAN.dsl

 

—-ERROR—- There was a problem locating GLAN's device-id property!

—-ERROR—- There was a problem locating GLAN's subsystem-id property!

—-ERROR—- There was a problem locating GLAN's subsystem-vendor-id property!

 

Attempting to compile: SSDT-GLAN.dsl

 

 

Intel ACPI Component Architecture

ASL+ Optimizing Compiler version 20161222-64(RM)

Copyright © 2000 - 2017 Intel Corporation

 

ASL Input:     /Users/labyone/Desktop/SSDT-GLAN.dsl - 24 lines, 841 bytes, 5 keywords

 

Compilation complete. 2 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

 

Removing: SSDT-GLAN.dsl

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

—-ERROR—- SSDT-GLAN.dsl has failed to compile!

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

 

 

 

Creating: SSDT-HDAS.dsl

 

—-ERROR—- There was a problem locating HDAS's acpi-path property!

—-ERROR—- There was a problem locating HDAS's compatible property!

 

Attempting to compile: SSDT-HDAS.dsl

 

 

Intel ACPI Component Architecture

ASL+ Optimizing Compiler version 20161222-64(RM)

Copyright © 2000 - 2017 Intel Corporation

 

ASL Input:     /Users/labyone/Desktop/SSDT-HDAS.dsl - 27 lines, 926 bytes, 8 keywords

 

Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

 

Removing: SSDT-HDAS.dsl

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

—-ERROR—- SSDT-HDAS.dsl has failed to compile!

-----------------------------------------------------------------------------------------------------------------------------------------------------

Link to comment
Share on other sites

 

Yeah i noticed that too

and when trying to make it i get this

 

Creating: SSDT-GLAN.dsl

 

—-ERROR—- There was a problem locating GLAN's device-id property!

—-ERROR—- There was a problem locating GLAN's subsystem-id property!

—-ERROR—- There was a problem locating GLAN's subsystem-vendor-id property!

 

Attempting to compile: SSDT-GLAN.dsl

 

 

Intel ACPI Component Architecture

ASL+ Optimizing Compiler version 20161222-64(RM)

Copyright © 2000 - 2017 Intel Corporation

 

ASL Input:     /Users/labyone/Desktop/SSDT-GLAN.dsl - 24 lines, 841 bytes, 5 keywords

 

Compilation complete. 2 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

 

Removing: SSDT-GLAN.dsl

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

—-ERROR—- SSDT-GLAN.dsl has failed to compile!

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

 

 

 

Creating: SSDT-HDAS.dsl

 

—-ERROR—- There was a problem locating HDAS's acpi-path property!

—-ERROR—- There was a problem locating HDAS's compatible property!

 

Attempting to compile: SSDT-HDAS.dsl

 

 

Intel ACPI Component Architecture

ASL+ Optimizing Compiler version 20161222-64(RM)

Copyright © 2000 - 2017 Intel Corporation

 

ASL Input:     /Users/labyone/Desktop/SSDT-HDAS.dsl - 27 lines, 926 bytes, 8 keywords

 

Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

 

Removing: SSDT-HDAS.dsl

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

—-ERROR—- SSDT-HDAS.dsl has failed to compile!

 

-----------------------------------------------------------------------------------------------------------------------------------------------------

 

Send me a current IORegistry dump.

Link to comment
Share on other sites

Need to see an IOReg without DSDT.aml installed. Otherwise, useless.

 

Also, send me generated SSDTs. Need to make sure they're built to expected specifications. 

 

On that note, you don't have a GLAN device, which is fine. Your internet is routed thru RP03 -- ethernet and RP05 -- WIFI. So GLAN is not needed. However, HDAS should be a device (unless it's already named HDEF which results in a ssdtGen compilation error -- should not be the case if running vanilla).

Link to comment
Share on other sites

Need to see an IOReg without DSDT.aml installed. Otherwise, useless.

 

Also, send me generated SSDTs. Need to make sure they're built to expected specifications. 

 

On that note, you don't have a GLAN device, which is fine. Your internet is routed thru RP03 -- ethernet and RP05 -- WIFI. So GLAN is not needed. However, HDAS should be a device (unless it's already named HDEF which results in a ssdtGen compilation error -- should not be the case if running vanilla).

indeed

 

Actually there isn't any in my current boot only ssdt's generated by your app

Link to comment
Share on other sites

indeed

 

Actually there isn't any in my current boot only ssdt's generated by your app

Do me a favor and dump your ACPI tables. At Clover Boot Manager screen, press F4, wait 5 seconds, then boot into the OS. Mount your drive, go to CLOVER->ACPI->origin and upload that folder.

Also, it looks like SBUS isn't being completely injected. Here's a fix for that...

ssdtGen_v0.2.2b.zip

Link to comment
Share on other sites

Do me a favor and dump your ACPI tables. At Clover Boot Manager screen, press F4, wait 5 seconds, then boot into the OS. Mount your drive, go to CLOVER->ACPI->origin and upload that folder.

Also, it looks like SBUS isn't being completely injected. Here's a fix for that...

 

No problem,

Done

Link to comment
Share on other sites

No problem,

Done

Okay... looks like your DSDT already has it named HDEF... perhaps a kext?

 

Also, it looks like something (kext again?) is altering some other devices.

 

Under PEG0, it should be: GFX1 and HDAU.

Instead it's: GFX1 and HDEF.

 

You're getting motherboard (on-board) sound, yes?

 

Also, add these patches to your config.plist, under Apci, DSDT patches ("Rename _DSM to XDSM" is optional for you):

Comment: Change _OSI to XOSI
Find: 5f4f5349 
Replace: 584f5349

Comment: Change EHC1 to EH01
Find: 45484331 
Replace: 45483031 

Comment: Change EHC2 to EH02
Find: 45484332 
Replace: 45483032
Link to comment
Share on other sites

 

Okay... looks like your DSDT already has it named HDEF... perhaps a kext?

 

Also, it looks like something (kext again?) is altering some other devices.

 

Under PEG0, it should be: GFX1 and HDAU.

Instead it's: GFX1 and HDEF.

 

You're getting motherboard (on-board) sound, yes?

 

Also, add these patches to your config.plist, under Apci, DSDT patches ("Rename _DSM to XDSM" is optional for you):

Comment: Change _OSI to XOSI
Find: 5f4f5349 
Replace: 584f5349

Comment: Change EHC1 to EH01
Find: 45484331 
Replace: 45483031 

Comment: Change EHC2 to EH02
Find: 45484332 
Replace: 45483032

ok i'll do that

about kext i din't install any particular, made excetion for an injector to get my audio working.. (done with HDA Patcher)

 

then i just want to let you know, that in latest ssdtGen you gave me something not working right, for GFX1 

with previous release i was able to see the nvidia card into pci's system profiler, now with this new one its gone.

 

otherwise all seem working fine i guess its just cosmetic.

Link to comment
Share on other sites

 

ok i'll do that

about kext i din't install any particular, made excetion for an injector to get my audio working.. (done with HDA Patcher)

 

then i just want to let you know, that in latest ssdtGen you gave me something not working right, for GFX1 

with previous release i was able to see the nvidia card into pci's system profiler, now with this new one its gone.

 

otherwise all seem working fine i guess its just cosmetic.

 

Should still be there... perhaps because it's named GFX1 instead of GFX0?

 

Try this... (remove GFX1, replace with GFX0)

SSDT-GFX0.aml.zip

Link to comment
Share on other sites

Should still be there... perhaps because it's named GFX1 instead of GFX0?

 

Try this... (remove GFX1, replace with GFX0)

Nope. no renaming by my side

but i genarated a new one with old ssdtGen_0.2.2.b(v2) and its working ok as GFX1

that's why i guessed something was wrong with latest

 

oops forgot to mention still unable to generate HDAS.aml

Link to comment
Share on other sites

Nope. no renaming by my side

but i genarated a new one with old ssdtGen_0.2.2.b(v2) and its working ok as GFX1

that's why i guessed something was wrong with latest

 

oops forgot to mention still unable to generate HDAS.aml

The ssdtGen.command file that generates the SSDTs wasn't changed from 0.2.2(v2) to what was released. Sounds like an injection issue.

 

Try rebooting multiple times and checking. I have a feeling it'll be inconsistent.

 

Also, you can't generate HDAS as it's already named HDEF. Whatever you're using for audio is changing your ACPI device names.

Link to comment
Share on other sites

You do not have to prove anything to anyone, but many ppl here know what they are doing.

Many times I've edited your post(without warning), you know we have rules here about some forum out there.

 

Take care and keep working!

 

Topic Locked

 

if u need open, send PM to mod or admin

Link to comment
Share on other sites

  • 2 weeks later...

Just wanted to preface this post by giving a huge, huge thank you to the InsanelyMac staff for all their support.

 

Anyway, I've updated the first post. However, in that time that this thread was locked, my passions have shifted and lie with web application development. As such, support for the ssdtGenApp will stop at v0.2.2b. However, the app will still be functional and work across the X99/Z170/Z97 and H97 platforms, but may run into future problems with future OS upgrades. As such, if any current or future developers/coders would like to continue supporting it, I've attached the source files to the post as well (with plenty of source notes). You are more than welcome to modify, adjust, alter, and change the app files to suit your needs.

  • Like 6
Link to comment
Share on other sites

 Share

×
×
  • Create New...