Jump to content
8755 posts in this topic

Recommended Posts

11 hours ago, 5T33Z0 said:

Since the last nightly build I can only move the cursor in the between 2 entries with the Keyboard, in the Bootpicker. I have 4 entries, though. And wherever I move the cursor this limits the cursor between these 2 entries. Really weird.

 

I'm going to build nightly OC. Can you tell me which commit you are talking about ! Please.

2 hours ago, 5T33Z0 said:

 

2 hours ago, eSaF said:

Correct, I am using the latest released Nightly Version and it is doing the same thing as the one before, to navigate further you need to tap the Space Bar as I said previously.

 

Thanks. I don't try this nightly. I use opencanopy instead of the text menu: so I don't know if the behavior is affected too.
Is a bug report possible through GitHub/BugTracker?

  • Like 1

Issue opened, it will get read and fixed faster:

https://github.com/acidanthera/bugtracker/issues/1965

13 hours ago, Stefanalmare said:

After the last build I have problem to insert 4th key to password. I have FileVault enable and OC full security. I need to type many times until I can get my password.

Stefanalmare, maybe related to opencanopy issue, it seems keyboard/mouse are missing some keys.

I would wait for that opened issue to get fixed and check if it fixes also yours.

Edited by ghost8282
  • Like 3
4 minutes ago, Matgen84 said:

 

 

Thanks. I don't try this nightly. I use opencanopy instead of the text menu: so I don't know if the behavior is affected too.
Is a bug report possible through GitHub/BugTracker?


I would suggest leaving a comment under the commit where things broke. This way, the dev who made the changes to the commit will be notified of the issue and act upon accordingly. This is what I usually do when testing Nightlies and so far the devs have been pretty quick with rectifying the issue. 

  • Like 2
Guest 5T33Z0

Vit says we should create an issue on the bug tracker: https://github.com/acidanthera/OpenCorePkg/commit/ef780318098d7c86691c378e1fb204f0e8c89fc2

 

I can't bother. going forth and back between testing OpenCore builds right now just to write what I already wrote again.

I had no idea that there was this much testing activity on the nightly OC builds.  Thank you to all those who test regularly so that our monthly OC releases are stable and reliable!

  • Like 5
16 hours ago, Stefanalmare said:

After the last build I have problem to insert 4th key to password. I have FileVault enable and OC full security. I need to type many times until I can get my password.

I just installed c91eebf. My problem is fixed. Don't know if because this build or ones before.

Edited by Stefanalmare
11 hours ago, Stefanalmare said:

FYI with ASPP-Override.kext enabled can't update to latest Monterey Beta. Need to disable and all OK.

 

If this kext solves your power management issues and prevents from updating, why not disable it before update and re-enable after? I have completely different hardware, so actually I shouldn’t give you any advice.;)

2 hours ago, hardcorehenry said:

 

If this kext solves your power management issues and prevents from updating, why not disable it before update and re-enable after? I have completely different hardware, so actually I shouldn’t give you any advice.;)

It is what I did. But at first I didn't know. That's why I posted to eventually help other people in the same situation.

  • Like 2

Hey guys, how do I boot into safe mode with OpenCore? I tried changing my refresh rate and got black screen. I have enablesafemodeslide true, pollapplehotkeys true and takeoffdelay at 5000 but using ctrl + x at the picker doesn’t work.


Sent from my iPhone using Tapatalk

Edited by SavageAUS
  • Sad 1
Guest 5T33Z0

@SavageAUS Looks like booting into safe mode (CMD+X) is not supported.  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+Enter, Shift+Index — safe mode, may be used in combination with CTRL+Enter, CTRL+Index.

[mention=1083558]SavageAUS[/mention] Looks like booting into safe mode (CMD+X) is not supported.  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+Enter, Shift+Index — safe mode, may be used in combination with CTRL+Enter, CTRL+Index.

I couldn’t get shift + enter to work. Luckily I could remote in and change refresh rate.
Anything above 120hz is a black screen. Monitor supports up to 170 or 175.


Sent from my iPhone using Tapatalk

@vit9696 sorry for pinging directly

I cannot find any information about this around.

For people running mac os in qemu, is it better to use OVMF_CODE/VARS.fd compiled from acidanthera's audk instead of the official edk2 repo?

I see the edk2 repo is forked and some more commits are added by acidanthera.

 

Most of users are running OVMF_CODE/VARS.fd included with linux distributions (most of the time compiled from edk2 stable releases).

Some users are running OVMF_CODE/VARS.fd compiled from edk2 repo (stable/nightly).

A minority of users (?) are running OVMF_CODE/VARS.fd compiled from audk repo.

 

I was wondering if it's better to run OVMF_CODE/VARS.fd from audk, maybe for better compatibility/bug fixes?

 

Thank you

×
×
  • Create New...