Jump to content

Search the Community: Showing results for tags 'LGA 2011'.



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
    • OSx86 Installation
    • Post-Installation
    • DSDT
    • Hardware Components and Drivers
    • Complete 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

Categories

  • OSx86
  • Apple News

Found 4 results

  1. Using a Sabertooth X79 motherboard (LGA 2011), I set up Yosemite with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], then went through a Clover install for that partition. Most everything worked fine, except for a few things here and there. I was trying to figure out why messages wasn't working ("An error occurred during activation. Try again.") and while troubleshooting and attempting at every guide/fix I could find (which still didn't work), I realized NVRAM was not working properly. If I run in the terminal: sudo nvram TestVar=HelloWorld then restart and run sudo nvram -p TestVar does not show up. (in case you need what does, here it is:) fmm-computer-name Mac Pro bluetoothActiveControllerInfo %01%00%12%0a%00%00%00%00%15%1d%00%1b%dc%06v%9a 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK223EC2EUH6N%ff SystemAudioVolume 0 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %09v%e0%b8%ee! IOPowerManagement <INVALID> SystemAudioVolumeDB %f0 Some pictures of my current clover configuration: I also noticed (while trying to use emulation NVRAM) that in the clover preference pane, even after setting the "Save NVRAM contents to disk" to Always, after restarting it would go back to auto. Not sure if this matters but figured I'd include it. /Volumes/EFI/ tree: If anyone has had experience with this before or knows a way to fix it, I'd appreciate it. Thanks
  2. First, a word of thanks to Omni, rampagedev, and others who have worked to get Power Management working on LGA 2011 boards. My current rig is a Sabertooth X79 (latest BIOS), 4930k PCU, 32gb 1866 memory (Corsair), EVGA GTX 650 graphics. I ran solid for about a year using a i7-3820. No stability issues at all. Everything just works. I upgraded to a 4930k a few months ago without much incident. No stability issues at all and again everything just works. I was excited to see that Apple finally supported Power Management for LGA2011 CPUs in 10.9.2. Following guides by rampagedev (http://rampagedev.wordpress.com/) I was able to get PM up and running, both under Chameleon and Clover. It works using the vanilla AICPUPM kext and an SSDT generated using Pike's script. However, what's tripped me up has been some stability issues. When I load SSDT I get random restarts. I've tried to pin down the cause using system log but it doesn't seem much help. I've chased a few red herrings (certain applications, sound drivers, etc.) but no matter what I do the crashes persist. Sometimes the restarts are instant, but typically they come after things start to crash -- especially Chrome and Finder. When I remove the PM SSDT things once again become stable. I've run memtest and my memory is fine. I've tried various BIOS settings and as long as I have the PM SSDT loaded, I get the random crashes. It happens on stock settings, overclock settings, etc. Shilohh suggested I do a CMOS reset, load optimized defaults, and try things out. I'm going to try that now, leaving my 1866-certified RAM at 1600. Any ideas?
  3. Using a DSDT that was extracted on a different build with different devices installed, may not work on your system even if you have an identical motherboard and BIOS. If you still would like to try a DSDT edited and extracted by another, rampagedev is the best place to get it. The DSDT edits in this guide are specifically for the Asus Rampage IV Extreme - Socket 2011 - X79 Motherboard, but some may work on similar systems. This guide will walk you through extracting and editing a DSDT from your specific RIVE build using DSDTSE v2 beta. Before We Start A DSDT is a translation of your system's BIOS so: 1) Make sure you are updated to the BIOS you want to extract the DSDT from and set up your BIOS completely and correctly for your system. 2) Make sure you have all your PCI devices installed in the locations you want them before you continue. 3) Remove DSDT.aml from /Extra, if present, or reboot using the "DSDT=No" boot flag. Getting Started Download and open DSDTSE V2 Beta and my list of patches. files.osx86.net/downloads.php?do=file&id=3099&act=down&actionhash=guest http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=121230 On the main pane, click "Extract DSDT". Your DSDT will be extracted from your active BIOS in a "Decompiled" window. Click compile. You will be presented with a "Compile error" window. Click "OK". An "Error" window will open showing you all the current errors, warnings, and remarks. Note there are lots of errors. Close the window. Click "Fixcompile". The DSDT should compile successfully and another "Code" window will open. In the "Code" window, note that the DSDT's errors have all been fixed except for one warning. Close the "Code" window. Patching Open my list of DSDT Patches and lets start patching. 1) Add Method DTGP: Copy "Method DTGP" from the list. Click on the right side of the " { " that follows the "DefinitionBlock". Hit the Right Arrow key. The cursor should be at the very start of the next line. Hit enter to make a space. Use the Up-Arrow key to move the cursor up to that space. Paste in "Method DTGP" there. You can change "Name (TMAC, "R4E 3404")" to read whatever you'd like it to. Example: Name (TMAC, "BIG BOB'S BIG DSDT"). I've only added this so I can see what version I've opened for future editing. Click "Fix Compile". 2) Cleaning up unnecessary stuff: Note: This one is not necessary and adds no functionality. Scroll down to Name (OSVR, Ones). Comment out the OS's. Also see example in my list of DSDT patches. Click "Fix Compile". 3) Fix the SIOS Warning: Copy "SIOS Warning" fix. Type "sios" in the search window and click search. Scroll to the bottom of the method and add a space right before the last " } " . Paste the fix in that space. Click "Fixcompile". Note that the last warning is no longer present in the "Code" widow that opens. 4) Get the LPC controller to load and use native OS X kexts: Copy the Device (SBRG) fix from the list. Search for "sbrg". Move the "Decompiled" window over to the left side of your screen so that the left side of the window is cut off right at the edge of the D in "Device (SBRG)". Scroll down until you find the " } " that lines up the the same spot as the D from "Device (SBRG)". This is where SBRG's sub device chain ends. Move the window back over so you can see all of the left side again. Select from right side of the " } " that you found, all the to the left edge. Paste over it with the Device (SBRG) fix from the list. Click "Fixcompile". 5) Remove dedicated IRQs from devices to later give them to the High Precision Event Timer: Type "IRQNoFlags ()" without the " " into the search box. Click "Next". The first match will be in "Device (PIC)". Select from the right edge of "{2}" below it, all the way up to the far left edge of "IRQNoFlags ()". Hit Delete. Click next again. It should now find "{0}" in "Device (TMR)". Delete it. Click next. You should now find "{8}" in "Device (RTC0). Delete it. Click next. You should find "{13}" in "Device (COPR)". Leave this one alone. Click "Next". Continue the same process and delete all the "{1}"s from "Device (PS2K)". Delete all the "{12}"s from "Device (PS2M)". Note: If you are using a PS2 mouse or keyboard, you may need to find different IRQ values to use instead of {1} and {12}. 6) Give Device (HPET) 4 dedicated IRQ values to use so it doesn't try to steal any from USB: Search "hpet" and paste in fix -as in my example on the list. Click "Fixcompile". 7) Add sub-device "Device (BUS0)" to "Device (SMB)" to load native SMBus kexts: Search "Device (SMB)" and paste in fix over the last " } " before the next device. Also see my example on the list. "Fixcompile". 8) Add Device (HDEF) to the end of Device (PCI0) to enable onboard audio with the "Interim IvyBridge" kext from Toleda: Search "Device (PCI0)". Find the end of the device chain the same way we did in the "Device (SBRG)" fix. It's a LONG ways down. For me, the PCI0 device chain starts at line 1670 and ends at line 6286. Paste the fix over the last " } " in the device chain. "Fixcompile". 9) Add AAPL,clock-id 2 to PEX1-4 to allow sleep (SleepEnabler.kext is necessary) while USB 3.0 storage is plugged in: Search "Device (PEX" and hit next until you find "Device (PEX1)". Paste patch in between "Name" and "OperationRegion". Repeat for "Device (PEX2)", "Device (PEX3)", and "Device (PEX4)". Fixcompile. Note: Any drives plugged into USB 3 ports will be force ejected upon wake. They will then automatically remount. This may be solved in the future with more USB 3.0 support from Apple. Fixcompile. Finishing Up Click on the "Compile" tab to get into the compile section. Check the "Autofix errors" box and the "Fixes report" box. Click the "Compile" button. Click the "Gimme my DSDT" button. A finder window will open containing your edited DSDT. It will be named "DSDT.aml". Drag "DSDT.aml" into your "/Extra" folder. Delete or overwrite the old DSDT.aml if one is present. If you haven't installed a boot loader yet, and don't have an "/Extra" folder, place "DSDT.aml" in /Extra after you've installed a boot loader. Verification On the "Main Pane", in the second box, under "Registry Info", click "Get". This will open IORegistryExplorer and show you all the devices loaded and information about them. 1) In the search box of the newly opened IOReg window, enter "hpet". With HPET selected on the left twirl open the disclosure triangle for "IOInteruptSpecifiers". In the "Values" column, the first pair of numbers (they are displayed as Hexadecimals and you will need to convert them to decimal using something like HexDecBin.app) -are the IRQs that HPET is using. You should have, 0c (12), 08, 02, and 01. 2) Find "SBRG" and note that AppleLPC shows up as a sub-device and that it has the native OS X driver loaded. 3) Find "SMB". Note that the device we added, "BUS0", shows up in the device tree and it is using the native OS X driver. 4) At "EUSB" and "USBE", you should see the"AAPL,clock-id" we added. 5) At "PEX1", "PEX2", "PEX3", and "PEX4", you should see the"AAPL,clock-id" we added. 6) Note that "HDEF" should now be present and loaded. Shilohhs_R4E_DSDT_Patches 2.rtf.zip Interim_898_Lion_AppleHDA.zip
  4. DSDT for X79 Motherboards

    For the past few week my friends and I have been developing DSDT for Intel LGA 2011 x79 Motherboards. Development first started with Asus motherboards and now we have recently added Gigabyte motherboards. This is my blog that will provide all of the information about these DSDT. http://rampagedev.wordpress.com/ If your x79 motherboard is not included on are blog please post your unedited DSDT, IOreg, and what GPU you were using at the time the DSDT was extracted. Post this information and files on here and we will work on it and add support as soon as we can. I can usually edit a basic DSDT within 30 minutes. Motherboards Currently Supported: All Asus Motherboards All Gigabyte Motherboards Limited AsRock Motherboards
×