Jump to content
ErmaC

Clover General discussion

19,039 posts in this topic

Recommended Posts

Advertisement
3 hours ago, ellaosx said:

@apianti

In config.plist/ACPI/DSDT/Fixes, bitmask suffix can be remove right?

 

@arsradu

you may also check this changes regarding my concern above.

 

Thanks for the new wiki :thumbsup_anim:

 

Hi Ella. So no need for "Old Way" in Wiki either. Ok, will update it.

 

\\Thanks!\\

Share this post


Link to post
Share on other sites
4 hours ago, Maniac10 said:

 thank you guys for moving the wiki, it was a much needed change. Do you have plans to add the translated pages too? I can work on the spanish section and get it up to date. 

I can only speak 2 languages fluently. One of which is my native language. :)) I also speak a bit of Spanish, French, Italian, Russian, and currently learning a bit of Japanese, as well. I definitely know the bad words in some of these. :))) But, for these last ones, I can't say I speak well enough to get a translation done.

 

So, in other words, yeah, that would help. :)

Share this post


Link to post
Share on other sites

Well, I have few questions:

1. Why after writing boot1f32 my EFI partition (/dev/disk0s1) becomes "Unknown"..?

 

Screenshot 7.png

 

2. I previously writing boot0ss to my /dev/disk0 bootsectors for booting Legacy.

While I think UEFI is stable enough on my laptop nowadays, how could I remove it?

 

3. I got these logs from Linux's $ sudo dmesg:

ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
pci 0000:00:01.0: ASPM: current common clock configuration is broken, reconfiguring

// PNP0A08 is referring to _SB.PCI0

Does it indicate that I need using "DisableASPM=Yes" on Clover ACPI section?

 

4. What do these warnings mean and (probably) any idea to fix them?

I don't think Clover's "FixRegions=Yes" helps, though.. I could just ignore these for sure.

ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F
conflicts with OpRegion	     0x0000000000000400-0x000000000000047F (\PMIO)

ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F
conflicts with OpRegion	     0x0000000000000500-0x0000000000000549 (\SBGP)

ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F
conflicts with OpRegion	     0x0000000000000500-0x0000000000000563 (\GPIO)

ACPI: If an ACPI driver is available for this device,
you should use it instead of the native driver

lpc_ich: Resource conflict(s) found affecting gpio_ich

Many thanks.

Edited by Badruzeus

Share this post


Link to post
Share on other sites
4 hours ago, arsradu said:

 

Hi Ella. So no need for "Old Way" in Wiki either. Ok, will update it.

 

\\Thanks!\\

 

Yeah, there's stuff all over it that needs finished, fixed, or removed. Anyone who is already at least a member of the project can edit the wiki. I decided against making it open to anyone to reduce the incorrect changes that could amass or prevent someone straight up deleting information.

 

4 hours ago, arsradu said:

I can only speak 2 languages fluently. One of which is my native language. :)) I also speak a bit of Spanish, French, Italian, Russian, and currently learning a bit of Japanese, as well. I definitely know the bad words in some of these. :))) But, for these last ones, I can't say I speak well enough to get a translation done.

 

So, in other words, yeah, that would help. :)

 

I agree, I know a few languages but not well enough to translate any better or even close to just literally using Google or Yandex translate. I'll stick to English and a mediocre illiterate child's Russian.

 

1 hour ago, Badruzeus said:

Well, I have few questions:

1. Why after writing boot1f32 my EFI partition (/dev/disk0s1) becomes "Unknown"..?

 

Screenshot 7.png

 

2. I previously writing boot0ss to my /dev/disk0 bootsectors for booting Legacy.

While I think UEFI is stable enough on my laptop nowadays, how could I remove it?

 

3. I got these logs from Linux's $ sudo dmesg:


ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
pci 0000:00:01.0: ASPM: current common clock configuration is broken, reconfiguring

// PNP0A08 is referring to _SB.PCI0

Does it indicate that I need using "DisableASPM=Yes" on Clover ACPI section?

 

4. What do these warnings mean and (probably) any idea to fix them?

I don't think Clover's "FixRegions=Yes" helps, though.. I could just ignore these for sure.


ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F
conflicts with OpRegion	     0x0000000000000400-0x000000000000047F (\PMIO)

ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F
conflicts with OpRegion	     0x0000000000000500-0x0000000000000549 (\SBGP)

ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F
conflicts with OpRegion	     0x0000000000000500-0x0000000000000563 (\GPIO)

ACPI: If an ACPI driver is available for this device,
you should use it instead of the native driver

lpc_ich: Resource conflict(s) found affecting gpio_ich

Many thanks.

 

1. It depends how you installed it, you may have overwritten the volume label or other information for the volume.

 

2. You can zero out the last two bytes of a MBR or PBR and that will make it not bootable. You can put 0x55, 0xAA back to make it bootable again. Refer to the PC BIOS boot reference for more information.

 

3. Fix only applies to macOS. You need to fix your ACPI tables for linux. You're missing that method to support ASPM states I'm guessing. Not sure if it's fixable in the legacy firmware, I don't see why it wouldn't be present in your original tables if your machine supported it, unless it's disabled in the firmware.

 

4. Also only fixes for macOS. Hmmmm..... Unsure why it would have overlapping regions, that's strange but I really doubt you need LPC. Also, the fact it is attempting to use ACPI and then says to use an ACPI driver instead makes no sense.... This may also be a side effect of legacy?

Share this post


Link to post
Share on other sites
13 hours ago, apianti said:

There is an issue with legacy booting from a different device not on the same bus, I am not sure there is a way to fix it because of firmware drive numbers appearing pretty much random to the EFI emulation.

 

EDIT: Typo.

 

 

ok, so i decided to install clover on EFI partition of a SSD which is formatted as APFS for Mojave.

 

since clover installer could not show EFI in partition selection (i dont know if i select Mojave partition then check ESP in installer window would work because EFI is in disk1 and MOJA partition is in disk2), i tried manual installation.

 

here is my mojave ssd disk with apfs.

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         249.8 GB   disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +249.8 GB   disk2
                                 Physical Store disk1s2
   1:                APFS Volume MOJA                    23.5 GB    disk2s1
   2:                APFS Volume Preboot                 44.9 MB    disk2s2
   3:                APFS Volume Recovery                517.0 MB   disk2s3
   4:                APFS Volume VM                      1.1 GB     disk2s4

 

i have USB stick with latest clover installed on it. Name is MM.

also i have fdisk440 from old clover installation. latest clover installation seems like does not include this tool.

 

and here is steps i tried.

1. install stage 0 loader

# fdisk440 -u -f /Volumes/MM/usr/standalone/i386/boot0af -y /dev/disk1

2. install stage 1 loader

# dd if=/Volume/MM/usr/standalone/i386/boot1f32 of=/dev/rdisk1s1

3. mounted EFI partition (disk1s1) using EFI Mounter app

4. install stage 2 loader

# copy -r /Volume/MM/boot /Volume/EFI

5. install Clover EFI contents

# copy -r /Volume/MM/EFI /Volume/MM/usr /Volume/MM/Library /Volume/EFI 

 

but it fails to boot. it could not print "6" in screen. just stuck there.

 

Could you give me clue of how to install clover manually in EFI partition of APFS volume?

 

tnx,

Edited by ea dd

Share this post


Link to post
Share on other sites

Yeah, this is known issue, asked maybe like ten posts ago... But the installer fails to install properly when using a volume in a container partition (APFS, CoreStorage, etc). You can just mount the EFI partition and move the /EFI folder from the root of the system volume to the EFI partition.

 

EDIT: Oh, wasn't paying attention that you were using legacy. You installed stage 1 wrong. And you don't need to copy at those folders, just EFI.

Edited by apianti

Share this post


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

Yeah, this is known issue, asked maybe like ten posts ago... But the installer fails to install properly when using a volume in a container partition (APFS, CoreStorage, etc). You can just mount the EFI partition and move the /EFI folder from the root of the system volume to the EFI partition.

 

EDIT: Oh, wasn't paying attention that you were using legacy. You installed stage 1 wrong. And you don't need to copy at those folders, just EFI.

 

 

ok, that stage 1 installation command messed my EFI partition.

now i have reformatted it with command 

newfs_msdos -F 32 -v EFI /dev/disk1s1 

then redid all above steps except step 2 and, instead, used following command.

/Volumes/MM/usr/local/bin/boot1-install -f /Volumes/MM/usr/standalone/i386/boot1f32 /dev/rdisk1s1 

 

and it works. thank you.

now i can boot windows 10 legacy.

 

i just wonder why latest clovers did not include fdisk440. and what if i use osx stock fdisk.

 

tnx,

Share this post


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

1. It depends how you installed it, you may have overwritten the volume label or other information for the volume.

Yeah, usually.. I change EFI as "EF00" type code with gdisk and "set attributes" as "0" (EFI System), then what I got from Linux gParted it becomes: boot, esp, hidden. If I remember correctly, after fully Erased my whole Disk using macOS's Disk Utility as GPT; the mount point is /Volumes/ESP, but now is /Volumes/EFI bcoz I re-erase /dev/disk0s1 with `$ sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdisk0s1` < also am not really sure, without "2048" my EFI contents become weird eg. LongNameBlahBlahBlah becomes LONGNAME~1. And hi, is CaseSensitive important for FAT32 filesystem? I use Fat-64.efi #btw

 

2 hours ago, apianti said:

Also only fixes for macOS. Hmmmm..... Unsure why it would have overlapping regions, that's strange but I really doubt you need LPC. Also, the fact it is attempting to use ACPI and then says to use an ACPI driver instead makes no sense.... This may also be a side effect of legacy?

I just realized it only appears from Linux Kernel 5.x dmesg. Having no warning with prev. kernel vers, at least on my firmware. And, it makes no sense for using with macOS, I think.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

Hi guys,

 

Starting with 10.14.5 Beta 2 (now with Beta 3, as well), I've got an issue upon boot. Beta 1 was fine.

 

There seem to be some pink/purple lines displayed on the top of the screen. Screenshot below.

 

IMG_1058.thumb.jpeg.8d0d5ac5b427a08546054c3c82cd257f.jpeg

 

Since they appear somewhat at the end of the first stage boot, and they do NOT appear at all on the second stage boot, my guess is that this could be something that Clover could help with...? Maybe?

 

It could just as well be a bug on the OS side...ooor something that needs to be changed on Clover side, to address it.

 

This does not occur with 10.14.4 (final release). And it did occur with both Clover 4920 and 4922. Same exact Clover for both 10.14.4 and 10.14.5 Beta 3.

 

If this is a Clover issue, it's a pretty weird one...

 

Anyway, right now I'm just curious if anyone else has this issue. I'm just thinking, if there is a way to fix it, assuming it's not a bug from Apple, maybe it should be fixed before everyone else upgrades to 10.14.5 (final release).

Edited by arsradu

Share this post


Link to post
Share on other sites
8 hours ago, ea dd said:

ok, that stage 1 installation command messed my EFI partition.

now i have reformatted it with command 

newfs_msdos -F 32 -v EFI /dev/disk1s1 

then redid all above steps except step 2 and, instead, used following command.

/Volumes/MM/usr/local/bin/boot1-install -f /Volumes/MM/usr/standalone/i386/boot1f32 /dev/rdisk1s1 

 

and it works. thank you.

now i can boot windows 10 legacy.

 

i just wonder why latest clovers did not include fdisk440. and what if i use osx stock fdisk.

 

tnx,

 

fdisk440 is not needed because you can just use dd, which is already available, so I'm pretty sure that is just a script. You need to preserve the last 72 bytes of the master/partition boot record, the first 440 are for boot code and the last two are the bootable flag, 70 bytes give a description of the format of the disk/partition beyond that boot record sector. fdisk will just modify that information for the master boot record, (i.e. the four primary partitions for the disk).

 

8 hours ago, Badruzeus said:

Yeah, usually.. I change EFI as "EF00" type code with gdisk and "set attributes" as "0" (EFI System), then what I got from Linux gParted it becomes: boot, esp, hidden. If I remember correctly, after fully Erased my whole Disk using macOS's Disk Utility as GPT; the mount point is /Volumes/ESP, but now is /Volumes/EFI bcoz I re-erase /dev/disk0s1 with `$ sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdisk0s1` < also am not really sure, without "2048" my EFI contents become weird eg. LongNameBlahBlahBlah becomes LONGNAME~1. And hi, is CaseSensitive important for FAT32 filesystem? I use Fat-64.efi #btw

 

I just realized it only appears from Linux Kernel 5.x dmesg. Having no warning with prev. kernel vers, at least on my firmware. And, it makes no sense for using with macOS, I think.

 

Because actually there is no such thing a FAT12/FAT16/FAT32 anymore it's actually VFAT and the number of total clusters determine the actual type that is used. So you had to reduce from 4096 to 2048 bytes per cluster to get less sectors per cluster giving you more clusters so that it probably became FAT32 like you specified instead of FAT16 like it would expect when being read after it checked the cluster count. FAT filesystems are not case sensitive. Yeah, I wouldn't really worry about the messages if you still have everything working, unless you have a really old machine I very much doubt it has LPC, let alone anything actually connected to it. Far more likely that it is using GPIO (i2c and SMBus) or SPI if it's newer.

1 hour ago, arsradu said:

Hi guys,

 

Starting with 10.14.5 Beta 2 (now with Beta 3, as well), I've got an issue upon boot. Beta 1 was fine.

 

There seem to be some pink/purple lines displayed on the top of the screen. Screenshot below.

 

Since they appear somewhat at the end of the first stage boot, and they do NOT appear at all on the second stage boot, my guess is that this could be something that Clover could help with...? Maybe?

 

It could be just as well be a bug on the OS side...ooor something that needs to be changed on Clover side, to address it.

 

This does not occur with 10.14.4 (final release). And it did occur with both Clover 4920 and 4922. Same exact Clover for both 10.14.4 and 10.14.5 Beta 3.

 

If this is a Clover issue, it's a pretty weird one...

 

Anyway, right now I'm just curious if anyone else has this issue. I'm just thinking, if there is a way to fix it, assuming it's not a bug from Apple, maybe it should be fixed before everyone else upgrades to 10.14.5 (final release).

 

It's probably a bug in the beta, this frequently happens in the betas, at least the image is there and not just a black screen for the first part like last time.....

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 rtke333
      Acer Aspire V15 V5-591G - Mojave 10.14.4
       
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS:Insyde Corp. v 1.15
      - CPU:Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM:SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth:Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio:Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader:Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam:HD Webcam
      - HDD:TOSHIBA MQ01ACF032 320 GB HDD
      - SSD:SPCC M.2 230 GB SSD
      - Display:1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad:Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      -Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      -HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255):(Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud(native)
      - Integrated webcam(native)
      - 3.0 USB (native)
      - Touchpad and Keyboard(ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info:Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method:You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      -2nd and I think the best method:Replace your M.2 Qualcomm Card with a compatible BCM94352Zcard (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareData.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode:UEFI
      Getting ready for Installation:
      - Download the install zip (bootpack & postinstall): Click here -> acer_aspire_v591g_installfiles.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

       
      Elan SmartTouchpad
      I only use scrolling, one-, double- & tripletap
      If you want to try other gestures go to this link for more informations, options (v4.7 beta 5) ->  DETAILS ABOUT THE SMART TOUCHPAD DRIVER FEATURES
      Fn Brightness keys not working with this, tried several things without success. With VoodoPS2Controller it's working, but you'll have no gestures (neither scrolling).
       
       
      Before updating to a new version of Mojave please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
       
      Mojave & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart
      list vol (Now select the "System" volume,(FAT 32) For example I select 4)
      sel vol 4
      list part(Select System type partition, for example 2)
      sel part 2
      assign letter=b(This will "mount" your EFI partition)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      remove letter=b (This will "unmount" your EFI)
      2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      mountvol b: /d (This will unmount your EFI)
      Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.04.25: Optimized touchpad scrolling -> updated install files
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip"-> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • By Gorec
      Hi.
      I apologize in advance if I didn't post in the right category and if my title and description aren't specific enough :c
       
      My config in a nutshell:
      CPU: i7 5820k GPU: MSI GTX 1060 3GB RAM: 16 GB MOBO: MSI X99 SLI PLUS I attached RunMe output with all the details of my built.
       
      Some background:
      I have my Hackintosh for about half a year. That time I managed to make it works and fix major issues, but some of them left unresolved since then and I ignored them until now.
      I use my Hackintosh for Adobe projects (PR, AE, PS, IL, AU and a lot more) - most of them connected with video editing of course browsing with Chrome and other small tasks.
       
      Problems:
      Random restarts - this is the biggest one. I'm starting to work on bigger and bigger projects and at this time I think I can't allow this to happen that often. In the past, they happened like once a day or a couple of times a week. However, now it's just frustrating when it happens even 5 or more times a day. I've tried to observe and find out what can be the cause but I haven't managed to find any connections. I thought it happens when Premiere or another app is using GPU, but I haven't seen increased usage when it restarts. I think that it can be connected with GPU, memory or PSU or... meh, anything else. I don't have resources to check if it'll work with other components. There should be some fix for this. I will really appreciate any help with this :c Restart instead of shutdown & sleep doesn't work. I've tried to look through some Google results for this and tried many solutions (as you can see in attached Clover folder), but I think the right one for many of these issues is to make my own DSDT. Glitches, freezes and other things while encoding a video. It happens very often when I try to do this. Maybe it is an issue with GPU or (hopefully) only with GPU drivers which can be fixed with some patch. Today my headphones stopped working. I have a multi-output device configured in the Audio MIDI Setup app which includes my headphones (HyperX Cloud via USB) and Soundflowerbed virtual audio device for capturing system audio. Today while I was trying (like 15 times) to encode a video in Media Encoder in the background and watch video on YouTube I stopped hearing anything from my system. Of course, it restarted a couple of times as always, but even this didn't solve this. If I plug them directly with mini jack (not via USB Soundcard which was in the box and which I always used) in the front IO or the back I only hear some loud noise It takes EX-Fat formatted volumes a few minutes to mount after each restart. I found a workaround to format it with NTFS since I have Tuxera installed and I will reformat these volumes when I will find time for this, but maybe there is some fix for this. GPU is a little bit hot. HW Monitor shows it is only 45-55 degrees, but for my hand is a little bit hot, idk. Also related to GPU - glitch after POST but before entering Clover boot menu. It is a black screen with little white squared glitches for a few seconds. Maybe it indicates the GPU drivers are loading, but maybe it shouldn't be like this. And if I can ask about that - I can't make all applications hide on startup. I, obviously, have "Hide" checkbox checked on every login item in settings, but it doesn't work, none of the apps is hidden in the dock. Is there a way to fix this? Also a small but annoying problem - I can't turn off permanently Mojave update notification (since I tried to install it, and I had to reverse to High Sierra because I had a black screen and I didn't have time for repairing all of them. Tags are not working in Finder - every time I tag a file or folder and make a change in it (for example save a text file) the tag disappears.  
      So, with knowing all of that, is there a way to make a proper DSDT file for my Hackintosh? I tried to look through some guides on how to make it but I think I reached my abilities to understand how Mac OS works and what all of these things are, so I'm asking you guys politely, would someone like to help me? At least with these random restarts? :/
      I really begin to think that I'm a newbie in configuring all of that Clover things - even after what I managed to do with my PC. Help me, pleease... :c
       
      If you have any questions post it below, I will really appreciate any help <3
      Send me MBP-Gorec.home.zip
    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By outdoormagic
      Short Version:
      I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
      More Detail:
      I've done a few hacks so far and this never happened. (Gigabyte z370 / 8700k / Vega, Asus z390 / i5-9600k / 1080). Now, I'm setting up a ThinkPad X1 Gen 6. (Yes, I do expect problems on laptops, but that's not the question).
       
      Mojave 10.14.4 now boots from the internal SSD. So far, so good. Here's the problem.
       
      I installed Mojave on a USB drive (for backup / rescue) and copied the entire EFI partition of my boot drive to the EFI partition on the USB drive. So... I should be able to boot from the USB drive, right? Wrong. Ran Clover installer on the USB itself. Same outcome.
       
      With F12, I can boot from the USB into Clover and select the OS on the USB. The boot sequence hangs on End Random Seed, but before the usual '++++++++' line.
      So, boot into Clover on internal boot drive, then select OS on USB. Same thing.
       
      Read the forums, I saw the posts about AptioMemoryFix, so I tried the various other drivers on the USB. No go.
       
      I haven't found the solution yet to the USB boot issue, but what puzzles me is that if I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
       
×