Jump to content


  • Content Count

  • Joined

  • Last visited

About genzai

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
  • Location
    San Francisco

Recent Profile Visitors

10,123 profile views
  1. genzai


    Ah ok, so just add EmuVariable for now. Many thanks. And let me know if I can help test workarounds. g\
  2. genzai


    About to update one of my systems from z370 to z390. What is the current best practice for Aptio and Z390 pending hopeful fixes to AptioMemortFix? Thanks, g\
  3. genzai

    ThunderBolt Drivers

    Thats just because the X299-Prime does not have any x4 slots. It only has x16 and x1. I can confirm that on Asus boards that have x4 slots that the option appears in the menu. g\
  4. Thanks @IronManJFF, So the main crux of my issues was indeed the Defaults plist. Bummer that the ones generated from Ozmosis Configurator don't seem to be loading or working properly. I was able to boot back in to my original drive after modifying and using the defaults plist that @ntsmkfob provided. Thanks man. Then was able to clone, boot the clone and update. 10.14 installer still would just hang immediately at the apple logo, so i decided to try 10.13.6 instead and that went well. Was able to install the latest SU as well using a combo of @IronManJFF's instructions for editing the boot plist and forcing a second boot from the installer folder's boot.efi after the first reboot. I did all the updates with imac13,2 smbios but eventually reverted back to macmini6,2 because imac13,2 still disabled some USB ports i use. I am still not sure why i cant seem to boot a 10.14 usb installer or a fresh 10.14 drive made on another computer, but i decided i would re-install my GTX 970 into this system for now so i'll stay on 10.13.6 anyway, at least until there are nvidia drivers for 10.14.x Anyway, thanks all- especially @IronManJFF and @ntsmkfob. g\ PS- If you end up making any new updated BIOS versions with other improvements, it might be best to change the default SMBIOS info in the BIOS so that it is iMac 13,2 or something thats likely to remain macOS compatible for a while. I'd think its safe to assume anyone updating to these later BIOS versions are doing so primarily for new OS support, and adding APFS support for instance certainly is in line with this.
  5. yes, i have used ozmosis configurator to generate and modify Defaults.plist and it seems to put the correct details in those fields. Would a non-functioning defaults plist cause even a 10.12.6 drive to fail to boot? it basically flashes black for a split second before giving me that symbol on screen. If you have a known working plist i would be happy to throw that on and try it though! Thanks, g\
  6. Hello dear Quo hive-mind, I finally decided to give my QUO based system some update love- its been on 10.12.6 and happy there for a long, long time. In order to do this i decided to clone my working 10.12.6 drive and then update. I made the clone, and then ran the BIOS update with the mojave compatible version provided by @IronManJFF. This all seemed to go without a hitch. However as soon as i tried to boot the cloned drive i was immediately greeted with the infamous "NO!" screen: This screen appears almost instantaneously after selecting either the macOS volume, or the recovery volume. I can still boot windows as long as i have the cloned or original drive in (the boot loader for windows also seems to be in that EFI partition, which i thought is weird but lets leave that be for now). Now even when i replace the cloned drive with my original working drive it has the exact same issue. I tried generating a simple Defaults.plist with proper Macmini 6,2 SMBIOS info just in case that might be an issue but that has not helped. Here is what i get with F12: RED is the 10.12.6 clone- and the same name as the original volume that has always booted just fine (but now also wont boot). And here is what i see when entering the shell: I can get into the EFI and OZ folders just fine, and see my defaults.plist in place- though i don't know why i would need one just to boot into 10.12.6 now (I have yet to start the OS updates). Finally, if i try loading boot.efi manually from the shell i also get the same result. Instant "NO!" as though it does not even try to load. Appreciate the support, g\
  7. genzai


    There is an X199? I have a loaded up x99 that does not even have a 4G decode option in bios (maybe its always forced on?) that is fully loaded up with PCIe cards and it boots fine. I have a z370 board with less hardware that needs 4G decoding enabled to boot. All definitely comes down to how much hardware you have enabled and some hard to understand specifics of each motherboard/firmware design. Thunderbolt, iGPU, dGPU and some RAID cards seem to be the worst culprits. Aptiomemoryfix has been the hands down best solution though and i really thank you for continuing its development. About macOS only using 32bit addresses when it starts, would a future version that can do 64bit addresses not be the holy grail that finally solves this once and for all? And why can you load up a real mac with as much hardware as it can possible support and never run into memory allocation issues on boot? Thanks, g\
  8. Hello @MaLd0n, Here is my sendme info again. this is already based on your work not long ago. But i have enabled iGPU in headless mode, which is working well so maybe it needs nothing new. But also wondering about your recent work with Z370 and if it can be applied to improve my ACPI. Thanks! g\ https://www.dropbox.com/s/08gch5uzmumafif/Send me GustavMahlerIII.zip?dl=0 Z370 Aurous Gaming 7, GTX 1080ti, TB3, UHD630 (headless acceleration working)
  9. with this DSDT: Focusing on Thunderbolt for the moment. Some interesting results. 1) no more express card in menu bar, also thunderbolt controller and devices do not appear at all in system profiler PCI devices, but may be found elsewhere in system profiler,. for instance firewire appears under firewire, even though it does not show up in PCI devices list. 2A- devices plugged at boot always appear (as expected) 2B- devices can very reliably be hot-removed. no system crashes. Device disappears from system profiler (for instance if it was there under firewire or ethernet- again it never shows up in PCI list) 2C - hot plug is very inconsistent. usually hot plugging a device does not work, however in a couple of cases it seems to work. for instance- boot with firewire in one port and 10G in the other port. Remove firewire (success) plug back in firewire (nothing happens), remove 10G (success), plug in firewire to port previously occupied by 10G (success). further hot plug events do not work until reboot. here is a sendme file. I booted with a blackmagic decklink card in one port, and an akitio RAID station in the other (akitio raid station has 2 sata drives, a usb3 controller with SD card reader connected, and intel GbE i210). I then plugged in the firewire adapter to the akitio raid station so it is #2 in the chain, and it was a successful hot plug (now see a firewire bus in system profiler). I then generated the sendme file. You are amazing, so many thanks! g\ PS- the other onboard ethernet (i211 based) is no longer showing up or working, it was working before with the hacked small tree drivers and fakePCIID. Send me Tims-iHac.zip
  10. Unfortunately hot-plug did not work in my initial tests (more on this below). Sleep also doesn't seem to work, though shutdown does. Sleep seems to put the screens to sleep but not the computer, i am able to wake the screens unlike on the other system. In my hot plug testing, first thing i tried when i got back was to plug in a couple of devices. The system had been booted without anything plugged into TB3 ports. in this case nothing happened, the hot plug event seemed to be ignored. Next i tried rebooting with a device attached. the device showed up as expected, however hot plugging a second device caused the system to immediately reboot. In fact i found hot plugging or removing any device once system was booted with any TB3 device connected at boot causes an instant reboot. I should probably test with other devices as the panic seems to relate to the driver of on of the devices i was testing with. I will try this next. In the meantime, if i boot with any TB device connected they appear in system profiler as an express card and the crashy menubar behavior is back. For reference i attached a sendme with a couple of devices attached at boot (apple firewire adapter with TB3->TB2 adapter on one port, and TB3 enclosure with 10GbE on the other port). Thanks! g\ Send me Tims-iHac.zip
  11. Hi Mald0n, Updated my EFI files. Here is the send me file attached. I am working remotely at the moment so can't test hot plug but will test it tonight. I do notice the express card in the system profile and menu bar. Menu bar does not crash and only the thunderbolt controller is listed as express card but thats probably because I don't have any devices plugged into it right now. thanks! g\ Send me Tims-iHac.zip
  12. Hi Mald0n, I have another system that could use some of your magic. This one is based off the GA-Z170X-Designare, which has a built in TB3 controller. Thanks! g\ Send me Tims-iHac.zip
  13. Thanks so i assume I should use the DSDT02 file with cosmetic patches? Do you recommend i enable the iGPU? I notice your edits include PCIHotplugEnable. Should i have hot plug support over thunderbolt now? Any other advice? Big thanks! g\
  14. IOReg with new DSDT02. System profile no longer shows express card devices and has unique names on the "PCI bus". this seems good no? also no crashy express card menu bar. Thanks, g\ and ioreg from the "without cosmetics" version (ioreg file labeled nc). shows no PCI devices in system profile. Thanks, g\ Gustav Mahler III 0226-1752-dsdt02.zip Gustav Mahler III 0226-1805-nc.zip