Jump to content
ErmaC

Clover problems report & features request

661 posts in this topic

Recommended Posts

I would like to report a bug in v4630 Legacy Bios Install, boot to cursor of death.  :)

 

Steps to reproduce:

 

1)  I used a Samsung SSD EVO 860 512GB to format Mac OS Extended (Journaled) then freshly install MacOS 10.13.6.

2)  Used flash drive with Clover to boot fresh MacOS install

3)  Installed Clover v4630 onto SSD fresh no prior clover versions.

 

Steps to Solve:

 

1)  install a prior known working version onto SSD, I went all the way back to v4097.

2)  Upgraded to v4630

3)  No issues encountered.

Edited by oSxFr33k
Clerical error on version number

Share this post


Link to post
Share on other sites
Advertisement
1 hour ago, oSxFr33k said:

I would like to report a bug in v4360 Legacy Bios Install, boot to cursor of death.  :)

 

Steps to reproduce:

 

1)  I used a Samsung SSD EVO 860 512GB to format Mac OS Extended (Journaled) then freshly install MacOS 10.13.6.

2)  Used flash drive with Clover to boot fresh MacOS install

3)  Installed Clover v4360 onto SSD fresh no prior clover versions.

 

Steps to Solve:

 

1)  install a prior known working version onto SSD, I went all the way back to v4097.

2)  Upgraded to v4360

3)  No issues encountered.

 

Hi

 

Latest release is r4630. You can use it instead of r4360.

Share this post


Link to post
Share on other sites

 

I can confirm this problem.  When installing the latest Clover versions in legacy mode on a new drive, boot0af is not being correctly installed in the MBR (but boot1f32 installs OK in the PBR).  Relevant part of Clover r4636 install log shown in spoiler...

 

Spoiler

 


Installer version: v2.4k r4636 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *53.7 GB    disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS macOS                   53.3 GB    disk0s2

/dev/disk1 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *512.5 MB   disk1
   1:                 DOS_FAT_32 CLOVER                  510.7 MB   disk1s1

======================================================
Backing up EFI files

Backing up stage2 file /Volumes/CLOVER/EFIROOTDIR/boot  to /Volumes/CLOVER/EFI-Backups/r4636/2018-08-05-22h17/boot
Backing up /Volumes/CLOVER/EFIROOTDIR/EFI folder to /Volumes/CLOVER/EFI-Backups/r4636/2018-08-05-22h17/EFI
Current Active Partition: 1

Stage 0 - Writting boot0af to /dev/disk1
dd: /Volumes/CLOVER/usr/standalone/i386/boot0af -> /dev/disk1

Stage 1 - Writting boot1f32 to /dev/rdisk1s1
dd if=/dev/rdisk1s1 count=1 bs=512 of=/tmp/origbs
boot volume format is FAT32
cp /tmp/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=/tmp/newbs of=/dev/rdisk1s1

Setup Active Partition to be: 1
New Active Partition: 1

Stage 2 - Written boot6 (x64) to /Volumes/CLOVER/boot

======================================================
=========== Clover EFI Installation Finish ===========
======================================================

 

 

 

 

Seems like regression caused by r4541 (uses dd to install boot sectors instead of fdisk440).  Using Bootice 64 bit in windows to install boot0af to MBR (or installing boot sectors with Clover version older than r4541 first) restores booting ability.

 

Edit Can manually install boot0af to target disk MBR with dd from terminal ...

1.  Download i386 folder (attached to this post) with boot0af inside to your ~/Downloads folder

2.  Determine disk number of target disk with diskutil list command - in my case, USB = disk1

3.  Unmount target disk

sudo diskutil unmountDisk rdisk1

4.  Write boot0af to MBR with dd

sudo dd if=/dev/rdisk1 bs=512 count=1 of=~/Downloads/i386/origMBR
cp ~/Downloads/i386/origMBR ~/Downloads/i386/newMBR
sudo dd if=~/Downloads/i386/boot0af of=~/Downloads/i386/newMBR bs=440 count=1 conv=notrunc
sudo dd if=~/Downloads/i386/newMBR of=/dev/rdisk1 count=1 bs=512
sudo diskutil mountDisk rdisk1

 

i386.zip

Edited by fusion71au
Procedure to manually install boot0af with dd from terminal

Share this post


Link to post
Share on other sites
6 hours ago, Matgen84 said:

 

Hi

 

Latest release is r4630. You can use it instead of r4360.

 

Sorry meant 4630. 

Share this post


Link to post
Share on other sites

I had rev 4458 on boot SSD. Updated it to 4630 and thereafter the Hackintosh rebooted after clover screeen.

Had to boot from USB stick and restore the EFI partition.

 

Share this post


Link to post
Share on other sites

I tried Windows 10 on my hackintosh #1 on the sig. Same BIOS settings that I use with macOS. I noticed that on recent Windows 10 builds when I turn on or reboot to do a full reboot, BIOS logo screen is completely disabled. It will instantly go to the Windows logo.

 

On Clover/macOS I'll see the BIOS logo screen and after that the Apple logo. Would it be possible to bypass BIOS screen completely with Clover, so that it would go directly to Apple logo on boot?

Share this post


Link to post
Share on other sites

[PROBLEM REPORT]

Hello, I'm using FileVault 2 of macOS Mojave beta 6.

Clover version 4644

The EFI login screen took too long(as long as booting the kernel).

When I use the -v, there are spamming of message "smcProtocol->SmcReadValue failed for key "blah"" after the LoginWindow loaded

Not sure if it is related to SMCHelper or not?

Thanks

Edited by Trung_Nguyen
add clover version

Share this post


Link to post
Share on other sites

Yes, it is related to SMCHelper. It reported that the key "blah" is absent is nvram.

It should be looking in boot.log as follow

1:300  0:060  Loading nvram.plist from Vol 'MacHD' - loaded, size=3072
1:327  0:026  === [ PutNvramPlistToRtVars ] =============================
1:327  0:000   Adding Key: ActualDensity: Size = 2, Data: E1 00 
1:327  0:000   Adding Key: BootCampHD: Size = 32, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 02 1F 03 12 0A 00 00 00 00 00 00 00 7F FF 04 00 
1:327  0:000   Adding Key: DensityThreshold: Size = 2, Data: 96 00 
1:327  0:000   Adding Key: EFILoginHiDPI: Size = 4, Data: 01 00 00 00 
1:327  0:000   Skipping EmuVariableUefiPresent
1:327  0:000   Adding Key: IOHibernateRTCVariables: Size = 44, Data: 41 41 50 4C 01 00 00 00 99 06 1D 18 CE 2D 50 43 FA C4 5C 8D AD DA D6 32 7D 5A F6 C1 7F 0E F1 DE 5B 23 C8 31 49 E2 52 E2 25 48 BD 68 
1:327  0:000   Adding Key: LocationServicesEnabled: Size = 1, Data: 01 
1:327  0:000   Adding Key: backlight-level: Size = 2, Data: 01 01 
1:327  0:000   Adding Key: boot-args: String: Size = 10, Val = 'nvda_drv=1'
1:327  0:000   Adding Key: bootercfg: Size = 2, Data: 28 00 
1:327  0:000   Adding Key: csr-active-config: Size = 4, Data: E7 03 00 00 
1:327  0:000   Adding Key: efi-boot-device: Size = 216, Data: 3C 61 72 72 61 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 50 72 6F 76 69 64 65 72 43 6C 61 73 73 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 49 4F 4D 65 64 69 61 3C 2F 73 74 72 69 6E 67 3E 3C 6B 65 79 3E 49 4F 50 72 6F 70 65 72 74 79 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 55 55 49 44 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 39 42 38 46 33 42 39 41 2D 46 31 33 45 2D 34 36 44 41 2D 41 38 45 38 2D 43 42 42 34 35 39 30 34 45 31 35 34 3C 2F 73 74 72 69 6E 67 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 61 72 72 61 79 3E 
1:327  0:000   Adding Key: efi-boot-device-data: Size = 74, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 02 1F 03 12 0A 00 00 00 FF FF 00 00 04 01 2A 00 05 00 00 00 90 19 75 0E 00 00 00 00 D8 71 BA 16 00 00 00 00 9A 3B 8F 9B 3E F1 DA 46 A8 E8 CB B4 59 04 E1 54 02 02 7F FF 04 00 
1:327  0:000   Adding Key: fakesmc-key-#KEY-ui32: Size = 4, Data: 00 00 00 11 
1:327  0:000   Adding Key: fakesmc-key-$Adr-ui32: Size = 4, Data: 00 00 03 00 
1:327  0:000   Adding Key: fakesmc-key-$Num-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BATP-flag: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-BBIN-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BEMB-flag: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BNum-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-CLKH-{clh: Size = 8, Data: 00 00 70 80 00 01 19 40 
1:327  0:000   Adding Key: fakesmc-key-CLKT-ui32: Size = 4, Data: 00 01 3C B8 
1:327  0:000   Adding Key: fakesmc-key-EPCI-ui32: Size = 4, Data: 06 40 07 00 
1:327  0:000   Adding Key: fakesmc-key-HE0N-ui8: Size = 1, Data: 0E 
1:327  0:000   Adding Key: fakesmc-key-MSAc-ui16: Size = 2, Data: 00 00 
1:327  0:000   Adding Key: fakesmc-key-MSDW-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-MSFW-ui8: Size = 2, Data: 01 00 
1:327  0:000   Adding Key: fakesmc-key-MSPS-ui16: Size = 2, Data: 00 03 
1:327  0:000   Adding Key: fakesmc-key-MSTc-ui8: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-MSWr-ui8: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-NATJ-ui8: Size = 1, Data: 02 
1:327  0:000   Adding Key: fakesmc-key-NATi-ui16: Size = 2, Data: 00 1E 
1:327  0:000   Adding Key: fakesmc-key-NTOK-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-RBr -ch8*: Size = 8, Data: 64 32 00 6A 31 33 00 00 
1:327  0:000   Adding Key: fakesmc-key-REV -ch8*: Size = 6, Data: 02 03 0F 00 00 36 
1:327  0:000   Adding Key: fakesmc-key-RMde-char: Size = 1, Data: 41 
1:327  0:000   Adding Key: fakesmc-key-RPlt-ch8*: Size = 8, Data: 64 32 00 00 00 00 00 00 

 

Share this post


Link to post
Share on other sites
2 hours ago, Slice said:

Yes, it is related to SMCHelper. It reported that the key "blah" is absent is nvram.

It should be looking in boot.log as follow


1:300  0:060  Loading nvram.plist from Vol 'MacHD' - loaded, size=3072
1:327  0:026  === [ PutNvramPlistToRtVars ] =============================
1:327  0:000   Adding Key: ActualDensity: Size = 2, Data: E1 00 
1:327  0:000   Adding Key: BootCampHD: Size = 32, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 02 1F 03 12 0A 00 00 00 00 00 00 00 7F FF 04 00 
1:327  0:000   Adding Key: DensityThreshold: Size = 2, Data: 96 00 
1:327  0:000   Adding Key: EFILoginHiDPI: Size = 4, Data: 01 00 00 00 
1:327  0:000   Skipping EmuVariableUefiPresent
1:327  0:000   Adding Key: IOHibernateRTCVariables: Size = 44, Data: 41 41 50 4C 01 00 00 00 99 06 1D 18 CE 2D 50 43 FA C4 5C 8D AD DA D6 32 7D 5A F6 C1 7F 0E F1 DE 5B 23 C8 31 49 E2 52 E2 25 48 BD 68 
1:327  0:000   Adding Key: LocationServicesEnabled: Size = 1, Data: 01 
1:327  0:000   Adding Key: backlight-level: Size = 2, Data: 01 01 
1:327  0:000   Adding Key: boot-args: String: Size = 10, Val = 'nvda_drv=1'
1:327  0:000   Adding Key: bootercfg: Size = 2, Data: 28 00 
1:327  0:000   Adding Key: csr-active-config: Size = 4, Data: E7 03 00 00 
1:327  0:000   Adding Key: efi-boot-device: Size = 216, Data: 3C 61 72 72 61 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 50 72 6F 76 69 64 65 72 43 6C 61 73 73 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 49 4F 4D 65 64 69 61 3C 2F 73 74 72 69 6E 67 3E 3C 6B 65 79 3E 49 4F 50 72 6F 70 65 72 74 79 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 55 55 49 44 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 39 42 38 46 33 42 39 41 2D 46 31 33 45 2D 34 36 44 41 2D 41 38 45 38 2D 43 42 42 34 35 39 30 34 45 31 35 34 3C 2F 73 74 72 69 6E 67 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 61 72 72 61 79 3E 
1:327  0:000   Adding Key: efi-boot-device-data: Size = 74, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 02 1F 03 12 0A 00 00 00 FF FF 00 00 04 01 2A 00 05 00 00 00 90 19 75 0E 00 00 00 00 D8 71 BA 16 00 00 00 00 9A 3B 8F 9B 3E F1 DA 46 A8 E8 CB B4 59 04 E1 54 02 02 7F FF 04 00 
1:327  0:000   Adding Key: fakesmc-key-#KEY-ui32: Size = 4, Data: 00 00 00 11 
1:327  0:000   Adding Key: fakesmc-key-$Adr-ui32: Size = 4, Data: 00 00 03 00 
1:327  0:000   Adding Key: fakesmc-key-$Num-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BATP-flag: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-BBIN-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BEMB-flag: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BNum-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-CLKH-{clh: Size = 8, Data: 00 00 70 80 00 01 19 40 
1:327  0:000   Adding Key: fakesmc-key-CLKT-ui32: Size = 4, Data: 00 01 3C B8 
1:327  0:000   Adding Key: fakesmc-key-EPCI-ui32: Size = 4, Data: 06 40 07 00 
1:327  0:000   Adding Key: fakesmc-key-HE0N-ui8: Size = 1, Data: 0E 
1:327  0:000   Adding Key: fakesmc-key-MSAc-ui16: Size = 2, Data: 00 00 
1:327  0:000   Adding Key: fakesmc-key-MSDW-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-MSFW-ui8: Size = 2, Data: 01 00 
1:327  0:000   Adding Key: fakesmc-key-MSPS-ui16: Size = 2, Data: 00 03 
1:327  0:000   Adding Key: fakesmc-key-MSTc-ui8: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-MSWr-ui8: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-NATJ-ui8: Size = 1, Data: 02 
1:327  0:000   Adding Key: fakesmc-key-NATi-ui16: Size = 2, Data: 00 1E 
1:327  0:000   Adding Key: fakesmc-key-NTOK-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-RBr -ch8*: Size = 8, Data: 64 32 00 6A 31 33 00 00 
1:327  0:000   Adding Key: fakesmc-key-REV -ch8*: Size = 6, Data: 02 03 0F 00 00 36 
1:327  0:000   Adding Key: fakesmc-key-RMde-char: Size = 1, Data: 41 
1:327  0:000   Adding Key: fakesmc-key-RPlt-ch8*: Size = 8, Data: 64 32 00 00 00 00 00 00 

 

Well, I use AptioMemoryFix, not EmuVariableUEFI, also, I can't find any lines of these in bdmesg

Edited by Trung_Nguyen

Share this post


Link to post
Share on other sites

 

Thanks a lot :) 

 

Is it possible to have a USB icon for external volumes Embedded Theme? Please.

Share this post


Link to post
Share on other sites
1 hour ago, Slice said:

It is already here.

 

I explained myself badly: I want to talk about the USB logo on vol-external icon  and vol_clover icon Embedded theme.

screenshot8.png

vol_external.png

Share this post


Link to post
Share on other sites
1 minute ago, Matgen84 said:

 

I explained myself badly: I want to talk about the USB logo on vol-external icon  and vol_clover icon Embedded theme.

screenshot8.png

vol_external.png

This is screenshot of Clover 4639

Share this post


Link to post
Share on other sites
21 minutes ago, Slice said:

This is screenshot of Clover 4639

 

Correct. I build and try Clover 4646: it's OK. Great job for new Embedded theme :)

Share this post


Link to post
Share on other sites

Can anyone explain why I get no icon for my main APFS Mojave beta volume when using the new embedded theme (just the yellow and gray striped 'no image' box). The volume is located on the NVME SSD in my hack. All the other APFS volumes show up fine (including a clone of the main volume on another SATA SSD)

Thanks very much for any help here...

Share this post


Link to post
Share on other sites

Hello @Slice, sorry for reporting this issue..

With "EmbeddedThemeType=Dark" key enabled on config.plist, it breaks another theme's font appearance on Clover GUI.

Thanks.

screenshot4.png

Share this post


Link to post
Share on other sites
31 minutes ago, Badruzeus said:

Hello @Slice, sorry for reporting this issue..

With "EmbeddedThemeType=Dark" key enabled on config.plist, it breaks another theme's font appearance on Clover GUI.

Thanks.

 

Yes, it influences. Use this key only if embedded theme.

There will be more changes in theme support so I somehow will resolve this problem too.

 

Share this post


Link to post
Share on other sites
fakesmc-key-BBIN-ui8	%01
fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j30%00%00%00%00%00
fakesmc-key-RBr -ch8*	branch%00%00
EFILoginHiDPI	%00%00%00%00
efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>D1D17580-8D7B-44EB-9587-9744768E0ADE</string></dict></dict></dict></array>
fakesmc-key-#KEY-ui32	%00%00%00%11
SystemAudioVolumeDB	%00
prev-lang:kbd	en:0
fakesmc-key-BATP-flag	%00
fakesmc-key-MSTc-ui8	%00
LocationServicesEnabled	%01
security-mode	none
fakesmc-key-BNum-ui8	%01
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%02%02%0f%00%00D
fakesmc-key-MSPS-ui16	%00%03
fmm-computer-name	Trung%e2%80%99s MacBook Pro
backlight-level	%0a%07
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%06`%07%00
bluetoothActiveControllerInfo	%97%81<A%00%00%00%00%14%1a$%fdR2%b8}
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	%1f
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%02%00%00%00%80`%1f%00%00%00%00%00%08%d2%af%1d%00%00%00%00%80u%d1%d1{%8d%ebD%95%87%97Dv%8e%0a%de%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBX`%efZ%8f@%97M%b5d%02%b2.C%f9%a4%7f%ff%04%00
fakesmc-key-RMde-char	A
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%02%00%00%00%80`%1f%00%00%00%00%00%08%d2%af%1d%00%00%00%00%80u%d1%d1{%8d%ebD%95%87%97Dv%8e%0a%de%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBX`%efZ%8f@%97M%b5d%02%b2.C%f9%a4%7f%ff%04%00
fakesmc-key-BEMB-flag	%01

Here you go

Share this post


Link to post
Share on other sites
On 14/8/2018 at 19:28, dgsga said:

¿Alguien puede explicar por qué no obtengo un ícono para mi principal volumen beta de APFS Mojave cuando uso el nuevo tema incrustado (solo el cuadro amarillo y gris con rayas "sin imagen"). El volumen está ubicado en el SSD NVME en mi hack. Todos los demás volúmenes APFS aparecen bien (incluyendo un clon del volumen principal en otro SSD SATA)

Muchas gracias por cualquier ayuda aquí ...

The same thing happens to me with the icons and the nvme unit.

 

On 14/8/2018 at 21:45, Slice said:

Porque NVME no es SATA.

¿Puedes proporcionar boot.log para ver qué encontró Clover?

Waiting for a possible solution with the help of @slice thk.-

Share this post


Link to post
Share on other sites
On 8/14/2018 at 9:26 PM, dgsga said:

Thanks Slice. Here you go...

bdmesg.txt

I don't know what is the bug

Starting Clover revision: 4780 on American Megatrends EFI

:surprised:

 

There is no messages from Clover about icons used for each entry

8:479  0:004  === [ ScanLoader ] ========================================
8:479  0:000  - [09]: 'EFI'
8:489  0:010          AddLoaderEntry for Volume Name=EFI
8:489  0:000          skipped because entry is hidden
8:489  0:000  - [12]: 'Windows 10'
8:489  0:000  - [13]: ''
8:489  0:000  - [14]: 'EFI'
8:498  0:009          AddLoaderEntry for Volume Name=EFI
8:503  0:004          AddLoaderEntry for Volume Name=EFI
8:503  0:000          skipped because entry is hidden
8:503  0:000  - [16]: 'EFI'
8:503  0:000          AddLoaderEntry for Volume Name=EFI
8:503  0:000          skipped because entry is hidden
8:503  0:000  - [18]: 'Preboot', hidden
8:503  0:000  - [19]: 'System'
8:641  0:137          AddLoaderEntry for Volume Name=System
8:710  0:069  - [20]: 'Recovery', hidden
8:710  0:000  - [21]: 'VM'
8:711  0:000  - [22]: 'Preboot', hidden
8:711  0:000  - [23]: 'Morgaine'
8:836  0:124          AddLoaderEntry for Volume Name=Morgaine
8:911  0:075  - [24]: 'Recovery', hidden
8:911  0:000  - [25]: 'VM'

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Reel
      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 
       
      SMBIOS: MacbookPro 8.3 or MacbookPro 9.1
       
       

       

       
       
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      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 )
       
       
      OR
       
       
       
      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 **
       
      Video summary:
       
      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 ) mbr2gpt /validate mbr2gpt /convert Restart 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 
       
       
    • By SepehrM
      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.
      Specs:
      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
      config-new.plist

    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
×