Jump to content


  • Content count

  • Joined

  • Last visited

About colddiver

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL

Profile Information

  • Gender
  1. Hello all, I decided to upgrade my Mobo and CPU after all the trouble I had booting the High Sierra installer. If anybody wants a 6-core/12 thread 990X chip (compatible with the GA-EX58-UD5 and 3 motherboards), message me privately and we'll negotiate something. I went for a Coffee Lake built (i7 8700K) still with an nVidia card (Geekbench score went from 15000 to 25000 and the overall build is fairly snappy). I ran into all kinds of issues with the nVidia card on this build as well. Having access to an iGPU made things a little bit easier to manage though and I think some of the fixes I had to apply on the new build could apply here as well... To boot into High Sierra with my nVidia card (1070 Ti), I needed the following (on the new build): kexts (in CLOVER/kexts/Other: FakeSMC Lilu NvidiaGraphicsFixup Shiki Clover config: boot flags: shikigva=12, -disablegfxfirmware=12 graphics: ig-platform-id=0x59120003 SMBIOS: iMac18,3 System Parameters: NvidiaWeb turned on Colddiver
  2. Hello, Having the same issue (getting the prohibited sign as well). I tried both to install directly (running the Install High Sierra from the Application folder) and by creating an installer like I usually do on a spare external hard drive (eSata). I was able to load the installer only once from the external hard drive but then, I could not see any of my internal hard drives when it was time to select the install location. Was not able to reboot it again for some reason. I then switched to a spare internal hard drive to setup the bootable installer. I'm using the latest version of Clover and tried both to load from my existing/working Sierra clover config and a generic one. Both failed to boot the installer (prohibited sign again). Tried removing all kext except FakeSMC, reinstalling Clover with different options (using SATA instead of BiosBlockIO)... Nothing seems to work. Boot always stalls after a whole bunch of AppleUSBHostResources@ messages. I didn't try launching the installer without apfs yet. Tried with kext installed in CLOVER/kexts/other or CLOVER/kexts/10.13 without success. Could anyone with a working High Sierra setup on an UD5 board share their clover config and clover installation options? My box: EX58-UD5 CPU: i7-990X GPU: nVidia GTX 670 I see a lot of reports of issues with nVidia GPUs and High Sierra. I am starting to suspect that this may be related to my problem. Out of curiosity, are any of the other seeing the prohibited sign using an nvidia GPU? Thanks! Colddiver
  3. Success (finally!). Couple of notes: The command to reformat the EFI partition is this: newfs_msdos -v EFI -F 32 /dev/diskXsX (need the -F 32 bit - otherwise you will get an error) I'm running with no DSDT and no custom kext installed in SLE (I started from a fresh Yosemite install to be sure I had a pristine setup) Doing audio with Toleda's script (make sure you mount your EFI partition first) Otherwise, I have followed @ROBASEFR's instructions What works: Sleep (though I can only wake with the power button for now) Reboot is still way too slow (like not rebooting after 10 min.) Network works with the RealtekRTL81xx.kext from Digital Dreamer's script (installed in kext/10.10) This is now my main setup. I'll try to keep working on the things that are not yet perfect... Colddiver
  4. Yep - went as far as running toleda's script. The scripts asks me to confirm if the codec is 885. My understanding is that our boards are using 889. When I run the script using the default values, it runs fine and the kext gets installed in my CLOVER/kext/10.10 folder. The kext does not get loaded however (owner/permissions issues). I tried setting up the permission manually and I had the same issue. When I run toleda's script using the 889 codec, the script complains about something not being a supported config (don't recall the exact error). I had audio stuff in my DSDT file. I think this was causing some problems with toleda's scripts so I used another DSDT that someone (not sure who) had posted along with a clover config. With my previous DSDT, toleda's scripts were complaining no matter what I did. With the new one, I get the error using the 889 codec but not the 885. Lastly, I did not try sleep yet but shutdown seems to take forever (not being the patient type, I end up holding the power button until the computer shuts down)... Anyway, this is where I am at at the moment (did not have more time to troubleshoot this yet). Still, being able to boot and have network is a great step in the right direction... Also, being still new with Clover, I am not sure what is the process to follow when messing around with kexts. Whenever we change the content of CLOVER/kext/10.10, do we need to rebuild caches, setup kext permissions, etc.? If so, what is the best way to do this? I played a bit with kext wizard but it was not obvious to me how/if this tool handled kext installed on the EFI partition... Colddiver
  5. Ah! Network is a go. I haven't had any success yet with the Toleda script though... Colddiver
  6. Partial success! Was able to boot Yosemite from Clover (finally!). I had no network and no sound though. I will try the toleda thing for audio. For network, I had the same RealtekRTL81xx.kext I used with the scripted setup in my CLOVER/kext/10.10 folder but somehow it didn't load. FakeSMC loaded fine though. Will be trying to troubleshoot the audio and network issues - if any of you has any pointers, let me know. Getting closer now at least! Colddiver
  7. VirusX, Thank for your screenshots. Yours are fairly different from the one from @robasefr. From what I gather, you are not installing in the EFI partition. I will play with that and see what happens... Colddiver
  8. @ROBASEFR I'm trying to make the switch to Clover. Attempted this a year ago and didn't have much luck... In post 4409, you provide two screenshots for the clover custom install setting. The 2 screenshots are identical. I'm assuming one of them should show the bottom portion of the options (drivers, etc.). Would you be so kind to upload the other screenshot? Thanks! Colddiver
  9. All right, I am up and running… Had a lot of issues initially booting into the installer. The installer would crash almost immediately. When using verbose, I found that it crashed only after loading all the kext (last lines were): Starting Darwin x86_64 Boot Args: boot-uuid=01367B6E-6307-34D4-BC3B-C8861296B07 rd=*uuid -f -v Solution: unplug most USB devices (except keyboard and mouse)... Rebooted fine after that and I was able to install to a spare drive and then, after testing, onto my main OS X drive. I'm using dood's DSDT native power management and a minimal set of KEXT. Sleep works fine. Audio only works with KEXT (didn't need them before). So far so good... Looks like I may get a few more years out of this rig! Colddiver
  10. Hey MAJ, Tried the script but it failed on my system with the 10.9 installer from the App Store. Tried to create a boot disk and got an error that no kernel was found (install failed)... I will try creating the boot disk manually but I thought you would like to know... Colddiver
  11. Made some progress... Looks like my issues are entirely dsdt-related. I started from a fresh DSDT, applied the native power management stuff from dOOd's thread and I was able to restore sleep. Interestingly enough, I wasn't able to restore the Orange Icon fix in the new DSDT. The "restart after power failure" option never came back but sleep works OK nevertheless. I will try again from Cruisar's original dsdt (I had it modified over the years looks like some of my edits started causing some issues). Compairing dOOd's dsdt with Cruisar's is quite revealing. I'm not sure which one is best but they are significantly different (lots of devices not having the same names, etc.). I was hoping to do an hybrid dsdt by combining the best of dOOd's and Cruisar but this turned out to be much more complex than anticipated (too many differences between the two). Colddiver
  12. Changing MacPro5,1 to 4,1 made no difference whatsoever...
  13. Hello all, Well... I have spent a significant amount of time trying to troubleshoot my setup (I'm using Cruisar's DSDT with only FakeSMC, IONetworking and AppleRTC kexts). My rig has been upgraded over the years to a GTX670 superclocked (4GB) and a Core i7 990X (6 cores). As mentioned in a previous post, my system started misbehaving a couple of weeks ago (it used to work perfectly). Here are the issues: The option to "Restart after power failure" in Energy System Prefs is gone. Without it, sleep does not work (computer restarts instead of waking up from sleep) Overall performance was getting slower than it should (Aperture took a long time to process RAW images, compiling stuff with XCode was longer than usual, etc.). Not being certain if the issues were caused by a recent upgrade to 10.8.3 or to a newer Chimera, I took the following steps to troubleshoot my rig: Reinstalled 10.8.1 from the ESD on a spare drive Rebooted using my original dsdt smbios and org.chameleon.boot.plist RESULT: "restart after power failure" option still gone - sleep still broken although overall performance seems better Upgraded to 10.8.2 using Combo updater, installed nvidia drivers (which were known to work better for the GTX670), rebooted RESULT: no improvements Downloaded a fresh copy of Cruisar's DSDT and installed in my /Extra folder & rebooted RESULT: no improvements Switched bootloader to Chameleon (latest version available from SVN), rebooted Reboot failed Switched back to Chameleon but used the version that comes with a freshly downloaded version of MAJ's script (instead of the latest version from SVN), rebooted RESULT: rebooted fine but no improvements (restart after power failure still gone, sleep not working) I am running out of things to try... Anybody has any ideas? Here are some relevant config info: SMBIOS is using MacPro5,1 (will try 4,1 shortly) boot.plist has no kernel flags set but has options turned on to generate P and C states Colddiver
  14. Hello all, I messed around in my BIOS and Hard Drive setup (repartitioned and cloned a Windows drive - didn't touch Mountain Lion) and I somehow managed to lose the option to restart automatically after power failure. This now breaks sleep on my setup. I'm at a loss as to what happened here and I can't seem to figure out how to recover the option. If anybody has any pointers, please let me know. While attempting to fix this: I updated to the latest Chimera I didn't touch my dsdt.aml (I'm using one similar to Cruisar) I didn't touch my smbios.plist I did reinstall FakeSMC I also recently upgraded to 10.8.3... I keep a spare Mountain Lion partition for testing purpose. Since someone was encouraging us to try Clover, I did it a go. I followed the instructions I could find on the web the best I could but I end up with a kernel panic on boot (I copied over my dsdt.aml and configured my smbios settings to match what I already had in Chimera). If someone here had some success with it, perhaps it would be a good idea to share a couple of pointers, especially if you are using a heavily patched dsdt to minimize the number of kext you have to load. Couple of specific questions: Are you letting clover generate the P and C states? Have you been messing with custom UUID? What SystemParemeters are you using? If you have a dsdt configured, are you leaving the FixDsdtMask = 0x0 as is or should it be removed? Clover look very promising so I will attempt to troubleshoot my install further when I get a chance (the first step will be to try to catch which kext is causing the KP before the system reboot). Any pointers to kickstart my clover learning process will be very much appreciated...
  15. iLLNESS, Sorry about that! I corrected the link in my previous post (was missing a 1 at the end of the topic ID). Colddiver