Jump to content
8755 posts in this topic

Recommended Posts

7 minutes ago, Maf3r0 said:

Seems that Misc/Security/AllowSetDefault=Yes not work yet with OpenCanopy.efi (External picker).

 

it would be great if could be added (or fixed) in future releases.

Hot keys not implemented in OpenCanopy.

  • Like 1
  • Thanks 1
32 minutes ago, vit9696 said:

@rottenpants the issue is probably with Input configuration. I would suggest you check all values there, but my first thought is that TimerResolution might be too high for your system.

 

Thank you for responding

 

What value should I put in TimerResolution?

 

Edit: Changed KeySupportMode to V2 and now the boot menu appears :)

Edited by rottenpants
1 hour ago, olmirror said:

Appreciate your input MacNB, I was already wondering about that since I'm not using clover. I also tried to boot without PMDrvr.kext (just in case) and am getting the same error message, but lower benchmark scores. I also have a separate disk with Catalina that gives me the exact same readings as in Mojave when I boot with a seperate config with the corresponding xcmp kernel patches. From where could clover still be injecting that information into my system?

 

Clover is NOT injecting anything as Clover is not the boot loader.

Like I said, the AppleIntelInfo.kext is HARDCODED with the comment about Clover (it is ASSUMING people always boot from Clover).

 

What I am suggesting is that it is a bug with that kext.

 

If you still have a Clover boot loader handy, you can boot your system off that Clover and check if you still get that "error".

I bet you the you will see it with Clover too.

I was been using OpenCore up to 0.5.3 successfully on my setup, with FileVault 2 enabled. But it stopped working since 0.5.4 release and still not work with latest 0.5.8 release.
 

I get to the FileVault 2 password screen successfully and can enter my password correctly, but then some debug lines appear and nothing else, it doesn't seem that the macOS kernel is started at all.

Find attached a shot of debug lines, as well as config tested (one is my working 0.5.3 config, the others are rewritten from scratch configs tries)
 

My computer:

- Gigabyte GA-Z87N-WIFI (rev. 1.x)
- AW-CE123H 802.11ac/nbg WiFi+BT Broadcom BCM4352 867Mbps mini-PCIe card
- Intel Core i7 4770k (not overclocked)
- AMD Vega 56 8GB
- 16GB RAM
- SSD drive (from Crucial) with APFS macOS partition

Any idea what could be the problem ?

config.plist

config_previous.plist

config.053.plist

IMG_0660.jpeg

Edited by iFrodo
26 minutes ago, iFrodo said:

I was been using OpenCore up to 0.5.3 successfully on my setup, with FileVault 2 enabled. But it stopped working since 0.5.4 release and still not work with latest 0.5.8 release.
 

I get to the FileVault 2 password screen successfully and can enter my password correctly, but then some debug lines appear and nothing else, it doesn't seem that the macOS kernel is started at all.

Find attached a shot of debug lines, as well as config tested (one is my working 0.5.3 config, the others are rewritten from scratch configs tries)
 

My computer:

- Gigabyte GA-Z87N-WIFI (rev. 1.x)
- AW-CE123H 802.11ac/nbg WiFi+BT Broadcom BCM4352 867Mbps mini-PCIe card
- Intel Core i7 4770k (not overclocked)
- AMD Vega 56 8GB
- 16GB RAM
- SSD drive (from Crucial) with APFS macOS partition

Any idea what could be the problem ?

config.plist

config_previous.plist

config.053.plist

IMG_0660.jpeg

 

 

Everyone says that from 10.15.4 it's normal.

 

I have it too, but the computer starts and works.

Edited by topolino1
3 hours ago, vit9696 said:

@rottenpants the issue is probably with Input configuration. I would suggest you check all values there, but my first thought is that TimerResolution might be too high for your system.

hi vit9696

after resetnvram windows boot break with blue screen  do not boot windows 10

without resetnvram working fine 

 

Edited by ameenjuz
3 hours ago, Andrey1970 said:

Hot keys not implemented in OpenCanopy.

 

Thks @Andrey1970 for attention

 

I've already used some hot keys that works fine under OpenCanopy, eg:

  • CMD+OPT+P+R → reset nvram
  • Hold OPT → show picker when it's hidden
  • CMD+R → boot Recovery
  • CMD+V → boot Verbose

The only one that I tested and cannot use is CTRL+Enter to set desired partition as Default :(

Edited by Maf3r0

@Maf3r0 Hotkey support is two stages - OC and picker. OC is shared and polls before showing picker (this is what works when using Canopy, because it happens before Canopy), Picker polling is implemented while it is shown (i.e. not here, because Canopy does not implement it).

  • Thanks 1
28 minutes ago, Download-Fritz said:

this is what works when using Canopy, because it happens before Canopy

 

Thanks @Download-Fritz to clarify things a little more

 

But I'll do like to share (and if possible, understand) an example:

  • If, under ext picker, I press CMD+V and hit Enter, system boot into verbose
  • If, under ext picker, I press CTRL and hit Enter, this particular hotkey do not work

Those two hotkeys are so distinct from each other?

33 minutes ago, Maf3r0 said:

 

Thks @Andrey1970 for attention

 

I've already used some hot keys that works fine under OpenCanopy, eg:

  • CMD+OPT+P+R → reset nvram
  • Hold OPT → show picker when it's hidden
  • CMD+R → boot Recovery
  • CMD+V → boot Verbose

The only one that I tested and cannot use is CTRL+Enter to set desired partition as Default :(

 

In the meantime, you can set the default boot OS using System Preferences -> Startup Disk

10 minutes ago, Download-Fritz said:

 

I have answered that question in the very post you quoted. CTRL+ENTER obviously makes no sense outside of a picker.

 

I don't think there's a requirement for CTRL+ENTER OUTSIDE of picker BUT while in the picker, it makes sense.

OpenCanopy currently detects RIGHT arrow key, LEFT arrow key and the SPACEBAR key (may be other keys in the future to turn ON/OFF audio picker).

It would be nice for it detect CTRL+ENTER to select the default boot drive. 

  • Thanks 1
12 hours ago, vamose said:

Please help with OpenCore Bootloader.  Made mutiple attempts but never made progress beyond the boot screen. Attached are the relevant files & system info.

 

Generated DSDT using DPCIManager 

SSDT-EC & SSDT-PLUG using MaciASL

 

Hardware

CPU: Intel® Core™ i7-4790K Processor

MOBO: Gigabyte B85M-D3H ver. F9

GPU: NVIDIA Quadro Fx 1800

OpenCore_Files.zip

 

Can some one help

5 minutes ago, vamose said:

 

Can some one help

 

You will not get much help without providing more details.

 

E.g. 1. Did you have a working macOS booting via Clover (If so you did not provide the Clover EFI folder) 

E.g.2 You did not provide your OpenCore config.plist file

E.g.3 You did not provide your OpenCore bootlog (in the root of the EFI partition)

E.g.4 What does "beyond boot screen mean" ?

 

4 hours ago, MacNB said:

 

Clover is NOT injecting anything as Clover is not the boot loader.

Like I said, the AppleIntelInfo.kext is HARDCODED with the comment about Clover (it is ASSUMING people always boot from Clover).

 

What I am suggesting is that it is a bug with that kext.

 

If you still have a Clover boot loader handy, you can boot your system off that Clover and check if you still get that "error".

I bet you the you will see it with Clover too.

Ah, thanks, I misunderstood. But in reply, no I don't see that error on clover. But xcmp is working much better on Opencore, that is why I would like to continue with this bootloader. The core req is working in tandem with core avg. In clover the two lines where always far apart from each other.

26 minutes ago, MacNB said:

I don't think there's a requirement … OUTSIDE of picker BUT while in the picker, it makes sense.

It would be nice for it detect CTRL+ENTER to select the default boot drive.

 

That is the point, thanks @MacNB

 

Seems that, when in external picker interface, OpenCanopy do not detect CTRL+Enter hotkey but does detect CMD+V hotkey

20 minutes ago, Maf3r0 said:

 

That is the point, thanks @MacNB

 

Seems that, when in external picker interface, OpenCanopy do not detect CTRL+Enter hotkey but does detect CMD+V hotkey

 

Yes it does seem strange that CMD+V actually works WITHIN OpenCanopy even though it's a hotkey.

 

The problem is terminology. CTRL+ENTER is NOT technically a HOT KEY.

According to the Configuration PDF, hot keys are:
 

This list of known modifier hotkeys includes:

 CMD+C+MINUS — disable board compatibility checking.
 CMD+K — boot release kernel, similar to kcsuffix=release.

 CMD+S — single user mode.
 CMD+S+MINUS — disable KASLR slide, requires disabled SIP.

 CMD+V — verbose mode.
 Shift — safe mode.

 

So let's not refer to CTRL+ENTER as a hot key as it may confuse the devs.

Call CTRL+ENTER as a boot picker ACTION Key.

Edited by MacNB
  • Like 1
3 minutes ago, MacNB said:

This list of known modifier hotkeys includes:

 CMD+V — verbose mode.

 

Call CTRL+ENTER as a boot picker ACTION Key.

 

In other words:

  • The hotkey are not implemented yet, so CMD+V theoretically should not work at external picker - but works fine
  • The action key CTRL+Enter theoretically should work - but doesn't works
2 minutes ago, Maf3r0 said:
  • The action key CTRL+Enter theoretically should work - but doesn't works

 

I believe CTRL+ENTER has not been implemented in OpenCanopy. It's only implemented in the builtin boot picker.

 

IMHO it should be a feature of OpenCanopy too.

 

×
×
  • Create New...