Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

For the clover wiki authentification, you need to provide a NAME and an EMAIL in your github profile.

Share this post


Link to post
Share on other sites
Advertisement

I do have both in my profile, just checked again just in case. Besides it was working fine before (up to last year I believe). Is anyone else having this problem?

Share this post


Link to post
Share on other sites

hi guys, good afternoon,

I noticed today that clover 4578, don't start in the same point it was when the pc was shutdown, is this normal?

I don't know if I explained me well, but her It comes: I have 2 ssd one with High Sierra, and other with Mojave, today I noticed that at clover screen the one highlighted was the Mojave one, and yesterday when I shutdown the pc was in High Sierra...

Thanks...

Share this post


Link to post
Share on other sites
hi guys, good afternoon,
I noticed today that clover 4578, don't start in the same point it was when the pc was shutdown, is this normal?
I don't know if I explained me well, but her It comes: I have 2 ssd one with High Sierra, and other with Mojave, today I noticed that at clover screen the one highlighted was the Mojave one, and yesterday when I shutdown the pc was in High Sierra...
Thanks...
What do you have set in config.plist as default boot volume? Last booted?

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

lHi SavageAus,

Last booted volume... but yesterday was the same, and it stayed on the last booted, and today no...

 

Edited by MorenoAv

Share this post


Link to post
Share on other sites

I hope this is the right place to ask for help, if not please forgive me and direct me to the correct place...

 

I successfully updated Clover from version 4558 to the new 4586 but immediately ran into a problem in that after the initial clover screen appears and the boot process is started, the screen goes black, the Apple screen progress bar does not appear and the system seems to hang. Pressing the restart button causes the system to go into a panic type rebooting over and over again cycle.

 

The problem, at a surface glance, seems to be an issue with the 4k monitor's chosen default resolution. Here is the tail of the debug log entry:

 

29:011  0:036  SetScreenResolution: 3840x2160 - already set
29:038  0:027  Custom boot is disabled
29:053  0:014  Closing log
39:347  10:293  Custom boot screen is not locked
39:360  0:013  Failed to unlock custom boot screen: Not Ready!
 

I have included the full debug log entry which has all of the system information included in it. I tried the installation on this system on two different os disks, one for 10.13 and one for 10.14 beta with the same result. Going back to version 4558 did work is all that seems to work at the moment.

 

Thank you for your help.

debug v4586.txt.zip

Share this post


Link to post
Share on other sites
25 minutes ago, jerryy2 said:

I hope this is the right place to ask for help, if not please forgive me and direct me to the correct place...

 

I successfully updated Clover from version 4558 to the new 4586 but immediately ran into a problem in that after the initial clover screen appears and the boot process is started, the screen goes black, the Apple screen progress bar does not appear and the system seems to hang. Pressing the restart button causes the system to go into a panic type rebooting over and over again cycle.

 

The problem, at a surface glance, seems to be an issue with the 4k monitor's chosen default resolution. Here is the tail of the debug log entry:

 

29:011  0:036  SetScreenResolution: 3840x2160 - already set
29:038  0:027  Custom boot is disabled
29:053  0:014  Closing log
39:347  10:293  Custom boot screen is not locked
39:360  0:013  Failed to unlock custom boot screen: Not Ready!
 

I have included the full debug log entry which has all of the system information included in it. I tried the installation on this system on two different os disks, one for 10.13 and one for 10.14 beta with the same result. Going back to version 4558 did work is all that seems to work at the moment.

 

Thank you for your help.

debug v4586.txt.zip

 

Looks like Custom boot screen is failing for some reason. Make sure you have all the drivers you need or just stay on whatever version works for now. 

Share this post


Link to post
Share on other sites
54 minutes ago, apianti said:

 

Looks like Custom boot screen is failing for some reason. Make sure you have all the drivers you need or just stay on whatever version works for now. 

 

Thank you for your reply.

 

I used the same drivers as for version 4558, at least the same named drivers anyway, I am guessing the v4586 Clover installer/updater installed newer versions of them. Right now, I have dropped back to version 4558 to be able to run the system.

Share this post


Link to post
Share on other sites
On 6/17/2018 at 3:24 PM, chris1111 said:

apianti WIKI Connections works here :(

 

Capture.png.e3a55def5c770ba8a5baedd3de7b75a5.png

Capture.png.478c5816da14d9a8e7e1be28b65cde56.png

 

On 6/17/2018 at 4:05 PM, Maniac10 said:

After that screen it fails saying:

 

Authentication failed

Insufficient data from authentication provider, email not provided or empty

 

This is the exact behavior I am getting, the initial authorization works but not after.

On 6/18/2018 at 2:01 AM, JrCs said:

For the clover wiki authentification, you need to provide a NAME and an EMAIL in your github profile.

 

I have both of these as well. But I figured out that if I enabled my email to be public, then disabled it to be private again, I can now log in. So it seems it may actually be a problem with github, since even though it was telling me it failed I was signed into github. It appears to be working for me now though. Thanks!

Share this post


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

 

Thank you for your reply.

 

I used the same drivers as for version 4558, at least the same named drivers anyway, I am guessing the v4586 Clover installer/updater installed newer versions of them. Right now, I have dropped back to version 4558 to be able to run the system.

 

Sorry, I didn't see you had your log before but bro, I see your issue, no AptioFix driver:

0:338  0:016  === [ LoadDrivers ] =======================================
0:909  0:571  Loading AppleImageCodec-64.efi  status=Success
0:951  0:042  Loading AppleUITheme-64.efi  status=Success
0:993  0:042  Loading DataHubDxe-64.efi  status=Success
1:039  0:045  Loading AppleKeyAggregator-64.efi  status=Success
1:081  0:041  Loading VBoxHfs-64.efi  status=Success
1:123  0:042   - driver needs connecting
1:136  0:013  Loading FSInject-64.efi  status=Success
1:179  0:042  Loading FirmwareVolume-64.efi  status=Success
1:232  0:053  Loading SMCHelper-64.efi  status=Success
1:274  0:042  Loading apfs.efi  status=Success
1:318  0:043   - driver needs connecting
1:331  0:013  2 drivers needs connecting ...

You also have your memory in the wrong slots, you should switch them to the other slots:

23:026  0:361  SMBIOS Type 17 Index = 0 => 0 0:
23:048  0:022  BANK 0 DIMM0 EMPTY
23:062  0:013  SMBIOS Type 17 Index = 1 => 2 2:
23:076  0:013  BANK 1 DIMM0 EMPTY
23:089  0:013  SMBIOS Type 17 Index = 2 => 1 1:
23:103  0:013  BANK 0 DIMM1 2666MHz 16384MB
23:117  0:013  SMBIOS Type 17 Index = 3 => 3 3:
23:131  0:013  BANK 1 DIMM1 2666MHz 16384MB

 

Share this post


Link to post
Share on other sites

I'am unsure if this has reported or discussed before. If so please ignore my post...

It seems as if macOS Mojave has some "special requirements" about BootVolume/InstallVolume assignments. Here is what I did:

 

I have 2 drives in my rig, both apfs formatted, one of them holds HighSierra as my daily driver and the Clover bootloader on it's EFI partition the other one is a spare drive for testing purpose. I cloned an existing clean Mojave install onto the spare drive for testing purpose which booted quite nice with clover installed on my primary drive. Today Apple rushed out Beta3 of Mojave and so I decided to give it a try. The 1st stage of the update loaded and installed fine and the 2nd stage also started fine but quits with an error "macOS could not be installed.... Installer Sources could not be found..." I took a look at the installers log and it states that it could not find installer files on my primary drive, the one Clover starts from (called Sierra as the one which should be updated is called Mojave)...

 

It also does not matter wether you want to update or do a clean Install onto an empty disk you'll always will end up in an error message stating "Installer Resources could not be found" if the 2nd Stage is not booted from the drive it should be installed on. Is there any way to pass the booted device UUID to macOS instead of the one the bootloader started from?

Edited by griven

Share this post


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

 

Sorry, I didn't see you had your log before but bro, I see your issue, no AptioFix driver:


0:338  0:016  === [ LoadDrivers ] =======================================
0:909  0:571  Loading AppleImageCodec-64.efi  status=Success
0:951  0:042  Loading AppleUITheme-64.efi  status=Success
0:993  0:042  Loading DataHubDxe-64.efi  status=Success
1:039  0:045  Loading AppleKeyAggregator-64.efi  status=Success
1:081  0:041  Loading VBoxHfs-64.efi  status=Success
1:123  0:042   - driver needs connecting
1:136  0:013  Loading FSInject-64.efi  status=Success
1:179  0:042  Loading FirmwareVolume-64.efi  status=Success
1:232  0:053  Loading SMCHelper-64.efi  status=Success
1:274  0:042  Loading apfs.efi  status=Success
1:318  0:043   - driver needs connecting
1:331  0:013  2 drivers needs connecting ...

You also have your memory in the wrong slots, you should switch them to the other slots:


23:026  0:361  SMBIOS Type 17 Index = 0 => 0 0:
23:048  0:022  BANK 0 DIMM0 EMPTY
23:062  0:013  SMBIOS Type 17 Index = 1 => 2 2:
23:076  0:013  BANK 1 DIMM0 EMPTY
23:089  0:013  SMBIOS Type 17 Index = 2 => 1 1:
23:103  0:013  BANK 0 DIMM1 2666MHz 16384MB
23:117  0:013  SMBIOS Type 17 Index = 3 => 3 3:
23:131  0:013  BANK 1 DIMM1 2666MHz 16384MB

 

 

Hello again,

 

Your answer was on the mark. It seems in v4558 the driver is called AptioMemoryFix.efi but in v4586 it has been renamed to AptioMemoryFix-64.efi and even though I use the custom install method to double check what is supposed to be installed, I managed to miss that the installer's auto-select method of upgrading already installed drivers did not select it.

 

Thank you very much for your help!

 

p.s. About the dimm slot choices, that comes from the motherboard user manual for a two dimm setup, using either pair is supposed to be okay, so the physical layout of the slots next to the cpu which then has the cpu cooler almost covering one of the dimm slots came into consideration. Right now, when prices come back into my affordability range so I can add the next pair, I will not have to take off the cpu cooler to do it.

Share this post


Link to post
Share on other sites

Hello!
It seems there is a bug with RC Scripts for saving nvram.plist in latest Clover revisions (e.g. 4586) when installed in legacy mode in Snow Leopard (10.6.8). The nvram is not saved and a forced shutdown is required (Normal shutdown does not occur when scripts are installed, the system stucks at final black screen before complete shutdown). After login, high CPU usage is verified when RC scripts are installed. Checking the System Monitor, this is caused by a process named SED. All these issues don't occur with newer releases of macOS. Is OS X 10.6 incompatible with latest versions of these scripts or is this really a bug? Thanks.

Edited by Oliver@Cheme

Share this post


Link to post
Share on other sites

Hello,

 

 

I have a quick question. What was the last clover release to use fdisk440 to install the bootloader files for non uefi boot?

 

I have had some trouble getting clover to install and boot on an old ga-x58a-ud3r, and was going mad trying to figure it out. I tried an older version (r4128) of clover and it worked. I noticed in the install logs that r4128 used fdisk440 but r4586 tried to use dd. 

 

For now, it works is I install r4128 first (just the bootloader) and then immediately install r4586 (full install) after it.

 

Also, is this a bug or is this intended behaviour after removing the "legacy boot" parts of clover?

 

 

Thanks!

Share this post


Link to post
Share on other sites

I created a UEFI USB installer and my UEFI setup cannot boot using it. I tried a UEFI Ubuntu USB installer and that works fine.

 

I inspected both sticks using the motherboard EFI shell and I can see that the EFI folder created by clover doesn't have the attribute of D (D for directory) hence the motherboard firmware cannot see the bootloader.

 

The fix I had to do is to run these commands inside motherboard EFI shell:

1. fsX: (change to correct location of the USB stick)

2. attrib * (to display all the attributes of files/folders. The EFI folder has no D attribute at this point. It does does the archive attribute set. The other OSX system folders like .FSxxx have one)

3. attrib -a EFI (strips the EFI of its attributes. for some reason this also creates a new file called EFI)

4. del EFI (deletes the EFI file)

5. attrib * (to display the attributes again and this time the EFI folder has a D attribute)

 

Can this be fix by Clover?

 

Thanks!

Share this post


Link to post
Share on other sites

image.png.996d8d075643ea2bb8017af55c824f6f.pngWow! the new design is very beautifil. Thank  plasplasplas

Is visually attractive down a bit the logo and center like sample.

 

Share this post


Link to post
Share on other sites
5 hours ago, WeBeRiO said:

image.png.996d8d075643ea2bb8017af55c824f6f.pngWow! the new design is very beautifil. Thank  plasplasplas

Is visually attractive down a bit the logo and center like sample.

 

Original logo correct center and adjust

26Capture.png.b34945ce13f08aa224db26b32401fc75.png

Let me know if this one is OK 296233927.gif.e657559f3a613f6d64a16c2d815d7c14.gif

background.tiff.zip

Edited by chris1111

Share this post


Link to post
Share on other sites

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
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

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 TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By MaLd0n
      ---TUTORIAL---
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Original Post--
      https://www.olarila.com/topic/6531-olarila-hackbeast-z390-designare-thunderbolt-full-dsdt-patches-clover-opencore/
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://www.olarila.com/topic/6364-mojave-catalina-on-mobos-series-100200300-with-opencore-bootloader/
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
    • By kingoffright
      Dear all,
       
      I have a external harddisk about 500GB, I installed the clover into it and the harddisk is GPT format, below is the 3 partitions details:
      FS01: EFI - disk0s1 - fat32
      FS02: install mac  image - disk0s2 -  hfs+
      FS03: install windows 10 - disk0s3 - fat32
       
      I can use this external harddisk to install Mac without issue, I use below steps to install windows 10
      enter the FS03:
      cd to efi/boot/ and excuete bootx64.efi
      after pop up the windows install screen, i click next and it shows error 'A media driver your computer needs is missing...' and the installation can not go any further.
      Firstly I use ultraiso to write the windows 10 image to a flash disk and no issue to start install window 10 so the image is working fine. Since I dont know how to write
      a wiindow installation image into harddisk partition, I used winrar extra all the files into disk0s3, am I missing some steps or actually clover not support to install windows
      by partitions, apprecating any helps.
       
×