True and on top of that, I don't see anyone else running to this thread to jump in with answers so, yeah. We both had to take a step back and just stay with 10.13.1 for now.
Nope and I will say this... Using MultiBeast, this build would boot so fast it would make your head spin. Vanilla Clover seems to take longer on the gigabyte splash screen.
For some reason, after using MultiBeast, I still could not boot from the drive directly. However, I decided to go ahead and do a clean install. I used the vanilla clover method this time and placed the Lilu kext, Fake SMC, Graphics Fix, etc in the Clover EFi kext folder myself. Downloaded the...
I changed the boot order in the bios from the USB installer to the High Sierra Drive and now the Clover Update is showing as well as these holiday Clover skins. It is also booting Windows now. The interesting thing is I swapped the Nvidia card with my old ATI Radeon card and it didn't change...
I opened the desktop and it gave me an Nvidia notification for an update. I did it and it still seemed to have a bit of screen flickering when using chrome or when I access the App tray. There was no screen flickering for any of my recording software so I was going to live with the flickering on...
As I have read the forums, most people are instructed to update their installer with the latest version of clover or swap out various kexts after update errors occur. So I have always been in the habit of doing those things prior to the update so as to avoid these situations and generally that...
The boot order never changed. In my bios, the Installer USB is in the 1st priority slot. Before this update, I had no issues with booting into High Sierra, a separate El Capitan drive, or my windows drive from the Clover Bootloader screen. They all worked. After this 10.13.2 update, the only...
Unfortunately, I updated Clover to the latest version and then performed the update from the App Store. It installed, rebooted as normal and then installed on my drive. It then rebooted again to the Clover selection screen. After selecting the Sierra drive, the Apple symbol appears and the bar...
I have the same issue. I'm missing the exact steps that you took to correct it. My set up worked perfectly for 2 weeks and as soon as I removed the installer usb, I received the same error as you did.
GA-Z170X-GAMING G1 EXTENDED ATX (rev. 1.0)
CPU:
Intel Core i7 7700k
Graphics:
Nvidia GeForce...
That's interesting. My startech Thunderbolt cable works perfectly but my Apple one does not. Now I'm wondering if the daisy chain might work if I was using startech for both....hmmm. I've never been able to make an apple firewire to Thunderbolt adapter work either. Had two new ones to test at...
Well, I can say that since I two ports, mine works consistently as long as I don't try to daisy chain any devices. Honestly, I only have the Caldigit dock and the Seagate Thunderbolt Drive so I imagine I'm good because if I purchased an Apogee Ensemble Thunderbolt, I would unplug the Caldigit...
This is excellent to know. It makes me feel very positive that as I put this next build together using the Z170x G1 extended, that there will be much less of a hassle getting those Thunderbolt ports fired up. I love the teamwork on this site.
I made the adjustments to match your settings to see if it made any difference. Once I rebooted into osx, I got a 0 with the slash through it.... Soooooo, I put everything back as it was previously and Thunderbolt went back to working for one device per port with no daisy chaining. So, I'm just...
Focus on the last line on the BIOS Screen, the Reserved I/O. I adjusted it from 0 to 8 and that caused the Thunderbolt to show up consistently. Last night, I increased it to 16 to test the allowance to daisy chain thunderbolt devices from one port, but it made no difference on that issue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.