Jump to content

IronManJFF

Members
  • Content count

    722
  • Joined

  • Last visited

About IronManJFF

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender
    Male
  • Location
    Montréal

Recent Profile Visitors

43,899 profile views
  1. IronManJFF

    New OS X compatible motherboard -> QUO

    Thanks@Cecekpawon Mmmm... Surely my QUO firmware image does not contain AptioMemoryFix R21 since it was released only days ago (That is if it contains it at all - not @ home atm so I cannot check it - and if it can be replaced safely with new version - I lack the required knowledge to determine that - Away until Monday )
  2. IronManJFF

    New OS X compatible motherboard -> QUO

    Wondering if the fact that I have 2 APFS drives connected might throw it off ...Which raise an interesting question ... Which one would it load ?
  3. IronManJFF

    New OS X compatible motherboard -> QUO

    Researching how to influence load order of driver images ....
  4. IronManJFF

    New OS X compatible motherboard -> QUO

    Will try that tonite, thanks APFS was listed as a driver but no APFS volume was mapped.
  5. IronManJFF

    New OS X compatible motherboard -> QUO

    I replaced the APFS module I had in my ROM image with the BA6ED98D-D133-4F5B-8787-D2464BB21122.ffs file, when I reboot the screen flashes green but I am not able to access any APFS file systems (I was able to boot but loading APFS,efi which I still had in ESP) . What am I missing ?
  6. IronManJFF

    New OS X compatible motherboard -> QUO

    Thanks Cecek, i'll test it out in the coming days. In the meantime I was able to make some progress.... had to boot in single-user mode to load FakeSMC.kext and change boot-args to disable Nvidia which caused Kernel Panic. There are limitations right now (like not Nvidia Web drivers) But the good news so far is Mojave on QUO -> It can be done (Disclaimer : We are still on Dev Beta so ...) Week-end is over
  7. IronManJFF

    New OS X compatible motherboard -> QUO

    If anyone can understand Russian ... what is this patch about APFS ?
  8. IronManJFF

    New OS X compatible motherboard -> QUO

    Thanks for your input ammoune78. Here is where I am now ... I waited and waited (thanks to Ammoune78 and HPB .. Mojave thread) and installer finally finished its work (clean install on separate partition). It rebooted and I am seeing a blank screen (mouse pointer is working) but there is no window or nothing to click ...maybe because I am using a GTX 970... I am pretty sure i should be at the config screen. I tried by putting it in EFI (we often forget that OZ lets up put kext in EFI) but still no go
  9. IronManJFF

    New OS X compatible motherboard -> QUO

    You are giving me to much credit... I am just an stubborn user with some experience with this board. My knowledge of firmware and UEFI is still lacking to be able to do the 'real' work. Just trying to bring the best out of this board and to give back to the community that has given me the little knowledge I have.
  10. IronManJFF

    New OS X compatible motherboard -> QUO

    After waiting a long long time , I got the installer going ...it completed its work but when I boot every kext is complaining about signature ... will restart with SIP disabled and see how it goes
  11. IronManJFF

    New OS X compatible motherboard -> QUO

    Having a look at Mojave DP -- No Firmware Update for iMac13 -- No SMC update for iMac13 Downloading again because of checksum error on InstallESD.dmg Created USB Installer ... -- Cannot get into Installer, getting messages about Architecture not recognized, Unsupported CPU, Unsupported PCH, kexts stalled AppleACPICPU That is all for today...
  12. IronManJFF

    New OS X compatible motherboard -> QUO

    You had extra spaces in BIOS date which make it fail firmware validation
  13. IronManJFF

    New OS X compatible motherboard -> QUO

    Yes there was ...You have to adjust Defaults.plist with <key>BiosDate</key> <string>04/09/2018</string> <key>BiosVersion</key> <string>IM142.88Z.0130.B00.1804091831</string>
  14. IronManJFF

    New OS X compatible motherboard -> QUO

    Checking (but I would not use iMac 14 on a QUO)...
  15. IronManJFF

    New OS X compatible motherboard -> QUO

    That file is invalid , it does not even have a serial number...the BIOS date is invalid Create your file from this template .. you don't need anything else <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Version</key> <string>1.0.1</string> <key>Date</key> <integer>0</integer> <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BiosDate</key> <string>04/09/2018</string> <key>BiosVersion</key> <string>IM131.88Z.0115.B00.1804091830</string> <key>FirmwareFeatures</key> <integer>0xE00DE137</integer> <key>FirmwareFeaturesMask</key> <integer>0xFF1FFF3F</integer> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string> <key>SystemSerial</key> <string>INSERT_SERIAL_HERE</string> <key>BaseBoardSerial</key> <string>INSERT_SERIAL_HERE_+FIVE_DIGITS</string> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v nvda_drv=1</string> <key>csr-active-config</key> <integer>103</integer> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>DisableNvidiaInjection</key> <true/> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label $platform.$major.$minor</string> </dict> </dict> </plist>
×