MacMan Build - GA-X79-UD5 - Core i7-3820 - Socket 2011

[maleorderbride]

Does USB 3.0 work at either 2.0 or 3.0 speeds?

 

[xHaroldS]

um will everything be working perfectly by around october? because thats when im getting a computer for my hackintosh

 

[Stork]

xHaroldS,
Yes, I fully expect it will follow the past maturity roadmaps. I build my 1st gen Core i5 / P55m system in September 2010 and the mobo and tonymacx86 software worked OOB, so to speak. I bought my 2nd generation Core i7 / Z68 system in late Spring 2011 and it became mature with Lion in late Summer. Thus, I expect Ivy Bridge to take the same amount of time.

However, it all depends on what's on Apple's roadmap. We'll find out at Apple's World Wide Developers' Conference in June 2012. Stay tune...

 

[paulash]

is 1394 working????

 

[paulash]

IS FIREWIRE WORKING ???PLEASE LET US KNOW.....FIREWIRE IS IMPORTANT TO DAW(AUDIO)

 

[paulash]

is firewire working?????please let us know

 

[Stork]

FW PCI (PCI-e) cards with Oxford chips work the best as they were the first chipset used and Apple supports them in OS X. I've used the Oxford chips cards in my Macs and Hacks since Moses was a child.

Other World Computing has some cards that work OOB.
http://eshop.macsales.com/item/Other World Computing/FW800PCI/
http://eshop.macsales.com/Search/Se...Ns=P_Popularity|1&Ne=5000&N=7058&Ntt=firewire

 

[shahar]

is firewire working?????please let us know

I haven't checked the on-board FW (which is FW400).

But I do have a Lacie PCIe FW800 card
http://www.lacie.com/products/product.htm?id=10525

which I can confirm it works with my SanDisk Extreme IV (FW800) card reader
http://www.kenrockwell.com/tech/sandisk-extreme-iv.htm

(this reader has become a relic due to USB3 ... but it is still one of the fastest)

Hope it helps

 

[shahar]

There's another thread discussing the bulid based of the GA-X79-UD5 board:
http://www.tonymacx86.com/viewtopic.php?f=168&t=45514

We have a DSDT for BIOS F9 (some work also being done on F10), which seems to work to a certain degree (CPU throttling - two P states - idle & full), some of the USB 2.0 ports working and audio.

Maybe we should combine efforts on this one?

 

[kizwan]

Hi MacMan,

I found "Scope (\_PR)" is missing in my Asus P9X79 PRO DSDT. And also SSDT only contains "_PDC (Processor Driver Capabilities)" & "_OSC (Operating System Capabilities)".

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20100428
 *
 * Disassembly of acpi_ssdt.bin, Wed Jun 20 13:35:18 2012
 *
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x000001D6 (470)
 *     Revision         0x01
 *     Checksum         0xF5
 *     OEM ID           "AMICPU"
 *     OEM Table ID     "PROC"
 *     OEM Revision     0x00000001 (1)
 *     Compiler ID      "MSFT"
 *     Compiler Version 0x03000001 (50331649)
 */
DefinitionBlock ("acpi_ssdt.aml", "SSDT", 1, "AMICPU", "PROC", 0x00000001)
{
    External (\_SB_.OSC_, IntObj)
    External (\_SB_.PDC_, MethodObj)    // 1 Arguments

    Scope (\_SB)
    {
        Processor (P000, 0x00, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P001, 0x01, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P002, 0x02, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P003, 0x03, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P004, 0x04, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P005, 0x05, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P006, 0x06, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }

        Processor (P007, 0x07, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_SB.PDC (Arg0)
            }

            Method (_OSC, 4, NotSerialized)
            {
                Return (\_SB.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
    }
}

Does adding the missing codes help SpeedStep a little bit?