Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About aliasa_anderson

  • Rank
    InsanelyMac Geek

Contact Methods

  • MSN
  • Yahoo
  1. aliasa_anderson

    FakeSMC 2.5 for Snow Leopard, Leopard, Tiger 10.4.11

    Well,there is nice development going on with FakeSMC kext.Slice and others have joined hands and are working collectively and have added these plugins : IntelThermal – Intel CPU temperature monitoring. LPCMonitor – temperatures and fans from ITE, Winbond and Fintek controllers. TZplugin – temperature from ACPI device “Thermal Zone” Since i cant post other links,you can check netkas website and the link there to get more details. @Andy Thanks alot.Yours kext works perfectly. Andy maybe you should also have a look at the new development going on with FakesSMC and we will have more good kexts as a result Thanks again for your hard work.
  2. aliasa_anderson

    DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Thanks. But then.....I already have SATA device in my DSDT: Device (SATA) { Name (_ADR, 0x001F0002) OperationRegion (SACS, PCI_Config, 0x40, 0xC0) Field (SACS, DWordAcc, NoLock, Preserve) { PRIT, 16, SECT, 16, PSIT, 4, SSIT, 4, Offset (0x08), SYNC, 4, Offset (0x0A), SDT0, 2, , 2, SDT1, 2, Offset (0x0B), SDT2, 2, , 2, SDT3, 2, Offset (0x14), ICR0, 4, ICR1, 4, ICR2, 4, ICR3, 4, ICR4, 4, ICR5, 4, Offset (0x50), MAPV, 2 } } The strange thing is I never expected SATA to show up in SSDT.The rest of the SSDT tables conatined code for P-States,C-States and T-States and this was the odd one out.Also....i obtained all SSDT tables for Ubuntu.I have merged the P-State and C-State(not T-States as I think its outdated in favour of more efficeint P-State,I may be wrong) code with complete success(now the CPU cores are 30 degrees celsius cooler!!!)..thanks to your wonderful guide . Any scope of merging the two SATA codes. Thanks again for your reply. Update: Successfully merged the codes,without any compiler errors.Tesing time now...
  3. aliasa_anderson

    AppleACPIBattery in 32/64 flavor for Snow Kitty.

    Exactly. I also have 00 specified by default and did not have any abttery settings.But then i added the key SystemType as 02 in com.apple.Boot.plist file and was able to get battery settings in system preferences. In case you were not able to locate system-type in ioreg,then you can try this command : ioreg -lw0|grep -i system-type This should work fine.
  4. aliasa_anderson

    DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Hi All, In an attempt to integrate the SSDT tables from Linux i came came across the following piece of code from my first SSDT table : DefinitionBlock ("cpu1.aml", "SSDT", 1, "HP ", "30BC ", 0x00001000) { External (GP39) External (GTF2, IntObj) External (GTF0, IntObj) External (\_SB_.PCI0.SATA, DeviceObj) Scope (\_SB.PCI0.SATA) { Device (PRT0) { Name (_ADR, 0xFFFF) Method (_SDD, 1, NotSerialized) { Name (GBU0, Buffer (0x07) { 0x00, 0x00, 0x00, 0x00, 0x00, 0xA0, 0x00 }) CreateByteField (GBU0, 0x00, GB00) CreateByteField (GBU0, 0x01, GB01) CreateByteField (GBU0, 0x02, GB02) CreateByteField (GBU0, 0x03, GB03) CreateByteField (GBU0, 0x04, GB04) CreateByteField (GBU0, 0x05, GB05) CreateByteField (GBU0, 0x06, GB06) If (LEqual (SizeOf (Arg0), 0x0200)) { CreateWordField (Arg0, 0x9C, W780) If (And (W780, 0x08)) { Store (0x10, GB00) Store (0x03, GB01) Store (0xEF, GB06) } Else { Store (0x90, GB00) Store (0x03, GB01) Store (0xEF, GB06) } } Store (GBU0, GTF0) } Method (_GTF, 0, NotSerialized) { Return (GTF0) } } Device (PRT2) { Name (_ADR, 0x0002FFFF) Method (_SDD, 1, NotSerialized) { Name (GBU2, Buffer (0x07) { 0x00, 0x00, 0x00, 0x00, 0x00, 0xA0, 0x00 }) CreateByteField (GBU2, 0x00, GB20) CreateByteField (GBU2, 0x01, GB21) CreateByteField (GBU2, 0x02, GB22) CreateByteField (GBU2, 0x03, GB23) CreateByteField (GBU2, 0x04, GB24) CreateByteField (GBU2, 0x05, GB25) CreateByteField (GBU2, 0x06, GB26) If (LEqual (SizeOf (Arg0), 0x0200)) { CreateWordField (Arg0, 0x9C, W782) If (And (W782, 0x08)) { Store (0x10, GB20) Store (0x03, GB21) Store (0xEF, GB26) } Else { Store (0x90, GB20) Store (0x03, GB21) Store (0xEF, GB26) } } Store (GBU2, GTF2) } Method (_GTF, 0, NotSerialized) { Return (GTF2) } Method (_PS0, 0, Serialized) { Store (0x00, GP39) } Method (_PS3, 0, Serialized) { Store (0x01, GP39) } Method (_PSC, 0, Serialized) { If (LNot (GP39)) { Return (0x00) } Return (0x03) } } } } I have successfully integrated the rest of the 7 SSDT tables but dont know what the above code is and where to put it. Could anyone please suggest if it could even be added to the DSDT table ...i mean is it worth it. Thanks in advance.
  5. aliasa_anderson

    AppleACPIBattery in 32/64 flavor for Snow Kitty.

    Well, it should be like : +-o MacPro3,1 <class IOPlatformExpertDevice, registered, matched, active, busy 0, retain 21> | { | "IOBusyInterest" = "IOCommand is not serializable" | "IOInterruptControllers" = ("io-apic-0") | "IOPlatformSerialNumber" = "W52182AHPL3" | "clock-frequency" = <00b5644f> | "version" = <"1.0"> | "product-name" = <"MacPro3,1"> | "IOInterruptSpecifiers" = (<0900000005000000>) | "board-id" = <"Mac-F42C88C8"> | "model" = <"MacPro3,1"> | "serial-number" = <154d53000000000000000000007535323138314148504c330 0000000000000000000000000000000000000> | "manufacturer" = <"Apple Inc."> | "IOPlatformArgs" = <0050b30000d069007880b20000000000> | "name" = <"/"> | "IOPlatformUUID" = "33DB4D5B-1FF7-401C-9657-7441C03DD766" | "compatible" = <"MacPro3,1"> | "IOGeneralInterest" = "IOCommand is not serializable" | "IOPolledInterface" = "SMCPolledInterface is not serializable" | "system-type" = <05> | } ---------------------------------------------------------------------------------------------------------------------- Actually FADT table is one of the table in BIOS like DSDT and this table containes a field "Preferred_PM_Profile" You can find more about the accepted values on page 118 of the ACPI v4 specs or just search for PM_PROFILE in that pdf. Chameleon can also override this PM_PROFILE value by using SystemType or system-type in the boot.plist file.The exact key depends upon the version of Chameleon used. Other way is to decompile the FADT table change this value and complile it and use Chameleon variant like Andy's which can load FADT tables as well. I use a HP DV6114TX laptop and my FADT table had Preferred_PM_Profile as 0(Unspecified).Also most Chameleon distros use default value as 0 which is for desktops and 2 is the value needed for laptops/mobile devices.
  6. aliasa_anderson

    AppleACPIBattery in 32/64 flavor for Snow Kitty.

    Hi, What is the value of system-type as per your ioreg ? If its not 02,then i guess you need to change that in FADT table by using PM_PROFILE value as 02 for mobile devices,compile it and there you go.... please let me know if it gives back all the power settings in system profiler ... Edit: As a simpler solution,you can also check if you sue the SystemType=n flag in the Boot.plist file
  7. aliasa_anderson

    DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Hi FormerlyKnownAs, Thanks for the wonderful guide,now I have got rid of LPC and _CST errors and also am able to activate P-States on my HP DV6114TX laptop.I eralier had 1 error and 13 warnings,read the ACPI specs,edited my DSDT and now no errors/warnings. I had also referred to the Processors Data sheet. I still had some doubts, I found that most of the examples of _CST method in this thread have FFixedHW implementation and have asymmetric C states values for CPU0 and CPU1,is it necessary ? because i referred to varuois examples for _CST method in the ACPI Spec guide and used similar values in _CST for both the CPUs(Single Core Duo),took C-State latency values from FACP table. I have attached the decompiled extract for the _PR with this message. The P-States are working perfectly but not sure of the C-States.Could somebody suggest if I implemented the logic correctly. From the original DSDT,i have added: _PSS _PCT _PSD _CST AND _CSD methods the latency values are correct just need to check the logic.I have used both FFixedHw and SystemIO. Would be really grateful. Thanks in advance. DSDT.zip
  8. aliasa_anderson

    VoodooPowerAcpi 1.2.5 for 10.6.x

    You could also use the command sysctl from within the command line/terminal. You could use : sysctl|grep -i freq the value corresponding to curfreq will give the current frequency of the CPU,by varying the load,this should vary and hence you can validate if frequency scaling is occuring or not.
  9. Which bootloader do you use ? I would suggest you to try using the latest pcefi by Netkas.
  10. thats cool. Actually i you have the latest pcefi,you will be able to display correct info in the "PCI Cards" section of system profiler.As far as i have known,this is only cosmetic effect but nevertheless,its good to have more precise info.
  11. aliasa_anderson


    Hi, Can someone please please provide me a link for HDAEnabler.kext to be used with VoodooHDA on Snow Leopard. I did download the HDAEnabler.kext but it doesnt seem to display the sound info correctly in System Profiler. Thanks in advance.
  12. aliasa_anderson

    VoodooPowerMini 1.2.4 for 10.6.x

    Hi Superhai, Sorry for being noob,but I just wanted to know if this kext also supports automatic voltage scaling apart from frequency scaling ?
  13. Hi, I have the same graphics card. You can try the following. 1. Backup NVinject.kext. 2. Download Ntekas efi 10.5(basically boot file) 3. Copy boot file file to root. 4. Edit boot.plist file to have graphics to have GraphicsEnabler to true. 5. Delete NVinject.kect from /S/L/E(no need of any graphics enabler kexts) 6. Reboot hope it works well. Do let me know the result.
  14. aliasa_anderson


    Did you try the snow leo kext here : http://www.projectosx.com/forum/index.php?showtopic=355
  15. aliasa_anderson

    PC EFI V10.4 (made by netkas) OUT!

    Hi mitch_de, Is there a switch/flag to disable the new CPU detection algorithm and use the old one. In my case i have Intel Core Duo but it is detected as Intel Core 2 Duo. Secondly,i was wondering that does the PCI v10.4/3 use the autodetection algo for detection of correct pciroot value and if not found then revert to default value or it uses only the hardcoded values ?