Search results

Thanks for your reply. This didnt seem to make any difference. also this problem existed before i installed any web drivers. for now i have dual wired a screen to alternate between mobo and GTX. why do you think this has changed in High Sierra (worked fine in Sierra)

did you fix this? i get the same error. i installed using 'boot igfx 1st' in bios (and nvidia GTX770 removed) and the install went smooth. I installed web drivers and rebooted with the GTX card inserted and all is fine, Card is detected and i can use 3 screens on it but......i'm still booting...

how can i add a 3sec loading timer to clover?

Sorry currently booting 'igfx' The top 2 screens are DVI from 770 Card. The right screen is usually Display Port on 770 and if i plug it in to Display Port i get the 3rd desktop but then i can't see clover/bios on boot. And OSX thinks i've got 4 screens (3x770 and 1xIGFX) if i change bios to...

i would like to just use 3 screens on the 770 card but if i try to bios boot from PCI i juat get all 3 screens black with "IOConsoleUsers: gIOScreenLockState" if i boot igfx i get 2 screens working (770 card) and igfx screen says "IOConsoleUsers: gIOScreenLockState" i just realised i havent...

thanks again for your help! ok so i ran a clean install of clover (4392) to give myself a clean starting point, then applied the kext and drivers64 changes. i didn't do the rt variables as i couldnt figure out how to create the ROM and MLB (asking me to create a UUID?) however it now boots...

clover attached CLOVER.zip

did you see the addition to above post (clover config?) more views of the same KP using different flags in CBM i will extract my clover folder from the EFI and attach asap

before reading this i re-established the Bios settings (not serial though now done!) - Load optimize defaults - VTd is greyed out but i turned of intel virtualisation - XMP to profile 1 - booting igfx first (not PCI SLot1)....... .......and i got to the installer! I completed install to SSD...

i'm using unibeast 8.1 to install High Sierra on my Mobo (GA-Z87X-OC Force) but keep getting to the same point then stops. i also tried a RehabMan style build (the one i used for my laptop) and this stops at the same place. here are the screenshots up to the crash

:-)

Yes working fine and running off a 2nd NVMe drive. Audio, WiFi, Ethernet, Battery Status. I created a fresh installer (RehabMan style - follow his guide to the letter then compare with my clover folder) i included my Clover folder from the NVMe drive (not the usb installer but it's pretty much...

Hi Gabry. how far do you get with the install. Ive managed to get 10.13 to install on my Alienware 17 r3. Currently running on both HDD and M2 drives. Ive coppied basic clover and both boot fine. However i have gone no further yet......(sound, wifi, ethernet, etc) can you boot verbose (-v)...

I ended up going for Sierra and yes it worked except audio but I gave up again due to work.

I've had this desktop running nicely for some time (Yosemite/El Cap/Sierra) and use it mainly for Pro Tools (HD 12.7.1) it started developing a habit of 'dropping' my audio hardware (Firewire Digi 002R on FW Card) so i replaced with a USB Interface (Focusrite 18i20) and now its doing the same...

Yay! Success! Thanks RehabMan. (like the man says 'go back and read post #1') i was following instructions for 'dual NVMe drive' not 'dual NVMe drive without leaf node' instructions here's the code that fixed my system: // Inject bogus class-code for NVMe SSD to prevent IONVMeFamily.kext...

are you suggesting that i add SSD0 or PXSX as the leaf node? or because i am using 960EVO (Special injections required for 10.11.x and Samsung 960 EVO (or other 144d:a804 NVMe device)? (I'm using 10.12.03) both of the ID's are displayed in the Device Manager image (RP09 and RP13)

sorry typo revision i used _SB.PC10.RP09.SSD0 _SB.PC10.RP13.SSD0 to create the .aml

I followed the Post #1 guide but still not seeing either of my 2 x MVMe drives (1 x Toshiba and 1 x 960 EVO) I used _SB_.PCI0.RP09.SSD0 _SB_.PCI0.RP13.SSD0 to create the .aml created --spoof .kext and copied to USB/ACPI/patched for installer and HDD/S/L/E using Kext Utility I don't see...

..............it's as if you breathe fire into the belly of the mountain! SATA-100-series-unsupported.kext seems to be missing. <--------didn't seem to make any difference EmuVariableUefi-64.efi generally required on Skylake. Also missing. <------------didn't seem to make any difference...