• Posts

    • Did you update your nVidia web driver, boot with nv_disable=1 and then update nvidia web driver.
    • Hackintosh after 10.12.05 Update (Intel/NVIDIA) I had some problems after the update so I tell you how to solve the issues: Black Screen (no signal): There is a problem with the Nvidia Web Driver. First try to boot without the nvidia driver. Just go to Options > GPU Injection and remove the tick from Nvidia Web Driver and boot. Uninstall the Web Driver -reboot- and Install the new Version 378.15.10.05f01 If you still get a black screen boot a live cd or windows and remove the NVDA.... Folders from System/Library/Extensions and try again to boot. Uninstall the Web Driver -reboot- and Install the new Version 378.15.10.05f01 (If you open the nvidia driver manager to uninstall the driver NVIDIA asked me to install an update - ignore that and uninstall the driver, because the update wont work) Error 8 / Volume could not be verified completely / fsck_hfs errors / Invalid node structure: Boot from sierra installation usb and try to repair with disk utility - reboot -> If that does not work reboot and boot again from sierra installation usb > open terminal > /sbin/fsck_hfs -yprd /dev/disk0s0  (replace 0 with the right number - you can find it in the disk utility)  - > the process takes 5-10min
    • Upgrade Sierra 10.12.6 - GT 710 Hi!! I have make a upgrade 10.12.6 Sierra and have a black Screen. Solution: Change SMBios for MACBOOK PRO Retina. I have a Core I7 3770 Ivy bridge.   
    • It did not work for me. In my case, I found that the installed Volume was renamed to "--" and the installation script stopped. After that the Volume was damaged and I had to erase it with Disk Utility.   I suspect that the error does not come from the script itself but happened prior to run the script. Some process was messing with the installed Volume.  
    • How Do I Get iCloud Working in Yosemite Zone? Hello! I recently installed Yosemite Zone and iCloud, FaceTime, iMessage, and Google Chrome and none of them work, each saying my computer isn't validated. I have tried many things including the one with EFI Studio and deleting stuff to messing around in Chameleon and none of it seems to work. The App Store and it's sister apps work just fine, though. Does anyone know how to get all this working, as they are things I'd like to use. Specs: AMD Phenom II x4 B55 3.3 GHz 8 GB DDR3 NVidia GeForce GTX 750 MSI 890GXM-G65 Yosemite Zone 10.10.1

iASL & Intel ACPI Tools x64 2014/04/24

   (1 review)
Sign in to follow this  
Followers 0

1 Screenshot

About This File

Intel ACPI tools. NEW version 2014/04/24 compiled by me from original sources. Use iasl compiler with your DSDTSE or another editor. To update your DSDTSE, simply right click on DSDTSE -> Show contents, drag'n'drop iasl into -> Contents -> Resources. Another editors have mostly the same way. Or another way by Terminal: drag iasl on Terminal window (bash), (press Return (Enter) to see all keys) -> write some keys, drag Aml/Dsl file to compile/decompile. This way you can more deeply configure/clean your DSDT during compile (especially with -w3 key), find more warnings and junk code, empty / uninitialized methods. Have a nice day compilings!.


What's New in Version 2014/04/24

Released

  • 24 April 2014. Summary of changes for version 20140424:
  • 1) ACPICA kernel-resident subsystem:
  • Implemented support to skip/ignore NULL address entries in the RSDT/XSDT. Some of these tables are known to contain a trailing NULL entry. Lv Zheng.
  • Removed an extraneous error message for the case where there are a large number of system GPEs (> 124). This was the "32-bit FADT register is too long to convert to GAS struct" message, which is irrelevant for GPEs since the GPEx_BLK_LEN fields of the FADT are always used instead of the (limited capacity) GAS bit length. Also, several changes to ensure proper support for GPE numbers > 255, where some "GPE number" fields were 8-bits internally.
  • Implemented and deployed additional configuration support for the public ACPICA external interfaces. Entire classes of interfaces can now be easily modified or configured out, replaced by stubbed inline functions by default. Lv Zheng.
  • Moved all public ACPICA runtime configuration globals to the public ACPICA external interface file for convenience. Also, removed some obsolete/unused globals. See the file acpixf.h. Lv Zheng.
  • Documentation: Added a new section to the ACPICA reference describing the maximum number of GPEs that can be supported by the FADT-defined GPEs in block zero and one. About 1200 total. See section 4.4.1 of the ACPICA reference.
  • Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 9.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size.
  • Current Release:
  • Non-Debug Version: 96.8K Code, 27.2K Data, 124.0K Total
  • Debug Version: 189.5K Code, 79.7K Data, 269.2K Total
  • Previous Release:
  • Non-Debug Version: 97.0K Code, 27.2K Data, 124.2K Total
  • Debug Version: 189.7K Code, 79.5K Data, 269.2K Total
  • 2) iASL Compiler/Disassembler and Tools:
  • iASL and disassembler: Add full support for the LPIT table (Low Power Idle Table). Includes support in the disassembler, data table compiler, and template generator.
  • AcpiDump utility:
  • 1) Add option to force the use of the RSDT (over the XSDT).
  • 2) Improve validation of the RSDP signature (use 8 chars instead of 4).
  • iASL: Add check for predefined packages that are too large. For predefined names that contain subpackages, check if each subpackage is too large. (Check for too small already exists.)
  • Debugger: Updated the GPE command (which simulates a GPE by executing the GPE code paths in ACPICA). The GPE device is now optional, and defaults to the GPE 0/1 FADT-defined blocks.
  • Unix application OSL: Update line-editing support. Add additional error checking and take care not to reset terminal attributes on exit if they were never set. This should help guarantee that the terminal is always left in the previous state on program exit.





User Feedback

Create an account or sign in to leave a review

You need to be a member in order to leave a review

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

Alain Frenois

  • 5
  

Share this review


Link to review