OpenCore General Discussion

[tmbt]

I'm having a problem when i disable the EC0 to EC rename and i use the SSDT-EC.dsl as suggested. 

At reboot i can't see the battery icon in the bar (and if i try to activate it again in system preference it stays there only for half a second and disappears again) and i've Kernel task at 30% cpu all the time.

 

Could someone help understand why ?

Thanks

Mattia

 

 

[vandroiy2012]

4 minutes ago, tmbt said:

I'm having a problem when i disable the EC0 to EC rename and i use the SSDT-EC.dsl as suggested. 

At reboot i can't see the battery icon in the bar (and if i try to activate it again in system preference it stays there only for half a second and disappears again) and i've Kernel task at 30% cpu all the time.

 

Could someone help understand why ?

Thanks

Mattia

 

 

 

If you have laptop you have to rename EC0 -> EC in ACPI-Patch section and not use SSDT-EC.dsl.   

[tmbt]

4 minutes ago, vandroiy2012 said:

 

If you have laptop you have to rename EC0 -> EC in ACPI-Patch section and not use SSDT-EC.dsl.   

Ok thanks i will do that way. I tried to change it because in the opencorepkg manual it says that renaming is never a good idea .. so i tried.

 

Thanks again

Mattia

[E-werd]

On 8/14/2019 at 7:47 AM, Andrw0380 said:

Here is mine after renaming ECDV to EC. Per looking over this thread, it says if this is a laptop, we have to keep the EC device after renaming since battery stats are tied to it. My laptop doesn't even allow me to disable ECDV as a test as if I do, my laptop will freeze during boot so just have to keep it there. Question I have though is I used Hackintool to customize my USB devices, in the past the tool wouldn't generate a SSDT-EC.aml, but now it does and it doesn't give me a SSDT-USBx.aml file. Is the USBx power properties no longer needed in 10.15 or in that case, do I just use the SSDT-ECUSBx.aml, without the EC portion? I do have a AppleBusPowerController in IOResources, but not on the EC device like 10.14 did when used with USBx. 

 

I pulled my hair out on this for a couple days.  I dug around and found that AppleBusPowerController in Catalina no longer looks for EC.  In Mojave it uses "IONameMatch = EC" whereas in Catalina it uses "IOResourceMatch = IORTC".  This explains the issue.  See this screenshot: https://i.imgur.com/ZjVktLR.png

 

What I did to get this working was adding a part to my SSDT-UIAC to add properties to AppleBusPowerController, rather than bothering with a new file.  This is working for me without adding or renaming EC, nor adding USBX.  From the top...

 

DefinitionBlock ("", "SSDT", 2, "hack", "_UIAC", 0)
{
    Device(UIAC)
    {
        Name(_HID, "UIA00000")

        Name(RMCF, Package()
        {
            "AppleBusPowerController", Package()
            {
                "kUSBSleepPortCurrentLimit", 
                0x0834, 
                "kUSBSleepPowerSupply", 
                0x125C, 
                "kUSBWakePortCurrentLimit", 
                0x0834, 
                "kUSBWakePowerSupply", 
                0x125C   
            },
...

 

For backwards compatibility, I feel like you could just as well add "IONameMatch", "EC" instead of the kUSB* values but I haven't actually tested that as I just thought of it.  That may conflict with the IOResourceMatch value, though.

Edited August 30, 2019 by E-werd

[Sniki]

I think i tried every possible Quirk but couldn't manage to boot once my (Haswell) Lenovo ThinkPad X240.

 

I tried to go as minimal to at least be able to boot first then fix the rest later.

 

I still get stuck at this screen where system reboots after like 2 sec there, also attached my EFI.zip

 

Here is where it reboots:

 

@vit9696 @vandroiy2012 @Download-Fritz @PMheart @Andrey1970 do any of you guys have an idea about where the problem could be, any suggestions ?

Edited August 30, 2019 by Sniki

[HmO]

47 minutes ago, Sniki said:

I think i tried every possible Quirk but couldn't manage to boot once my (Haswell) Lenovo ThinkPad X240.

 

I tried to go as minimal to at least be able to boot first then fix the rest later.

 

I still get stuck at this screen where system reboots after like 2 sec there, also attached my EFI.zip

 

Here is where it reboots:

 

@vit9696 @vandroiy2012 @Download-Fritz @PMheart @Andrey1970 do any of you guys have an idea about where the problem could be, any suggestions ?

Enable PanicNoKextDump quirk and you can see kernel panic

1. PanicNoKextDump

[dracoflar]

1 hour ago, Sniki said:

I think i tried every possible Quirk but couldn't manage to boot once my (Haswell) Lenovo ThinkPad X240.

 

I tried to go as minimal to at least be able to boot first then fix the rest later.

 

I still get stuck at this screen where system reboots after like 2 sec there, also attached my EFI.zip

 

Here is where it reboots:

 

@vit9696 @vandroiy2012 @Download-Fritz @PMheart @Andrey1970 do any of you guys have an idea about where the problem could be, any suggestions ?

Did your system need FixHPET from clover? If so, you might find CorpNewt's FixHPET script useful

[Andrey1970]

1 hour ago, Sniki said:

I think i tried every possible Quirk but couldn't manage to boot once my (Haswell) Lenovo ThinkPad X240.

 

I tried to go as minimal to at least be able to boot first then fix the rest later.

 

I still get stuck at this screen where system reboots after like 2 sec there, also attached my EFI.zip

 

Here is where it reboots:

 

@vit9696 @vandroiy2012 @Download-Fritz @PMheart @Andrey1970 do any of you guys have an idea about where the problem could be, any suggestions ?

 

Enable PanicNoKextDump аs at told, differently the screen is not informative.

Your CPU with vt-d, enable DisableIoMapper

[Sniki]

27 minutes ago, Andrey1970 said:

 

Enable PanicNoKextDump аs at told, differently the screen is not informative.

Your CPU with vt-d, enable DisableIoMapper

ok @Andrey1970 here is the new screenshot with PanicNoKextDump and DisableIOMapper enabled:

 

Does someone have an idea about this ?

Edited August 30, 2019 by Sniki

[Andrey1970]

40 minutes ago, Sniki said:

ok @Andrey1970 here is the new screenshot with PanicNoKextDump and DisableIOMapper enabled:

 

Does someone have an idea about this ?

Enable ShrinkMemoryMap and ForceExitBootServices.

Also also try enable ProtectCsmRegion, then disable if no effect.

If helped nothing, try ExitBootServicesDelay 5

[xtddd]

hi,how to get oc to choose automactically boot disk?

[ctich]

10 minutes ago, xtddd said:

hi,how to get oc to choose automactically boot disk?

 System Preferences - > Startup Disk - > Select disk -> Reboot. 

[hardcorehenry]

@Sniki you have wrong kext order in config>kernel>add. First Lilu, then its plug-ins, then the rest(voodoo,internet,etc). VirtualSMC and its plug-ins after Lilu. Also I'd try UEFI>protocols>ConsoleControl=YES, Quirks>ProvideConsoleGOP=YES. Don't know if it's related, but since you tried everything, shouldn't harm.

 

[xtddd]

1 hour ago, ctich said:

 System Preferences - > Startup Disk - > Select disk -> Reboot. 

thanks ,i will try

[Sniki]

3 hours ago, hardcorehenry said:

@Sniki you have wrong kext order in config>kernel>add. First Lilu, then its plug-ins, then the rest(voodoo,internet,etc). VirtualSMC and its plug-ins after Lilu. Also I'd try UEFI>protocols>ConsoleControl=YES, Quirks>ProvideConsoleGOP=YES. Don't know if it's related, but since you tried everything, shouldn't harm.

 

Thanks for the tips @hardcorehenry

I know about the kext order and i have it correctly set on my main oc folder that i was using as i created this one as minimal as possible to try hunting the problem in a more easy way however kext order has no correlation with my current issue.

It should logically be somewhere in FwRuntimeServices.efi quirks or another quirk as logically i see no other possible reason for this to happen as my Clover setup is as perfect as it can currently get.

 

Maybe i should try OC 0.0.3 with AptioMemoryFix just as a confirmation that the problem is in there somewhere and need to adjust the config.plist or if the problem persists i have to look somewhere outside of FwRuntimeServices and it configs on the plist.

 

Will try your options and the ones @Andrey1970 suggested and update with results later tonight as im at work right now.

 

Thanks,

Sniki

[FredWst]

Hi,

 

Just a little trick to enable TRIM for SATA SSD under Mojave last build and Catalina Beta 7.

 

Add at NVRAM in dict 7C436110-AB2A-4BBB-A880-FE41995C9F82

EnableTRIM data <01000000>

 

Fred

Edited August 31, 2019 by FredWst

[Sniki]

20 hours ago, Andrey1970 said:

Enable ShrinkMemoryMap and ForceExitBootServices.

Also also try enable ProtectCsmRegion, then disable if no effect.

If helped nothing, try ExitBootServicesDelay 5

None of these options worked unfortunately, I do get same screen.

[vit9696]

@Sniki, this is very strange. Can you confirm that you use the latest set of drivers and files? Either master or 0.0.4?

Please enable RequestBootVarRouting. If that helps, we probably have a bug somewhere.

What you have in the log is UEFI runtime services executing from non executable memory. It is probably reasonable to try 0.0.3 and AptioMemoryFix, as I see no reason any of these would behave anyhow differently.

[Sniki]

47 minutes ago, vit9696 said:

@Sniki, this is very strange. Can you confirm that you use the latest set of drivers and files? Either master or 0.0.4?

Please enable RequestBootVarRouting. If that helps, we probably have a bug somewhere.

What you have in the log is UEFI runtime services executing from non executable memory. It is probably reasonable to try 0.0.3 and AptioMemoryFix, as I see no reason any of these would behave anyhow differently.

Yes I'm running 0.0.4 and latest AppleSupportPkg (release) not master.

 

Will try OC 0.0.3 and AptioMemoryFix and let you know.

[Sniki]

@vit9696 Confirmed !

with Open Core 0.0.3 and latest AptioMemoryFix it worked from the first try,

 

Where could the problem be, let me know what to do if you need additional logs to find the bug/problem.

 

Thanks,

Sniki

[vit9696]

@Sniki, please do not ignore this request:

Quote

Please enable RequestBootVarRouting. If that helps, we probably have a bug somewhere.

Also provide me with the latest EFI directory with 0.0.4 or 0.5.0 you had with all the recommendations.

@Sniki, please do not ignore this request:

Quote

Please enable RequestBootVarRouting. If that helps, we probably have a bug somewhere.

Also provide me with the latest EFI directory with 0.0.4 or 0.5.0 you had with all the recommendations.

[Sniki]

1 hour ago, vit9696 said:

@Sniki, please do not ignore this request:

Also provide me with the latest EFI directory with 0.0.4 or 0.5.0 you had with all the recommendations.

@Sniki, please do not ignore this request:

Also provide me with the latest EFI directory with 0.0.4 or 0.5.0 you had with all the recommendations.

Thanks @vit9696

I will provide the data tomorrow as I'm about to sleep now.

[justin]

EDIT: add my current config.plist

 

I'm having a strange issue on my Desktop hack, 

 

1. if power cable always on, just shutdown macOS, then do a cold boot, I'm able to see Apple Logo from the beginning to the end, everything works fine.

2. If power cable is plugged off and then plugged on and do a cold boot, i'm not able to see the Apple Logo, OC shows "Time Out" on the boot menu, wait for a while it brings me directly to the second boot stage and then login window, everything other than that works fine too. 

 

My hardware is in signature, OC was compared just now. (OC 0.04 same issue), but IIRC,  OC 0.03 with AptioMemoryFix.efi did not have this issue.

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version   DBG-050-2019-09-01

ProvideConsoleGop is set to YES.

 

I have attached the debug log of the 2 case, hope you guys take a look and give some advise. Thank you a lot. @vit9696 @Download-Fritz @Andrey1970

power_cable_always_on_coldboot.txt

power_cable_off_then_on_coldboot.txt

 

 

config.plist

 

Update: Problem solved, I reflashed BIOS firmware, and the problem gone. I think it was due to running ClearNVRAM too many times... 

Edited September 3, 2019 by justin

[Sniki]

11 hours ago, vit9696 said:

@Sniki, please do not ignore this request:

Also provide me with the latest EFI directory with 0.0.4 or 0.5.0 you had with all the recommendations.

@Sniki, please do not ignore this request:

Also provide me with the latest EFI directory with 0.0.4 or 0.5.0 you had with all the recommendations.

@vit9696 here is the latest Release OC 0.0.4 + latest Release AppleSupportPkg 2.0.9 and RequestBootVarRouting enabled but this option didn't change anything at all whatsoever: OC.zip

Here is the screenshot done again:

 

Here is also a short video if you can catch something else unusual in the logs:

 

 

Thanks,

Sniki

Edited September 1, 2019 by Sniki

[vit9696]

@Sniki, this sounds like a serious bug in your firmware, I will PM you here, and we will try to find some working solution.