Jump to content

OS X compatible motherboard -> QUO

meklort

By meklort,
in New Releases and Updates

 Share
4,397 posts in this topic

Recommended Posts

guido13456
guido13456
Posted
Posted
5 minutes ago, Casm101 said:

 

 

I’m currently running the latest developer version of Mojave on the Intel HD4000 graphics and I had no problems installing vanilla MacOS...

 

 

If you feel the need to get a graphics card it’s worth investing in an AMD Radeon

ok thank you for information 

can I ask 

what bios did you use 

and what did you do for it to work with only intel HD4000

question ,is vanilla like clover 

5 hours ago, IronManJFF said:

If it can work with Clover then I don't see why it would not with Ozmosis.

 

Have you tried to increase IGPU Memory in BIOS like I suggested ?

 

About that GTX750, is it installed on the board (don't install it if it is not installed atm) ?

yes I tried 

can we start for begening , I have read from page 140 to 149 and people are trying different aproche

and I am lost lol

 

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted (edited)

I would start from the top the way it should be ... and btw throwing Clover in the mix is to gonna solve anything just make more noise.

 

I would 

 

0) Reset CMOS

1) Create a USB Installer

2) Copy on the USB stick the Defaults.plist file i provided you

3) Re-Format the target drive and plug it in SATA0,0

4) Flash BIOS (so it will create the required directory structure in the ESP partition 

5) Boot to UEFI Shell  and Copy Defaults,plist to fs0:\EFI\Oz (nothing else should be needed) and flash nvram

6) Verify in UEFI shell that Defaults.plist was read and applied (thru the use of the dmpstore and bdmesg commands)

7) And only after this has been successful I would then start installation of the target OS

 

 

Edited by IronManJFF
Link to comment
Share on other sites
guido13456
guido13456
Posted
Posted
1 hour ago, IronManJFF said:

I would start from the top the way it should be ... and btw throwing Clover in the mix is to gonna solve anything just make more noise.

 

I would 

 

0) Reset CMOS

1) Create a USB Installer

2) Copy on the USB stick the Defaults.plist file i provided you

3) Re-Format the target drive and plug it in SATA0,0

4) Flash BIOS (so it will create the required directory structure in the ESP partition 

5) Boot to UEFI Shell  and Copy Defaults,plist to fs0:\EFI\Oz (nothing else should be needed) and

 

flash nvram why flash NVRAM 

and this is the part that I am lost

 

1 hour ago, IronManJFF said:

6) Verify in UEFI shell that Defaults.plist was read and applied (thru the use of the dmpstore and bdmesg commands)

7) And only after this has been successful I would then start installation of the target OS

 

 

 

Link to comment
Share on other sites
guido13456
guido13456
Posted
Posted
10 hours ago, IronManJFF said:

Need to Flash nvram (Command-Option-P-R) so the values in Defaults.plist will override the values in the BIOS because Ozmosis does not override existing values so just putting them in Defaults.plist does nothing.

 

10 hours ago, IronManJFF said:

Need to Flash nvram (Command-Option-P-R) so the values in Defaults.plist will override the values in the BIOS because Ozmosis does not override existing values so just putting them in Defaults.plist does nothing.

I did that to 

 

1- flash Bios

2-  Flash nvram (Command-Option-P-R)

3 - put the plist in the EFI

4 - what is next

yes 

7 hours ago, IronManJFF said:

mmm just remembered that you can disable property injection for Intel ... 


<key>DisableIntelInjection</key>
<true/>

Maybe try that since HD4000 is what you would find in a real Mac Mini(Late 2012)

yes 400 intel is in the Mac mini 2012 , why disableintelinjection 

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

@guido13456

You have to Command-Option-P-R after putting Defaults.plist not before.

I don't want to to improvise .. do what I told you to and  in the same order, if that is not what you did go to step 0 and start over

 

Quote

I would 

 

0) Reset CMOS

1) Create a USB Installer

2) Copy on the USB stick the Defaults.plist file i provided you

3) Re-Format the target drive and plug it in SATA0,0

4) Flash BIOS (so it will create the required directory structure in the ESP partition 

5) Boot to UEFI Shell  and Copy Defaults,plist to fs0:\EFI\Oz (nothing else should be needed) and flash nvram

6) Verify in UEFI shell that Defaults.plist was read and applied (thru the use of the dmpstore and bdmesg commands)

7) And only after this has been successful I would then start installation of the target OS

 

Link to comment
Share on other sites
niXta
niXta
Posted
Posted
On 1/11/2019 at 3:33 PM, elviejo said:

It's there anybody who had had success installing or upgrading to 10.14.1 or 10.14.2 with only internal GPU?. I think the problem resides with the way the Intel HD 4000 is managed in the ROM.

 

I have an i7-3770k with HD 4000 working fine in 10.14.

I havn't upgraded since I havn't seen an easy, safe, way to do it from IronManJFF.

Until I do I will stay put.

Link to comment
Share on other sites
guido13456
guido13456
Posted
Posted
On 1/12/2019 at 12:41 AM, IronManJFF said:

@guido13456

You have to Command-Option-P-R after putting Defaults.plist not before.

I don't want to to improvise .. do what I told you to and  in the same order, if that is not what you did go to step 0 and start over

6) Verify in UEFI shell that Defaults.plist was read and applied (thru the use of the dmpstore and bdmesg commands)

On 1/12/2019 at 12:41 AM, IronManJFF said:

 

 

this is where nothing happens 

 

 

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted (edited)

@guido13456

Nothing shows up when you type bdmesg in UEFI shell ? That is almost impossible. It should output something like 

  

00:000 00:000 Ozmosis 1.03.167X-XMAX RELEASE (2018-06-06 09:12:07 VS2013x86) on 2019-01-14 12:33:46
00:000 00:000 Found Firmware UEFI Spec  :2.31:
00:000 00:000 Found Firmware Vendor     :American Megatrends:
00:000 00:000 Found Firmware Revision   :4.653:
06:689 06:689 BootOrder 01 02 0E 03 0F 10 11 12 13 14 15 16 17 18 19
06:689 00:000 Found Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (3A.06.00) Cores 4 Threads 4
06:689 00:000  P-State Coordination Type HW_ALL -> SW_ANY = SW_ANY
06:689 00:000  Bus Ratio 16 - 34 (40) Unlocked
06:689 00:000  Disabling Invalid Flex-Ratio F0000 -> E0000 = E0000
06:689 00:000  TSC Frequency  3403358490  3403MHz
06:689 00:000  CPU Frequency  3403358486  3403MHz
06:689 00:000  FSB Frequency   100098779   100MHz
06:689 00:000 Found 00.01.00.0 Nvidia Graphics Controller [10DE:13C2] [1462:3160] rev 161
06:689 00:000 Found 00.6D.00.0 Intel Lan Controller [8086:10F6] [8086:0000] rev 0 94:DE:80:A1:36:26
06:689 00:000 Found 00.6E.00.0 Broadcom Wireless Lan Controller [14E4:43A0] [106B:0111] rev 3 00:00:00:00:00:00
06:689 00:000 Found 00.70.00.0 Texas Instruments Firewire Controller [104C:823F] [3412:7856] rev 1 00:00:00:00:00:00:00:00
06:689 00:000 Found 00.00.1F.3 Intel SMBUS Controller [8086:1E22] [8086:7270] rev 4
06:690 00:001  Slot 0 8192MB DDR3 SDRAM 1600MHz "Corsair" "CMZ16GX3M2A1600C1" "00000684"
06:691 00:000  Slot 1 8192MB DDR3 SDRAM 1600MHz "Corsair" "CMZ16GX3M2A1600C1" "37761195"
06:691 00:000  Slot 2 8192MB DDR3 SDRAM 1600MHz "Corsair" "CMZ16GX3M2A1600C1" "00000683"
06:691 00:000  Slot 3 8192MB DDR3 SDRAM 1600MHz "Corsair" "CMZ16GX3M2A1600C1" "2F761195"
06:694 00:002 Found 1 GPU Controller 
06:694 00:000 Found Storage PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,8C7A1EDC-8BB7-4F70-AB74-69141E2C8351,0x28,0x64000)
06:694 00:000 Found Defaults \Efi\Oz\Defaults.plist
...
...
...

 

You sure you are not booting with Clover ?

Edited by IronManJFF
Link to comment
Share on other sites
Casm101
Casm101
Posted
Posted

Hi guys,  ^_^

I was thinking of getting a PCIe card with wifi and bluetooth for my Quo Mobo, as my bluetooth USB dongle is giving up on life.... :bye:

 

Do you think this will work without any problems if I'm running the iMac "defualts.plist"??

 

Thanks in advanced :)

Link to comment
Share on other sites
shadowsceptre
shadowsceptre
Posted
Posted

New on the form so would appreciate some direction as to where I can find some answers:

1. Can Hi-Sierra be installed on HPFS?

2. Which is best ROM for Hi-Sierra?
3. Where can I find the right combination of ROM / defaults.plist end kexts for hi-Sierra?

 

I need to upgrade to use newer software but am afraid to jump up to Mojave just yet. This list has moved beyond Hi-Sierra and so I am confused as to the best combination.

 

Using: Z77MX-QUO-AOS / Core i7 3770K / NVidea GeForce GTX 650 / 16Gb RAM / 2TB Seagate HDD / 10.10.5 Yosemite / H3C.1409122327 ROM

 

Any help appreciated.

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

1) HPFS: NO, HPFS is a filesystem that was made for OS/2; but I guess you meant HFS+.. yes but it will be converted to APFS in the installation/upgrade process

 

2) Firmware:You can use the one I posted a little while ago or use Alberto's variartion. There are no more 'offical' version so it is all on the community

 

3) Defaults.plist: you will have to make your own. I/ElvieJo/Alberto have posted templates you can use. No Kext are needed, the firmware I and Alberto posted have everything that is needed. You will need Nvidia Web Drivers for the GTX650.

Link to comment
Share on other sites
shadowsceptre
shadowsceptre
Posted
Posted
34 minutes ago, IronManJFF said:

1) HPFS: NO, HPFS is a filesystem that was made for OS/2; but I guess you meant HFS+.. yes but it will be converted to APFS in the installation/upgrade process

 

2) Firmware:You can use the one I posted a little while ago or use Alberto's variartion. There are no more 'offical' version so it is all on the community

 

3) Defaults.plist: you will have to make your own. I/ElvieJo/Alberto have posted templates you can use. No Kext are needed, the firmware I and Alberto posted have everything that is needed. You will need Nvidia Web Drivers for the GTX650.

Many thanks!

Link to comment
Share on other sites
ntsmkfob
ntsmkfob
Posted
Posted (edited)

10.14.3 update fairly smooth. For me, it needed flagsnv_disable=1 added to the kernel parameters in /macos Install Data/Locked Files/Boot Files/com.apple.boot.plist, followed by reboot and rerun the boot.efi in that directory from the shell (need to find the right filesystem fsx:) as detailed by IronmanJFF a few pages back. I did the edit from terminal after the first install failed using sudo nano ..... followed by sudo reboot and F12 to get the shell. For some reason I couldn't do the edit from the shell itself, as the Locked Files folder was locked.

Edited by ntsmkfob
Link to comment
Share on other sites
jjrecort
jjrecort
Posted
Posted (edited)

Hello,

 

Just wanted to post an update, I have succesfully upgraded my QUO to Mojave with a RX580.

 

For those who don't know I have two QUO builds, one is my main computer, and the second is my dad's QUO, which when he died a few months ago I keep it as a "spare" computer. 1st I tried out to install Mojave on my dad's QUO and when confident I moved to my QUO build which is the one I use for my daily work.

 

1st, in order to install the RX580 I sadly had to ditch my sleek 1U case and buy a bulky-led-lit stupid gaming box, once I had all my old El Capitan build working again, I dipped into Mojave.

 

Here are my findings.

 

I started with Alberto21 H3C ROM, not for any reason in particular.. it was the 1st to appear on the list.

With this BIOS, when the computer booted after the BIOS flash, at the 1st boot, the MAC OS NO BOOT DISK logo appeared. This was new to me, and for me it meant, it was recognising some part of the MacOS Drive partition.

Then I took off the disk, following a previous JFF recommendation, and nothing: black screen on boot.

I rebooted again on the BIOS config (F2) and NO UEFI SHELL at all--  (I remember that from JFF also).


Second, I installed H20 from Alberto21, same behavior (no boot disk logo) but this time the UEFI Shell it was present

So I tried a manual boot ( fs4: System/Library/CoreServices/boot.efi) and the computer performed a shut down, after a while in black.

 

Third I tried JFF H20 BIOS.

It booted with the UEFI Shell as expected, I did a manual boot ( fs4: System/Library/CoreServices/boot.efi) and Volià! Mojave was there!

 

Then I rebooted again on UEFI, to fix the bcfg boot...and my system is now up and running. :)

 

All seems to work fine for now, but I still need to test the Thunderbolt port with my RAID.

 

 

Hope this helps to anyone!

 

And thanks to all, but specially to JFF for his infinite patience.. If someday I drop by Montréal..I would like to buy you a drink!

 

Edited by jjrecort
  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...