OpenCore General Discussion

[iTTT]

16 hours ago, Ellybz said:

@anmool

If You had only 1 single drive formatted for your OSX ( APFS or HFS+ ), you would need to use bootcamp to allow the installation of Windows alongside OSX. Unless you prefer the use of a virtual Machine.

I choose to have a dedicated drive with Windows that you "bless" thru OpenCore, via ENTRIES. Safer & simpler. You'd only need to find the path of your dedicated windows drive & voila:
Everything works.
 

 

looks great.

 

may i know your scanpolicy?  is it 2689795 ?

also seems you disable Entries for OSX right? and deleted REC for both osx ?

 

thanks

 

Edited November 9, 2019 by iTTT

[n.d.k]

1 hour ago, arsradu said:

 

Few questions here:

 

1. Is this for dedicated GPUs, as well? So...basically, all I have to add is key=APPL00,override-no-connect with value=[my custom EDID] to PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) which is my dedicated GPU?

2. Does OC come with drivers built-in? Or...how is someone supposed to get those?

 

Thing is, after upgrading to OC 0.5.3 I can't boot anymore. Get stuck at the Apple logo. It used to work perfectly fine before (I think I had version 0.5.0 or something). I'm assuming it could be a driver issue... but if you have a better idea, please, let me know.

 

3. How can I test if the custom EDID has actually been injected?

4. Assuming this is not a driver issue and it's my mistake, could you, please, let me know if these errors are intended?

 

Ran 280 tests in 1.374s

OK
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Build environment: Darwin-19.0.0-x86_64-i386-64bit
Build start time: 09:58:10, Nov.09 2019

WORKSPACE        = /Users/jimmy/Desktop/OpenCorePkg-master/UDK
EDK_TOOLS_PATH   = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/BaseTools
CONF_PATH        = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/Conf
PYTHON_COMMAND   = /usr/bin/python3

Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8

Architecture(s)  = X64
Build target     = DEBUG

Processing meta-data Toolchain        = XCODE5
.
Active Platform          = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/OpenCorePkg/OpenCorePkg.dsc
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
. done!

I kept getting these when building OC.

 Those error are caused by using Python 3, you can just ignore them, it will go away when OC update their edk2.

 

If you get stuck at Apple Logo right after updating your OC version, a hard reboot would get it going again. 

[iTTT]

On 10/30/2019 at 8:39 PM, Andrey1970 said:

@Elende

Don't use UsbKbDxe.efi and KeySupport=yes at the same time.

Delete UsbKbDxe.efi or set all NO in Input section. (Decide as works for you better.)

Replace VBoxHfs.efi on HfsPlus.efi

VBoxHfs.efi it is license it is pure, but it is very slow therefore problems with boot RecoveryHD (dmg).

 

good day Andrey1970,

 

i use apple wired keyboard and must need to UsbKbDxe.efi to make AppleHotKeys (like CMD + V ....) available during PC is turned on.

 

but i have one issue , if i select SHELL, then keyboard will auto input the same keys in command line or its hard to input the correct key in command line.

 

any solution to prevent keyboard to auto input in shell command line?

 

thanks.

 

 

[vit9696]

@iTTT, I am afraid we did not understand you. Could you be more descriptive on what happens, perhaps make a video or something…

 

Is it the following?

1. You hold CMD+V before starting OpenCore

2. You release it

3. You launch OpenCore Shell

4. A number of v keys appears in shell input, i.e. you see:

Shell> vvvvvvvvvvvv

 

If so, I cannot imagine why would you do that, and it feels kind of expected to me?

[Badruzeus]

5 hours ago, arsradu said:

4. Assuming this is not a driver issue and it's my mistake, could you, please, let me know if these errors are intended?

Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
. done!

I kept getting these when building OC.

 

https://coderwall.com/p/-k_93g/mac-os-x-valueerror-unknown-locale-utf-8-in-python

(Would be different with ZSH)

Edited November 9, 2019 by Badruzeus

[BiggestCookie]

@vit9696, Thank you for your efforts with the Configuration PDF and the Docs.

 

If I could make a suggestion regarding sample.plist:

 

Have it defaulting to logging to screen and to file. Nothing hidden in the sample version booting up.  Cutting back on the logging after you get things up and running is easier for a newbie than searching through all the nuances to get things turned on at the start.

 

It would also help if you could just install the EFI folder to the hidden EFI partition on a USB Flash and you try to boot that.  If there is nothing for OpenCore to then boot, fine, you get to see the OpenCore log and fix away.

 

I am really impressed with the development protocol being used with OpenCore.  You folks are more top down than bottom up.  Concurrently generated documentation is really helpful.

 

Thank you again from a newbie.

[arsradu]

Ooook... So, I couldn't get it to boot with OC, and however I try to inject another EDID, doesn't seem to work. Also using the plist from edid-gen.sh from WhateverGreen, under Catalina, doesn't seem to work either since /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-xxxx/ seems to be read-only with no option to authenticate.

 

So, I don't know if anyone tried to inject a different EDID recently, but using AAPL00,override-no-connect doesn't seem to work anymore. Ooor...maybe I'm doing something wrong.

 

In short, what I'm trying to achieve here is to force the OS into 8-bit color mode (since the monitor doesn't support full 10-bit; the specs say "10 bit (8-bit + FRC)") in an attempt to fix the infamous screen flashing on boot time with AMD cards. Looks like the issue happens when switching from ARGB8888 (from bios) to ARGB210101010 from the OS. Not sure why it doesn't happen on Windows, or Linux, or any other OS outside of MacOS, but that's beside the point. And even with MacOS, it doesn't always happen. But it does happen 99% of the time.

 

And since MacOS doesn't have an option to set ARGB8888 from the OS itself...I'm trying to do it from the EDID. Problem is...I can't seem to get the EDID to inject. Either with Clover or OC. And right now, with OC I can't even boot anymore. But I guess I can revert to an older version just to test this part.

 

Anyway, I just installed High Sierra on a spare HDD, for testing. Just to see if there are any differences. But if you have any clues here, please, let me know. This is an oooold issue. :))

Edited November 9, 2019 by arsradu

[Badruzeus]

7 minutes ago, arsradu said:

Also using the plist from edid-gen.sh from WhateverGreen, under Catalina, doesn't seem to work either since /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-xxxx/ seems to be read-only with no option to authenticate.

 

Uhmmmb... guessing, OC does nothing with this APFS read-only system, but Catalina.

Though, we've discussed about this one many times:

sudo mount -uw / && killall Finder

 

[arsradu]

2 minutes ago, Badruzeus said:

 

Uhmmmb... guessing, OC does nothing with this APFS read-only system, but Catalina.

Though, we've discussed about this one many times:

sudo mount -uw / && killall Finder

 

Yeah, it's not OC's fault. But because of that, I also couldn't inject edid into Displays/Overrides...

 

Right now I'm on HS.  Where I can add that DisplayProductID-xxxx.plist after authentication.

 

Will try the command above when I'm coming back to Catalina. I don't expect it to make any difference. But we'll see.  At least I don't need to boot into an HDD to test this anymore. So thank you!  

[vit9696]

52 minutes ago, BiggestCookie said:

@vit9696, Thank you for your efforts with the Configuration PDF and the Docs.

 

If I could make a suggestion regarding sample.plist:

 

Have it defaulting to logging to screen and to file. Nothing hidden in the sample version booting up.  Cutting back on the logging after you get things up and running is easier for a newbie than searching through all the nuances to get things turned on at the start.

 

It would also help if you could just install the EFI folder to the hidden EFI partition on a USB Flash and you try to boot that.  If there is nothing for OpenCore to then boot, fine, you get to see the OpenCore log and fix away.

 

I am really impressed with the development protocol being used with OpenCore.  You folks are more top down than bottom up.  Concurrently generated documentation is really helpful.

 

Thank you again from a newbie.

Unfortunately logging to file is slow (way over 5 minutes) on many firmwares when logging to USB flash, so we prefer to keep it off by default.

[Andrey1970]

57 minutes ago, arsradu said:

In short, what I'm trying to achieve here is to force the OS into 8-bit color mode (since the monitor doesn't support full 10-bit; the specs say "10 bit (8-bit + FRC)") in an attempt to fix the infamous screen flashing on boot time with AMD cards.

 

-rad24

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Radeon.en.md

[arsradu]

8 minutes ago, Andrey1970 said:

 

-rad24

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Radeon.en.md

 

Thank you!

 

While that did (finally!!) make the OS use 24-bit colors (8-bit per channel), the flashing was still there...  Either I'm doing something wrong, or there's something else I'm missing.

 

Edited November 9, 2019 by arsradu

[Matgen84]

34 minutes ago, arsradu said:

 

Thank you!

 

While that did (finally!!) make the OS use 24-bit colors (8-bit per channel), the flashing was still there...  Either I'm doing something wrong, or there's something else I'm missing.

 

 

How do you  to make RX580 in your signature become Radeon Pro 580, flashing? Please tell me. 

[Andrey1970]

4 hours ago, iTTT said:

 

good day Andrey1970,

 

i use apple wired keyboard and must need to UsbKbDxe.efi to make AppleHotKeys (like CMD + V ....) available during PC is turned on.

 

but i have one issue , if i select SHELL, then keyboard will auto input the same keys in command line or its hard to input the correct key in command line.

 

any solution to prevent keyboard to auto input in shell command line?

 

thanks.

 

 

 

I too use apple wired keyboard. Without UsbKbDxe.efi, with Input section:

And with PollAppleHotKeys Yes

 

Check the last version OpenCore from master, there were many improvings for keys.

[arsradu]

8 minutes ago, Matgen84 said:

 

How do you  to make RX580 in your signature become Radeon Pro 580, flashing? Please tell me. 

 

While I think this is mostly cosmetic, you can do this with Device Properties, by adding to your GPU (mine is located at PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) ) the following combination of key + value:

key: model
value: 52616465 6F6E2050 726F2035 3830
type: data

 

Edited November 9, 2019 by arsradu

[arsradu]

@Andrey1970 just for reference, this is the issue I'm trying to fix: 

 

So...since switching to 24-bit didn't seem to do anything to fix this, I'm guessing there's probably something else causing it...or there's something else I'm missing.

[Andrey1970]

@arsradu

Your question doesn't belong to OpenCore.

Write to a topic.

 

[arsradu]

3 minutes ago, Andrey1970 said:

@arsradu

Your question doesn't belong to OpenCore.

Write to a topic.

 

 

Well, I was thinking maybe there is something OpenCore can do to fix this. So...that's kind of the reason why I was posting here. Sorry about the off-topic.

 

But anyway, please, feel free to share your thoughts.  If this is not a good place for that, I'd love to know your opinion in the other thread. So far, I'm out of ideas. So...any help is appreciated.

[n.d.k]

15 minutes ago, arsradu said:

 

Well, I was thinking maybe there is something OpenCore can do to fix this. So...that's kind of the reason why I was posting here. Sorry about the off-topic.

 

But anyway, please, feel free to share your thoughts.  If this is not a good place for that, I'd love to know your opinion in the other thread. So far, I'm out of ideas. So...any help is appreciated.

I would be nice if that flash issue can be fixed, but i think OC team would have fixed long time ago if they were able to. Some said, it was caused by gpu memory timing test performed by Apple, since it only happen on macOs.

[iTTT]

13 hours ago, vit9696 said:

@iTTT, I am afraid we did not understand you. Could you be more descriptive on what happens, perhaps make a video or something…

 

Is it the following?

1. You hold CMD+V before starting OpenCore

2. You release it

3. You launch OpenCore Shell

4. A number of v keys appears in shell input, i.e. you see:

Shell> vvvvvvvvvvvv

 

If so, I cannot imagine why would you do that, and it feels kind of expected to me?

 

 

10 hours ago, Andrey1970 said:

 

I too use apple wired keyboard. Without UsbKbDxe.efi, with Input section:

And with PollAppleHotKeys Yes

 

Check the last version OpenCore from master, there were many improvings for keys.

 

 

hello @vit9696 @Andrey1970

 

apple wired keyboard

 

 

A. use UsbKbDxe.efi, PollAppleHotKeys=NO, KeySupport=NO

1. ShowPicker=NO

2. i hold Option button before starting OpenCore

3. release it and lanuch OpeCore Shell

4. if i try to input some words like .. a , b .... then it will auto input and show like 

Shell > aaaaaaaaaaaaaaaa i/o just Shell > a

 

B. remove UsbKbDxe.efii, PollAppleHotKeys=YES, KeySupport=YES

1. ShowPicker=NO

2. i hold Option button before starting OpenCore

3. system just auto login OSX i/o show up OpenCore Picker.

 

now i use Pavo's OCBuilder to upgrade all my OpenCore files and drivers but still nothing change.

 

thanks.

 

 

 

 

Edited November 10, 2019 by iTTT

[Addrii30]

Hi. How do i setup the CPU frequency and BUS speed in opencore. Because in opencore have ARTfrequency and FSB frequency. My clock is very slow.

[RMTT]

Hi,guys, dose anyone know that how to record backlight on OC, it works on clover.

I find that the nvram contains backlight variable, but it seems can not be read when booting.

[jl4c]

Hello guys

What is the way to boot Linux with OC?

In my old setup, I boot Linux through Clover using this:

 

[Sniki]

After resetting NVRAM from OpenCore everything starts on russian language ?

Linux, macOS Installer, etc

 

How do i reset it as english ?

[Guest]

22 minutes ago, Sniki said:

After resetting NVRAM from OpenCore everything starts on russian language ?

Linux, macOS Installer, etc

 

How do i reset it as english ?

search in config

prev-lang:kbd

and put there right value

if you use string value it is

en:0

if you use data value you have to convert in that format

 

for your info here you can convert value on line:

https://codebeautify.org/string-hex-converter

Edited November 10, 2019 by Guest
add site info