Jump to content

Search the Community: Showing results for tags 'DSDT'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 234 results

  1. *****NOW UPDATED FOR YOSEMITE - PLEASE REPORT ANY PROBLEMS IN THE COMMENTS***** *****There are subtle differences in the guide depending on whether you’re using Lion / Mountain Lion or Mavericks***** *****For Lion / ML use the blue line. For Mavericks use the red line. For Yosemite use the green line.***** *****If you're creating the installer for Lion/ML use "Essential 03.08.2012" attachment***** *****Otherwise use the attachment for the version you’re using***** *****This guide will not work for versions of OS X earlier than Lion (10.7)***** The all-in-one guide to vanilla OS X + Chameleon + DSDT for beginners Preface: So I’ve built a few hackintoshes now to the point where I’ve a good idea what I’m doing. I’ve gone the distro way before as well as the vanilla way and I agree fully with the idea that vanilla is better. The problem with it being that I haven’t found a well explained start to finish guide of how to do it without a lot of Googling and combining numerous different guides so my idea is to collate everything into one place for beginners to hopefully understand the process better and build better systems. A lot of the leg-work for this guide has been done by other people; although I’m rewriting most of it if anyone wants credit adding to something I’ve accidentally stolen from them just PM me. Throughout the guide I try to avoid scripts and utilities so you can learn what your doing. If you want a one-click install this is not the guide for you; having said that there is nothing technically complicated that isn’t clearly explained so don’t be scared off if you’re a rookie. If any one has any suggestions on how to improve this guide PM me or mention it on the forum thread. Those who experience problems make sure you’ve read Part 7 before posting to the forum asking for help. Part 1 - Prerequisites 1.0. Basic Requirements: The basic requirements for OS X from Lion onwards are: 1. A Core 2 Duo processor or later 2. 2GB or more RAM 3. 8GB of disk space N.B. For details of specific hardware compatibility see the hardware compatibility list (HCL) in the wiki: http://wiki.osx86project.org/wiki/index.php/Main_Page Further to compatible hardware you will need: 1. A working install of OS X (this may be in a virtual machine or a native install) to prepare the installer 2. A flash drive of minimum size 8GB 3. A copy of Lion / ML / Mavericks 4. Patience Note: All essential software / kexts below are in the attachment. 1.1. Essential Software You will need to obtain the following. I suggest you place them all in the same folder along with the essential kexts below for use later: 1. The Chameleon boot loader, the latest version of which can always be found here (You want "The Latest Trunk PKG ~ Standard and Official Revision"): http://www.insanelymac.com/forum/index.php?showtopic=231075 2. Chameleon wizard to create a smbios (basically identify your machine as a mac) and to help with bootloader problems http://www.insanelymac.com/forum/index.php?showtopic=257464 3. System info for finding device ID’s for general post-install troubleshooting (Check you get the Mac version). http://www.insanelymac.com/forum/index.php?showtopic=219584 4. DSDT editor for extracting your DSDT once were up and running: http://www.insanelymac.com/forum/index.php?showtopic=223205 5. Kext utility for installing additional kexts post-install: http://cvad-mac.narod2.ru/Kext_Utility/ 1.2. Essential Kexts (kernel extensions) 1. FakeSMC – absolutely essential – tricks OS X into thinking it’s a real Mac. http://www.projectosx.com/forum/index.php?showtopic=1643 2. NullCPUPowerManagement – generally required initially to prevent kernel panics, may not be needed once AppleIntelCPUPowerManagement is patched after install. http://www.osx86.net/view/16-nullcpupowermanagement_(32--64-bit).html Part 2 - Creating the installer 2.0. Preparing the USB 1. In your working OS X install open Disk Utility 2. Click on your USB drive in the left sidebar 3. Click the “Partition” tab 4. Under “Partition Layout” click “1 Partition” 5. Click Options -> select “GUID Partition Table”; check the format is set to “Mac OS X Extended (Journaled)”; name it “USB” and click Apply 2.1. Creating the OS X installer on the USB drive 1. Mount your OS X DMG. If using a copy downloaded from the app store: Navigate to Applications (which is where it will save your downloaded copy of OS X by default) -> right click "Install OS X *version*" and click "Show Package Contents" -> Contents -> SharedSupport -> Double click "InstallESD.dmg" 2. Mount BaseSystem.dmg by typing the following in terminal: open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg 3. Go back to disk utility and click on “(Mac )OS X Base System”, click the “Restore” tab then drag and drop “(Mac )OS X Base System” to “source” and your USB to “destination” and click restore then erase. This will take a while. 4. You’ll now have 2 “(Mac )OS X Base Systems present in Finder, right click them and “get info” to determine which is your USB drive (hint: look at the size). 5. Navigate to the one which is your USB drive, open it and go to /System/Installation. Delete the “Packages” link then create a folder called “Packages”. 6. Open a new Finder window and navigate to “(Mac )OS X Install ESD”. Copy everything inside the packages folder to the packages folder you have just created. This will take a while. 7. Copy mach_kernel from “OS X Install ESD” to the root of your USB drive. 7. Use pacifist to extract mach_kernel from “OS X Install ESD/Packages/BaseSystemBinaries.pkg” and copy it to the root of your USB drive (note: this is in the attachment). 7. Use pacifist to extract kernel from “OS X Installed ESD/Packages/Essentials.pkg/System/Library/Kernels/Kernel” and copy it to /System/Library/Kernels/ (You may need to create the “Kernes” folder) (note: this is in the attachment). 8. Copy BaseSystem.chunklist and BaseSystem.dmg from InstallESD.img to the root of your USB drive. Since these files are hidden you must first show hidden files by typing the following in Terminal "defaults write com.apple.Finder AppleShowAllFiles YES" followed by "killall Finder". Once copied you can type "defaults write com.apple.Finder AppleShowAllFiles NO" followed by "killall Finder" to hide hidden files. The terminal will look something like this when you are done: 2.2. Patching the installer for a PC 1. Remember the two kexts we downloaded above? Copy both of them to /System/Library/Extensions on your USB stick. 2. Run the chameleon installation package and ensure to choose your USB drive as the destination. 3. Go to the root of your USB drive and create a folder called “Extra”. This is used to store configuration files for the chameleon boot-loader. 4. Open Chameleon wizard, click the “SMBios” tab then click "Edit". Now there is a list of “Premade SMBioses”. Look through this list to see which relates best to your PC (Hint: iMac 12.2 for modern desktops or MacBook Pro 8.3 for modern laptops is a good place to look to start with). Click “Save As” and save it to the /Extra folder we created on the USB stick. N.B. make sure you’ve got a smbios from a Mac which supports your version of OS X, for a list of which do see here: http://www.apple.com/osx/specs/ 5. Use chameleon wizard to generate an “org.chameleon.boot.plist” this is necessary to set the kernel flag “kext-dev-mode=1” which allows us to boot using unsigned kexts. If you already have an org.boot.chameleon.plist you may simply add “kext-dev-mode=1” to your list of kernel flags. If not then use the one from the attachment. Copy this file to the /Extra folder we created on the USB stick. 6. Copy your folder of essential software & kexts to the root of your USB stick. N.B.1: For those with a fully-working Lion / ML install you may omit 2.C.3. & 2.C.4. and use your old /Extra folder (including smbios & org.chameleon.boot.plist & DSDT). N.B.2: ATi6xxx users see step 7.6 now! 2.3. A note for those wishing to boot OS X and Windows on the same HDD (This is not recommended but may be necessary for those installing on laptops) The OS X installer won’t install to an MBR partition scheme which Windows requires so we must patch the installer to allow this. If you intend on dual-booting OS X and Windows 7 then I suggest you install Windows 7 and update to Service Pack 1 before you install OS X to prevent problems updating to SP1 later. How to patch: 1. Download the required files from here: http://www.osx86.net/view/2815-osinstallmbr+osinstall.mpkg_10.8.gm.html 2. On the USB stick navigate to /System/Installation/Packages/. Delete OSInstall.mpkg and replace it with the one you just downloaded. 3. On the USB stick navigate to /System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/. Delete OSInstall and replace it with the one you just downloaded. Part 3 – Installing OS X 3.1 Installing OS X 1. Stick the USB drive in the computer you wish to install OS X on and boot from your USB drive. If you’re unsure how to do this when your computer first turns on look for a prompt that says “Press X for boot selection menu” (where X is a key) or something of that effect. Common keys are F8 & F12. 2. When Chameleon comes up press enter to boot OS X. The OS X installer should boot. Go to the utilities menu and click disk utility. Select the disk / partition you wish to install OS X to, call it "OS X" and format it as “Mac OS X Extended (Journaled)” (See Part 2.1. if you’re a bit rusty with disk utility). N.B. For those dual booting on the same HDD as Windows ensure you've got the Partition Scheme set to MBR. 3. Follow the installer to install OS X to the desired partition. 4. Take a well-deserved rest while it installs. 5. Once the installer is finished it will reboot, on reboot boot back into the install USB NOT your OS X install. 3.1 Fixing the OS X install 1. From the installer go to Utilities and Terminal. 2. Type cp –R /System/Library/Extensions/NullCPUPowerManagement.kext /Volumes/"OS X"/System/Library/Extensions/ 3. Type: cp –R /System/Library/Extensions/FakeSMC.kext /Volumes/"OS X"/System/Library/Extensions/ 4. Type reboot NOTE: Include the quotes in the lines above. This assumes your install partition is called “OS X” as I said above. If for whatever reason you called it something else replace “OS X” with whatever you called it (still surrounded by quotation marks). Part 4 – Initial booot 1. Reboot your system and boot to the USB stick again but this time select your OS X install. This should boot you into your installed copy of OS X. 2. Open "System Preferences" go-to "Security and Privacy", click the lock and give it your password then set "Allow applications downloaded from" to anywhere. 3. Navigate to your folder of essential software and run the chameleon package, install it to your OS X drive. 4. Copy the Extra folder on your USB drive to the root of your HDD (open Finder -> Go -> Computer -> OS X -> paste folder). 5. Reboot, remove USB, and let the computer boot from your HDD, select OS X and it should boot straight to OS X. You are not finished! You now need to at least read through step 6! Part 5 – DSDT 5.0 Extraction Although not strictly required it is useful to have a DSDT for your system; with a bit of research and patching it can be used to solve almost all problems you may encounter. For those interested in what it actually is see here: http://wiki.osx86pro.../index.php/DSDT How to create it: 1. Open DSDT Editor 2. Go-to File -> Extract DSDT 3. Go-to to IASL -> Compile (if you get any errors click “Fix Errors”) 4. Go-to IASL -> Save AML as. Save it as “DSDT.aml” in /Extra. 5.1 Common Fixes (coming soon eventually…) Part 6 – Finishing Touches 6.0. A note on non-Mac monitors Most non-Mac monitors will start with the wrong color calibration. To fix this go-to "System Preferences" -> "Displays" -> "Color" -> select "Generic RGB Profile". Further to this, due to Mac monitor having a different dot pitch to normal monitors, LCD font smoothing may make the fonts appear blurred. To turn this off go-to “System Preferences” -> General -> uncheck “Use LCD Font…” (at the bottom). 6.1. Keymaps If you have a British standard keyboard you will need to install the keymaps in the attachment. To do so decompress the attached zip and copy its contents to /Library/Keyboard Layouts then change the keymap by going to System Preferences -> Keyboard -> Input Sources. 6.2. org.chameleon.boot.plist If you open Chameleon Wizard you can navigate to “org.chameleon.boot” here you can assign numerous settings which will be useful later as well as setting the default timeout and specifying the location of your SMBios and DSDT if you don’t place them in /Extra. I suggest you ensure the “Ethernet Built In” box is checked then set the "Time Out" to a reasonable figure and then click "Save As' and save it to /Extra (Note: save it as org.chameleon.boot, it automatically appends the .plist extension). When you've saved it you can go to "Theme" and download and apply a theme for the boot loader rather than having the default text boot. Once your system is stable and with all necessary hardware enabled set UseKernelCache=Yes to speed up boot times. 6.3. NullCPUPowerManagement Currently we have NullCPUPowerManagement.kext installed. This disables speed-stepping and thus sleep (by disabling AppleIntelCPUPowerManagement.kext) so we need to remove it for a better system. Unfortunately not all system’s will work with the version that comes with OS X. The first thing to do is to try your system without it, to do this simply navigate to /System/Library/Extensions on your OS X drive and delete it then reboot. It’s possible you will see a kernel panic on reboot, if this is the case you will need to reinstall the kext by following Part 3.1.1&3.1.2. If your system panics on boot then you require a patched version of AppleIntelCPUPowermanagement; reading round the forum should allow you to obtain this relatively easily. 6.4. Device Compatibility At this point it’s very likely you will have some devices not working. The best way to get devices working is through DSDT edits rather than by adding kernel extensions; often additional kernel extensions will have to be re-installed after updates whereas DSDT edit are permanent. To enable devices by using additional kexts: Run the “System Info” app we downloaded and click File -> check compatibility. This will let you see which devices are working and which aren’t. You can Google your vendor & device ID to find info about making them work. Once you find a kext that appears to be compatible for your hardware drag and drop it onto kext utility to install it. Example: If your Wi-Fi isn’t working you can look for your Wi-Fi device and find its device / vendor ID’s in my case its vendor ID is 168c and its device ID is 002a so Googling for “168c:002a kext” would return results about making the device work. 6.5. Finder grid view (windows explorer behaviour) To make finder sort files in a grid by default open Finder, navigate to your root folder of the OS X install. Go-to View -> Show View options -> Arrange by "Name" -> Click "Use As Defaults" Part 7 – Common Errors & Basic Diagnostics 7.0. Boot0:Error Boot0 error is most likely caused by incorrectly installing chameleon or having a drive with 4k-sector allocation. Try to reinstall chameleon (use the latest version!), if that doesn’t work see here: http://www.macbreaker.com/2012/02/hackintosh-boot0-error.html 7.1. Boot flags When the chameleon screen boots you can specify kernel arguments to attempt to solve problems you may be having. When you see the boot-loader pop up press any key and ensure your OS X install is highlighted. You can then type any combination of kernel flags (with a space between them) to try to boot OS X / diagnose problems. For a complete list of kernel flags see here: http://www.osx86.net/guides-tutorials/10747-guide-chameleon-bootloader-basics.html A few of the more common ones are: 1. –v verbose mode. If the system panics take a screen shot of the panic when you have typed this at boot and post it to the forums. It will help people diagnose your problems but won’t fix any problems. 2. –x safe boot (like windows safe mode – minimal drivers). 3. –f boot without the kernel cache (useful if you’ve installed kexts without rebuilding the kext cache – if you’ve used kext utility you shouldn’t have to use this). 4. –npci=0x2000 (or –npci=0x3000) fixes the “PCI configuration Begin” error. 5. PCIRootUID=0 solves problems for some NVIDIA graphics card users (if it doesn't solve your issue try =1 instead). 6. GraphicsEnabler=Yes (or GraphicsEnabler=No) add support for some non-OS X graphics cards. 7. Note: The arch=i386 boot flag is now depreciated due to ML’s 64-bit only kernel. 7.2. The console The console gives you a verbose output of any and all errors the system may encounter. It's particularly useful if you've a system which won't stay in sleep mode. Go-to Applications -> Utilities -> Console to open it. 7.3. App store "Your device or computer could not be recognised..." error. App-store requires a MAC address to verify your computer (any address, it doesn't have to be an apple one) hence you MUST have a working Ethernet or Airport card for App Store to work. The problem is if you've enabled network hardware after first boot OS X won't update its caches. The fix: Ensure "ethernet buit in" is checked in your org.chameleon.boot.plist. Go to system preferences and delete all the devices in the network section. Navigate to /Library/Preferences/SystemConfiguration and delete com.apple.airport.preferences.plist and networkinterfaces.plist and com.apple.boot.plist. Reboot then add your network interfaces in system preferences. Check app-store is now working. 7.4 Motherboard POST Freeze I your motherboard freezes during POST (you don’t even get past the BIOS screen) it’s possible your BIOS isn’t compatible with the GUID partition table of the USB we created the installer on. To fix this in step 2.0.5 select MBR instead of GUID. Note: If you make it to the OS X boot-loader this is not your problem and will not fix any issues other than hanging at POST. For more information see here: http://www.rodsbooks.com/gdisk/bios.html 7.5 When posting to the forum asking for help When posting to the forum asking for help if the installer / installation won’t boot please post a screenshot of where it stops – I suggest you post this to a new thread in a suitable place in the forum rather than this guide. 7.6 ATi6xxx card white screen error There is a know permissions error in Mountain Lion regarding the ATi6000Controller kext causing white screen. To fix this: Navigate to /System/Library/Extensions on your install USB and copy ATi6000Ccontroller to your folder of essential kexts. Delete ATi6000Controller from /S/L/E. Install OS X (note: you will only have basic graphics support). After install (at the end of step 4) you can drag & drop the kext onto kextutility then reboot to enable your card. Part 8 - Useful Tips 8.0. To show or hide hidden files: In the terminal type: defaults write com.apple.finder AppleShowAllFiles YES or defaults write com.apple.finder AppleShowAllFiles NO Followed by killall Finder 8.1. Spaces in terminal When using the terminal spaces must be preceded by \ or the file or folder name placed in quotations e.g.: open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg or open /Volumes/"Mac OS X Install ESD"/BaseSystem.dmg Part 9 – References Massive credit goes to this guide here: http://thetecherra.com/2012/07/10/tutorial-run-os-x-mountain-lion-10-8-gm-on-a-pc-hackintoshosx86-video/ and this guide here: http://www.insanelymac.com/forum/index.php?showtopic=277015 Part 10 – Change-log v2.3 - 25/07/2012 - Minor update to include InstallESD location from app-store. v2.4 - 27/07/2012 - Minor updates regarding Gringo Vermelho’s post. v2.5 - 03/08/2012 - Minor updates and touch-ups. v2.6 - 22/08/2012 - Addition of UseKernelCache=Yes plus key-maps and a few minor tweaks. v3.0 – 24/10/2012 – Addition of screenshots v3.1 – 03/12/2012 – British keyboard layout added v4.0 – 07/10/2013 – Updates so guide complies with Mavericks install procedure v4.2 – 10/11/2013 – Ironed out differences between Lion/ML and Mavericks v4.3 – 16/10/2014 – Added Yosemite support Essential - 03.08.12.zip Keyboard Layouts.zip Essential - Mavericks GM - 7.10.2013.zip Mavericks Install Guide - v0 - Quick Ref.pdf Mavericks install Guide - v4.2 - With Sreenshots.pdf Vanilla OS X Install Guide - v4.3 - With Sreenshots.pdf
  2. Hi to all, I just wont to give inough informations on one place for all the people with same Hardware with costimization steps witch i have done. I have fast perfect working High Sierra 10.13.3 on my PC but still needs to be actualized thru the DSDT, because it ist the only way to get all the hardware properly working. Gigabyte Z370 Aorus Ultra Gaming - BIOS F7h Intel i7-8700K (4.8GHz) Gigabyte GTX 1080 G1 Gaming 8G DDR4 64GB PC 3000 CL15 G.Skill KIT (4x16GB) 64GVR Ripjaws V Dual-Band PCI-e Adapter TP-Link TL-WDN4800 Firewire PCI-e Digitus (Texas Instruments Chipset) Bluetooth 4.0 USB Dongle ASUS BT400 (Broadcom) PSU: LC-Power Metatron Prophecy 2 LC8750II V2.2, 750 Watt 2 x NVMe SSD 960 Evo 500GB (Win10Pro & High Sierra 10.13.3) 1 x SSD Crucial 500GB (Sierra 10.12.6) 1 x 4TB Segate Barracuda SATA 3 (Multimedia) Tripple-boot Win10Pro, Sierra 10.12.6 & High Sierra 10.13.3 Bios Settings: 1. M.I.T. → Advanced Memory Settings Extreme Memory Profile(X.M.P.) : Profile1 2. BIOS → Fast Boot : Disabled 3. BIOS → LAN PXE Boot Option ROM : Disabled 4. BIOS → Storage Boot Option Control : UEFI 5. Peripherals → Trusted Computing → Security Device Support : Disable 6. Peripherals → Network Stack Configuration → Network Stack : Disabled 7. Peripherals → USB Configuration → Legacy USB Support : Auto 8. Peripherals → USB Configuration → XHCI Hand-off : Enabled 9. Chipset → Vt-d : Enabled 10. Chipset → Wake on LAN Enable : Disabled 11. Chipset → IOAPIC 24-119 Entries : Enabled Dedicated graphics card: 1. Peripherals → Initial Display Output : PCIe 1 Slot 2. Chipset → Integrated Graphics : Enabled Chipset → DVMT Pre-Allocated :128M Wake for Ethernet Network access - Unchecked Enable Power Nap - Unchecked First step: I have a perfect Sierra 10.12.6 working on my HP Z800 witch i use to clone to one SSD Second step: Delete old EFI on cloned SSD and put the new one from here: https://hackintosher.com/guides/high-sierra-install-full-guide/ Adjusted Kexts and Config.plist for my Rig: Kext Folder: FakeSMC.kext + Sensors Kexts Lilu.kext CodecCommander.kext AppleALC.kext IntelGraphicsFixup.kext FakePCIID_Intel_HD_Graphics.kext IntelMausiEthernet.kext NvidiaGraphicsFixup.kext Shiki.kext USBInjectAll.kext XHCI-200-series-injector.kext Thread step: connected new cloned SSD on the SATA port and Sierra started up and working. Fourth step: regulary updated to HighSierra 10.13.3 running installer from App folder. Fifth step: Cloned Sierra SSD to NVMe SSD 960 Evo 500GB Made changes to BIOS & Config.plist to become hardware encoding acceleration in FCPX and HEVC support: BIOS Gigabyte: § Chipset → Integrated Graphics : Enabled § Chipset → DVMT Pre-Allocated :128 § Peripherals → Initial Display Output : PCIe 1 Slot Config.plist: 1. Inject Kexts is set to Yes 2. In Boot Under Custom flags added: Nvidia users: shikigva=60 3. Kaby Lake & Coffee Lake Users: In Devices Using Nvidia - Set ig-platform-id to: 0x59120003 DSDT Patching: 1. HECI -> IMEI Patch 1. Comment: change HECI to IMEI 2. Find* [Hex]: 48454349 3. Replace [Hex]: 494d4549 2. GFX0 -> IGPU Patch 1. Comment: change GFX0 to IGPU 2. Find* [Hex]: 47465830 3. Replace* [Hex] : 49475055 3. PEGP -> GFX0 Patch 1. Comment: change PEGP to GFX0 2. Find* [Hex]: 50454750 3. Replace [Hex]: 47465830 I think that in my Config.plist (used EFI from here https://hackintosher.com/guides/high-sierra-install-full-guide/ and edited by me) are the double entries, but i am not shure and i dont wont to make a mess myself. It is beter to leave it to the profis like Maldon! Maldon, i have attached my Send me iMac_4FX.zip file generated with RunMe.app Can you post the list of maded Patches for this RIG please. THX in advance QuattroFX Send me iMac_4FX.zip
  3. I was wondering for a long time if it is possible to have the power LED pulsing on a hackintosh in the same as a real Mac but never really found the time for an in-depth research. Reading through the datasheet of my board's SuperIO, a Nuvoton NCT6776D, I found the following table which confirms that the hardware supports this feature too. As sleep/wake is controlled by the DSDT, I had the idea that it might be possible to get the pulsing power LED just with a small DSDT patch and, to my great surprise, its much simpler than expected. But see for yourself. In the DSDT of my board, an Asrock B85 Killer, I found method SLED controlling the switch between on in S0 and blinking mode in S3 (sleep): Method (SLED, 1, NotSerialized) { ENFG (0x0B) If (Arg0) { If (LEqual (OPT7, 0x87)) { Store (0x45, OPT7) } } Else { If (LNotEqual (OPT7, Zero)) { Store (0x87, OPT7) } } EXFG () } Replacing the line "Store (0x45, OPT7)" with "Store (0x4A, OPT7)" gave me a slowly pulsing power LED while the machine sleeps. That's really trivial. Ok, it's not as pretty as on a real Mac, but very close to the original. This patch should work for most of Asrock's series 8 and 9 ATX/µATX boards as far as I can see. The mini-ITX boards may be different, at least my Asrock B85M-ITX is, but it should be possible to get this feature working with them too. Many of Asrock's 100 series board also come with the same SuperIO chip but the DSDT looks different. Here is an example from an Asrock Z170M-Pro4S which woks in the same way. The following code snippet was found in method SIOS, which is called in order to prepare the SuperIO for sleep mode: If (LEqual (Arg0, 0x03)) { Store (0x0A, LDN) Or (OPT0, 0x20, OPT0) Or (RGE4, 0x10, RGE4) Store (0x0B, LDN) If (LEqual (OPT7, 0x87)) { Store (0x45, OPT7) } } Changing 0x45 to 0x4A should give you the pulsing power LED on this board too. As far as I know, Nuvoton SuperIOs can be also found on many ASUS and MSI boards. The NCT5577D supports this feature too. Other chips might support it as well but you need to have a datasheet to verify it and learn how to control the LED. Mieze
  4. This is the guide how to make monitoring of hardware parameters (temperatures, fan speeds, voltages etc) using DSDT programming. The method invented by me with THeKiNG presence and improved by Kozlek. Prerequisites There is FakeSMC plugin named ACPImonitor in my branch or renamed to ACPISensors in kozlek's branch. They are the same. HWMonitor or other monitoring application: iStat, K-Stat-i, ... How it works. HWMonitor or other software make a request for known SMC key, for example TA0P (ambient temperature), every 1 seconds. The request catched by FakeSMC which knows that the key registered by ACPImonitor plugin. This plugin knows that the value for the key must be read from ACPI device "monitor" by method "TCRR" and make a request to AppleACPIPlatform for evaluate this method. AppleACPIPlatform interpretates AML codes written into DSDT, finds the method and calculates the value using hardware access. The value return back to ACPImonitor -> FakeSMC -> AppleSMC -> HWMonitor which shows the "temperature". The kext ACPImonitor will not work OOB. It will work only with DSDT patches for the usage. Simple example DSDT. Device (FSAM) { Name (_HID, EisaId ("APP0111")) Name (_CID, "monitor") Name (TCRK, Zero) Method (TCRR, 0, NotSerialized) { Return (TCRK) } Method (TCRW, 1, NotSerialized) { Store (Arg0, TCRK) Return (TCRK) } Method (TCPP, 1, NotSerialized) { Store (\_TZ.THM._TMP (), Local0) Return (Local0) } } You have to create new device. It must have Name (_CID, "monitor") This is the key for ACPImonitor attached to it. Then see Method (TCRR,0, NotSerialized) mentioned above. It will return a value or variable TCRK. In this demo I made a method TCRW which will fill the variable TCRK from SMC key. The I have to make correspondence ACPI_methodSMC_key in ACPImonitor.kext/info.plist I can write values to the SMC key TA1P ./SMC_util3 -kTA1P -w28 and see the value 28 appears in HWMonitor as "Ambient temperature" Value conversions must be provided in DSDT. Predefined keys ACPI SMC Name TCPU Th0H CPU heatsink TSYS TN0P Northbridge temperature TDIM Tm0P DIMM temperature TAMB TA0P Ambient TCPP TC0P CPU proximity VCPU VC0C CPU voltage VMEM VM0R DIMM voltage ACDC ACIN, ACEN Presence of AC power FAN0 - FAN9 for FAN speed FTN0 -FTN9 for FAN rotation time In the case of FAN reading we also want to assign name to them. It is also possible with the Info.plist What to monitor in real DSDT? This is individual. So why the ACPImonitor will not work OOB. See example from my notebook. looking through DSDT I found the follow region. OperationRegion (TMIF, SystemMemory, 0xFF800160, 0x20) Field (TMIF, ByteAcc, Lock, Preserve) { THS0, 8, THS1, 8, THS2, 8, Offset (0x08), FAN1, 8, Offset (0x10), TSP0, 8, TSC0, 8, TSP1, 8, TSC1, 8 } Looks like three temperatures and one FAN. As well I found ThermalZone Scope (_TZ) { ThermalZone (THM) { Method (_CRT, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.TSC0), Local0) Return (Local0) } Method (_TMP, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.THS0), Local0) Return (Local0) } _CRT - critical temperature _TMP - current temperature _SB.PCI0.LPCB.WSEC.C2K is a method to convert Celsius to Kelvin degrees. So I see that the field THS0 is really CPU temperature. Using ACPImonitor is only way to do monitoring on notebooks because no other methods works and because it usually contains ThermalZone. I know my guide is too short and hope some users shows own examples how to do ACPI monitoring. Note. This method is useful mostly for notebook where temperature and FANs control present in DSDT. For desktops there are plugins like ITE87xx, Winbond, Fintek depending on you LPC chip installed. 10.10.2017 ACPIMonitor version 1.0.3 There is a possibility to define some types and sizes for custom keys <key>keysToAdd</key> <dict> <key>TCRR</key> <string>TA0P-2</string> <key>TCRW</key> <string>TA1P-3</string> <key>MSLD</key> <string>MSLD-1</string> </dict> The number after key name means follow 0 -> "flag", len 1 1 -> "ui8 ", len 1 2 -> "ui16", len 2 3 -> "sp78", len 2 4 -> "ui32", len 4
  5. Hola: Para los usb 3 de mi placa uso un inyector USB_Series8_Injector.kext modificado para mis puertos. http://www.insanelymac.com/forum/topic/331511-dudas-existenciales-con-los-ssdt/ Deseo eliminar dicho inyector poniendo los datos de los puertos en el DSDT directamente pero no se si es posible ni como hacerlo. Tengo dos instalaciones en dos discos con 10.13.3 Uno con un DSDT basado en el que crea Clover y luego modificado para mi equipo. Otro con un DSDT basado en el de Pikeralpha y luego modificado para mi equipo http://www.insanelymac.com/forum/topic/319358-dsdt-ga-h87m-d3h/ ¿Podrían echarme una mano? Dejo el inyector o un SSDT-UIAC con los datos de los puertos. Muchas gracias. DSDTuzmi.zip
  6. FOREWORD: Be warned this is a messy guide for advanced users. This guide will apply if you have first generation Intel graphics also known as GMA 5700MHD (PCI id 8086:0046) It is guaranteed to work on a HP G62 laptop (this laptop doesn't seem to use EC to manage brightness) It may also work on other laptops, with some experimenting! If it doesn't work, see the replies in this thread before asking for help. Update: make sure you read other posts in this thread, if your laptop is not a HP G62 laptop, especially post 68 from jerrywilborn which may help you http://www.insanelymac.com/forum/topic/287133-guide-backlight-brightness-for-intel-80860046-1st-gen-hd-gma-5700mhd/page__st__60?do=findComment&comment=1903273 OBJECTIVES: This guide should help you enable: Brightness keys Brightness slider in preference panel Backlight will work on waking up from ACPI sleep (note: if you ONLY want to enable this fix, and no other fixes, then see post number #6 ) Screen dimming will work after a short period of inactivity Screen sleeping will work off after a longer period of inactivity Automatic screen dim when switching to battery power If you have applied my fixes from another thread, you will need to review them, as a lot has changed. PREREQUISITES: First you will need to install hotKoffy's ACPI BACKLIGHT kext (attached). (Note: Do not install the Generic Brightness kext -- if you have it , try and delete it) ---- GUIDE ---- Step1: Find out our graphics BAR0 register (sometimes known as BAR1 register because some people count from 1...) Mine is at 0xB0000004 so you will notice all my "magic numbers" starting with 0xB.... To find your BAR0/BAR1 address, you will have to look at your integrated graphics PCI configuration space. It will usually be the second device on PCI bus 0 (device 00:02:00) You have two options, Expert option: You can use the 64bit lspci driver from these forums and do it on your Mac. Easier option: you can find this info even easier using RW-Everything on windows, but you will have to boot from windows. Download the RW-everything app from Download | RWEverything , start it, go to PCI window, and select your Intel Graphics from the drop down, take note of the BAR1 number (screenshot below:) The screenshot above is from giofrida's system. Because his BAR0 starts with 0xC.. we will need to modify the OperationRegions below so that 0xB00048254 becomes 0xC00048254, and 0xB00048250 becomes 0xC0048250 etc. You will need to do this for your system. Step 2: --- ACTUAL PATCHES--- Open your DSDT.aml in a DSDT Editor (see other threads for how to use this. MODIFYING DSDT MAY SCREW UP YOUR COMPUTER SO BE SURE YOU KNOW WHAT YOU'RE DOING.) The following needs to be placed just before the beginning of " Scope (_SB)" ( before the first occurence of this string in your DSDT). Make sure you change the magic numbers to comply with your BAR0. OperationRegion (BRIT, SystemMemory, 0xB0048254, 0x04) Field (BRIT, AnyAcc, Lock, Preserve) { LEVL, 32 } OperationRegion (BRI2, SystemMemory, 0xB0048250, 0x04) Field (BRI2, AnyAcc, Lock, Preserve) { LEV2, 32 } OperationRegion (BRI3, SystemMemory, 0xB00C8250, 0x04) Field (BRI3, AnyAcc, Lock, Preserve) { LEVW, 32 } OperationRegion (BRI4, SystemMemory, 0xB00C8254, 0x04) Field (BRI4, AnyAcc, Lock, Preserve) { LEVX, 32 } 2. Now, the following assumes your graphics module is called GFX0 and that the LCD is listed as the second sub-device of GFX0. To find your graphics module, you can try and look for the line "Name (_ADR, 0x00020000)". The LCD should be the second sub device, mine is called DD02. You can use IOREG to confirm the name of your graphics (eg. GFX0). You can use the following method to identify the LCD sub-device: simply, go to your GFX0 (or equivalent), and then under that device, identify the sub-device that has those methods (_BCM, _BCQ, _BCL). YOU NEED TO REMEMBER TO NAME THIS SUB- DEVICE by adding the following line: Name (_HID, EisaId ("LCD1234")) in my case it looks like this Device (DD02) { Name (_HID, EisaId ("LCD1234")) ... 3. Then, you will need to add a new device PNLF. Usually you will have to add this before the beginning of Scope _PR, or after all other devices. IF YOU ALREADY HAVE ANOTHER PNLF DEVICE, you will need to replace any other PNLF you may already have (delete it and then use my code instead). Device (PNLF) { Name (_HID, EisaId ("APP0002")) Name (_CID, "backlight") Name (_UID, 0x0A) Name (_STA, 0x0B) Method (_BCL, 0, NotSerialized) { Return (Package (0x13) { 0x64, 0x32, Zero, 0x06, 0x0C, 0x12, 0x18, 0x1E, 0x24, 0x2A, 0x30, 0x36, 0x3C, 0x42, 0x48, 0x4E, 0x54, 0x5A, 0x64 }) } Method (_BCM, 1, NotSerialized) { Store (0x80000000, LEV2) If (LGreaterEqual (Arg0, 0x64)) { Store (0x12FF, LEVL) } Else { If (LGreaterEqual (Arg0, 0x5A)) { Store (0x11FF, LEVL) } Else { If (LGreaterEqual (Arg0, 0x54)) { Store (0x103A, LEVL) } Else { If (LGreaterEqual (Arg0, 0x4E)) { Store (0x0EBB, LEVL) } Else { If (LGreaterEqual (Arg0, 0x48)) { Store (0x0B24, LEVL) } Else { If (LGreaterEqual (Arg0, 0x42)) { Store (0x0873, LEVL) } Else { If (LGreaterEqual (Arg0, 0x3C)) { Store (0x065B, LEVL) } Else { If (LGreaterEqual (Arg0, 0x36)) { Store (0x04C8, LEVL) } Else { If (LGreaterEqual (Arg0, 0x30)) { Store (0x0396, LEVL) } Else { If (LGreaterEqual (Arg0, 0x2A)) { Store (0x02B0, LEVL) } Else { If (LGreaterEqual (Arg0, 0x24)) { Store (0x0266, LEVL) } Else { If (LGreaterEqual (Arg0, 0x1E)) { Store (0x0218, LEVL) } Else { If (LGreaterEqual (Arg0, 0x18)) { Store (0x01D1, LEVL) } Else { If (LGreaterEqual (Arg0, 0x12)) { Store (0x0191, LEVL) } Else { If (LGreaterEqual (Arg0, 0x0C)) { Store (0x0161, LEVL) } Else { If (LGreaterEqual (Arg0, 0x06)) { Store (0x0132, LEVL) } Else { If (LGreaterEqual (Arg0, Zero)) { Store (0x82, LEVL) } Else { Store (0x11FF, LEVL) } } } } } } } } } } } } } } } } } } Method (_BQC, 0, NotSerialized) { Return (^^PCI0.GFX0.DD02._BQC ()) } Method (_DOS, 1, NotSerialized) { ^^PCI0.GFX0._DOS (Arg0) } } In the code snippet above, you may have to change whenever it says "PCI0.GFX0..." to your equivalent, eg. say "_SB.PCI0.VGA0" or something. Provided, the KEXTs were installed, this will enable your brightness slider, and it should work without problems incrementing/decrementing brightness in 17 discrete brightness steps (16 + zero state), and this is the number of steps needed to enable the brightness keys, so they will work now! The final step is to enable Backlight after wake-up. The 1st gen HD graphics uses two special registers to achieve this, and the following will fix it for you: Search your DSDT for the method _WAK Add two lines to the beginning, so that it looks like this: Method (_WAK, 1, Serialized) { Store (0x80000000, LEVW) Store (0x13121312, LEVX) ... Voila! Happy to help you with your DSDT's if you have any problems! Report if it's worked! ACPIBacklight.kext.zip
  7. robi101012981

    Help with patching DSDT

    Hello! Can somebody please help me with patching the DSDT? I tried to do this but I always fail.. The problem is that my graphic card it's recognised, but I don't have QE/CI... I have 1.5GB of VRAM, but my laptop it's working like a cra#...Injected Intel in Clover, applied fake ID, and still doesn't work.. I also tried with my 1050 TI, but this still doesn't seems to work.. Any suggestions? My rig it's: Acer Aspire VX 15, Intel I7-7770HQ, Intel HD 630+ nVidia Geforce 1050 TI. I also have problems with brightness, it's very low and I can't control it... EFI - robi101012981.zip ioreg.rar config_good.plist.zip
  8. Hi, Im new at this forum and I have some problems with my DSDT file. It is the untouched original file but I get always 3 errors. The errors: Intel ACPI Component Architecture ASL Optimizing Compiler version 20091214 [Dec 16 2009] Copyright (C) 2000 - 2009 Intel Corporation Supports ACPI Specification Revision 4.0 /Users/omer/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl 6674: } Error 4096 - syntax error, unexpected '}', expecting '(' ^ /Users/omer/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl 6740: } Error 4096 - syntax error, unexpected '}', expecting '(' ^ /Users/omer/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl 12795: [*** iASL: Read error on source code temp file /Users/omer/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.src ***] Error 4096 - syntax error, unexpected $end ^ ASL Input: /Users/omer/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl - 12796 lines, 402558 bytes, 5016 keywords Compilation complete. 3 Errors, 0 Warnings, 0 Remarks, 0 Optimizations My System: Lenovo G510 Motherboard Chipset: Intel HM86 (Lynx Point) CPU: Intel® Core i7-4700MQ CPU @ 2.40GHz Ram: DDR3 8GB SODIMM Graphic: Intel HD 4600/AMD Radeon 8670m Wlan: Atheros Communications AR9565 Wireless Network Adapter Thanks in advance. dsdt.aml.zip
  9. I recently got my XP941 to UEFI boot on my Gigabyte GA-Z87X-UD5 TH however the device was showing up in System Information as Generic AHCI device. As the XP941 is nearly identical to the flash SSD used in the new Apple iMacs and MacPros I decided to spoof it in DSDT I inserted this code into PCI0 in my DSDT (Bear in mind I have my XP941 on a Lycom adapter in PCI slot 1) might be useful for others with this device.. Device (PCI1) // Rename to appropriate slot number { Name (_ADR, 0x00010000) // _ADR: Address change this depending on appropriate pci bridge address in IORegistryexplorer Device (SSD0) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "device-id", //spoofs Apple SSD Controller Buffer (0x04) { 0x00, 0x16, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } } Now it looks like this: If this code could be improved please feel free to let me know. I'm also curious to know if something similar could be achieved using Fake id in Clover..
  10. Boltron

    A660 Yosemite Help

    HI everyone, I have a Toshiba A660 that i have managed to get Yosemite installed and 90% functioning, The only issues (that i know of) are: - No battery level (unticks itself) - No Sleep - No ethernet (not important as wireless is functioning) I have done some reading and believe that i need to patch my DSDT to resolve my battery problem but have no idea what to do with it! Attached is my DSDT dumped from Windows with RWEverything, if anyone could help i would be forever greatful Thanks in advance DSDT.aml.zip
  11. Using DSDT Editor I've extracted my DSDT file and I have one error left when I try to compile. I've attached a screenshot of the error log and attached the full text of the DSDT extraction. What can I do to fix this error? Any Help is greatly appreciated. dsdt-gigabyte-z87-ud5h.zip
  12. Hola después de mucho aprovecharme de este foro me he decidido a colaborar yo también, aquí dejo mi DSDT, SSDT, config file de Clover (excepto numero de serie etc) y los kexts que he instalado, todo lo demás original yosemite. Instalacion limpia con clover y arranque UEFI. Creo que me funciona todo reposo, cámara, sd, teclas Funcion, HDMI, USB3.0. La grafica Nvidia esta desactivada por DSDT para mac os x. El wifi no es la tarjeta original, la cambie por una BCM943224 que funciona de manera nativa en Yosemite seleccionando smbios MacbookAir. Para speedstep recomiendo macbookAir4,2 o macbookpro8,1 Aquí va el enlace a la Bios modificada que instale para el control de la energia nativo extraída de aquí: http://www.insanelymac.com/forum/topic/283774-patched-bios-for-native-speedstep-on-asus-n53sv/ Un saludo y gracias. Archivo comprimido.zip KextsAsus.zip
  13. Hello everybody, My machine is a HP Pavilion P6230it with the addition of a TP-LINK TG-3468 LAN interface, and I'm running OS X 10.9.3. I'm approaching DSDT and SSDT editing in order to get as many features as possible to work natively without the need of patched kexts of sort. As of my understandment of the practice its two goals are: 1 - To update the code so that it matches the latest iASL compiler syntax and standars. 2 - To modify the names and specifications of listed devices to match the names that the system natively expects to find. Still I can't find an exhaustive list of global or common modifications, providing explanations so that I understand what I'm turning into what and why. For example, I'm trying to get the devices to match those contained into the iMac11,1, which seems to me close enough to my machine. In a previous attempt to edit AGPM.kext to set better fitting thresholds I found that the graphic device is listed as GFX0: Which leads me into thinking that's the name given by Apple to graphic devices at least in this Mac. In my current DSDT the graphic device is also listed as GFX0, does this mean I should leave it as it is for the OS to find it? Am I getting this right? Thanks in advance.
  14. EDIT : Working https://www.dropbox.com/s/hl2hmat9nrz7ldq/working%20DSDT.aml Hi all ! I can't make a clean version of DSDT... - I have extracted my DSDT with aida - decompile it with iasl :"/Applications/MaciASL\ 1.3.app/Contents/MacOS/iasl5 -d /Users/Gus/Desktop/acpi_dsdt.bin" - make a clean version in .dsl with 0 error But when i compil it in aml, i have 2 errors in _L1E and clover won't boot because in my boot log, i have : "IOAPIC : Version 0x20 Vectors 64:07" link : acpi_dsdt.bin --> acpi_dsdt.dsl --> acpi_dsdt.aml specs : http://www.msi.com/product/nb/GT70_2PE_Dominator_Pro.html#hero-specification If one can help me ? RehabMan ?
  15. I recently built a new PC with MSI Z97 Gaming 3. I installed Mavericks but no HD4600 working. Trying to patch with DSDT but 2 errors stopped me from compiling. Any one here sheds the light will be appreciated. I attached with my DSDT below. Btw my country blocked Google service and related sites, I tried to use Toleda`s 8 series clean compile patch but failed to connect to the site. I don`t know whether it work with Z97 or not. Please help.dsdt.zip
  16. Frank Nitty

    Help needed cleaning up a DSDT

    Like the title says I am needing help cleaning up a couple of DSDTs. I've already extracted (2) different DSDT.dsl's from separate dual-boot machines under Windows. However, there are numerous errors on each of them that I can't fix alone in order to compile them into a DSDT.aml. I would greatly appreciate any kind soul willing to help me complete this task. I have included the (2) different DSDT.dsl's as a attachment in this post. Thanks in advance. dsdt-Z97.zip dsdt-Z170.zip
  17. The title pretty much sums it, but here it goes: I upgraded an otherwise fully working hackintosh from Yosemite to Sierra. Now I'm stuck, already for two days. It will boot only in Safe Mode, or if I removed my DSDT from the appropriate Clover folder (and in this case I need to inject the HD4000 with Clover's Graphics Injector). What happens is the boot goes fine until the last stage, crash-rebooting at the exact instant the Desktop should appear. If I use verbose, I see a quite messy screen before the sudden reboot. No panic message. If I set Clover to prevent reboot on kernel panics, the said messy screen stays frozen until I do a hard reset. At first I thought my old DSDT became corrupt, so I deleted, restarted with no DSDT (injecting the intel graphics via Clover) and created a new one, using macIASL and Pjalm's patches for my board and a HD4000 patches. Surprise, surprise: the problem didn't go away. Then I deleted the new DSDT, restarted the computer in safe mode, and I tried again, this time using Toleda's Clover audio HDMI command tool, which created two SSDTs in the Clover ACPI/Patched folder - I need HDMI audio, and that's why I cannot settle with simply using Graphics Injector - and, as I feared, it didn't solve anything. I already ruled out the basic mistakes: lack of FakeSMC, VT-D being enabled in the BIOS, wrong SMBIOS for the build etc. The specs are: i7 3770 (non K), HD4000, Gigabyte B75M D3H, macOS Sierra 10.12.1, Clover (legacy mode) rev 3923 and SMBIOS set to iMac 13,1. All these settings worked fine since Mountain Lion (I started using Clover with Yosemite though). Any help would be much appreciated! All the best.
  18. Hey guys. I'm new to this whole DSDT patching thing; i can't get one patched correctly to save my life. My current install is Mavericks 10.9.5...WiFi works, sleep, qe/ci, vga out, etc But i know a patched dsdt will complete my build.Could anyone patch this up for me? My system specs and all necessary files are attached below. Any help would be much appreciated! My System Specs: Intel Core i3 Processor 2.2GHz 8GB SDRAM RAM 250GB 5400RPM Hard Drive 17.3-Inch Screen, Intel HD 3000 Graphics (2nd Gen) origin.zip Gymel’s MacBook Pro.zip
  19. Hi, i Have built a new PC, currently running windows 10 pro, and looking to dual boot OSX El Capitan. I have been patiently waiting to see what the state of play is regarding Skylake, and the 10 series chipset motherboards. Hardware wise it is a Skylake i5 6600K, Gigabyte GA-Z170X-UD5 TH motherboards, Apple airport native PCIe with Bluetooth 4, 32GB DDR4 2133, 2 x Samsung 850 Evo SSD, 2x Seagate 4tb Hybrid drives, and elderly maxtor HDD i use for backup purposes only. 2 x Gigabyte wind force 970 GTX 4gb. Now onto what I've found, the motherboard has been updated to F4 bios (last stable non beta at time of writing). I am trying to figure out what DSDT patches i would need to get a stable install of EL Capitan, I plan on using clover as the boot loader, and to dual boot win 10. There does not seem to be a lot of information regarding 10 series boards, and what is usually points to Asus 170 based boards. I would like to have as simple a list of required patches as possible. so i can enable them via MacIASL. I have extracted the DSDT and all 8.. yes 8 SSDT files. I want to have as "vanilla" a setup as possible. So far i have kexts to enable the Intel Ethernet i219 (mausi kext), latest FakeSMC, The USBInjectAll.kext to help enable the USB ports. I really want to get on with installing OSX onto this machine. So any pointers as to what else i will need to get a successful install done would be gratefully appreciated. I have a elderly mountain lion system running to do the editing of DSDT and build my installer from.
  20. Hello friends! I have installed kext AppleHDA.kext patched from Patcher 1.1(thanks for patcher ), and also patched config.plist, by this method I got sound working, but microphone still doesn't working . Please help me to get microphone working. Thank you! OS X El Capitan 10.11.3 Asus K52F Intel Core i5 M480 Intel HD Graphics Conexant CX20585 ---------------- How to fix? ok, now the only problem was in platforms.xml.zlib (applehda.kext>resurces>platforms.xml.zlib) 1.open applehda.kext>resurces 2.convert file platforms.xml.zlib to platforms.xml (convert with special program Zlib xml convertor) 3.open this xml file with plist edit program 4.open root>CommonPeripheralDSP 5.delete 12,13,14....22 lines (1>11 = speaker lines, 12>22 microphone lines) 6.save file 7.convert file platforms.xml to zlib 8.install edited applehda.kext and rebuild cache don't understand or any problems? write me PM
  21. rizmajody

    Help me Disabling NVIDIA

    Hey bro, would you like to help me to disable my NVIDIA cars using my own created DSDT I have tried it but it failed while compiling DropTable.zip
  22. Hi! I have recently been able to install Mac OS X El Capitan onto my Dell Inspiron 7558. I am very happy but I am having a problem with audio, and I'm trying one last thing before I have to (sadly) go back to Windows. I have Realtek ALC 255, I know it's supported and uses Audio ID 3 but the problem I am having is compiling my DSDT. I have already try to search the internet, but I'm not getting a resolution. I haven't done DSDT work before, I have only read about it. Anyways, the reason I came here today is to ask how or if someone can help me fix these errors that I am getting error code 6126 with various errors: I am using RehabMan's Laptop Patches Github. The specific file is under Audio and is audio_HDEF-layout3.txt. I am wondering what I can do to get this DSDT fix, I have been trying to solve my no sound issue for almost a week now, and I'm getting really inpatient at the moment. I have tried decompiling it again, and have also downloaded the latest iasl version. I'm using MaciASL 5.1. Thanks! Stransform EDIT: I can't seem to upload files so I'm going to leave a Google Drive link. I'm not sure if that is not allowed, if it is not I will remove it immediately. https://drive.google.com/file/d/0B_ugSfp4UtLWcWg1bHNyWlFNcWc/view?usp=sharing- DSDT.aml https://drive.google.com/file/d/0B_ugSfp4UtLWUUR6NjB5ajNxbnc/view?usp=sharing- DSDT.dsl EDIT 2: I found the version of MaciASL with ACPI 6.1. Now I'm getting just one error "Name already exists in scope (_DSM)"
  23. Hi, I've already fixed some Warnings and Remarks, but I can't fix the Errors on my own. Please help. Thanks! X10DAi DSDT.zip
  24. rand0777

    DSDT Contradicting Itself

    I've been trying to clean up my DSDT and cleaned up all of the petty errors, however it seems to be confused as to whether or not it wants a Package or a Buffer toward the end. If anyone could help me out here, I'd greatly appreciate it. It's also worth noting that none of my USB ports (all 2.0) aren't working and if you see anything in there that might be the problem, brownie points all around! RandyDSDT.dsl.zip EDIT: Still haven't figured out the issue on my end, could really use some help here. It turns out all of the errors here seem to be related to USB so that could be a step in the right direction (or not.) My DSDT size is pretty large so I'm thinking there may be redundant or conflicting info inside. Can anyone take a crack at it? RandyDSDT.dsl.zip
  25. I'm trying to disable my discrete graphics card and the consensus seems to be that it should be disabled through an SSDT, not necessarily in the DSDT itself. So I extracted my DSDT and SSDT's using Ubuntu, added the .aml extension and using maciASL I can't find the area the area that I need to turn off. All of my knowledge I have on this comes from the guides and forum posts I go over, I don't have any prior experience with DSDT's. Here is the most precise guide I can find on the subject, and it specifically states that it's for Radeon cards. Here's the issue: it says to look for \_SB.PCI0.PEG0.PEGP function. I don't have this function anywhere in my SSDT's; most of them look like they're for the processor. I do, however, have SB.PCI0/PEG0/PEGP in my DSDT but it's in subdirectories and not all on one line. I also can't find the _OFF or _ON methods that it states that it would have neither anywhere in my DSDT or in any of my SSDT's. I think that PEGP is definitely something to look at, but there doesn't seem to be anything there that I would need to go forward. Does anyone have any suggestions? I'm using Clover on Yosemite 10.10.5. This is an HP DV6t 6100 i7 + HD3000. My DSDT has already been modified a few times to get brightness, battery, etc.
×