Jump to content

jkim74

Members
  • Content Count

    20
  • Joined

  • Last visited

About jkim74

  • Rank
    InsanelyMac Protégé
  1. I had the same problem of getting a black screen after booting Mojave installer USB. What specific BIOS changes did you have to make for the Mojave installer to work?
  2. I recently installed Sapphire Nitro RX580 card, and then experienced significant slow downs and freezes, especially when using Photos. I didn't make the connection with the RX580 card and the issue right away. I have a large Photos library (500gb) and first performed repair of Photos library, and even recreated the Library (and imported the master images). Then I reformatted the startup drive with clean install of High Sierra, but still had issues with slow down and freezing. Finally, after I pulled the RX580 card and used integrated graphics again, the computer was back to its stable self. I found reported cases of freezing with this card and Photos which was related to mediaanalysisd in background with fix using the following: sudo rm /System/Library/LaunchAgents/com.apple.mediaanalysisd.plist" Others stated resolution with upgrade to Mojave. I tried updating to Mojave, but got stuck mid-install due to my inability to add disable_nvflags=1 option to fsx:\macos Install Data\Locked Files\Boot Files\com.apple.boot.plist. So for now I am still using High Sierra. Anyone else experience similar issues with this card?
  3. Running High Sierra with no issues on Quo MB. (Thanks everyone!) About to get RX 560 video card to use with FCPX. I know there have been some posts about this, but with High Sierra, does this video card work out of box our will I have to patch kext? Thanks
  4. Anyone having problems with Parallels 12 with their system? I keep getting freezing issues when starting up Windows 7.
  5. eaym3tal: It is just like IronManJFF stated: "You are probaly getting the X because your Defaults.plist is not being recognized or found.. so the system thinks you are still on a Mac Pro which is not allowed to run Sierra" I had the same exact problem you did. Here is what I did after struggling for hours: 
 --You need to flash back to the MacMini.ROM that works. --From there you have to boot into OS X (I had to reinstall El Capitan from DVD). 
 --Then follow the instructions PERFECTLY about loading the Defaults.plist file into Efi/Oz. --Use Chameleon Wizard to generate a fake serial number for Imac 13,2 --Use TextEdit to make a file called 'Defaults.plist' using the code given by IronManJFF in post #3137 (http://www.insanelymac.com/forum/topic/285920-new-os-x-compatible-motherboard-quo/?p=2352341) --Copy the serial number from Chameleon Wizard in 2 places within the Defaults.plist file; 2nd place with additional random 5 numbers. --Make sure you save this Defaults.plist file as a TEXT file with this exact name and extension. --Mount the Efi partition using TERMINAL and 'diskutil mount efi'. An Efi disk will then show up on your desktop --Place the Defaults.plist file in the Oz folder (within Efi) --Restart --F12 to enter boot selection and reset NVRAM (Command-Option-P-R). 
 --Flash the XMASS.SIERRA bios from IronManJFF's dropbox account (see post 3168 or https://www.dropbox.com/s/t73yeaqu9wooqg4/Z77MXQUOAOS.H2O.167X-MASS-SIERRA.ROM.zip?dl=0) --You are good to go to install Sierra. 
 I think the XMASS.SIERRA.MacMini bios changes it to a MacMini product name, but something is carried over (or missing) even after flashing to another bios (which typically don't affect product name). Getting a working Defaults.plist gets around this issue completely. 
 Thanks to IronManJFF for all his hard work!!! He has taken the role of Grandmaster Yoda for this thread! 
 --johnny
  6. Could you make this custom SSDT available for all through the Quo wiki? How much of a performance difference does this account for? thanks! For those of you who have upgraded from Yosemite to El Capitan on your Quo: Worth the upgrade?
  7. I don't have any bluetooth devices attached, so for me it's not a bluetooth issue. Also, for me, I don't think my computer is in a "deep sleep", because the power LED is still on and fans are still running (but the monitor is getting no signal, and there is no response to keyboard/mouse ). When I put the computer to sleep, though, power LED is off and fans are silent, and it wakes with no problems. However, I recently did a PRAM reset (command+option+P+R--on startup), which then gave me a kext signing startup error (due to Trim Enabler), and then I ended up doing a reinstall of Yosemite (though not clean), and so far no wake freeze issue. I wonder if the PRAM reset fixed the issue. Also I will keep Trim Enabler off for now. UPDATE: Still having the freezing issue. This is a bit maddening...
  8. Wake Freeze Problem I've been having intermittent freezing on wake up after passive sleep. It wakes up fine after I actively put it to sleep. However, at times, when I have left the computer on, it automatically seems to go to an unresponsive "sleep" state--the power LED is still on, the monitor is in standby, and there is no response to keyboard or mouse. I have to press the hardware reset button to restart the computer. There have been a number of posts with Mac Mini's and Mac Pro's having this issue since upgrading to Yosemite. Possibly related to the "displaypolicyd" permissions error. Some have attributed it to using the onboard audio port. I continue to have this issue despite upgrading to 10.10.1. Changing video from HDMI to DVI has not helped. Anyone else having this problem?
  9. Just upgraded to 10.10.1. Initial message stating that NVIDIA driver was not compatible with OS. Then prompted for an automatic NVIDIA driver update and install. Took 2 reboots to make the NVIDIA driver stick (typical). No issues so far. EDIT: Got the annoying "CUDA driver update required" control panel prompt on startup again. Fixed by adding the following to the info.plist file (thanks DarwinX): <key>343.01.02</key> <string>343.01.02</string> Reference: http://www.insanelymac.com/forum/topic/301416-nvidia-web-driver-updates-for-yosemite
  10. Just tried overclocking (thanks InteliMac Pro). Limited bios options, but I set the CPU base clock to 40 (default 35) for 4.0GHz. Also the X.M.P. memory settings to Profile1. Geekbench 3 (64bit) results: 4.0GHz, X.M.P.-profile1 single-core: 3602 multi-core: 13959 3.5GHz, X.M.P.-disabled single-core: 3684 multi-core: 14947 Not enough of a difference to keep it overlocked for my purposes on a regular basis. Probably see less of a difference because I kept turbo boost enabled (upclocks to 3.9Ghz). Others have stably overlocked to 4.3 and even 4.8GHz with increased performance returns, but with watercooling.
  11. Now that I have my QUO Yosemite system up and running, apparently flawlessly (thanks everyone!).... ...I would like to go for gold and try overclocking this guy. It's been a while since I've overclocked, so any pointers would be appreciated. Looking at older posts in this thread, "InteliMac Pro" (PM'ed) had a stable overclock at 4.3GHz. My RAM (1600, CL11) will be a limitation, and I'm using just a Cooler Master 212+ CPU heatsink. The XML profile1 in RAM settings may be a start?
  12. DarwinX: That worked brilliantly! Annoying popup message on startup gone. Thanks so much!
  13. Update re: NVIDIA drivers and 650 Ti. I keep getting a prompt from the NVIDIA control panel about CUDA driver "update required." This apparently is a known issue amongst the Mac Pro community using NVIDIA drivers, and are awaiting another CUDA driver update. When I revert back to OS X graphics drivers, I keep getting the same panic/error on startup/shutdown, so I will keep it on the NVIDIA driver for now, despite the annoying update prompt. [when reverting back to NVIDIA driver it seems to require 2-3 attempts/reboots...]
  14. I just loaded the Trim enabler. Working fine without any other tweaks / boot flags.
  15. Toastie and others: I dove in and just got this quo motherboard setup. 1479 bios. Vanilla 10.10 install. Also with 650 Ti graphics card (with HDMI cable). I was getting the same panic report on nearly every shutdown, just like you and Redtigerxx. I was able to find the following drivers on the Nvidia website for Yosemite: - Cuda driver: http://www.nvidia.com/object/macosx-cuda-6.5.18-driver.html - GeForce for Mac: http://www.nvidia.com/download/driverResults.aspx/78853/en-us Installed both, then in the "NVIDIA Driver Manager" control panel in System Preferences, selected "NVIDIA Web Driver". Reboot, and no more panic messages! (for now) Any of you using Trim Enabler by Cindori? If so, any issues? I know there is that kext security disable thing with Yosemite, but I figure it doesn't really matter to us. Thanks.
×