dwdrummer0 Posted April 11, 2017 Share Posted April 11, 2017 Here are the new Pascal drivers guys! all the 10 series Nvidia cards are working! https://images.nvidia.com/mac/pkg/378/WebDriver-378.05.05.05f01.pkg Link to comment Share on other sites More sharing options...
yeh Posted April 11, 2017 Share Posted April 11, 2017 Well, I just tried the Z77MXQUOAOS.H3C.1479.ROM from the wiki with sierra and got the circle with a line through it at boot... Don't suppose someone can PM me with a ROM that works for them in Sierra and that has TB active? I only ever ran this mobo with F2N for Windows booting for that last few years and so am playing catchup with the knowledge/experience of this mobo. Link to comment Share on other sites More sharing options...
mhaeuser Posted April 11, 2017 Share Posted April 11, 2017 Z77MXQUOAOS.H3C.1479.ROM Ancient, use the X-MASS release. Link to comment Share on other sites More sharing options...
IronManJFF Posted April 11, 2017 Share Posted April 11, 2017 Don't suppose someone can PM me with a ROM that works for them in Sierra and that has TB active? Grab this one from my own Dropbox https://www.dropbox.com/s/t73yeaqu9wooqg4/Z77MXQUOAOS.H2O.167X-MASS-SIERRA.ROM.zip?dl=0 Link to comment Share on other sites More sharing options...
yeh Posted April 12, 2017 Share Posted April 12, 2017 Hi IronManJFF, Thanks for providing the ROM, unfortunately I get the same result as the "ancient ROM" (circle with diagonal line through it)... After flashing, I set the Firmware to Optimised Defaults, and then bumped the RAM back up to 1600MHz. I've read through this forum and am I correct that some of these BIOS files initially write to the EFI partition upon first boot? If this is the case, do I also need to mount this EFI partition on another machine and clean out the partition before attempting to boot up? Link to comment Share on other sites More sharing options...
IronManJFF Posted April 12, 2017 Share Posted April 12, 2017 The prohibition sign indicates that you are trying to load unsigned kexts ... Boot with F12 and choose your RecoveryHD to boot from. Once booted (it should boot) get in Terminal and csrutil disable shutdown -r NOW Link to comment Share on other sites More sharing options...
toastie Posted April 12, 2017 Share Posted April 12, 2017 Anyone using ATI RX4x0 cards with this board under Sierra? I've been using an nVidia 650Ti for a couple years and it is starting to show its age. Given that nVidia has official drivers for the 10x0 series of cards it would seem that going that way has fewer speedbumps, but I wanted to know if anyone has experience with recent ATI cards. Link to comment Share on other sites More sharing options...
yeh Posted April 13, 2017 Share Posted April 13, 2017 The prohibition sign indicates that you are trying to load unsigned kexts ... Boot with F12 and choose your RecoveryHD to boot from. Once booted (it should boot) get in Terminal and csrutil disable shutdown -r NOW Hi IronMan, Booting into Recovery Boot is the same outcome, (circle with diagonal line) Using the same macOS (10.12.4) installed SSD, I'm successfully able to boot to the desktop using the MacMini ROM, so am scratching head here now... SIP is disabled already, I did that right at the start, but I'll double check. (I'm assuming it stays disabled no matter what ROM I apply?) This is most strange that you guys are able to boot... I'll check/clean out the EFI partition if I see anything there and see what happens... Thanks for all the input too guys, really really handy to have a community like willing to help! Link to comment Share on other sites More sharing options...
dwdrummer0 Posted April 13, 2017 Share Posted April 13, 2017 Anyone using ATI RX4x0 cards with this board under Sierra? I've been using an nVidia 650Ti for a couple years and it is starting to show its age. Given that nVidia has official drivers for the 10x0 series of cards it would seem that going that way has fewer speedbumps, but I wanted to know if anyone has experience with recent ATI cards. Im not on the ATI RX4x0 over here, but I am on a R9 280x. Its great but ill probably upgrade to a 1080 TI very soon now that the drivers are out. It really depends on what your using your computer for. If your working on a lot of Final Cut Pro projects, I would say stick with AMD as they work much better with FCPX. If your planning on working in between mac and windows and you will game in windows, then go with the 10 series graphics cards. Link to comment Share on other sites More sharing options...
yeh Posted April 13, 2017 Share Posted April 13, 2017 Hi IronMan, Booting into Recovery Boot is the same outcome, (circle with diagonal line) Using the same macOS (10.12.4) installed SSD, I'm successfully able to boot to the desktop using the MacMini ROM, so am scratching head here now... SIP is disabled already, I did that right at the start, but I'll double check. (I'm assuming it stays disabled no matter what ROM I apply?) This is most strange that you guys are able to boot... I'll check/clean out the EFI partition if I see anything there and see what happens... Thanks for all the input too guys, really really handy to have a community like willing to help! Turns out there were two folders in the EFI partition: Apple and Oz. Apple folder had a firmware.scap file present. Oz folder just had empty folders. I deleted them both, moved SSD back into quo mobo and still get circle-with-diagonal. I then refreshed the BIOS again using the BIOS that IronMan provided. Still no go though. Have flashed back to Z77MXQUOAOS.H2O.167X-MASS.SIERRA.MacMini.ROM and booted into Recovery Partition and can confirm that SIP is disabled. I really don't know what to do now as I can't think of anything else that's causing this... Link to comment Share on other sites More sharing options...
elviejo Posted April 13, 2017 Share Posted April 13, 2017 Turns out there were two folders in the EFI partition: Apple and Oz. Apple folder had a firmware.scap file present. Oz folder just had empty folders. I deleted them both, moved SSD back into quo mobo and still get circle-with-diagonal. I then refreshed the BIOS again using the BIOS that IronMan provided. Still no go though. Have flashed back to Z77MXQUOAOS.H2O.167X-MASS.SIERRA.MacMini.ROM and booted into Recovery Partition and can confirm that SIP is disabled. I really don't know what to do now as I can't think of anything else that's causing this... Did you clear the nvram after installing the Bios IronMan provided?, after that disable csr on the recovery partition and boot to macOS. Let us know what happens. Link to comment Share on other sites More sharing options...
Kynyo Posted April 13, 2017 Share Posted April 13, 2017 Just install the driver before pluggin' in then i see now problem. Link to comment Share on other sites More sharing options...
yeh Posted April 14, 2017 Share Posted April 14, 2017 Well, I give up... I think the Thunderbolt chipset is dead on my mobo. The only ROM that I can boot to desktop is Z77MXQUOAOS.H2O.167X-MASS.SIERRA.MacMini.ROM All others (even after following Tosk's flashing method back at post #3034) give me a circle-with-diagonal or stall at some point after bringing ethernet up, so this doesn't help... I even flashed back to the last official ROM being F3A and booted off Ubuntu 16.10 runtime DVD. Using modprobe, lshw & lspci – no sign of Thunderbolt at all... I also connected my Win10 SSD that I've been using with this mobo for the last 3 years and booted from that – no sign of Thunderbolt in device manager either... I know I haven't applied that Thunderbolt firmware update because it still appears in the AppStore Updates when I do successfully boot up using the MacMini ROM. Oh well... I bought this mobo to initially game with and then retire it to being the server motherboard (something I've done for 20 years now) All I want is a mobo with Thunderbolt and PCIe ports (something Apple can't provide atm) so I can hook up my SAS array and share with 10GB ethernet using Thunderbolt fibre cables. Have just purchased a Gigabyte X99 UD4 and so will have a play with clover and see how far I get. Thanks again for everyone's suggestions – such a shame my mobo's TB has failed as it would've been a great/fast ZFS NAS box. Cheers all. Link to comment Share on other sites More sharing options...
ledude Posted April 19, 2017 Share Posted April 19, 2017 Hi all For me thunderbolt work fine oob with all Mac OS. The only part that does not work is when I want to plug my macbook pro into target mode. Link to comment Share on other sites More sharing options...
kevinaba Posted April 20, 2017 Share Posted April 20, 2017 OK, I am running the XMASS.Rom with El Capitan 10.11.6 how do I update from mac3,1 to an imac14,2 so I can update to Sierra? Link to comment Share on other sites More sharing options...
IronManJFF Posted April 21, 2017 Share Posted April 21, 2017 You need a Default.plist file... Look at Post #3133 1 Link to comment Share on other sites More sharing options...
kevinaba Posted April 27, 2017 Share Posted April 27, 2017 Got default.plist in the EFI partition but it is still registering as a 3,1. I used terminal to clear NVRAM before restart. Put the plist generated by chameleon wizard for a mac 13,2. what did I miss? Link to comment Share on other sites More sharing options...
IronManJFF Posted April 27, 2017 Share Posted April 27, 2017 You should take the values for serial numbers generated by Chameleon Wizard and put them in the Defaults.plist file and place the Default.plist file in /EFI/Oz on the EFI partition. The plist file generated by Chameleon Wizard will do nothing on Ozmosis 1 Link to comment Share on other sites More sharing options...
kevinaba Posted April 27, 2017 Share Posted April 27, 2017 Still got nothing, copied the default from earlier post replaced the serial and then the serial+5 numbers on the default and then clear nvram by terminal. Still sitting at a 3,1. Link to comment Share on other sites More sharing options...
ntsmkfob Posted April 27, 2017 Share Posted April 27, 2017 Still got nothing, copied the default from earlier post replaced the serial and then the serial+5 numbers on the default and then clear nvram by terminal. Still sitting at a 3,1. Use Command Option P R boot option to reload the nvram from the defaults.plist, and make sure your boot disk is port 0, otherwise it will look on the wrong HD for the EFI partition. Link to comment Share on other sites More sharing options...
kevinaba Posted April 28, 2017 Share Posted April 28, 2017 Use Command Option P R boot option to reload the nvram from the defaults.plist, and make sure your boot disk is port 0, otherwise it will look on the wrong HD for the EFI partition. I had to unplug a hard drive to get to the main one to come up at 0. Held option command p r and I still am at 3,1. It's super frustrating, if you have anything else send it my way. Link to comment Share on other sites More sharing options...
IronManJFF Posted April 28, 2017 Share Posted April 28, 2017 DarwinDumper ! Link to comment Share on other sites More sharing options...
kevinaba Posted April 28, 2017 Share Posted April 28, 2017 DarwinDumper ! I ran it so what do you need out of it? Link to comment Share on other sites More sharing options...
IronManJFF Posted May 4, 2017 Share Posted May 4, 2017 The Boot log .. If the Defaults.plist is detected it will say so in the Boot/Firmware log Link to comment Share on other sites More sharing options...
kevinaba Posted May 8, 2017 Share Posted May 8, 2017 I don't see it in there but maybe I missed it. Apple_X64_BootLog.txt Link to comment Share on other sites More sharing options...
Recommended Posts