Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

Advertisement
On 4/2/2019 at 9:47 AM, Download-Fritz said:

 

Let me second that real quick, utter rubbish, please stop spreading FUD. The kext data to link, i.e. the executable and the Info.plist, are put in a buffer that resides in the booter's Device Tree memory, then it is picked up by the kernel from there and linked into the kernel space, as any kext is. The mechanism used to inject kexts now is literally the Apple mechanism to boot without kextcache several versions ago.


I'm not a computer engineer, so please don't be aggressive. I understand what you and the others explained. I've been building hackintoshes for me and friends for about ten years, so I have no interest in spreading rubbish, nor am I naive enough to not be able to understand the meaning and implications of choices like this one, of a kext, flag or whatever. 
Sadly, I have no time to further discuss this, given that I've been experiencing random and quite fast KP reboots once or twice a day. The system never had a single issue, literally the only change I made this month was moving all my kexts from L/E to Extra, but I'm sure there is no relation: post hoc ergo propter hoc, right? This is going off-topic though, sorry for that.

Share this post


Link to post
Share on other sites
17 hours ago, Power Mac said:


I'm not a computer engineer, so please don't be aggressive. I understand what you and the others explained. I've been building hackintoshes for me and friends for about ten years, so I have no interest in spreading rubbish, nor am I naive enough to not be able to understand the meaning and implications of choices like this one, of a kext, flag or whatever. 
Sadly, I have no time to further discuss this, given that I've been experiencing random and quite fast KP reboots once or twice a day. The system never had a single issue, literally the only change I made this month was moving all my kexts from L/E to Extra, but I'm sure there is no relation: post hoc ergo propter hoc, right? This is going off-topic though, sorry for that.

 

Yeah, no problem because this will be the last time I respond. No one said you were a computer engineer but I'm going to go ahead and say you have completely no idea what you are talking about. You've been building hackintoshes for ten years?? But yet you don't even know how clover works, also that clover doesn't even have an Extra folder, that you don't even know how to see what is causing the panic and fix it, that installing to /L/E is stupid for any kext you need to boot, because you won't be able to run the installer to upgrade, and also some kexts do not work properly if they are not injected, so no idea what you mean. No one said inject all your kexts, in fact I am now explicitly stating it to you for the FOURTH time, INJECT KEXTS THAT ARE NEEDED TO BOOT OR REQUIRE INJECTION AND PROPERLY INSTALL THE REST. For the sake of everyone in the world's sanity, stop reading tonymac! That website is full of trash and misinformation, and why every other hackintosh site literally will remove anything to do with that site, and even ban you for repeatedly doing it. Not to mention that you are far more likely to be banned from that site for just saying something inane than anywhere I have ever seen. I just googled install unsigned kexts and found several guides that literally are almost word for word copies, it's like no one there can actually do anything but look at the same site and make the same posts with the same wrong information. They don't even have consistent information, I will go over that below because I see this exact same block of text in multiple places on that site and it is wrong. Also, I really hope you don't use any of those tools from that site because you have absolutely no idea what they do and they sign stuff with an actual developer certificate so they can pretty much install any sort of malware and you'd have absolutely no idea unless you knew what to look for, which it's obvious you would not. And hilariously those tools are all available from the actual developers, tonymac just steals everything to make advertising money off unsuspecting people like yourself. There's very little useful information on that site and I only trust two people because I know that they research and go else where too, Rehabman and Toleda.

 

The previous three times, I stated to inject kexts needed for booting and that don't work unless injected:

 

Destroying this idiotic statement I see all over tonymac:

Injected Kexts live outside of "protected MacOS memory" *
...
* Note: I use the term "protected MacOS memory" in this guide as a generic descriptive term. In reality kext's installed in /L/E are loaded into MacOS's kernel memory which is 'protected' (IE: segregated) form application memory and execution memory. Everything running in kernel memory (including kexts) is actively managed and monitored by MacOS.

Doesn't realize that every kext must be in kernel memory or it couldn't work, also how would it be extending the kernel if it wasn't? You know, the main purpose of a kernel extension....? Every kext no matter what is placed into kernel memory.

Injecting a large amount of kexts can result in an unstable system.

This is somewhat true, but unless you have very little memory (less than the requirement for macOS) it's most likely not going to be any issue since at most this may be a few hundred MBs (which even that is extremely high and you are probably more likely injecting somewhere around a few to maybe tens of MBs). You actually have a higher chance of having too many devices cause more memory problems than this, also newer aptio fix helps alleviate this issue by placing the kernel in any random position that is still available for KASLR.

Many 3rd party kexts will not work correctly when injected by Clover.

Then it doesn't need injected. The only reason to inject kexts is to boot and because they need to be loaded and initialized before other kexts that are in the kernelcache, especially ones that are prioritized by the kernel.

 

EDIT: I forgot that the kext doesn't work because you injected the kext before its prerequisite kexts were initialized. If you force load those prereq kexts it will work, however you now run the risk of one of the injection only kexts that patch any of those kexts to possibly fail to do so.

Injected Kexts are not included in the kernel cache and thus are excluded form MacOS error checking.

I don't even know how to respond to this. This is just so utterly stupid. First, every kext is loaded by the kernel, checked, and initialized, no matter what. This scenario here would be equivalent to using kextload to only load a kext temporarily, it's not in the cache but it's certainly in kernel memory and checked....

Installing kexts in /Library/Extensions is the Apple endorsed and recommended location for all 3rd Party kexts.

Ok, that's wonderful, and has absolutely nothing to do with how to boot macOS because you can't really do that without injecting kexts or making special installers every time and constantly installing kexts every time you use the installer...

If you purchase a piece of hardware that requires the installation of a manufactures MacOS driver, the kexts will be installed in /Library/Extensions so why treat hackingtosh kexts any different ?

Because a hackintosh IS different, if it wasn't, clover would not be needed in the first place. You can install stuff into /L/E all day but if you need that kext to boot, because of my last point it's not really that helpful is it...?

 

EDIT: Typos.

 

EDIT2: I totally forgot about RampageDev, where he removed his posts from tonymac because they were being jerks, so they sent a DMCA request against his site because it had the same information. Or Mieze (who wrote like every network driver) got banned for pointing out that one of the drivers from tonymac was from an open source linux GPL driver, which requires the source code to be released and they refused. Why would they do that? Probably because it does something that they don't want people to know about. Not to mention literally everything on the site is stolen, modified(?), and closed sourced, which is pretty much against the license of almost every project. In fact, they are currently violating the clover license as well as they actually are not allowed to use the name of the project or authors without the written consent of the project.

Edited by apianti

Share this post


Link to post
Share on other sites

There's a ticket on SourceForge about this. The installer fails to find the ESP partition of APFS-formatted Fusion Drives and instead installs Clover to the system root. To update I have to manually copy those files to the ESP partition. I'm not sure if the same issue occurs with AppleRAID volumes, APFS or not.

Share this post


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

There's a ticket on SourceForge about this. The installer fails to find the ESP partition of APFS-formatted Fusion Drives and instead installs Clover to the system root. To update I have to manually copy those files to the ESP partition. I'm not sure if the same issue occurs with AppleRAID volumes, APFS or not.

Yes, known problem with all system volumes in a container partition. It is detection problem in installer, workaround is exactly what you are doing for now...

Share this post


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

There's a ticket on SourceForge about this. The installer fails to find the ESP partition of APFS-formatted Fusion Drives and instead installs Clover to the system root. To update I have to manually copy those files to the ESP partition. I'm not sure if the same issue occurs with AppleRAID volumes, APFS or not. 

https://github.com/corpnewt/CloverExtractor.git Use this script to install Clover in the right partition

Share this post


Link to post
Share on other sites

Hi @Slice

 

Clover r4928: I've a problem with Windows partition name (see pictures below). One in french language: é is not recognized, another is blank no name at all. I don't understand why?

 

screenshot0.png

screenshot1.png

Share this post


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

Hi @Slice

 

Clover r4928: I've a problem with Windows partition name (see pictures below). One in french language: é is not recognized, another is blank no name at all. I don't understand why?

 

 

 

Raster themes have only ascii character set, no extended latin. (as a bonus russian and korean by special efforts)

SVG themes may have any characters including chinese but author or user should provide the SVG font with all needed letters.

Share this post


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

For different additional SSDT table. You seems have 8 tables.

Then the message must include SSDT ID just to avoid confusion?

Share this post


Link to post
Share on other sites

Clover 4988 is a stinker!  I can't boot at all with it.   Can't even get to the Apple logo before it stops me dead......managed to disable all of my booting for all of my drives (mainly because I use Clover as my bootloader)......

 

Clover 4972 works............this one's (4988) a turkey, guys.........

Edited by meaganmargaret

Share this post


Link to post
Share on other sites
11 minutes ago, meaganmargaret said:

Clover 4988 is a stinker!  I can't boot at all with it.   Can't even get to the Apple logo before it stops me dead......managed to disable all of my booting for all of my drives (mainly because I use Clover as my bootloader)......

 

Clover 4972 works............this one's a turkey, guys.........

 

Agree! 

The «driverss64UEFI» folder has disappeared and in its place there is another one called simply «drivers» and inside it is the «UEFI» folder.

On reboot the nvidia 1080Ti is no longer detected.

 

 

Share this post


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

The «driverss64UEFI» folder has disappeared and in its place there is another one called simply «drivers» and inside it is the «UEFI» folder.

On reboot the nvidia 1080Ti is no longer detected.

Since the official release didn't remove the driverss64UEFI nor drivers64, can I ask where did you get the installer

if [[ -d  "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64" && \
    ! -d "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_LEGACY@" ]]; then
  mkdir -p "${EFI_ROOT_DIR}/EFI/CLOVER/drivers"
  cp "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64" "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_LEGACY@"
fi

if [[ -d  "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64UEFI" && \
    ! -d "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_UEFI@" ]]; then
  mkdir -p "${EFI_ROOT_DIR}/EFI/CLOVER/drivers"
  cp "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64UEFI" "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_UEFI@"
fi

as I can see only cp commands in official release?

Edited by vector sigma

Share this post


Link to post
Share on other sites

Hello vector sigma

 

I downloaded the version from sourceforge. I prepared a comparison in images between the version of clover 4972 and the 4988. Look at the differences.
In 4988, by installing the same drivers that i install in 4972, when i restarted High Sierra don't see 1080Ti

 

screenshot-84.png

screenshot-85.png

screenshot-86.png

Share this post


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

I downloaded the version from sourceforge. I prepared a comparison in images between the version of clover 4972 and the 4988. Look at the differences.

I know the difference but you aren't surprised a directory gone without lauch any rm command? I'm saying this because only unreleased revision before 4988 did this during our tests you can follow at the "general discussion" topic.

1 hour ago, Extreme™ said:

In 4988, by installing the same drivers that i install in 4972, when i restarted High Sierra don't see 1080Ti

Changing directory to load drivers do nothing to the functionality of Clover. A change regarding nvidia is introduced in r4981 but not sure can have downsides for you.

Share this post


Link to post
Share on other sites

Problem solved. 

 

The nvidia 1080Ti was not detected because in the 4998 version of Clover it is no longer possible to install the AptioMemoryFix-64.efi driver. 

So i took this AptioMemoryFix-64.efi driver from version 4972 and put it in the Clover / drivers / UEFI/ folder of version 4998: now everything works fine.

screenshot_89.png

Edited by Extreme™

Share this post


Link to post
Share on other sites
2 minutes ago, Extreme™ said:

The nvidia 1080Ti was not detected because in the 4998 version of Clover it is no longer possible to install the AptioMemoryFix-64.efi driver. 

So i took this AptioMemoryFix-64.efi driver from version 4972 and put it in the Clover / drivers / UEFI/ folder of version 4998: now everything works fine.

Is not included in Clover unless you compile it with third party scripts (unless Slice did this). By the way to avoid surprise next time ensure that no one driver is selected under "Memory Fix" because if one of them is selected all other drivers that contains "aptiomem" or "osxaptiofix" will get deleted. If none of them is selected your AptioMemoryFix wil stay in safe forever. This because the installer records what have you done in previous installations.

Share this post


Link to post
Share on other sites

Feature request:

 

As I understand if you want to change the boot order in Clover in a multi boot system you have define what disk should load first in the plist via its UUID. A little complicated.

 

So I had an idea that it would be pretty cool if you could with in Clover boot environment click and drag to the front the icon for the partition you want to 

boot first. Much like how some UEFI bioses do it where you drag the disk up top.

 

Thanks

Edited by davidm71
added multiboot

Share this post


Link to post
Share on other sites
3 hours ago, davidm71 said:

Feature request:

 

As I understand if you want to change the boot order in Clover in a multi boot system you have define what disk should load first in the plist via its UUID. A little complicated.

 

So I had an idea that it would be pretty cool if you could with in Clover boot environment click and drag to the front the icon for the partition you want to 

boot first. Much like how some UEFI bioses do it where you drag the disk up top.

 

Thanks

Click "Restart" and it will be first loaded system

Снимок экрана 2019-07-17 в 19.16.35.png

Share this post


Link to post
Share on other sites

Just tried setting Mojave as the startup disk  in settings and when it rebooted it had selected the 'Preboot' partition instead. 

 

Using Clover 4920.

 

So it didn't work.

 

 

Edited by davidm71
added details

Share this post


Link to post
Share on other sites

It did work. Show me Clover preboot.log corresponding to the situation.

It must work because this is Apple's control panel, invented by Apple not me.

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 Klaidonis
      I am making a minimal Clover build for the fastest boot possible with the boot6 file in legacy mode.
      While looking at the preboot.log, I noticed that there is a line without explanation (at 0:892). Apparently, whatever it is, the execution time of it is close to 2 seconds, more than 55% of the total logged boot time in the current configuration. This does not change whether I use USB 2 or USB 3 port.
       
      Is there a way to eliminate or speed up the above? Also, is there anything else you can suggest to improve the performance based on the below log file? Which moment in the boot process corresponds to the start time in preboot.log?  
      The last thing I would like to understand is the delay/timeout after the boot6 file has loaded, and the number 6 disappears from the screen. For about 2 seconds or slightly less, I can press any key, and then it will enter the BIOS-like interface from the boot6 file. Without further knowledge, it seems like those 2 seconds are just delay time, and only after that is CLOVERX64.efi actually started, which, I presume, is approximately when the preboot.log timer starts. So, if the aforementioned is correct, can I get rid of this delay as well? Note that I am using the boot1f32 file to chain-load boot6, which does not include the initial 2-second wait period for a keypress.
       
      === preboot.log ===
      0:100 0:100 MemLog inited, TSC freq: 2394459554 0:100 0:000 CPU was calibrated with ACPI PM Timer 0:100 0:000 LegacyRegion2: Chipset/proc: 0x0A048086 0:100 0:000 Next Generation Core processors (PAM 0x80-0x86) 0:100 0:000 Test PAM1=(0x41=90, 0x5a=90, 0x81=11, 0x91=00) at chipset 0A048086 0:100 0:000 , Install = Success 0:112 0:012 BiosVideoDriverBindingStart! 0:112 0:000 BiosVideoCheckForVbe 0:112 0:000 EdidOverride not found 0:121 0:009 Edid1+ 0:121 0:000 found Detail Timing 1920x1080 0:121 0:000 timing string after 0xFE:AUO 0:121 0:000 timing string after 0xFE:B156HAN01.2 0:122 0:000 0 1280x1024 attr=9B - ok, edid- 0:122 0:000 1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1 0:122 0:000 2 640x480 attr=9B - ok, edid-, 640x480, working 0:122 0:000 3 800x600 attr=9B - ok, edid-, 800x600, working 0:123 0:000 4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4 0:123 0:000 BV new mode: 4 1920x1080 0:398 0:275 SetMode pref 4 (4) = Success 0:892 0:493 VGA Pci.Hdr.Command=6 - not enabled 2:623 1:731 2:623 0:000 Now is 21.02.2020, 13:03:21 (GMT) 2:623 0:000 Starting Clover revision: 5103 (master, commit 3f3b85da0) on CLOVER EFI 2:623 0:000 Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -t GCC53 | -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/sergey/src/CloverHackyColor/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 10.14.6] 2:623 0:000 SelfDevicePath=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) @940C9698 2:623 0:000 SelfDirPath = \EFI\CLOVER 2:623 0:000 SimpleTextEx Status=Success 2:623 0:000 === [ Get Smbios ] ======================================== 2:623 0:000 Type 16 Index = 0 2:623 0:000 Total Memory Slots Count = 2 2:623 0:000 Type 17 Index = 0 2:623 0:000 SmbiosTable.Type17->Speed = 1600MHz 2:623 0:000 SmbiosTable.Type17->Size = 4096MB 2:623 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 DIMM0 2:623 0:000 SmbiosTable.Type17->Vendor = Hynix 2:623 0:000 SmbiosTable.Type17->SerialNumber = 00000000 2:623 0:000 SmbiosTable.Type17->PartNumber = HMT451S6MFR6A-PB 2:623 0:000 Type 17 Index = 1 2:623 0:000 SmbiosTable.Type17->Speed = 1600MHz 2:623 0:000 SmbiosTable.Type17->Size = 8192MB 2:623 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 DIMM1 2:623 0:000 SmbiosTable.Type17->Vendor = Kingston 2:623 0:000 SmbiosTable.Type17->SerialNumber = 5A060A8A 2:623 0:000 SmbiosTable.Type17->PartNumber = KHX1600C9S3L/8G 2:623 0:000 Boot status=0 2:623 0:000 Running on: 'Aspire V5-573G' with board 'Dazzle_HW' 2:623 0:000 === [ GetCPUProperties ] ================================== 2:623 0:000 CPU Vendor = 756E6547 Model=40651 2:623 0:000 The CPU supported SSE4.1 2:623 0:000 BrandString = Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz 2:623 0:000 The CPU supported turbo 2:623 0:000 MSR 0x35 20004 2:623 0:000 MSR 0xE2 before patch 1E008405 2:623 0:000 MSR 0xE2 is locked, PM patches will be turned on 2:623 0:000 MSR 0xCE 0008083D_F3011800 2:623 0:000 corrected FLEX_RATIO = 0 2:623 0:000 MSR 0x1B0 00000000 2:623 0:000 FSBFrequency = 71 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz 2:623 0:000 MaxDiv/MinDiv: 24.0/8 2:623 0:000 Turbo: 27/27/27/30 2:623 0:000 Features: 0xBFEBFBFF 2:623 0:000 Threads: 4 2:623 0:000 Cores: 2 2:623 0:000 FSB: 100 MHz 2:623 0:000 CPU: 1700 MHz 2:623 0:000 TSC: 1700 MHz 2:623 0:000 PIS: 100 MHz 2:623 0:000 ExternalClock: 25 MHz 2:623 0:000 === [ GetDevices ] ======================================== 2:623 0:000 GOP found at: PcieRoot(0x0)/Pci(0x2,0x0)/AcpiAdr(0x80010100) 2:623 0:000 PCI (00|00:00.00) : 8086 0A04 class=060000 2:623 0:000 PCI (00|00:02.00) : 8086 0A16 class=030000 2:623 0:000 - GOP: Provided by device 2:623 0:000 - GFX: Model=Intel HD Graphics 4400 (Intel) 2:623 0:000 PCI (00|00:03.00) : 8086 0A0C class=040300 2:623 0:000 PCI (00|00:14.00) : 8086 9C31 class=0C0330 2:623 0:000 PCI (00|00:16.00) : 8086 9C3A class=078000 2:623 0:000 PCI (00|00:1B.00) : 8086 9C20 class=040300 2:623 0:000 PCI (00|00:1C.00) : 8086 9C10 class=060400 2:623 0:000 PCI (00|00:1C.02) : 8086 9C14 class=060400 2:623 0:000 PCI (00|04:00.00) : 168C 0034 class=028000 2:623 0:000 - WIFI: Vendor=Atheros 2:623 0:000 PCI (00|00:1C.03) : 8086 9C16 class=060400 2:623 0:000 PCI (00|05:00.00) : 10EC 5287 class=FF0000 2:623 0:000 PCI (00|05:00.01) : 10EC 8168 class=020000 2:623 0:000 - LAN: 0 Vendor=Realtek 2:623 0:000 PCI (00|00:1C.04) : 8086 9C18 class=060400 2:624 0:000 PCI (00|01:00.00) : 10DE 0FE4 class=030200 2:624 0:000 PCI (00|00:1D.00) : 8086 9C26 class=0C0320 2:624 0:000 PCI (00|00:1F.00) : 8086 9C43 class=060100 2:624 0:000 PCI (00|00:1F.02) : 8086 9C03 class=010601 2:624 0:000 PCI (00|00:1F.03) : 8086 9C22 class=0C0500 2:624 0:000 === [ GetDefaultSettings ] ================================ 2:624 0:000 Clover load options size = 0 bytes 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G--00-00-00-00-00-00. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G-1700. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Dazzle_HW. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Dazzle_HW-1700. Dir not exists 2:624 0:000 set OEMPath by default: EFI\CLOVER 2:637 0:012 EFI\CLOVER\config.plist loaded: Success 2:637 0:000 === [ GetListOfThemes ] =================================== 2:637 0:000 === [ Found config plists ] =============================== 2:637 0:000 - config.plist 2:637 0:000 === [ GetEarlyUserSettings ] ============================== 2:637 0:000 timeout set to 0 2:637 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 2:637 0:000 Default theme: embedded 2:637 0:000 === [ LoadDrivers ] ======================================= 2:637 0:000 === [ InitScreen ] ======================================== 2:637 0:000 Console modes reported: 4, available modes: 2:637 0:000 - [01]: 80x25 2:637 0:000 - [02]: 80x50 2:637 0:000 - [03]: 100x31 2:637 0:000 - [04]: 240x56 (current mode) 2:637 0:000 SetScreenResolution: 1920x1080 - already set 2:637 0:000 SetScreenResolution: 1920x1080 - already set 2:637 0:000 reinit: self device path=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) 2:637 0:000 === [ GetMacAddress ] ===================================== 2:637 0:000 === [ ScanSPD ] =========================================== 2:637 0:000 Scanning SMBus [8086:9C22], mmio: 0xB3619004, ioport: 0x5040, hostc: 0x1 2:656 0:018 Slot: 2 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C9S3L8G SerialNo=050A0006000A080A 2:657 0:000 === [ GetAcpiTablesList ] ================================= 2:657 0:000 Get Acpi Tables List from RSDT: 2:657 0:000 - [00]: FACP ACRPRDCT len=268 2:657 0:000 - [01]: UEFI ACRPRDCT len=566 2:657 0:000 - [02]: FPDT ACRPRDCT len=68 2:657 0:000 - [03]: ASF! ACRPRDCT len=165 2:657 0:000 - [04]: HPET ACRPRDCT len=56 2:657 0:000 - [05]: APIC ACRPRDCT len=140 2:657 0:000 - [06]: MCFG ACRPRDCT len=60 2:657 0:000 - [07]: BOOT ACRPRDCT len=40 2:657 0:000 - [08]: LPIT ACRPRDCT len=148 2:657 0:000 - [09]: ASPT ACRPRDCT len=52 2:657 0:000 - [10]: DBGP ACRPRDCT len=52 2:657 0:000 - [11]: SSDT ACRPRDCT len=1337 2:657 0:000 - [12]: SSDT ACRPRDCT len=2776 2:657 0:000 - [13]: SSDT ACRPRDCT len=12013 2:657 0:000 - [14]: SSDT ACRPRDCT len=11433 2:657 0:000 - [15]: SSDT ACRPRDCT len=2230 2:657 0:000 Calibrated TSC Frequency = 2394459554 = 2394MHz 2:657 0:000 === [ GetUserSettings ] =================================== 2:657 0:000 === [ Found DSDT tables ] ================================= 2:657 0:000 === [ ScanVolumes ] ======================================= 2:657 0:000 Found 8 volumes with blockIO 2:657 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0) 2:659 0:001 Result of bootcode detection: bootable Linux (grub,linux) 2:659 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0) 2:660 0:001 Result of bootcode detection: bootable unknown (legacy) 2:660 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,8017BD66-1E24-4B31-8E09-BC49BECD6CC4,0x800,0x21330000) 2:661 0:001 Result of bootcode detection: bootable Windows (vista,win) 2:661 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,82F3B738-65E9-458E-B2F1-BB55D4F00885,0x21331000,0x3D0800) 2:663 0:001 - [04]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,E701DCD8-E3C5-4BFA-B61B-BFF4D80153FD,0x21701800,0x18C4F000) 2:664 0:001 - [05]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(4,GPT,4DB1239A-A9D7-4045-A162-7EF1B3A5913B,0x3A350C21,0x3A3B616E) 2:665 0:001 Result of bootcode detection: bootable Windows (vista,win) 2:665 0:000 - [06]: Volume: PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0) 2:677 0:011 Result of bootcode detection: bootable unknown (legacy) 2:677 0:000 USB volume 2:677 0:000 USB volume 2:677 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) 2:688 0:011 Result of bootcode detection: bootable unknown (legacy) 2:688 0:000 USB volume 2:688 0:000 USB volume 2:688 0:000 This is SelfVolume !! 2:688 0:000 PutNvramPlistToRtVars: nvram.plist not found 2:689 0:000 No AudioIoProtocols, status=Not Found 2:689 0:000 === [ InitTheme ] ========================================= 2:689 0:000 use daylight theme 2:689 0:000 using embedded theme 2:689 0:000 got embedded sound 2:689 0:000 Channels: 2 Sample rate: 8000 Hz Bits: 16 2:689 0:000 output to channel 0 with volume 70, len=25600 2:689 0:000 sound channels=2 bits=16 freq=8000 2:689 0:000 sound converted to 48kHz 2:689 0:000 not found AudioIo to play 2:689 0:000 sound play end with status=Not Found 2:690 0:001 Using embedded font: Success 2:691 0:000 theme inited 2:691 0:000 Chosen embedded theme 2:691 0:000 after NVRAM boot-args= 2:691 0:000 === [ Dump SMC keys from NVRAM ] ========================== 2:691 0:000 no AppleSMC protocol 2:691 0:000 Entry scan disabled 2:691 0:000 === [ AddCustomTool ] ===================================== 2:692 0:000 === [ GetEfiBootDeviceFromNvram ] ========================= 2:692 0:000 Default boot entry not found 2:692 0:000 DefaultIndex=-1 and MainMenu.EntryCount=4 2:973 0:281 GUI ready  
    • By Jancey
      I used this command: diskutil info disk0s2 | grep -i "Partition UUID" | rev | cut -d' ' -f 1 | rev

      But I accidentally removed the wrong disk and now my main windows drive is not appearing in the bootloader. I can't figure out how to get it back. I tried resetting my windows drive, but I kept getting an error. I also reset my mac and reinstalled Catalina.
    • By gengstapo
      @Hervé
       
      Im having similar issue with my HS setup, dell latitute 3480, i5-7200U
      Once the hdmi plugged in, the laptop display went blank, only could see the external tv
      But, when i put my laptop to sleep & wake up again, both screen got display (hdmi still connected)
      Even the hdmi could be plugged off & in (after sleep), the laptop display is fine
       
      What could be the culprit?
      Dell’s MacBook Pro IORegistry.zip
      config.plist.zip
    • 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
×