Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

ad911
ad911
Posted
Posted
6 minutes ago, SV0911 said:

I upgraded OpenCore to V. 0.5.6 , everything works great, only on boot a little error occurs:

 

"ocr: only 19 acpi tables out of 20 were valid"

 

Maybe someone can give me a hint.. how to fix it. I've searched a few hours, found nothing....

Big thanks for help

 

 

 

 

myabe you can post your EFI folder and debug log file

canyondust
canyondust
Posted
Posted
10 hours ago, telepati said:

If you don't mind could you please share your config.plist I want to compare with mine.

 

BTW is your timeout set 0 or 5? To be sure set 0 then try is it still working or not?

 

I tried Auto and AMI too with timeout 0 it's never working. It always boots with the default drivers. Also set TakeOffDelay 5.000 and 10.000 but it never helped either. For me best options looks like AppleUsbKbDxe.efi. With this efi works like a real make. I don't even think when I must press its always accurate and its always working. 

 

I attached my config.plist.

 

config.plist

I will next time I’m at my machine. I switched from AppleUsbKbDxe because it kept key presses in a buffer; in order to choose a picker option I had to press the number more than once and found that annoying.

  • Like 2
darthsian
darthsian
Posted
Posted

I want to ask the developers if they could consider adding these features after all:

  • ACPI patches are optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
  • Booter Quirtks, SMBIOS and Device Properties patches will only applied to macOS.

I have read the reasons why you do not want to implement these functions, but after considering all the pros and cons, I think the lesser evil is to have these functions implemented.

What do you think guys?

  • Like 1
telepati
telepati
Posted
Posted
1 hour ago, darthsian said:

I want to ask the developers if they could consider adding these features after all:

  • ACPI patches are optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
  • Booter Quirtks, SMBIOS and Device Properties patches will only applied to macOS.

I have read the reasons why you do not want to implement these functions, but after considering all the pros and cons, I think the lesser evil is to have these functions implemented.

What do you think guys?

Cause enables all quirks to make the system unusable.

darthsian
darthsian
Posted
Posted
22 minutes ago, telepati said:

Cause enables all quirks to make the system unusable.

I do not know what you mean by this. I dont want to enable all quirks. I want ACPI patches to be applied only to macOS with Quirk "EnableForAll set to NO".

  • Like 1
Pavo
Pavo
Posted
Posted
24 minutes ago, darthsian said:

I do not know what you mean by this. I dont want to enable all quirks. I want ACPI patches to be applied only to macOS with Quirk "EnableForAll set to NO".

Then write your ACPI patches to only be effected when its macOS, this is easily done with a if {} else {} statement in the SSDT. Look at the examples.

  • Like 5
darthsian
darthsian
Posted
Posted (edited)
3 hours ago, vit9696 said:

This has already been answered many times, but long story short, we will not make ACPI patches OS-dependent. There are many reasons for them, and there is a good explanation here: 

.

I read that explanation before... and i still think that its not good idea to "simulate" Mac on Windows with "Windows native" hardware and BIOS which is already ACPI ready for Windows, Linux etc. You cant use proprietary logic board software, many hardware sensors are missing etc. But of course I respect that this is your project and your decision :)

Edited by darthsian
  • Like 3
mhaeuser
mhaeuser
Posted
Posted

@darthsian That point does not relate to ACPI, which there is no good point for such a quirk, but only to SMBIOS. The thing with SMBIOS is, we consider OpenCore to be an environment, where we expose Mac information to seamlessly boot macOS. Now, if you do not want Windows to be part of that environment, the most intuitive solution is to just not boot Windows through this environment. Why do you want to boot Windows via OpenCore "so badly" if it causes trouble?

  • Like 3
mathew2019
mathew2019
Posted
Posted
16 hours ago, Pavo said:

Looks like you missed quite of few updates to the config, compare yours to the newer Sample.plist

HI Pavo

 

Thank you, you were right. I have used old config.plist to the updated OC version which made this issue. 

 

One more question, how can I add CPU type to OC?

Pavo
Pavo
Posted
Posted
11 minutes ago, mathew2019 said:

HI Pavo

 

Thank you, you were right. I have used old config.plist to the updated OC version which made this issue. 

 

One more question, how can I add CPU type to OC?

Either by using Kernel > Emulate or PlatformInfo > SMBIOS

darthsian
darthsian
Posted
Posted
1 hour ago, Download-Fritz said:

@darthsian That point does not relate to ACPI, which there is no good point for such a quirk, but only to SMBIOS. The thing with SMBIOS is, we consider OpenCore to be an environment, where we expose Mac information to seamlessly boot macOS. Now, if you do not want Windows to be part of that environment, the most intuitive solution is to just not boot Windows through this environment. Why do you want to boot Windows via OpenCore "so badly" if it causes trouble?

Because i just want one environment for multi boot purpose. Never mind, I just wanted to share some of my opinions. You are doing great job with OpenCore. Thanks for that.

ameenjuz
ameenjuz
Posted
Posted

When i play video 1920x1080 60fps with quicktime player the screen flickering black

When i play video 1920x1080 30fps or 25fps video worked  fine no flickering

What is this issue 

anyone can tell me about this issue i think this issue is related shiki or quicktime player

hardcorehenry
hardcorehenry
Posted
Posted
On 1/30/2020 at 5:44 PM, Sniki said:

In case you added a kext or ACPI table and it's causing the system trouble and not being able to boot anymore:

is there a way to edit the config.plist file of OpenCore in boot picker/or using a OC tool so you can drop that specific ACPI table or not inject that specific kext that is causing trouble ?

 

For now i always make a USB flash drive with current working EFI so in case i mess, i boot from the USB as a last known good working bootloader configuration.

 

Enter shell from picker: 

fs0:
cd EFI/OC
edit config.plist

You'll figure out rest.

  • Like 1
  • Thanks 3
hardcorehenry
hardcorehenry
Posted
Posted

If anyone is interested in disabeling divices that aren’t present in real MAC like AMW0, SIO1, MBDA, TPMX here some small SSDT examples. They are reenabled for other OSes( If (_OSI ("Darwin”)…). Check if you have the same scopes and rename “fits”. Works for ASUS H81M-E. Tested for over month no issue.REM_DEV.zip

  • Thanks 1
Slice
Slice
Posted
Posted
8 hours ago, hardcorehenry said:

If anyone is interested in disabeling divices that aren’t present in real MAC like AMW0, SIO1, MBDA, TPMX here some small SSDT examples. They are reenabled for other OSes( If (_OSI ("Darwin”)…). Check if you have the same scopes and rename “fits”. Works for ASUS H81M-E. Tested for over month no issue.REM_DEV.zip

AMW0, for example, just ignored by macOS. Not needed to disable it manually.

Tested for nine years by thousands users no issue.

  • Like 2
hardcorehenry
hardcorehenry
Posted
Posted
3 hours ago, Slice said:

AMW0, for example, just ignored by macOS. Not needed to disable it manually.

Tested for nine years by thousands users no issue.

 

You right removing AMW0 from IOReg is rather cosmetic, but for example device CWDT which also not present in real Mac, may confuse monitoring(here older topic), I’m far from being expert, thou. As I mentioned I have no issue after removing them, the only non MAC devices in my IOReg are FAN(0,1…)  and TZ01,2

 

CWDT.png.dcf3e1d23c01b818120bc0d7c40c42a3.png

  

DefinitionBlock ("", "SSDT", 2, "hack", "CWDT", 0x00000000)
{
    External (_SB_.PCI0.LPCB.CWDT, DeviceObj)
    External (_SB_.PCI0.LPCB.CWDT.XSTA, MethodObj)    // 0 Arguments
    External (XSTA, MethodObj)    // 0 Arguments

    Scope (\_SB.PCI0.LPCB.CWDT)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (XSTA)
            }
        }
    }
}

 

MacNB
MacNB
Posted
Posted

So I am testing OC.

I "transplanted" my Clover config over to OC 0.5.6 for my Z77X-UP5-TH motherboard and now booting Mojave & Catalina.

 

Questions about DEBUG output:

 

1. With the debug build, at boot I see the following on the screen :

OC-start2.thumb.jpg.7f8884c89befebee243cb52089708326.jpg

 

I have removed Clover on the EFI Partition and installed OC on it. Why is OC starting two times ?

 

2. Is there a way to have this initial text redirected to the OC log file on the root of the EFI together with he rest of the log ?

 

In my config.plist, I have set :

Root->Misc->Debug->DisplayLevel->0x80000042

Root->Misc->Debug->Target->0x45

 

I have tried different settings of DisplayLevel and Target but the initial screen output (shown above) never makes it to the log file.

 

3. With the Non-DEBUG version of OC, is it possible to still have the PREBOOT log (like Clover) instead of: 

00:000 00:000 Starting ApfsDriverLoader ver. 2.1.5
01:384 01:384 EfiBootRecord located at: 5833904 block
01:389 00:004 Real image size: 628216
01:396 00:007 Signature verified!
01:777 00:380 EfiBootRecord located at: 0 block
05:126 03:349 EfiBootRecord located at: 16033038 block
05:131 00:004 Real image size: 602936
05:138 00:007 Signature verified!
05:359 00:220 EfiBootRecord located at: 4300351 block
05:364 00:005 Real image size: 583992
05:371 00:007 Signature verified!

PS. Alt/Esc, CMD+R, etc keys work well and even got the BootChime :)

Simonej
Simonej
Posted
Posted (edited)

Hi guys, I was curious to check the new changes in Config from the upcoming 0.5.6 version, compiled with OCBuilder (thanks Pavo) and adapted my working 0.5.5 config, I was not able to boot receiving Apple prohibitory symbol and also notices a little bit longer time between boot screen and picker. Carefully compared the plists and read about changes, here is my 0.5.6 config file is you want to take a look in case of any error from my side> https://pastebin.com/02R2e4fp
No complaints at all just for info.

SOLVED UPDATING FwRuntimeService

Edited by Simonej
Pavo
Pavo
Posted
Posted
28 minutes ago, Simonej said:

Hi guys, I was curious to check the new changes in Config from the upcoming 0.5.6 version, compiled with OCBuilder (thanks Pavo) and adapted my working 0.5.5 config, I was not able to boot receiving Apple prohibitory symbol and also notices a little bit longer time between boot screen and picker. Carefully compared the plists and read about changes, here is my 0.5.6 config file is you want to take a look in case of any error from my side> https://pastebin.com/02R2e4fp
No complaints at all just for info.

Make sure you are also updating the FwRuntimeService driver and BootX64 module when updating opencore module.

  • Like 1
  • Thanks 1
mathew2019
mathew2019
Posted
Posted (edited)

Hi

 

I am getting Disk Not Ejected Properly error even though ejected properly. this is happening only with USB external drives but ejecting USB keys are fine. What may be the issue?

 

EDIT: No problem, I fixed it

Edited by mathew2019
mhkmichaell
mhkmichaell
Posted
Posted

Hello. 
Anybody can help me with this?

My probook 6470b.  
Another HP laptop on this forum with this problem. 
Can’t choose: „Install Catalina... etc.” and „Recovery”.

If I use that same USB in PC everything is ok. Problem is with HP. No matter what Setting i’ve set in config, kext, efi, acpi. 
Any sollution? What should I do to boot OpenCore MacOs instalalation on HP laptop? 
Help!

3BE88DD7-2B05-42EA-A584-42E1F68CABF6.jpeg

 Share
Go to topic listing
×
×
  • Create New...