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,621 posts in this topic

Recommended Posts

joe75,

I'm still trying to figure out why I even care about this EFI BS :P The OZ BIOS clutter up the boot list with all kinds of entries for my single linux drive(which contains about 8 different partitions of various *nixes) so it looks like it adds an EFI entry for each separate partition. The drive came out of my old desktop which had no EFI stuff whatsoever. I use a custom GRUB bootloader to chainload any partition in my box. I'm not sure if I can chainload OSX yet as I haven't tried but I will eventually. I wonder how many people here have 16 different entries to boot from in their BIOS because I did when all my drives were hooked up lol.

 

minimig,

I unplugged my OSX drive, flashed back to the stock F2N BIOS and left everything on defaults and it POST's fine. I'm on my linux drive right now and just built the Nvidia driver for it and installed it. It's clear now that the 816M BIOS definitely was the problem, I'll try 801M and see if it fairs better.

http://img.photobucket.com/albums/v77/red_team316/linux/nvidia-linux.png

 

I'm making progress, but it all seems backwards :D

 

BTW, Is the source code for the BIOS available? I thought I read that somewhere it was going to be open source. 

Share this post


Link to post
Share on other sites

Is it neccessary to update the BIOS from 801M to 816M? I'm running the Version 801M and everything works fine. Don't touch a running system or what are the advantages of the 816M?

Has anyone done the latest Mac OSX update for 10.8.5? This should fix audio and Bluetooth things...

 

Kind regards

Share this post


Link to post
Share on other sites

sTaN,

According to the changelog:

816M Fix loading SSDT table overrides. 801M 10.8.5 audio distortion fixed.

 

The 801M BIOS also does not POST with my EVGA GTX680 Mac Edition card. How many other BIOS are there? I have a 739M also that I will try to narrow down where the problem started, or if all of the OZ BIOS are like this. The stock F2N BIOS wont boot into Mountain Lion at all, yet it POST's properly with the card. What I need is a mix of the two...

Share this post


Link to post
Share on other sites

@ red_team316:

 

1. is your old HDD which you migrated MBR or GPT partition scheme?

 

2a. Do you have clover or Chameleon (latest versions I guess) installed on your ML partition?

 

2b. pls post your chameleon or clover boot and smbios plists

 

3. you can install DIRECTLY via pacifist, w/o extracting first. Try google or better metacrawl something like 'install package with pacifist' or 'install package via pacifist'

 

@ all:

In general I wonder if it might be better to start w/ the latest regular f3a BIOS + either clover or Chameleon, and work everything out which tends to cause probs w/ h'tosh, esp. hot-plugging monitors, live res switching on all connected mons, OS and monitor sleep and wake-up.

 

Which smbios model identifier makes sense for this board? Which one do the h3a bootloader use?

 

Would you folks who use the f3a BIOS on your 100% working system + cham. or clover pls. post their boot and smbios plists?

 

Thanks,

Bugs

Share this post


Link to post
Share on other sites

...What I need is  ...

The fix might be under your nose. Since you are using an Apple card, and as joe75 warned you, it has EFI VBIOS, it may be the source of your problem.

You can try to solve it like this:

Go to BIOS/Bios Features menu and change on Display Boot Option ROM Control from UEFI First to Legacy Only.

Share this post


Link to post
Share on other sites

THe KiNG, when I use any of your devs h3a BIOS, can I still use overwrites in /Extra (plists etc.)? Or is it like on a real Mac w/ any h3a BIOS that OS X does completely ignore /boot and /Extra?

Share this post


Link to post
Share on other sites

The fix might be under your nose. Since you are using an Apple card, and as joe75 warned you, it has EFI VBIOS, it may be the source of your problem.

You can try to solve it like this:

Go to BIOS/Bios Features menu and change on Display Boot Option ROM Control from UEFI First to Legacy Only.

Thank you both so much. I've been battling the beeps all night long. I certainly did not understand what he was getting at. like yoda, joe speaks :)

Share this post


Link to post
Share on other sites

THe KiNG, when I use any of your devs h3a BIOS, can I still use overwrites in /Extra (plists etc.)? Or is it like on a real Mac w/ any h3a BIOS that OS X does completely ignore /boot and /Extra?

Ignored.

Share this post


Link to post
Share on other sites

Is it neccessary to update the BIOS from 801M to 816M? I'm running the Version 801M and everything works fine. Don't touch a running system or what are the advantages of the 816M?

Has anyone done the latest Mac OSX update for 10.8.5? This should fix audio and Bluetooth things...

 

Kind regards

I ran 801M for a week with no problems (10.8.4) using the on-board graphics. Then i wanted to use my GTX 650 as a compute engine; this required 816M.  Its been reported that 816M supports 10.8.5 and may fix the sound distortion problem, but others have had to apply the legacy found patch. But, currently i have no plans to update to 10.8.5. ( i even have an old Mac Mini running 10.6.8 running OwnCloud )

Share this post


Link to post
Share on other sites

Its been reported that 816M supports 10.8.5 and may fix the sound distortion problem, but others have had to apply the legacy found patch.

 

I think you mix two separate things: 816M indeed fixed the sound problem but you have to patch audio anyway.

 

I is needed because the audio chip is not supported by Apple kext as they used unobtainium hardware in their line of products.

The chip used for Quo board is an alternative hardware commonly used by mobo manufacturers, but as it is unsupported OOB by OSX, you have to add support by patching kext or adding an other kext.

 

For the same reason you could have to add non-Apple kexts to support new hardware that you install on a genuine Mac (printer, TB enclosure with specialized hardware, etc)

 

No big deal, and not a problem AFAIC.

Share this post


Link to post
Share on other sites

I'm not amazed there is a mix-up. The reason is that the package which contains the AppleHDA ALC892 audio patch scripts is inappropriately called 'QUO_Legacy.080720131.zip' ..

 

I duplicated that zip and split it into 'QUO_Legacy.08072013 by hackintoshfreedom.zip' and 'AppleHDA ALC892 audio patch scripts.zip' with only respective files inside, deleting the ones that belong into the other zip.

Share this post


Link to post
Share on other sites

Everything out fine without using 801M and 816M, but cant get sleep to work. I heard that Parallels is the problem, but dont want to uninstall cause I need it. How do I let HWMonitor read the temperatures for the CPU? Do I have to install fakesmc.kext?

Share this post


Link to post
Share on other sites

Which BIOS ARE you using - stock Fxx? Oz 739M contains FakeSMC.

 

(sleep: migrate to VMware Fusion)

Share this post


Link to post
Share on other sites

Everything out fine without using 801M and 816M, but cant get sleep to work. I heard that Parallels is the problem, but dont want to uninstall cause I need it.

Upgrade to Parallels 9. i was having this issue with version 7, i can confirm it fixed in version 9 (at least for i5 3570k)

Share this post


Link to post
Share on other sites

Which BIOS ARE you using - stock Fxx? Oz 739M contains FakeSMC.

 

(sleep: migrate to VMware Fusion)

I decided to try Oz 801M and the BIOS is H3A

 

Upgrade to Parallels 9. i was having this issue with version 7, i can confirm it fixed in version 9 (at least for i5 3570k)

Thanks. I will do that dat if I have the money for version 9. Sleep is not a BIG problem for me though. Wanted to make a fully compatible hackintosh.

 

 

I forgot to mention I'm new to hackintosh 

Share this post


Link to post
Share on other sites

Yes it will be exactelly the same, I have the second EVT sample and touch it every day, still can't believe it was possible.. :)

 

People know what I think about clone makers, closed source and {censored} like that, at first I didn't looked good at QUO until iztech talked with me and told me what he is trying to do, that did ring a bell in my head, and I said what a heck this was never done before!

I saw the oportunitty to move hackint0sh 'scene' beyond the actual limits and pieces, this is not just about making a motherboard with hardware that 'fits' OS X needs, just think why projects like coreboot does not have big success, because developers are not working on same project, just imagine how would be to get the majority of osx86 developers to work on this one...

The AOS stands for more, no vendor test on all OS's, you know they say '"íf works on windows is fine..'', we are doing several tests on Windows and Linux to make sure works as good as on OS X or even better if possible(sic!), and more then that everything we add/change in firmware will be open source!

 

From my point of view the fun just starts...

"will be open source!"

Its this still true or this its lie?

Any chance that u upload source to http://forest.com/

Share this post


Link to post
Share on other sites

"will be open source!"

Its this still true or this its lie?

Any chance that u upload source to http://forest.com/

 

Why do you want the source ?

 

Are you a programmer ?

 

Can you contribute ?

 

Or just want to take cheap shots ?

Share this post


Link to post
Share on other sites

Why do you want the source ?

 

Are you a programmer ?

 

Can you contribute ?

 

Or just want to take cheap shots ?

I dont want a source..

I am not a programmer.

I cannot contribute but others surely can.

In my point of view if u tell something and not make like that then thats a lie.

Its not important what i want to take.

 

what u think will happen if some tm86 terrorist just kill all of oz developers ?

There will be no source to fix things to help users of this board... :ninja:  :ninja:  :ninja:

Share this post


Link to post
Share on other sites

"will be open source!"

Its this still true or this its lie?

 

And who are you to question my words?

I dont want a source..

I am not a programmer.

I cannot contribute but others surely can.

Then STFU!

Share this post


Link to post
Share on other sites

1. is your old HDD which you migrated MBR or GPT partition scheme?

 

2a. Do you have clover or Chameleon (latest versions I guess) installed on your ML partition?

 

2b. pls post your chameleon or clover boot and smbios plists

 

3. you can install DIRECTLY via pacifist, w/o extracting first. Try google or better metacrawl something like 'install package with pacifist' or 'install package via pacifist'

1) It's MBR and contains a bunch of Linux paritions, only the GPT are the OSX installs which are on separate drives.

 

2) No, not that I know of. I did look into chainloading OSX from GRUB and GRUB2 and tried, but it seems that Chameleon is needed on the OSX drive for this to work. If Chameleon is purely a bootloader like GRUB and will not mess up OSX updates or anything, I may play around with it in the future.

 

3) Thanks, I will definitely look into this more. I was setting up other partitions properly after getting the card working yesterday. I think getting Pacifist working with the driver is basically the last major configuration item I am looking at OS-wise, then I'll start looking at overclocking, more into OSX inner workings and other stuff like actually making proper .app/.pkg/.dmg 

Share this post


Link to post
Share on other sites

hey folks, relax .. ;) From reading MANY of THe KiNG's postings I have learned to know him as 100% authentic so I do not doubt his words. Mind they state 'WILL be open source' not 'IS open source' .. the point in time WHEN they release the source is COMPLETELY up to them, and needs to be respected.

 

One reason is to protect their hard work in this toddler phase of the project .. Obviously there is a natural interest of some to apply the source to the EFI BIOS of competing similar boards like the Gigabyte Z77X UD5H ..

 

Let them profit from their investment with this awesome kickstarter project first by selling a at least for them sufficient # of mobos (and parts).. thereafter the sources will get released to the public, as they promise. Just be patient.. ;)

Share this post


Link to post
Share on other sites

xpamamadeus, bs0d, THe KiNG,

I am a programmer and I am interested in the source. I mostly do application development, but also have experience in embedded programming. It seems that since hackintosh development is mostly the focus at this point, I would say that the reason it isn't released yet is that it needs more polish and so that when it is released, that the chance of someone bricking their system is minimized. Also, as BugsB mentioned, addressing the kickstarter is an important factor. One benefit of having it open source though is that other tools could be made to improve the development process. Anyone who is not a programmer could certainly improve the documentation, tutorials or help by collaborating in some other way.

 

1) lockup - occasionally the computer locks up at boot when holding down a key rather than entering BIOS, boot menu, flash menu, etc...

2) Boot screen - since this apparently runs on more than one mobo, maybe that is the reason for not displaying the proper keys to press at boot. Regardless, this should and could be easily improved. I've done custom windows(XP, 2000, 98) and linux boot screens(usplash, plymouth) in the past and I'm sure this isn't much more complicated than that. I'm sure it's just an embedded image. This would be relatively easy for others to handle while the core devs focus on more complex tasks.

3)Why do I have a list of 16 boot options even if I disable all of them? Refreshing the screen when the boot menu is changed to reflect lesser or more entries would be a nice addition. It's possible the menu entry generation is based on an index the first time the computer boots rather than incrementing the number of boot options to the index. Just a guess, but without source, can't be sure. This probably isn't a complex task either.

 

I'm quite pleased with how the Oz BIOS works with the Quo mobo. There are some rough edges I've probably encountered that aren't listed that I forget, but otherwise it's great. This mobo/BIOS combo lives up to "Any OS" when it comes to the 3 major OS. I'm going to try BSD at some point in the future, but I would guess that it probably works fine too as from my understanding, it's closer to Linux than OSX.

Share this post


Link to post
Share on other sites

@ red_team316: the installer might not work because of MBR? Yes, force-install via Pacifist following the guides (updating folders incl. package folders rather than overwrite, then overwrite existing FILES only) usually always works.

 

The MBR scheme might also be the reason for your convoluted boot-screen. An (U)EFI firmware based BIOS is simply made to boot GPT HDDs.

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.

×