Contribute
Register

Alienware Alpha DSDT help!

Status
Not open for further replies.
Joined
Jan 31, 2011
Messages
89
Motherboard
HP ProBook 4530 | HP ProBook 5330m | Intel NUC BOXD54250WYKH1 | Alienware Alpha
CPU
i3-2350m | i3-2350m | i5-4250U | i3-4130T
Graphics
Intel HD 3000 | Intel HD 5000 | NVIDIA Geforce GTX 860M 2989 MB
Mac
  1. MacBook Pro
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hi all,

I'm trying to compile a non-patched DSDT but got 81 errors... Can someone help fix the errors? The errors consists of "Object does not exist (LNKF)", etc. I believe I have an IF statement outside of a Method() but I can't seem to find it or maybe it's something else. Need help of a DSDT guru.

The specs of my system are:
Alienware Alpha
Core i3-4130t
4GB Ram
500GB HD
Nvidia Geforce GTX 860M 2989 MB with Graphic Acceleration

I will write a tutorial on how to get this system up once I finish editing the DSDT.

Thank you!
 

Attachments

  • Alienware Alpha Original DSDT.zip
    33.7 KB · Views: 56
Hi all,

I'm trying to compile a non-patched DSDT but got 81 errors... Can someone help fix the errors? The errors consists of "Object does not exist (LNKF)", etc. I believe I have an IF statement outside of a Method() but I can't seem to find it or maybe it's something else. Need help of a DSDT guru.

The specs of my system are:
Alienware Alpha
Core i3-4130t
4GB Ram
500GB HD
Nvidia Geforce GTX 860M 2989 MB with Graphic Acceleration

I will write a tutorial on how to get this system up once I finish editing the DSDT.

Thank you!

Disassemble correctly... You need to disassemble with all SSDTs as context (iasl -da -dl *.aml).

Read laptop guide for details: http://www.tonymacx86.com/yosemite-laptop-support/152573-guide-patching-laptop-dsdt-ssdts.html
 

Attachments

  • AML Format.zip
    25.2 KB · Views: 81
  • DSL Format.zip
    50.7 KB · Views: 59
Awesome! Now to the DSDT patching... Is extracting DSDT/SSDT different now? I used MacIASL in the past but now we're using patchmatic/iasl.

Extracting DSDT/SSDT is covered in the guide linked by post #2.
 
Extracting DSDT/SSDT is covered in the guide linked by post #2.

Rehabman, I almost have it fully working now. I managed to fix sleep by using your GenericUSBXHCI.kext but I would like to switch it to the native AppleUSBXHCI.kext. The motherboard that comes with the Alienware Alpha is a 8 series motherboard - which DSDT edits do I need for USB 3.0? You mentioned on another website that you used "For Intel XHCI, I use DSDT patches to solve various problems (instant wake, USB2 defer to EHC, etc)." so I was wondering if I could apply those same DSDT patches to my DSDT.

Thanks.
 
Rehabman, I almost have it fully working now. I managed to fix sleep by using your GenericUSBXHCI.kext but I would like to switch it to the native AppleUSBXHCI.kext. The motherboard that comes with the Alienware Alpha is a 8 series motherboard - which DSDT edits do I need for USB 3.0? You mentioned on another website that you used "For Intel XHCI, I use DSDT patches to solve various problems (instant wake, USB2 defer to EHC, etc)." so I was wondering if I could apply those same DSDT patches to my DSDT.

Thanks.

The patches I use are covered at the link in post #2.
 
Just wanted to verify that power management is working... Here's the output from console:

May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 800 MHz
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 2900 MHz
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 2900 MHz
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU C7-Cores [ 0 2 3 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 17 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 17 18 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 17 18 20 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 20 25 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 20 24 25 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 19 20 24 25 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 17 18 19 20 23 24 25 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 19 20 22 23 24 25 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 15 17 18 19 20 22 23 24 25 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 15 17 18 19 20 21 22 23 24 25 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 15 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 15 17 18 19 20 21 22 23 24 25 26 28 (29) ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 15 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 15 16 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:45:45 localhost kernel[0]: AICPUPMI: CPU P-States [ (8) 10 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:45:55 LiLrYus-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (8) 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:45:56 LiLrYus-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (8) 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 28 29 ]
May 28 07:46:00 LiLrYus-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (8) 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 ]
May 28 07:46:25 LiLrYus-Mac-Pro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 ]
May 28 07:46:30 LiLrYus-Mac-Pro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 ]

but HWMonitor only moves from x8.0 to x29.0 and then from x29.0 back to x8.0, I haven't seen any other steps.

Thanks!
 
Just wanted to verify that power management is working... Here's the output from console:



but HWMonitor only moves from x8.0 to x29.0 and then from x29.0 back to x8.0, I haven't seen any other steps.

Thanks!

HwMonitor is not a valid way to track pstates.
 
Status
Not open for further replies.
Back
Top