Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
meklort

New OS X compatible motherboard -> QUO

3,618 posts in this topic

Recommended Posts

It's Phobos!' method should work. In my experience the jumper method has been hit or miss on a variety of boards with a recovery BIOS.

 

It sounds like you may have had a bad flash. Give the aforementioned method a few tries. After the stock firmware is restored. Re-flash with 820M, await the double restart, then enter the BIOS and select "Restore Optimized Defaults".

Share this post


Link to post
Share on other sites

King, come on, please get back down to reality .. if the BIOS update did not overwrite my settings, I WOULD NOT NEED TO HAVE TO GO BACK INTO THE BIOS !!

And yes, it needs to be accsessible ON FIRST TRY, not having to reboot a couple of time .. but thanks for at least acknowledging the bugs ..

This BIOS has been tuned and tested before release, you do not need to make modifications to it, however, as I said before you are free to do whatever you like, with your 18 years of experience you know what you  doing and results will come in no time(and they did(first brick...)

Your settings for what?(LOL)

 

 

why don't they correct that on their homepage? For how long has it not been ALT? They just changed on that page from 816 to 820, but were not able to change a wrong instructions? Am I really dealing with professionals? More and more I need to say: unfortunately not ..

Yeah a bunch of unpro who lose time so that you and many others can be unhappy, Why you are not using tonycrap soft then? isnt that on your level of knowledge?

 

.. when I look at the QUO web-page with dead sections and links ....

If you have something with QUO go complain there not here.

 

aha, getting closer ..

 

At some point when booted into OS X I wanted to see if the Startup Volume sys pane works ..

 

I guess that NVRAM entry might be blocking the OZ Boot Menu.

 

So I ran

dmpstore -d boot-args

resulting msg: something like "entry boot-args not found"

 

so I ran

dmpstore -d

Now the QUO does not boot anymore. It starts, black screen, restarts.

 

Every 8th or so restart I see some screen w/ a grey Q + a mouse pointer, or a line in the bottom offering me F12, DEL, END for Q-Flash, but before I can tap any key --> reboot

 

Obviously not even the double BIOS feature is implemented correctly ..

 

buggy buggy buggy buggy ..

 

So what now? CMOS (or whatever that's now called in UEFIverse) reset?

Proof of "you have no idea of what you are doing" and again is the board fault or developers fault for you killing your BIOS....

 

For now on you are on my ignore list, so do not bother to reply.

Share this post


Link to post
Share on other sites

Considering what some of us know about this board, here are Gigabyte's instructions for invoking the backup BIOS.

 

1. Shut off the power supply using the switch on the back of the PSU, wait 10-15 seconds.

2. Press and hold the case Power On swtich, then while still holding turn on the power supply from the switch on the rear.

3. Still holding the case power on switch, the board will start, once it does release the case power on switch and shut off the power supply via the switch on the read of the unit. (Do the latter two parts as quickly as you can once the board starts)

4. The board will shut down.

5. Turn the power supply back on using the switch on the rear of the unit.

6. Turn on the motherboard by pressing the case power on button.

:thumbsup_anim:

 

In the meantime I had found these instrus metacrawling for "Gigabyte z77 motherboard dual bios recovery" at http://www.tomshardware.com/forum/316115-30-gigabyte-bios-hell, and yes, they do work.

 

Same moment I was back up, QUO support sent me the same instrus via email - THANK YOU!

 

GREAT! I sure don't enjoy being doubtful.

 

I'll see in a moment if now also the OZ Bootloader finally shows up here ..

kudos all the way across the Pacific to Rochester, NY ..

 

now honestly .. is that maybe something worth including 1. into e_Z77MX-QUO-AOS_1001.pdf and 2. onto the webpage? No? That would be too little hackintosh and too much lamers mainstream?

@ THe KiNG: you really don't get it, and sure did either not read my posts completely, or don't understand them, or do not WANT to understand them ..

 

So here a consolidated digest especially for you:

 

If the OZ Bootloader worked, I would not need F12 ..

 

If F12 always worked, I would not need to go into the BIOS to increase the timeframe to be able to ACCESS either, F12 and BIOS ..

 

If the BIOS did automatically detect/ clock/ time my RAM correctly, I WOULD NOT NEED TO GO INTO THE BIOS, either (I have to turn on XMP so it runs at the desired 1600 vs. 1300MHz. I have used the SAME RAM IN OTHER BOARDS, which DID clock it correctly right away @ 1600/ 8 8 8 24, vs. the QUO @ 1300 9 9 9 27) ..

 

If the Mavericks M820 had not also overwritten my SETTINGS (which I dare say it shouldn't after having applied HUNDREDS of BIOS updates in my life, and it's an exception that they also overwrite the CMOS or NVRAM), I WOULD NOT HAVE NEEDED TO GO BACK INTO THE BIOS to again correct the wrong memory auto-settings and increase the god-**** time-frame ..

 

Does rationaity finally make it through your stubborn "I don't wanna see therefore it's not true and you out there are full of BS" mentality?

 

My friend, I LOVE and HONOR and MORE THAN RESPECT your work, intelligence, ever-presence etc. in this community - so let my advice to you be: TAKE SOME TIME OFF! Jump in the car/ train/ airplance, and merge back into the country-side for a while - it looks as if a vacation could not hurt ..

Apart from that: do you REALLY want to maintain your remark that the sticky BIOS and F12 access is kind of a feature to keep dumbheads out of the BIOS? Really, king ...?

.. Now back to the technical aspects which are priority ..

 

just as information: after the Dual BIOS restore, the stock F2N BIOS has been reapplied, which I guess is how it's supped to be. As expected, not even Win 8.1 (installed with 816M BIOS loaded) will boot.

 

So now I'll re-apply the 820M BIOS, and report back if the OZ Boot Menu finally displays here. I WANT TO SEE THIS GHOSTLY BEING WITH MY VERY OWN EYES :)!

After 820M BIOS flash:

 

The main BIOS is corrupt. Restoring BIOS from dual BIOS backup

that processes and finishes, then back into the BIOS, again back to F2N ..

 

--> Q-Flash, 820M once more .. --> finally, back to 820M on BIOS 1, OS X boots via H3A ..

AHA!! Finally, PARTIAL success ..

 

On my ACD via DVI, same as before: black screen ..

 

When I plug in my HDMI monitor, same thing, black screen.

 

But now the NEXT step which I had done before suddenly produces an image (however very distorted and stretched far accross the screen) of volumes and their labels underneath, not really readable (extremely obfuscated).

 

FYI: usually both of these displays are plugged into the SAPPHIRE Radeon HD 6670 of my Optiplex which boots via Chameleon GUI, being displayed properly on BOTH displays ..

 

So next I boot w/ HDMI only --> same as on DVI display = black screen ..

 

I pull the HDMI plug, replug .. now I see only ONE big HD volume icon in correct proportions, with the volume label underneath cut off to the left and to the right ..

 

buggy buggy buggy buggy ..

 

Too bad the crowned one has already forbidden me to go into the BIOS because a) it's so well-balanced and B) I'm too dumb to handle it anyway.. otherwise I would dare to ask if maybe there is a need to toggle some iGPU related settings (Legacy/ UEFI) etc, as it has been necessary for many others before [....]

 

I am getting tired of this project which is beyond the slightest shadow of a doubt still rather in an alpha state .. differentiating between HermitCrab Kitchen and the QUO AOS mobo itself which I think is AWESOME, esp. for its price ..

 

I can only encourage the OZ team to do their due homework by looking at the Chameleon code for the GUI .. understand it, then implement it into the OZ bootloader and into the H3A fw

 

I'll also post my findings into the Ozmosis bootloader posting and email it to QUO (even though the channels are shady, and I guess are supposed to be that way).

 

IN THE MEANTIME I WILL EXTRACT THE DSDT AND USE IT WITH ONE OF THE BOOTLOADERS THAT ACTUALLY OFFER A FULLY WORKING GUI = CHAMELEON OR CLOVER ..

 

see attachment, for those that want to spare themselves from being alpha-testers for pre-release enthusiasts and rather opt to go with the method that DOES work, backed up by a huge team of devs, vs. a small team ..

 

Thank you,

Bugs

PS: unless there is a way to default the OZ boot menu to load verbose right after BIOS post?

Z77MXQUOAOS.H3A.820M.DSDT.ZIP

Share this post


Link to post
Share on other sites

Its possible that you have to set the CSM boot mode to legacy only in the BIOS. See if that works. If not try UEFI only. Legacy only has fixed it on most of the high rez monitors i have had issues with.

g\

there is no such setting combo in the BIOS ..

 

BIOS/ BIOS Features:

CSM support: ENABLED/ DISABLED

Display Boot Option ROM Control: Legacy First/ Legacy Only/ UEFI First/ UEFI Only/ Disabled

 

Even w/ CSM support DISabled, Display Boot Option ROM Control can be set to Legacy First or Only ..

 

The Compatibility Support Module does not seem to influence if the the OZ boot menu is displayed or not from what I see; however toggling CSM to DISabled corrects the resolution or/and proportions so the Icon is actually SCALED correctly on my 30" ACD DVI, that's all.

 

Display Boot Option ROM Control: Legacy DOES display PARTS of the OZ boot menu on either, DVI and HDMI display, here. Only the OS X Icon - the Windows drive not visible. Booted last time via F12 right before the 820M BIOS Update ...

 

Bye Bye OZ .. gonna grant you some time to go back to wizardry school and learn some basics from good ole teacher Chameleon ..

Share this post


Link to post
Share on other sites

 

Bye Bye OZ .. gonna grant you some time to go back to wizardry school and learn some basics from good ole teacher Chameleon ..

 

Good, and please stop spamming this thread with useless "information"

g\

Share this post


Link to post
Share on other sites

Good, and please stop spamming this thread with useless "information"

g\

how informative a sentence you just added to this thread .. FYI, I consider your subjective remark useless spamming - go figure ..

Share this post


Link to post
Share on other sites

@BugsB Could it be that your keyboard is faulty? I have no such problems entering either Setup (DEL) or the Boot Menu (F12). And Setup Prompt Timeout is set to 0 here. Also Startup Disk PrefPane works just fine here.

Share this post


Link to post
Share on other sites

Hi modbin. Thanks for following my plight. I was experiencing this with ANY keyboard I tried ..

 

It turns out that after all I did (CMOS reset/ CMOS Battery/ restore BIOS/ re-apply 820M) the stick/ stall bug is GONE :) Hopefully the huge journey was worth it ..

 

I am currently reinstalling Windows 8.1 in UEFI mode (from my FAT32 MBR/ UEFI combo USB Flash Drive via Rufus) which stopped booting after the 820M BIOS update for Mavericks compatibility. Luckily I had not installed anything into it yet .. and this will be the last OZ BIOS I'll install until it has left alpha state ..

 

Once Win 8.1 is fully running I'll see one more time if 1. the OZ boot menu works and 2. both OS entries are displayed. Last chance for OZ here ..

 

Next then is Mavericks, if need be w/ Chameleon + extracted 820M DSDT ..

 

Thanks again for staying rational and being neutral.

Share this post


Link to post
Share on other sites

@bugsb doing dmpstore -d on most uefi motherboard's will erase vital variables requiring you to reflash the board.

 

you say your an IT guy ... facts don't seem to be proving that.


@all , regarding Ozmosis GUI.

 

With the advent of Fast Boot modes, which can cause usb devices to not function until the OS is reached, ie Keyboard / Mouse

 

the concept of configuration and setting boot disks is shifting towards doing these in the OS.

 

so really the oz gui is not really useful in a modern world.

 

and it really only duplicates the function of F12 

Share this post


Link to post
Share on other sites

@bugsb doing dmpstore -d on most uefi motherboard's will erase vital variables requiring you to reflash the board.

 

you say your an IT guy ... facts don't seem to be proving that.

oh really .. accdg. to your dubious definition, knowledge of an extremely specific command defines if one is an IT guy, or not .. go ask 10 people out here who also consider themselves IT guys, if a) they have EVER heard of dmpstore -d, and B) know what such command means, or does ..

 

I did not add any * wildcard and would've expected a list of what can be deleted, or at the very least a warning "This will delete all entries - are you sure (y/n)?" Whoever was/ is responsible for this UEFI shell code is - irresponsible ..

 

c'mon, don't give me bs, oh d, you can do better than that ..

 

re. graphical boot loader: let's say I set this comp up for somebody else - a user, a NON techy person that needs to run both, Windows and OS X and can't always run Win apps in Parallels or Fusion.. how does a regular user feel about the F12 boot menu?

 

Chameleon and Clover work mighty fine on all sorts of hacks. I hope the OZ coders (Ozmosis & HermitCrab?) manage to incorporate more of the Chameleon GUI features into theirs ..

Share this post


Link to post
Share on other sites

Hey BugsB - I see you are using an apple display. Is your keyboard plugged into the display, or directly into a port on the mobo? I experienced similar issues until I plugged the keyboard directly. 

Share this post


Link to post
Share on other sites

Hopefully I am speaking for the silent majority...

Thanks Lanceomni for the instructions I was able to make a bootable USB copy of 10.9. However it looks like upgrading the BIOS to 820m did the trick. After updating the BIOS I booted back into 10.8.5 and clicked on the auto 10.9 installer just to see what difference 820m would make and it worked like a charm! The auto installer went through the full installation with 2 reboots and loaded 10.9 without a hitch and not require me to resetup my Apple account or reload applications.  I applied the King's 10.9 audio patch and it works with no audio distortion. The sleep function works with the hard drives shutting down. I still need to patch the system serial for Imessage.  The only minor issues are the same ones I have always had with 10.8.4, 10.8.5, the Symbios reports the system as a "MAC Pro (early 2008)" and the TB Hardware is not detected in the system report (have not tested functionality). So overall I could not be more pleased with the effortless upgrade to 10.9. Thanks to Hermit Crab Labs, the King and QUO for developing a superior solution.

Share this post


Link to post
Share on other sites

 

I did not add any * wildcard and would've expected a list of what can be deleted, or at the very least a warning "This will delete all entries - are you sure (y/n)?" Whoever was/ is responsible for this UEFI shell code is - irresponsible ..

 

 that would be intel.

Chameleon and Clover work mighty fine on all sorts of hacks. I hope the OZ coders (Ozmosis & HermitCrab?) manage to incorporate more of the Chameleon GUI features into theirs ..

don't hold out i explained the reasoning already,

Share this post


Link to post
Share on other sites

"Methods used for launching UEFI shell depend on the manufacturer and model of the system motherboard"

 

...so, are we to blame the mother(intel) for the actions of the child(manufacturer)? ...poor mommy :smoke:

Share this post


Link to post
Share on other sites

Hey BugsB - I see you are using an apple display. Is your keyboard plugged into the display, or directly into a port on the mobo? I experienced similar issues until I plugged the keyboard directly. 

directly. I don't like USB hubs in general - too many probs. Thanks.

"Methods used for launching UEFI shell depend on the manufacturer and model of the system motherboard"

 

...so, are we to blame the mother(intel) for the actions of the child(manufacturer)? ...poor mommy :smoke:

as to be expected, obviously nobody's perfect - not even Intel .. there's always room for improvement. Otherwise none of us would post into this forum, any forum, walk this planet.

Share this post


Link to post
Share on other sites

Just want to say, HD 7870 card is working great in my machine without any modification.

I'm using the HDMI output for video and audio.

Set in bios "Init Display" and "Integrated Graphics" to auto.

 

Have:

Z77MX-QUO-AOS with 820M

i7-3770 CPU

Mac OSX 10.9

2x8GB Crucial Ballistix

XFX HD 7870 Black Edition

 

Only the virtualization setting in bios is not working.

Setting it to enabled, system stays loading with the gray screen.

I think, this issue is already known.

Share this post


Link to post
Share on other sites
Only the virtualization setting in bios is not working.

Setting it to enabled, system stays loading with the gray screen.

I think, this issue is already known.

That is known bug, but to be clear only VT-d cannot be enabled, you can enable VT-x and use virtualization software!

Share this post


Link to post
Share on other sites
Hello,

I have the following setup:

 

Z77MX QUO AOS with 816M


i7-3770K


32GB Corsair Dominator


Samsung 840Pro 512GB


EVGA GeForce GTX Titan


OS X 10.9


 


All is well.


1. But when I install the new firmware (820M), the first Thunderbolt port does not work. With the version "816M" both Thunderbolt ports are ok.


2. Is it possible to overclock the processor better? In the BIOS, everything is to be grayed out.


Share this post


Link to post
Share on other sites

akindy,

 

I have not tested with Windows 7; however, I had no issues with an UEFI install of Windows 8 and the GTX760 listed in my signature. Im currently connected via a DVI-D Dual Link.

 

Is you do a UEFI install of Windows 7?

 

I just did a clean install of Windows 8, confirmed in msinfo32 that it's a UEFI install, but I'm still getting a conflict between the integrated graphics and my GTX 760:

 

 

I/O Port 0x0000E000-0x0000EFFF Xeon® processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151

I/O Port 0x0000E000-0x0000EFFF NVIDIA GeForce GTX 760
 
Lanceomni, which version of the BIOS are you running? The latest I found was 816M, but I've noticed some people referring to the 820M version. I'll try that now, but I'm not super hopeful that it'll get my graphics card working in Windows. Has anyone run into this issue?

Share this post


Link to post
Share on other sites

When I hit Del to go into the BIOS, sometimes after a few seconds, the BIOS top bar starts flashing blue and red and all the values for the options disappear. I've reflashed the BIOS going back to 801M and then back to 816M and 820M and it appears to happen with the later BIOSes. Is anyone else getting this problem?

Share this post


Link to post
Share on other sites

Thanks @apfel_nico, just downloaded and updated to 820M.

 

Still having the issue with my GTX 760. Disabling the HD4000 in BIOS just causes the computer to boot to Windows, then no video after the 'loading' screen. Same resource conflict listed in msinfo32.

 

Windows 8 will boot with my DVI cable connected to the GTX 760, show the loading screen, then go to a black screen. Mac OS X loads no problem with the DVI cable connected to the GPU.

 

Edit: I guess what I'm really looking for is a more comprehensive source of information than this forum. There's a lot of good info in here, but very little of it seems to apply to my situation.

Edit 2: From what I can tell, my Mac install will boot and output video with my GTX760 connected, but it's not actually using it for processing (relatively low Geekbench score)

 

Follow-up: Is there a list graphics cards that Ozmosis is built to work with? I'd be up for returning the GTX 760 in favor of something that is supported.

Share this post


Link to post
Share on other sites

Hello,

 

I have updated my BIOS from M801 to M820 successful. Then I installed Mavericks from the appstore without any issues. I have only to fix iMessage (audio works fine without distortion) and set my BaseBoardSerial again to 17 letters.

But I have one problem with my sleep mode. I'm using a Dell 2408 WFP with HDMI cable from amazon. If I wake up my system, the monitor remains black but if I switch the source to DVI and then back to HDMI I get the screen and everything is okay. This works under Mountain Lion without any problems before. Is there any solution for this problem?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×