Ga-x58a-ud3r

[rommy]

If you suspect the DSDT is incorrect, then install NullCPUPM kext and delete the DSDT. Reboot. This gives you a clean boot with the main boards DSDT assuming you are using Chimera/Chameleon boot loader and not injecting anything with Clover.

You can then go back to the very beginning of learning the DSDT edits for your board. Some are needed for socket 1155, 1156 and 1366.
For your reference if you want to do your own editing see:
http://macmanx86.blogspot.com/2010/06/new-minimal-dsdt-edits-for-gigabyte.html
http://macmanx86.blogspot.com/2010/11/minimal-dsdt-edits-for-gigabyte-socket.html
and the patches have been scripted for use with MACIASL app at http://www.tonymacx86.com/dsdt/1082...ward-1155-1156-1366-dsdt-patches-maciasl.html

You could also go back to d00d's very good guide at http://www.insanelymac.com/forum/to...a-dsdt-native-power-management-modifications/ to understand what to patch and why.

thank you Going Bald, very precise as usual. I must say it's too difficult for me to deepen the complexity of DSDT. I gave a look at pages you refer to and also downloaded maciasl tool to open my DSDT. It's the one I downloaded from tonymac site: more than 6000 lines!! So I immediately gave up. I only noticed the strange message about the checksum mismatch into the header of the file:
*
* Intel ACPI Component Architecture
* AML Disassembler version 20100331
*
* Disassembly of iASLzP8JPg.aml, Fri Mar 6 22:07:51 2015
*
*
* Original Table Header:
* Signature "DSDT"
* Length 0x000050EB (20715)
* Revision 0x01 **** ACPI 1.0, no 64-bit math support
* Checksum 0x7B **** Incorrect checksum, should be 0xF6
* OEM ID "GBT "
* OEM Table ID "GBTUACPI"
* OEM Revision 0x00001000 (4096)
* Compiler ID "INTL"
* Compiler Version 0x20110623 (537986595)
*/
DefinitionBlock ("iASLzP8JPg.aml", "DSDT", 1, "GBT ", "GBTUACPI", 0x00001000)
{
Name (TMAC, "GA-X58A-UD3R-2.0-FH DSDT edits by MacMan at tonymacx86.com 2012-02-16")
Method (DTGP, 5, NotSerialized)
{
If (LEqual (Arg0, Buffer (0x10)
{
/* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44,
/* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B
}))
{
If (LEqual (Arg1, One))
{
If (LEqual (Arg2, Zero))
{
Store (Buffer (One)
{
0x03
}, Arg4)
Return (One)
}

If (LEqual (Arg2, One))
{
Return (One)
}
}
}

Store (Buffer (One)
{
0x00
}, Arg4)
Return (Zero)
}

Scope (_PR)
{
Processor (CPU0, 0x00, 0x00000410, 0x06) {}
Processor (CPU1, 0x01, 0x00000410, 0x06) {}
Processor (CPU2, 0x02, 0x00000410, 0x06) {}
Processor (CPU3, 0x03, 0x00000410, 0x06) {}
Processor (CPU4, 0x04, 0x00000410, 0x06) {}
Processor (CPU5, 0x05, 0x00000410, 0x06) {}
Processor (CPU6, 0x06, 0x00000410, 0x06) {}
Processor (CPU7, 0x07, 0x00000410, 0x06) {}
Processor (CPU8, 0x08, 0x00000410, 0x06) {}
Processor (CPU9, 0x09, 0x00000410, 0x06) {}
Processor (CPUA, 0x0A, 0x00000410, 0x06) {}
Processor (CPUB, 0x0B, 0x00000410, 0x06) {}
Processor (CPUC, 0x0C, 0x00000410, 0x06) {}
Processor (CPUD, 0x0D, 0x00000410, 0x06) {}
Processor (CPUE, 0x0E, 0x00000410, 0x06) {}
Processor (CPUF, 0x0F, 0x00000410, 0x06) {}
}
.................

Do I have to worry about that?
Regardless my CPUs troubles, it seems they are declared, but cannot read anything else.
Hope I'm not stressing too much.
bye
Rommy

 

[RandomNumber]

I hope this isn't too off topic. It seems like this area is responsive to most issues pertaining to the X58 1366 series Mother Boards. My signature describes mine. My specific question is has anyone here successfully gotten imessage to work on this set up? Like many I had it working for a long time and then back in maybe Nov. of 2014 it stopped and even with all the recent pronouncements of it working for others again, I have had zero success. Is anyone using Clover to boot? Is imessage working for you with clover? I'm aware of the dedicated "how to fix imessage" topic and I've ran that thing frontwards and backwards....still can't get things to work. Maybe we can get some advise with respect to our specific MB's right here in this post....Thanks

 

[RandomNumber]

Anyone have success with this MB and Clover/Yosemite? I'm having a serious issue with sleep not waking. When it sleeps the screen goes black the fans stop and it seems like normal sleep until I try and wake it. If I try to wake it by pressing the power button (*see note below) The computer initiates a restart but cycles continuously trying to post but never posts. To get the MB to post at that stage the only thing I can do is remove and replace the CMOS battery and reset the BIOS settings. My motherboard is an EX58 UD3R 1.6 FK with Xeon 5650 cpu.

*Note- This system using Chimera and Mavericks sleep worked fine as long as AppleRTC was patched and the normal way to wake from sleep was to press the power button to re-activate the system and then touch the keyboard or mouse to bring monitor to life.

I have ‘AppleRTC = True’ in the Clover config.plist & I’ve tried ‘Darkwake = 1’. Neither has an effect on the behavior I described. Full system in the signature.

 

[Richard325]

Q. will Yosemite run on bios FB?

I've used bios FB with Yosemite and a Sapphire HD5770.
I had lots of problems with Yosemite installation, but got it working with these:


Here my org.chameleon.Boot

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>EthernetBuiltIn</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
<key>Graphics Mode</key>
<string>2560x1440x32</string>
<key>HDAEnabler</key>
<string>Yes</string>
<key>HDEFLayoutID</key>
<string>01000000</string>
<key>IGPEnabler</key>
<string>Yes</string>
<key>Kernel Flags</key>
<string>kext-dev-mode=1</string>
<key>Timeout</key>
<string>2</string>
<key>UseKernelCache</key>
<string>Yes</string>
</dict>
</plist>


I might have also used these (it was a long time ago!!!)
Multibeast - add
Drivers/System/AppleACPIPlatform/10.9.5 AppleACPIPlatform

Boot Options/Ket Dev Mode (This is to allow third party drivers - solves stuck progress bar).


I returned to Mavericks because the computer would not wake after sleep. I'm using BIOS FB because sleep/wake seems to work more reliably with Mavericks.

 

[Going Bald]

I've used bios FB with Yosemite and a Sapphire HD5770.
I had lots of problems with Yosemite installation, but got it working with these:


Here my org.chameleon.Boot

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>EthernetBuiltIn</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
<key>Graphics Mode</key>
<string>2560x1440x32</string>
<key>HDAEnabler</key>
<string>Yes</string>
<key>HDEFLayoutID</key>
<string>01000000</string>
<key>IGPEnabler</key>
<string>Yes</string>
<key>Kernel Flags</key>
<string>kext-dev-mode=1</string>
<key>Timeout</key>
<string>2</string>
<key>UseKernelCache</key>
<string>Yes</string>
</dict>
</plist>


I might have also used these (it was a long time ago!!!)
Multibeast - add
Drivers/System/AppleACPIPlatform/10.9.5 AppleACPIPlatform

Boot Options/Ket Dev Mode (This is to allow third party drivers - solves stuck progress bar).


I returned to Mavericks because the computer would not wake after sleep. I'm using BIOS FB because sleep/wake seems to work more reliably with Mavericks.

Since you have no CPU graphics you should delete the lines


<key>IGPEnabler</key>
<string>Yes</string>

from your .plist

 

[Richard325]

Since you have no CPU graphics you should delete the lines


<key>IGPEnabler</key>
<string>Yes</string>

from your .plist

Great!
Thanks for your help.

 

[lump]

I've attached a copy of my Multibeast settings.

However, Multibeast now creates an org.chameleon.boot.plist optimized for new boards that have intel HD.

Make sure you set IGPEnabler=No and GraphicsEnabler=Yes.

If you have an existing Mavericks or even Snow Mountain running build you can even copy your DSDT.aml and org.chameleon.boot.plist to the /Extra folder of your unibeast installer. My install was a breeze!


Here's my org.chameleon.boot.plist :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>EthernetBuiltIn</key>
    <string>Yes</string>
    <key>GraphicsEnabler</key>
        <string>Yes</string>
    <key>IGPEnabler</key>
    <string>No</string>
    <key>Kernel Flags</key>
    <string>kext-dev-mode=1</string>
    <key>Legacy Logo</key>
    <string>Yes</string>
    <key>Timeout</key>
    <string>2</string>
        <key>GenerateCStates</key>
        <string>Yes</string>
        <key>GeneratePStates</key>
        <string>Yes</string>
        <key>UseKernelCache</key>
        <string>Yes</string>
        <key>HDAEnabler</key>
        <string>Yes</string>
        <key>HDEFLayoutID</key>
        <string>01000000</string>
</dict>
</plist>

Hope it helps.

Haven't done a clean install in a couple years & don't follow tonnymac all that closely but I simply used ElectronShapers Multibeast settings then used the code for trim enabler & this was the easiest install ever.

Thank you community!

 

[sportq]

Thanks to this thread and especially electronshaper I got my system updated to Yosmite 10.10.3 last night. I tried to re-use my Mavericks Multibeast settings file but I couldn't get it to boot outside of safe mode so I started with electronshapers "known good" settings but I found I had to add 3rd party SATA support (does that mean I'm using non-optimal SATA ports???).

Anyway, all good now and finally got rid of the nagging App store updates.

Pete

 

[giofox]

Hello,
I write because I have seen your post regarding "Yosemite Desktop Support Ga-X58A-UD3R" and Unibeast configuration.

I have several problems and do not know how to resolve them, if you can help me I would be eternally grateful

INSTALL MultiBeast 7.0.2
X58A-UD3R DSDT v2.0 FH (Tonymac) and example ElectronShaper

RESULT:

- I do not recognize the USB 3.0 motherboard
- When entering rest, no restarts. Activated manually, I reset the BIOS
- There is only 1 monitor signal (I have 2 monitors, 1 connected by DVI display and one for Port - DVI)




If you can help me or give any advice you would be eternally grateful, but can you help me, also thank you very much.
No more do.

Greetings from Barcelona and sorry for my English,

My Settings

Gigabyte GA-X58A-UD3R FH v2.0 (PCI Express x16)
Intel Core i7-960 Processor 3.20 GHz 8 MB Cache Socket LGA1366
Asus GeForce GTX 660 2GB GDDR5 OC - Graphic Card

Other HardwareEdit Value

6 x 4 GB Memory 1333Mhz = (24GB)

SSD 1 -> YOSEMITE 10.2 (SATA 6 GB) SYSTEM

SSD 2 -> WINDOWS 7 SP1 (SATA 6 GB) SYSTEM

HD1 = 1TB WD Caviar Blue SATA 3 GB (MEDIA MAC)
HD 2 = 1TB WD Caviar Blue SATA 3 GB (WINDOWS MEDIA)

2 PCI Express USB 3.0, a total of 4 USB 3.0 ports

DVD ROM
COOLER MASTER 690 II
POWER SUPPLY Bequiet 630w

 

[RandomNumber]

I finally got Yosemite working with Clover. No issues with sleep or sound or iMessage. All working perfectly!
I have a question. Is anyone using more than the max Ram of 16GB on this board? That seems to be the max (and is identified as such on Gigabyte.com). However, I know sometimes the specs don't tell the whole story and since I'm maxed out at 16GB I ask the question...