All work 10.10, 10.11, 10,12
camera not work in 10.13, 10.14
You need SwitchResX that the screen does not freeze
Custom resolutions: Back porch - lines change to 2
UEFI boot moded bios https://github.com/Thiblizz/l502x-modded-bios
For 10.14 you need: HD3000 Fix for Mojave.zip Installed in S/L/E
So at boot you will have two options: boot macOS Mojave or Windows 10
STEP 2 - Using a drive without Windows 10 installed
Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
Proceed with a Windows 10 UEFI install.
After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover.
If Windows 10 is not detected or able to boot, then verify you installed Windows 10 as UEFI and not MBR ----> ( Read step 2 - For a drive with Windows 10 installed )
STEP 2 - Using a drive with Windows 10 already installed
Verify your Windows install is GPT / UEFI or MBR / Legacy BIOS.
If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen.
But if Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
then this is most likely because Windows drive is MBR ( Legacy BIOS ). You can easily convert MBR to GPT using Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again )
If Windows 10 install is MBR / Legacy BIOS then simply convert to GPT / UEFI following instructions below ( read video summary and view video )
** To use Windows 10 MBR2GPT tool you must have Windows 10 version 1703 ( creators update ) or later and less than 3 partitions on
the Windows 10 drive **
Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management )
Reboot into Windows PE ( Advanced Startup )
Convert from MBR Legacy BIOS to GPT UEFI ( using commands below )
Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )
After conversion Windows 10 is ready to use at the Clover boot menu
I'm trying to install High Sierra 10.13.3 on an ASUS N552VW laptop, and I get stuck after this message:
"could not recover SATA HDD after 5 attempts, terminating"
And some other warnings afterwards.
CPU: Intel Skylake 6700HQ 2.6GHz
RAM: 16GB DDR4
2TB HDD + 128GB SSD
GPU: Intel HD Graphics 530 + Nvidia GTX960m
I'm installing using a 16GB USB3 flash drive on one of HDD volumes (UEFI Mode)
I uploaded the verbose log and clover config.plist
hello to everyone, i managed to install mojave on my asus ux303ub with i5 cpu and now sleep does not work when i press sleep display turns black and pc stays on and then i have to force shut down by holding power button in order to restart pc ,by the way i used the clover folder from a guide on the internet, any help would be appreciated, thanks
I have a Kingston HyperX Predator PCIE-SSD (model: SHPM2280P2H) matched with an X58 motherboard (legacy bios). The card has a Marvell 88SS9293 controller with an Option ROM which allows it to be detected on my motherboard as a bootable drive - listed as "IDE: Kingston SHPM". As my BIOS is non-UEFI, I assume the Option ROM presents it in IDE mode instead of AHCI.
I use Clover legacy with BiosBlockIO to get around this, and it works well - Clover detects my drive and allows me to install macOS onto it and use it as a boot drive. macOS detects the drive correctly as a SATA AHCI drive. I guess Clover correctly detects (configures?) the Option ROM into AHCI mode and presents it as such to macOS - getting full speed read Read/Write performance. All is well.
Except waking from sleep. When waking from sleep, depending on clover config options + dsdt, I either get an immediate reboot or hang on black screen that requires hard reset. I eventually realised that nothing after entering sleep mode is recorded in the logs, its completely empty until next boot up. This makes me think that on resume from sleep, macOS isn't seeing the drive anymore (hence can't even write to logs). My assumption here is that the Option ROM is presenting/configuring the card in IDE mode, which is not what macOS is expecting.
This post describes the problem:
and also has a solution: in dsdt, simply write the correct values to 0x40, 0x41, 0x42 (which must be the BAR0 register?) to configure Option ROM to use AHCI mode. But I have no idea what address BAR0 is on the Marvell 88SS9293 - there appears to be no documentation whatsoever on this controller available online!
I managed to dump the ROM using Linux sysfs, but don't have the skills to disassemble/decipher the binary to find the correct addresses. Anyone with such experience able to help?? I've attached the ROM dump and lspci output.