Contribute
Register

SSDT generation script (Ivybridge PM)

Status
Not open for further replies.
Hey pike sorry for bugging so much i use your newest update and i get this waring so how do i go about fixing it.




sdtPRGen.sh v4.7 Copyright (c) 2013 by Pike R. Alpha
----------------------------------------------------------------
Generating SSDT_PR.dsl for a Macmini6,2 [Mac-F65AE981FFA204ED]
Ivy Bridge Core i7-3770K processor [0x0701] setup
With a maximum TDP of 77 Watt, as specified by Intel
Number logical CPU's: 8 (Core Frequency: 3500 MHz)
Number of Turbo States: 4 (3600-3900 MHz)
Number of P-States: 24 (1600-3900 MHz)
Injected C-States for CPU0 (C1,C3,C6)
Injected C-States for CPU1 (C1,C2,C3)
Warning: Model identifier [Macmini6,2] is missing from: /S*/L*/CoreServices/PlatformSupport.plist
Warning: boardID [Mac-F65AE981FFA204ED] is missing from: /S*/L*/CoreServices/PlatformSupport.plist


Intel ACPI Component Architecture
ASL Optimizing Compiler version 20130117-64 [Jan 19 2013]
Copyright (c) 2000 - 2013 Intel Corporation


ASL Input: /Users/mikey/Desktop/SSDT_PR.dsl - 260 lines, 8322 bytes, 56 keywords
AML Output: /Users/mikey/Desktop/SSDT_PR.aml - 1594 bytes, 27 named objects, 29 executable opcodes


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


Do you want to copy /Users/mikey/Desktop/SSDT_PR.aml to /Extra/SSDT.aml? (y/n)?y
 
Hey Pike --

I made some mods to the original script a while ago to generate for all the Sandy Bridge mobile chips. I'm no script wiz like you guys are (I'm still a bash noob), but it worked and I thought why not contribute the data for SNB mobile.

So I added this table to your current script:
Code:
...

gMobileSandyBridgeCPUList=(
# i3 SNB mobile
i3-2310M,35,800,2100,2100,2,4
i3-2330M,35,800,2200,2200,2,4
i3-2350M,35,800,2300,2300,2,4
i3-2370M,35,800,2400,2400,2,4
# i5 SNB mobile
i5-2410M,35,800,2300,2900,2,4
i5-2430M,35,800,2400,3000,2,4
i5-2450M,35,800,2500,3100,2,4
i5-2520M,35,800,2500,3200,2,4
i5-2540M,35,800,2600,3300,2,4
# i7 SNB mobile (dual core)
i7-2620M,35,800,2700,3400,2,4
i7-2640M,35,800,2800,3500,2,4
# i7 SNB mobile (quad core, 45w)
i7-2630QM,45,800,2000,2900,4,8
i7-2670QM,45,800,2200,3100,4,8
i7-2720QM,45,800,2200,3300,4,8
i7-2760QM,45,800,2400,3500,4,8
i7-2820QM,45,800,2300,3400,4,8
i7-2860QM,45,800,2500,3600,4,8
# i7 SNB mobile (quad core, 55w)
i7-2920QM,55,800,2500,3500,4,8
i7-2960QM,55,800,2700,3700,4,8
)
...

And added code to search it:
Code:
...
    if (!(($gTypeCPU))); then
        __searchList gMobileIvyBridgeCPUList[@] $gMobileCPU
    fi

# added for sandy bridge...
    if (!(($gTypeCPU))); then
        __searchList gMobileSandyBridgeCPUList[@] $gMobileCPU
    fi

...

Tried it and it seemed to generate the right thing for my i3-2310m in my ProBook?

Can you add this to the script?

Thanks!
 
Hey Pike --

I made some mods to the original script a while ago to generate for all the Sandy Bridge mobile chips. I'm no script wiz like you guys are (I'm still a bash noob), but it worked and I thought why not contribute the data for SNB mobile.

So I added this table to your current script:
...
Tried it and it seemed to generate the right thing for my i3-2310m in my ProBook?
Can you add this to the script?
Thanks!
Francis made a long list of Sandy Bridge CPU's in post #138 (thanks for that by the way Francis) and that list will be used in a next update – Jeroen asked me to review it, but I forgot about it so thank you for the reminder.
 
Francis made a long list of Sandy Bridge CPU's in post #138 (thanks for that by the way Francis) and that list will be used in a next update – Jeroen asked me to review it, but I forgot about it so thank you for the reminder.

That's great. I haven't really been following this thread that closely. Might need some review as perhaps some things have changed in the script since then (the entries don't specify the lower 800mhz frequency, for example).
 
Pike --

BTW, there is something funny about your RevoBoot github repo. When I clone it with:

Code:
git clone git://github.com/Piker-Alpha/RevoBoot.git revoboot.git

Then try to get to the acpi/Tools area...
Code:
localhost:Projects Admin$ cd revoboot.git/
localhost:revoboot.git Admin$ cd i386/libsaio/acpi
localhost:acpi Admin$ cd Tools
-bash: cd: Tools: No such file or directory
localhost:acpi Admin$ ls
debug.h			patcher.h		static_data.h
essentials.h		ssdt_pr_generator.h
localhost:acpi Admin$

Weird, huh?
 
I have moved my Home folder to partition "Data OSX", and it causes me problem while running the code because there is a space in name. Can you fix it for me without changing partition name?

@RehabMan: Will the ssdt created by this be more accurate than your exising ssdt files?
 
I have moved my Home folder to partition "Data OSX", and it causes me problem while running the code because there is a space in name. Can you fix it for me without changing partition name?

Very, very, very off-topic, eh?

@RehabMan: Will the ssdt created by this be more accurate than your exising ssdt files?

No. It generated the exact same thing. Sandy Bridge SSDTs are pretty well understood, so there isn't any idea of "more accurate" at this point.
 
Pike --

BTW, there is something funny about your RevoBoot github repo. When I clone it with:

Code:
git clone git://github.com/Piker-Alpha/RevoBoot.git revoboot.git

Then try to get to the acpi/Tools area...
Code:
localhost:Projects Admin$ cd revoboot.git/
localhost:revoboot.git Admin$ cd i386/libsaio/acpi
localhost:acpi Admin$ cd Tools
-bash: cd: Tools: No such file or directory
localhost:acpi Admin$ ls
debug.h            patcher.h        static_data.h
essentials.h        ssdt_pr_generator.h
localhost:acpi Admin$

Weird, huh?

I had this issue too. It seems this file is in a different branch of the source tree.

Edit: it's in the clang branch, not in the main (master) branch.
 
I have moved my Home folder to partition "Data OSX", and it causes me problem while running the code because there is a space in name. Can you fix it for me without changing partition name?
I don't know what fails, but can you try this change:
Code:
-gPath=~/Desktop
+gPath="~/Desktop"
And if that doesn't solve the problem, then add the terminal output in your next reply. Thank you.

Update: This problem should be fixed in v4.9

@RehabMan,

We cannot use 800/1200 MHz without first knowing if the processor supports it. And we have to be 100% sure about it so that is why I am working on a side project, writing a tool that will give us vital information about the processor/power management. This will also be the first tool to report the C-States the processor supports/was in, and for how long.

p.s. What philip_petev said -> clang branch.
 
We cannot use 800/1200 MHz without first knowing if the processor supports it. And we have to be 100% sure about it so that is why I am working on a side project, writing a tool that will give us vital information about the processor/power management. This will also be the first tool to report the C-States the processor supports/was in, and for how long.

I'm pretty sure all Sandy Bridge mobile is 800Mhz.

p.s. What philip_petev said -> clang branch.

Thanks. And... "Duh..." I feel dumb for not thinking of a separate branch (I don't use branches much...)
 
Status
Not open for further replies.
Back
Top