Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,888 posts in this topic

Recommended Posts

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

@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.

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
[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
Link to comment
Share on other sites
ghost8282
ghost8282
Posted
Posted

@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

Link to comment
Share on other sites
ghost8282
ghost8282
Posted
Posted (edited)

Anyone can confirm that he's able to boot monterey 12.2.1 in safe mode (shift+enter in boot picker) with latest oc?

Tried it with EnableSafeModeSlide true but I have prohibited symbol and:

29:552 10:052 OC: Boot failed - Aborted
29:569 00:016 OCB: StartImage failed - Aborted

 

Tried also with AllowRelocationBlock true without luck.

 

Could it be the sata port number to which the mac os disk is attached to?

Currently I noticed that it should be in port 2:

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(2,GPT,E636DEB8-61BD-4F0F-92F8-A4B4F3DFDBDB,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,9989AD964DF9C040961BF5E6599B3C33)

 

with port 1 attached to the windows hd:

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,C064A430-7E07-42A4-B89B-398227A1FB32,0x28,0x64000)

 

Unfortunately sata ports are behind the gpu and changing that is not so simple to test..

 

Update...stupid me...I can swap the cables on the hd sides!Testing it now...

 

No, no luck, even with the only mac os hd attached.

Edited by ghost8282
  • Sad 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
Anyone can confirm that he's able to boot monterey 12.2.1 in safe mode (shift+enter in boot picker) with latest oc?
Tried it with EnableSafeModeSlide true but I have prohibited symbol and:
29:552 10:052 OC: Boot failed - Aborted
29:569 00:016 OCB: StartImage failed - Aborted
 
Tried also with AllowRelocationBlock true without luck.
 
Could it be the sata port number to which the mac os disk is attached to?
Currently I noticed that it should be in port 2:
PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(2,GPT,E636DEB8-61BD-4F0F-92F8-A4B4F3DFDBDB,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,9989AD964DF9C040961BF5E6599B3C33)
 
with port 1 attached to the windows hd:
PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,C064A430-7E07-42A4-B89B-398227A1FB32,0x28,0x64000)
 
Unfortunately sata ports are behind the gpu and changing that is not so simple to test..
 
Update...stupid me...I can swap the cables on the hd sides!Testing it now...
 
No, no luck, even with the only mac os hd attached.

I get the prohibit sign then kicked back to the picker.


Sent from my iPhone using Tapatalk
  • Like 1
Link to comment
Share on other sites
thefat32
thefat32
Posted
Posted (edited)

Hi! I'm trying to make `hibernatemode 25` work in my laptop. When going to sleep the powerbutton keeps flashing until I press it. Then on first boot after that MacOs reboots instantly after being picked in OC. Next boot works fine and get this error info about wakeup failure

  

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time:        2022-03-07 01:23:24.971 -0300
OS Version:       ??? ??? (Build ???)
Architecture:     x86_64
Report Version:   32

Data Source:      Stackshots
Shared Cache:     E45F54A1-EAA4-3321-ADBF-BA15B120A5AE slid base address 0x7fff2034b000, slide 0x34b000

Event:            Sleep Wake Failure
Duration:         0.00s
Steps:            1

Boot args:        keepsyms=1 alcid=28 debug=0x100 -wegnoegpu swd_panic=1 

Time Awake Since Boot: 35s



Process:          swd [337]
Architecture:     x86_64
Footprint:        344 KB
Time Since Fork:  1s
Num samples:      1 (1)

  Thread 0x9b9    1 sample (1)    priority 4 (base 4)
  <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
  1  start + 1 (libdyld.dylib + 89917) [0x7fff20674f3d] 1
    1  ??? [0x1044b1454] 1
      1  ??? [0x1044b11e8] 1
        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 146934) [0x7fff20646df6] 1
         *1  ??? [0xffffff80002311f6] 1
           *1  ??? [0xffffff800093ed0e] 1
             *1  ??? [0xffffff8000848e71] 1
               *1  ??? [0xffffff80002544ff] 1
                 *1  ??? [0xffffff800028ba8d] (running) 1

  Binary Images:
        0x7fff20623000 -     0x7fff20652fff  libsystem_kernel.dylib (7195.141.19) <FDF07FB0-42C8-3732-8868-1E9518FB99B3>  /usr/lib/system/libsystem_kernel.dylib
        0x7fff2065f000 -     0x7fff2069afff  libdyld.dylib (852.2)                <5FBD0E1A-ACCE-36DB-B11C-622F26C85132>  /usr/lib/system/libdyld.dylib
Model: MacBookPro11,1, BootROM 432.60.3.0.0, 2 processors, Dual-Core Intel Core i3, 2,5 GHz, 12 GB, SMC 2.16f68
Graphics: kHW_IntelHD4000Item, Intel HD Graphics 4000, spdisplays_builtin
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR3, 1600 MHz, Kingston, 9905428-155.A00LF
Memory Module: BANK 2/ChannelB-DIMM0, 4 GB, DDR3, 1600 MHz, 0000, -
AirPort: spairport_wireless_card_type_third_party
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: KINGSTON SA400S37960G, 960,2 GB
Serial ATA Device: Hitachi HTS547575A9E384, 750,16 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: ASUS USB2.0 Webcam
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 3.0 Bus
USB Device: 2.4G Receiver
Thunderbolt Bus:

I have no clue how to continue debugging this problem. Any information is welcome!
Thanks u' all!

UPDATE: Forgot to mention hibernatemode 3 works nicely

Edited by thefat32
Link to comment
Share on other sites
ghost8282
ghost8282
Posted
Posted
7 hours ago, SavageAUS said:


I get the prohibit sign then kicked back to the picker.


Sent from my iPhone using Tapatalk

Thank you for testing!

I ended in opening an issue in bugtracker, maybe the actual "sur-2" method needs to be updated for safe mode.

  • Like 1
Link to comment
Share on other sites
aben
aben
Posted
Posted (edited)

@ghost8282 Never had a reason to boot safe mode on macOS but just tried testing now with latest OC build 6fdd6da on my Dell system and safe mode does boot successfully on both macOS 12.2.1 and 12.3 Beta (21E5227a) with combo Shift+Enter without Canopy/Picker too. Most likely an issue with your config being incompatible with current OC is what I would suspect.

Edited by aben
  • Like 1
Link to comment
Share on other sites
ghost8282
ghost8282
Posted
Posted

Thank you @aben for testing, this means it should not be an issue with the safe mode patch(es).

However, apart EnableSafeModeSlide and ProvideCustomSlide set to true and EnableSafeModeSlide, ProvideCustomSlide, AllowRelocationBlock, AvoidRuntimeDefrag set to true (which should not be compatible with mac os >=11) I cannot see any other setting for safe mode.

Link to comment
Share on other sites
aben
aben
Posted
Posted

@ghost8282 Hmm, I kinda doubt this is an issue with your OC config.plist's attributes. Sounds more like your system-config itself and/or some I/O attached that could be possibly preventing OC's safe mode patches from detecting the startup disk and further booting into safe mode but I could be totally wrong here. The only suggestion I can think of is: have you tried launching OC directly using OpenCore.efi instead of EFI/BOOT/BOOTx64.efi

  • Like 1
Link to comment
Share on other sites
ghost8282
ghost8282
Posted
Posted (edited)

Trying to boot Opencore.efi is the same unfortunately.

Maybe this could be related to the need of a third party kext to detect the sata controller.

I think too that this could be something related to the disk/controller...Does your disk controller work out of the box with mac os?

Edited by ghost8282
Link to comment
Share on other sites
aben
aben
Posted
Posted

@ghost8282 Yup, my SATA controller works OOB with macOS; probably all the more reason the system's firmware also happens to be compatible with OC being able to boot into macOS safe mode. Makes even more sense with Vit further confirming the same. A bummer I guess but it is what it is.

  • Like 2
Link to comment
Share on other sites
ghost8282
ghost8282
Posted
Posted (edited)
2 hours ago, KanaYan said:

I saw the news that the Russian Internet is being cut off from the global Internet.

That's really odd if this will happen..unfortunately nobody at the time of writing can know how this will evolve..

Some usa companies like namech** already announced to its customers forced transfers of russian domains and domains related to russian activities.

Apple already stopped exporting products to russia, lots of companies did the same.

In real I don't see it now as a real issue, people are not stupid, and once you give them a thing it will be difficult to take it off.

Moreover (for now), they are not "cutting the internet", but moving gov/russian related assets internally, dns, hosting, etc.

Only thing to do is to wait and see, unfortunately we are all subjected to our governments, one may agree or disagree.

I have no prejudice for russian people, and nobody should have it, I hope all the best to Vitaly and all the russian friends in the opencore community.

Edited by ghost8282
  • Like 1
Link to comment
Share on other sites
miliuco
miliuco
Posted
Posted (edited)
12 hours ago, ghost8282 said:

... I ended in opening an issue in bugtracker, maybe the actual "sur-2" method needs to be updated for safe mode.

Adding -x in config.plist boot-args I can boot in safe-mode correctly.
But pressing keys on the picker (Shift Enter...) safe-mode boot ends in black screen.

Native mode, not QEMU.

 

Edited by miliuco
  • Like 2
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
Adding -x in config.plist boot-args I can boot in safe-mode correctly.
But pressing keys on the picker (Shift Enter...) safe-mode boot ends in black screen.
Native mode, not QEMU.
 

On my AMD desktop I get prohibit sign.
On intel laptop I get black screen.
Seems safe mode is a no go for a lot of people.


Sent from my iPhone using Tapatalk
  • Like 2
Link to comment
Share on other sites
miliuco
miliuco
Posted
Posted
21 minutes ago, Henry.M. said:

As mentioned before, it‘s working for me with Monterey and the latest beta by just holding SHIFT.

No for me, I can boot safe mode only with -x boot arg. Any keys (Shift, Enter...) end in black screen.

  • Like 2
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)

I upgraded my HackBookPro15,2 to OC 0.7.9.  Manual (no configurator) upgrade was painless following the steps here.  Hackintool v3.8.4 is still reporting my OC version as 0.7.8.  Is anyone else still seeing version 0.7.8 after upgrading to 0.7.9?  I have cleared NVRAM following the 0.7.9 upgrade and I have double-checked my OC drivers.

 

All good - initial issue was user error (booting from wrong EFI).

Edited by deeveedee
  • Like 1
  • Sad 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...