Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About aparis

  • Rank
    InsanelyMac Protégé
  1. I tried both versions (I have several installs on different hard drives so easy to swap one quickly) and same result. Is there any way to see on the bios level if it sees the graphic card?
  2. Oh I fully agree with you. This is very strange and I did manage to get the 1080 work on another computer so it's really not the 1080 at fault here. I'm running Windows10 on the Quo right now so there is no reason why it wouldn't see the 1080 while it does see the 690. The only thing I can think of is power consumption? The PSU not delivering enough juice or just a hardware failure of my Quo board (but then again why would the 690 work...) And I also borrowed another 1080 card just to try and it wouldn't work either in Windows 10 when installed on the Quo motherboard... At this point I'm thinking my only hope is to find another Quo board to buy from somebody...
  3. Ok so I did a test with yet an older graphic card (GTX690) and this one actually comes up when I plug it on the first PCI port, the second one doesn't and yet that's where I used to plug the GTX 1080. So I gave it a few more trials at getting the 1080 to work again in that first PCI slot. But still no luck. I noticed the fans on the 1080 stop after a couple of minutes, while windows has fully started. I'm not sure if it's because the card sees it's not being used and it goes to power saving mode. But I was wondering if this might have to do with the PSU not delivering enough juice. Yet the GTx690 is using the exact same connectors and it works fine. So really I'm a bit clueless here. Any help is welcome.
  4. Hello all, It seems my Quo Motherboard had a hardware failure as it doesn't see any PCI graphic card anymore. I tried a different graphic card, a different PSU, all PCI ports, I went back to the original bios and started under windows and it still doesn't see the graphic card either. So I think there must be a hardware failure (yet the graphic card does light up and the fan fan works...). I was wondering if any of you have a board that you would be willing to sell? I really need to continue using that exact same setup. Thanks
  5. Yes, USB 2, they are connected to the QUO OSX motherboard USB port that the most further to the right when looking at this side of the board. For the sound I was able to get it to work after messing with the Audio Preferences (I had a Matrox Audio device installed in the system that seemed to have overtaken the preferences but I deactivated it and the regular audio options were back on).
  6. So the combo update did the trick. I now have a 1080 running smoothly in Sierra with the Cuda mode activated. This is simply awesome! So much faster than the equivalent on PC! The only thing that doesn't seem to be working from my previous build in Capitan is the audio that for some reason is not available at all and the front USB ports. Do you guys know if there is some specific kernel I should play with to get these two back to working in Sierra? Thanks
  7. So now that the upgrade to 10.12 is complete I'm running into a new issue... upgrade to 10.12.4 .... Indeed to be able to use my new GTX 1080 I need the new nvidia rivers that are only compatible with 10.12.4 So I downloaded the upgrade package for 10.12.4 but when I try to run it on my OS hard drive it says "macOs Sierra Update can't be installed on this disk.This volume doesn't not meet the requirements for this updated." And yet there is more than 50GB room on this drive so I'm a bit confused as what is the issue with my drive that prevents the upgrade. Thanks for any help
  8. It was indeed the port that was causing the issue, my bad for not paying more attention in the other mentions of this in the thread. Going through the Sierra upgrade as I'm typing this Thanks IronMan and Ntsmkfob for your help on this!
  9. Hey Iron Man, thanks a lot for your help so far, so I installed your bios and I updated my Defaults.plist accordingly: <?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>BiosVersion</key> <string>IM131.88Z.010A.B05.1210121459</string> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string> <key>SystemSerial</key> <string>F5KLA770F9VM</string> <key>BaseBoardSerial</key> <string>F5KLA770F9VM12345</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>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DisableNvidiaInjection</key> <true/> </dict> </dict> </plist> But when I restart the computer and do the NVRAM reset it just doesn't seem to take into account the Defaults.plist
  10. On-board audio would be the best in my case.
  11. So I tried to use the Defaults.plist that STLVNUB created for my build and I did a NVRAM reset has suggested. But it doesn't seem to do the trick. My specs are still saying that it's a macpro late 2008... Any suggestions as to how I could change my specs to be able to do the Sierra upgrade? Or if there is another way to install my GTX1080 staying with El Capitan I'll take that too, I like that build it's very stable and everything works Thanks!
  12. It's a GTX690. Just updated my signature with details of my build. Thanks
  13. So what will I need to get 10.12.4 to boot? I thought using the X-MASS bios was sufficient and the only challenge was to get the upgrade to be installed. Which plist format should I be using so that my system is seen as a recent macpro? Thanks.
  14. Hello all, trying to upgrade from El Capitan to Sierra to be able to upgrade my graphic card to a GTX1080. Here is what I did so far: 1) Updated my bios to Z77MXQUOAOS.H2O.167X-MASS-SIERRA.ROM 2) Restarted and checked that El Capitan still works ok with new BIOS and the older graphic card (seems to be the case for a few hours now) 3) Tried to do the regular Upgrade to Sierra from the App store but it gives me the message 'This version of macOS 10.12.4 cannot be installed on this computer.' I checked my 'About this mac' specs and it sees my computer as a Mac Pro (Early 2008). So obviously it doesn't think it's compatible... 4) Did a few hours of research in this forum and on google. It seemed like the solution would be to change the Defaults.plist to make the computer think it's compatible with Sierra. (following this link: https://www.tonymacx86.com/threads/guide-how-to-configure-your-systems-smbios-correctly.198155/) 5) Created a custom Defaults.plist with Clover Configuration to fake being a Mac Pro latest generation that I copied to my Efi/Oz/ folder. But I was surprised to see that there wasn't any .plist file in this folder already. (see attached custom Defaults.plist I created) 6) Tried a reboot of the computer but nothing changed, it still sees it as an Early 2008 Mac Pro ;( 7) Asking for help on this forum. Thanks to anyone who has a second to tell me what I'm doing wrong. I'm suspect that the BIOS we're using doesn't need a Defaults.plist file and that it doesn't even look for one in the Efi/Oz folder. Thanks again for any help. Defaults.plist.zip