Giacomoleopardo's Gigabyte GA-Z77N-WiFi Build for DB

giacomoleopardo · Apr 27, 2013

Giacomoleopardo's Prodigy MacMini 6,2 Gigabyte GA-Z77N-WiFi | Intel® Core™ i7-3770K Step by step guide

Change wifi card, and put Atheros AR9280, it works OOB
I used Belkin 2.1 bluetooth adapter, it works OOB and works in UEFI Bios and Chimera bootloader screen as well
Learn how to extract and edit dsdt. This mobo doesn't need it, actually, but in order to optimize the system and have a more vanilla OS as possible DSDT is the key. So basically, everything works on this machine, except a little minor issue when, waking from sleep, usb devices appear disconnected (and instantly auto-reconnected).

That's it! Let's start with the guide. Have fun!

Installation

Tools:

- Download the latest non-beta UEFI Bios from Gigabyte web site (F2 version at the time of writing)
- UniBeast for Mountain Lion and MultiBeast for Mountain Lion (registration required)
- MaciASL Open Beta for editing .aml files
- MaciASL patches from MaciASL Patch Repository Thread
- KextBeast (registration required)
- Chameleon Wizard (registration required)
- Kext Wizard
- Show All Files (registration required)
- IORegistryExplorer attached by toleda in his post#1 (registration required)
- Trim Enabler by Groths
- A working Mac or Hackintosh machine (or use iBoot method to start from scratch, if you don't have a Mac)
- Internet connection

Step 1 - Update and setting UEFI Bios

- Power on the PC and press DEL key to gain Bios screen
- Check Bios version in the first screen (M.I.T), something like this

- If your bios is already the last one just skip this step, otherwise put your bios file (not the .exe file, the .bin or .rom file!) in a FAT formatted usb pen drive and update with Gigabyte Flash Update utility (check in bios or in mobo's manual wich is the key to press at boot to do that)
- Press F7 to load Optimized Default Settings
- Set parameters as in these pictures

PAY ATTENTION! The following screenshot will show default Turbo Ratio values of i7 3770K. If you want to overclock change those values, and most important, keep the max Turbo Ratio value you set in mind (the first two are usually the highest), you'll need to set proper Power Management generating SSDT.aml (don't worry, we'll get there soon).

UPDATE #3: I've found that Internal CPU PLL Overvoltage can jeopardize wake from sleep function: If so, consider to set it as Disabled.

as exemple, here it is a little overclock (I'll leave that to 41 as max Turbo Ratio value, that means 4100 MHz as max CPU turbo frequency)
Side Note: still Internal CPU PLL Overvoltage should be set as Disabled to avoid wake from sleep issue (UPDATE #3)

The next screen shows the fans settings: since the case I choose has a lot of room (and good air flow), I set the fans as "Silent". Choose at your convenience

PAY ATTENTION! The next one will show you the right sets for discrete graphics. If you don't have a graphic card, set Init Display First as IGFX (PEG stands for discrete graphic). With discrete graphics don't set Internal Graphics as Enabled: it won't work.

- Set boot orders at your convenience, then press F10 key to save settings.
You're ready to boot into usb UniBeast install flash drive.

Step 2 - Mountain Lion Installation

- install Mountain Lion with UniBeast method as explained in Tonymac's guide. Note: if you have trouble booting, you'll probably have to type -x before hitting enter, otherwise you won't reach installation screen. Take your time, install process will take 15-20 minutes.
- Reboot from Unibeast and at Chimera screen choose your new OSX installed partition (probably still typing -x)
- Assuming you have all of the tools mentioned above, now we have to take care of DSDT. This is one of the most important steps of the installation process, many people don't care about DSDT (even with Gigabyte boards) and probably they are satisfied in that way (I was!) as their system works, but to optimize the components, make a hackintosh as close as possible to a real Mac and more vanilla as possible, DSDT is the key to do that. My advice is: learn how to edit dsdt, spend some time (or headache!), and new perspectives will open to you as hackintosher. This guide is not really about a DSDT editing, but in this section I will explain what and why I did it, in order to make anyone able to compile his own DSDT, not just trying to use others' one. So:

UPDATE #1
Thanks to the massive work of forum moderator PJALM, and the support of forum moderator SJ_Underwater, now only two patches are necessary to make this board fully functional. Simply follow these steps (the red ones are not necessary anymore, but basically are the same job that PJALM patch does).
- Download MaciASL from here, unzip it and open it. It automatically will open a "clean" DSDT. It's important to know that these patches can be applied just one time, so if you want re-patch dsdt you'll have to start from a clean dsdt.aml again. So my advice is: save a backup copy of this file just in case you need to re-patch it. To do that just go to MaciASL menu bar click on File/Save as, choose the directory where you want to keep your backup clean dsdt, select Disassembled ASL file as File Format and name it "clean dsdt".
- in Menu bar open MaciASL\Preferences and select Sources in Preferences window
- set iASL as ACPI 5.0 as in the following picture

- select sources icon, click on "+" to add Name and URL of the patches that you need: in my case they are

PJALM Gigabyte ---> http://maciasl.sourceforge.net/pjalm/gigabyte/
PJALM Graphics ---> http://maciasl.sourceforge.net/pjalm/graphics/

- Close completely MaciASL and re-open it: again a clean DSDT will appear as before, click on Patch command: now in the left side of the Patch window you should see all the patches we've just added like this

- Under PJALM Gigabyte choose your motherboard's patch, click on Apply, then Close. Now click on Compile command: no Errors, Warnings nor Remarks should appear, but some Warnings may stay: they won't affect your installation; the mandatory thing is NOT TO HAVE ERRORS when compiling a DSDT! Go on
- Re-open patch windows and under PJALM Graphics select

Generic Discrete Graphics (AMD/nVidia) to enable HDMI Audio if you have a discrete graphic card or
Intel HD4000 to enable HDMI Audio if you have ONLY Intel HD 4000 onboard graphic)

- Apply your right patch and check compile: now you should have 0 Errors, 0 Warnings, 0 Remarks, XX Optimizations.

The next red steps are not necessary anymore, but I leave them here 'cause they're still valuable infos

- Apply USB Multiplex from PJALM Intel7 patch, this method is based on Forum member Mieze's work
PAY ATTENTION! As mrengles stated, this method will work ONLY with these System Definition:

Macmini5,1 (Sandy Bridge)
Macpro3,1 (Sandy Bridge)
Any Ivy Bridge SysDef

So mind what SysDef you choose, based on your hardware, 'cause it will influence your Power Management optimization (see the step down here, below MultiBeast screenshot).

/END UPDATE #1

- Compile DSDT from MaciASL (0 Errors, 0 Warnings, 0 Remarks, XX Optimizations) and save it as DSDT.aml (add extension manually) on desktop (This time, choose ACPI Machine Language Binary File Format).

Your DSDT is finally ready to be used for installation :thumbup:

- Put your cool DSDT.aml on desktop and run latest MultiBeast. As for me, I ran this configuration

- Run Chameleon Wizard to change System Definitions in smbios.plist: select SMBios from menu icons, select Edit command in the top right corner, select "Mac Mini (6,2) - Core i7 (Ivy Bridge)" in the first options in top left corner and Save. Don't worry if you don't have an i7 CPU, what really matters is the Ivy Bridge System Definition: it will be necessary to reach a good Power Management (of course if you have a Ivy Bridge CPU). System Definition MacMini 6,2 is the best choice at the moment to optimize Ivy Bridge Power Management
- Go to System\Extra and open org.chameleon.Boot.plist with Text Edit
- Add this

Code:

<key>Graphics Mode</key>
<string>1920x1080x32</string>

in order to make Chimera boot with proper resolution. Keep in mind that you have to use your display resolution, normally full hd monitors reach 1920x1080 (leave x32 as it is), do your research
- Stay in org.chameleon.Boot.plist and change darkwake value into 10 in order to make auto sleep working
- Remember - if you have an nVidia card (like me) - to add

Code:

<key>GraphicsEnabler</key>
<string>No</string>

to org.chameleon.Boot.plist
- Install Trim Enabler (see Tools section above)
- Repair permission with Disk utility, rebuild cache with Kext Wizard and Reboot

Now the system will be able to boot without UniBeast flash drive. We need to optimize it taking care of Ivy Bridge Power Management.
Jump to the next post.

giacomoleopardo · Apr 27, 2013

Step 3 - Post Installation
Time to load Ivy Bridge Power Management.
A great thread where I learn a lot of stuff about Power Management (PM) is this, if you want to learn, give it a shot!
Now we need to get CPU PM (generating SSDT.aml) and GPU PM (editing AppleGraphicsPowerManagement.kext).

- Download SSDT generation script from here (attached in post n. 1 of that thread) and unzip it
- In Download Folder click just one time on unzipped ssdtPRGen and you'll see ssdtPRGen.command and ssdtPRGen.sh (alias) in your User Folder.
- Now it is necessary to know which Turbo Ratio 1 & 2 value you set in UEFI Bios (step 1 of this guide): if you left stock values, click a second time on ssdtPRGen and it will automatically generate the script for your system with stock values of your CPU. If you changed those cpu multipliers (Core Ratio Limit) like me then open terminal and type

Code:

~/ssdtPRGen.sh/ 4100 70

where 4100 is my 1 & 2 Turbo ratio values (41 - see bios screenshot #4) multiplied x 100, and 70 is the max TDP (in Watt) I want my CPU to use. It's important to know that every cpu has its TDP, my 3770K has 77 Watts as you can see here. ssdtPRGen automatically give 77 as TDP value, but if you insert another value in the command string as I did, SSDT will be generated upon your custom TDP. Why this? As PikeRAlpha stated, Ivy Bridge Power Management optimization allows CPU to run with less TDP keeping pretty much the same performance level with lower temperature. So why not?

Summarizing: you'll need Turbo Ratio and TDP values.
- So type your custom values or click for the second time on ssdtPRGen command and in terminal you'll see something like this

Code:

Last login: Fri Apr 19 11:39:16 on console
localhost:~ daniele$ ~/ssdtPRGen.sh/ 4100 70























sdtPRGen.sh v6.1 Copyright (c) 2013 by Pike R. Alpha
----------------------------------------------------------------
Processor Declaration(s) Found in DSDT (ACPI 1.0 compliant)
Generating ssdt_pr.dsl for a Macmini6,2 [Mac-F65AE981FFA204ED]
Ivy Bridge Core i7-3770K processor [0x0701] setup
With a maximum TDP of 77 Watt, as specified by Intel
Override value: Max Turbo Frequency, now using: 4100 MHz!
Override value: Max TDP, now using: 70 Watt!
Number logical CPU's: 8 (Core Frequency: 3500 MHz)
Number of Turbo States: 6 (3600-4100 MHz)
Number of P-States: 26 (1600-4100 MHz)
Injected C-States for CPU0 (C1,C3,C6)
Injected C-States for CPU1 (C1,C2,C3)
Warning: Model identifier [Macmini6,2] is missing from: /S*/L*/CoreServices/PlatformSupport.plist

IASL not found. Creating target directory... 
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:
Downloading iasl...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1132k  100 1132k    0     0   348k      0  0:00:03  0:00:03 --:--:--  412k
Done.

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20130117-64 [Jan 19 2013]
Copyright (c) 2000 - 2013 Intel Corporation

ASL Input:     /Users/daniele/Desktop/ssdt_pr.dsl - 262 lines, 8502 bytes, 56 keywords
AML Output:    /Users/daniele/Desktop/ssdt_pr.aml - 1637 bytes, 27 named objects, 29 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

And it will ask you if you want to copy /Users/Your name/Desktop/ssdt_pr.aml to /Extra/ssdt.aml? (y/n)
Type y (for yes), type your password and in your System\Extra folder you'll find the right ssdt.aml file to get power management for your cpu.

UPDATE #2
The last (at this time) release of ssdtPRGen will put ssdt_pr.aml in /Extra folder. If you're using Chimera bootloader, simply go to /Extra and rename the file ssdt.aml. PikeRAlpha explained to me this: he did this to make ssdtPRGen more compatible to other bootloaders such Revoboot or Clover.
END UPDATE #2

- Open with Text Edit org.chameleon.Boot.plist in System\Extra folder and add this

Code:

<key>DropSSDT</key>
<string>Yes</string>

- also remove

Code:

<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>

or simply turn both string lines into

Code:

<string>No</string>

- Reboot system and open IORegistryExplorer (see Tools section - post n. 1 of this thread) and you should find X86PlatformPlugin like this

because for Ivy Bridge processors, native power management is enabled by the X86PlatformPlugin.kext (injected by SSDT)
- To check your Speed Step, go to this thread and follow the instruction provided. You'll need to install AppleIntelCPUPowerManagementInfo.kext. Here are the SpeedSteps I got here

Code:

Apr 19 12:47:51 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 35 ]
Apr 19 12:47:53 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 35 41 ]
Apr 19 12:47:58 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 22 35 41 ]
Apr 19 12:47:58 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 22 35 39 41 ]
Apr 19 12:48:01 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 22 35 39 40 41 ]
Apr 19 12:48:05 localhost kernel[0]: AICPUPMI: CPU P-States [ 16 22 29 35 39 40 41 ]

Once achieved CPU Ivy Bridge Power Management, let's optimize GPU Ivy Bridge Power Management.
As Toleda stated, AppleGraphicsPowerManagement.kext is used for product specific graphics power management. So here it is:

- If you have only onboard Intel HD 4000 integrated graphics, follow the next steps
- copy AppleGraphicsPowerManagement.kext from S/L/E to the Desktop, then you need to edit AppleGraphicsPowerManagement.kext/Contents/Info.plist. I recommend not to use text edit, but a plist editor
- If you have (like me) SysDef Macmini 6,2, find in Info.plist "Mac-F65AE981FFA204ED" following this path Information Property List/IOKitPersonalities/AGPM/Machines (as that's Board-ID for Macmini6,2) and change from this

to this

- If you have ONLY HD4000 onboard graphics save the file, delete AppleGraphicsPowerManagement.kext from S/L/E, run KextBeast (with the edited AppleGraphicsPowerManagement.kext placed on desktop), repair permission, rebuilt cache and reboot.
- Check IOReg/[email protected]/AGPM, and you'll find min and max values just inserted (in AppleGraphicsPowerManagement.kext/Contents/Info.plist we added decimal - 18 and 0 - and in IOReg we find hexadecimal - 0x12 and 0x0)
NOTE: in my IOReg AGPM shows max value=0x10 and min value=0x0 because this screenshot was taken from my other hack with i7 3770S. Now, hex 0x10 correspond to dec 16 (not 18 as inserted in plist, I don't know why it happens, maybe CPU i7 3770S doesn't reach hex 12, that is a mistery to me!)
Anyway, with 3770k you should see proper 0x12 hex value.

- If you have another SysDef (e.g. imac13 or macbookpro9/10) you'll have to edit AppleGraphicsPowerManagement.kext/Contents/Info.plist finding the right board ID.

For those like me that have a graphic card, other changes to optimize AppleGraphicsPowerManagement.kext are needed.

- First of all copy AppleGraphicsPowerManagement.kext from System/Library/Extensions to desktop.
- In my case, I need to be aware of my graphic card. I have an nVidia GTX 650 ti, vendor id is 10de, and device id is 11c6 (these values are available in About this Mac\More info\System report\Graphics). Since there is no real Mac with this card (yet?), we don't actually know what is the perfectly right Power Management for GTX 650 ti. So the best match I found, testing different configurations, is iMac 13,2 config with GTX 660M (vendor id 10de and device id 0fe0), and its board id in AGPM.kext\Contents\Info.plist is Mac-FC02E91DDD3FA6A4
As you can see in the next screenshot, I copied GFX0 and IGPU from Mac-FC02E91DDD3FA6A4 (iMac 13,2) to Mac-F65AE981FFA204ED (MacMini 6,2) replacing what was there, plus I created Vendor10deDevice11c6 copying the same values that I found in Vendor10deDevice0fe0, so my MacMini has the same Graphic Power Management as iMac 13,2.

As you probably can see, I added LogControl and I put "1" as value: I needed "1" to check in Console what was happening on AGPM, when you finish testing, change that value to "0".
This is my result

Code:

Apr 19 13:55:30 localhost kernel[0]: AGPM: updateGPUHwPstate(): state = 10. Calling fFB->setAggressiveness()...
Apr 19 13:55:30 localhost kernel[0]: AGPM: GPU = GFX0 AGPM P state changes to 0 (mapped to VP state 10) from 0, ControlID = 16. SW occupancy updated.
Apr 19 13:55:30 localhost kernel[0]: AGPM: updateGPUHwPstate(10, 0): fHwPstate = 0 fFB = 0xffffff80202e0800

Don't ask me what that means! I have no idea! :lol:

- So when you finish to edit AppleGraphicsPowerManagement.kext\Contents\Info.plist, save it, delete the AppleGraphicsPowerManagement.kext from System/Library/Extensions, run KextBeast (with the edited AppleGraphicsPowerManagement.kext placed on desktop), then repair permissions with Disk Utility, rebuild cache with Kext Wizard and reboot.
My knowledge about Graphic Power Management ends here, for more info check toleda's thread!
What's next?
If Auto Sleep doesn't work follow this steps:
- open terminal and type "pmset -g assertions" (no quotes)
- if you see something like that

Code:

Assertion status system-wide:
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
PreventUserIdleSystemSleep 0
ExternalMedia 0
DisableLowPowerBatteryWarnings 0
UserIsActive 0
ApplePushServiceTask 0
BackgroundTask 1

lmediamounted" 
pid 192(helpd): [0x0000000c00000133] 00:03:06 BackgroundTask named: "com.apple.helpd.sdmbuilding"

you just have to type "launchctl unload -w /System/Library/LaunchAgents/com.apple.helpd.plist".
- type again "pmset -g assertions", and when all numbers are 0 you go on
- Reboot.
That worked for me.

UPDATE #4 --- Update to Mountain Lion 10.8.4 from Combo Update

If you have installed from Mountain Lion 10.8.4 UniBeast flash drive, skip this update, of course!

Download Combo Update OSX Mountain Lion 10.8.4
make a full backup of your system with Carbon Copy Cloner on a temporary partition
run combo update
reboot
run multibeast with ONLY audio option (Drivers & Bootloaders/Drivers/Audio/Realtek ALC8xx/With DSDT/ALC892)
repair permission with Disk Utility, rebuild cache with Kext Wizard
active trim enabler from Application folder
reboot
delete your temporary partition if everything has gone well

SIDE NOTE 1: if you have ONLY integrated graphics HD 4000, no need to edit AppleGraphicsPowerManagement.kext, it works as it is.
SIDE NOTE 2: if you have an nVidia card, my tip is NOT TO UPDATE until a new release of Cuda Drivers for Mac will be out (at this time Cuda Drivers are not compatible with 10.8.4) ---> Cuda Drivers updated for Mountain Lion 10.8.4. BTW, native AppleGraphicsPowerManagement.kext seems to work without editing for AGPM
SIDE NOTE 3: the whole installation process can be done with Mountain Lion 10.8.4 Install App (UniBeast method) fresh installation either!
END UPDATE #4

UPDATE #5 --- Fixed Safari/Firefox crashes on Flash Player plug-in YouTube videos, mostly with discrete card

For some reason, YouTube (and others) videos make the system crash, showing flickering images just before the issue, no video at all. I've noticed that happens with discrete card only (most nVidia, can't really say for ATI/AMD), while with onboard HD4000 that doesn't happen. Here's the fix:

Choose a web video that gives you this issue (not all videos do that, I believe just tose ones that require Flash Player plug-in)
Don't play it, otherwise the system will probably crash (but you already know that, don't you?)
Right click on the video and choose settings
A window like this will appear
Simply uncheck Enable Hardware Acceleration (my pic is in italian, I guess you'll find it in your system language)
Close and re-open the browser (Safari/Firefox) and check: hopefully that will do the trick.

Done!
Thanks to this post, zuzudom and my friend PL for testing
END UPDATE #5

Well, that's pretty much it, Now you should have a optimized Ivy Bridge Hackintosh with the minimum amount of modified kext. Basically DSDT, SSDT, org.chameleon.Boot.plist and smbios.plist are not affected by the system update, but keep a backup copy of your Extra folder, just in case

Updates, Geek tests and Timelapse posted down here in post #3

Enjoy your fully working Hack Mini! :clap:

Credits

Tonymac for Unibeast method and MultiBeast post installation
MacMan for UniBeast, MultiBeast and Chimera
samisnake for auto sleep info
toleda for HDMI audio here and here
toleda for SSDT support
toleda for MaciASL Patches
flytiger for auto sleep info
PikeRAlpha and Jeroen for SSDT script
PikeRAlpha for AppleIntelCPUPowerManagementInfo.kext
SJ_UnderWater for the great MaciASL Open Beta tool
PJALM for MaciASL Patches
Mieze for great support and outstanding work on Intel® USB 3.0 fix (I was actually pointed by mrengles, whom I thank very much either)
Groths for Trim Enabler
Zenith432 and RehabMan for GenericUSBXHCI.kext

giacomoleopardo · Apr 27, 2013

Updates

May, 31st 2013 - UPDATE #1 - Gathered dsdt patches into PJALM Gigabyte patch
May, 31st 2013 - UPDATE #2 - Added instruction to rename ssdt_pr.aml into ssdt.aml in /Extra folder for Chimera-Chameleon users
June, 3rd 2013 - UPDATE #3 - Added info to disable Internal CPU PLL Overvoltage in bios screenshot #3 and #4
June, 6th 2013 - UPDATE #4 - Explained how to safely update the system via Mountain Lion 10.8.4 Combo Update
June, 15th 2013 - UPDATE #5 - Fixed Safari/Firefox crashes on Flash Player plug-in YouTube videos

A little Timelapse. enjoy the great Miles Davis' Quintet in "Seven steps to Heaven"!

[video=youtube;3bD04PYVjqM]http://www.youtube.com/watch?v=3bD04PYVjqM[/video]

monty007 · Apr 28, 2013

Great build and love the time lapse vid!!

giacomoleopardo · Apr 29, 2013

Thanks, man! :headbang:

jmpa · Apr 29, 2013

Great build and description!

killrbeez · Apr 29, 2013

Thanks for the info. I have almost the exact same parts (just picked them up yesterday.) This will be my go-to guide for building my first hackintosh!

giacomoleopardo · Apr 29, 2013

Thanks guys :thumbup:

@killrbeez: ask for anything you need! Good Hack!
G.

tstones · Apr 29, 2013

First of all a big thanks for the three detailed guides and impressive builds all of them great machines! I love mini powerfull builds! I have one question, what mini itx is your favorite, Zotac, Gigabyte or Asrock?

giacomoleopardo · Apr 29, 2013

tstones said:
First of all a big thanks for the three detailed guides and impressive builds all of them great machines! I love mini powerfull builds! I have one question, what mini itx is your favorite, Zotac, Gigabyte or Asrock?

Well, that's a good question, tstones!
All of them are really good mobos, and here are my considerations.
Zotac:
Plus - msata connectivity, everythings works properly, included full sleep, autosleep, WOL, easy overclock etc.
Minus - a little annoying bios flash utility and some patches in dsdt (that are not required in ASRock and Gigabyte) such as network card atheros AR 9285 (note that in ASRock anf Gigabyte wifi card in not supported, so I changed with a working OOB Atheros AR9280). But no big deal about that. I found one thing really disappointing: miniDisplayPort does not support 27" Apple Cinema Display! Furthermore it was necessary edit AppleIntelFramebufferCapri.kext to have the right mappature of physical connectors as I explained here as they were recognized as two dp and one hdmi (instead of two hdmi and one dp). It has no DVI port, and that could be a limitation for more than somebody.

Gigabyte
Plus - no bios patching, minimum dsdt edit required
Minus - no msata, after wake from sleep - no matter what - any usb device plugged seems to be disconnected (and auto reconnected). That is really disappointing to me!

ASRock
Plus - msata connectivity, easy bios flash utility, less dsdt edit than Zotac, no issues on usb after wake from sleep (for Intel controller, not ASMedia)
Minus - none except flashig patched bios (2 minutes, no big deal).

Conclusion: ASRock is my n.1, followed by Zotac (more features than Gigabyte) and then Gigabyte.
But as I stated before: they all are great mobos!

Search

Giacomoleopardo's Gigabyte GA-Z77N-WiFi Build for DB

giacomoleopardo

giacomoleopardo

giacomoleopardo

monty007

giacomoleopardo

jmpa

killrbeez

giacomoleopardo

tstones

giacomoleopardo

Forum

Guides

Downloads