Jump to content

[pre-release] macOS Big Sur

gengik84

By gengik84,
in New Releases and Updates

 Share
3,698 posts in this topic

Recommended Posts

corint1
corint1
Posted
Posted

that is this ?

 

 

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time:        2020-09-11 06:16:05.313 +0300
OS Version:       ??? ??? (Build ???)
Architecture:     x86_64
Report Version:   32

Data Source:      Stackshots
Shared Cache:     B29CE7E7-6D47-344D-88F6-69075E72F0B9 slid base address 0x7fff25116000, slide 0x5116000

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

Boot args:        -v keepsyms=1 alcid=3 darkwake=0 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 23s

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

  Thread 0x815    1 sample (1)    priority 4 (base 4)
  <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
  1  start + 1 (libdyld.dylib + 88401) [0x7fff25314951] 1
    1  ??? [0x10e441454] 1
      1  ??? [0x10e4411e8] 1
        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 143418) [0x7fff2521503a] 1
         *1  ??? [0xffffff80002651f6] 1
           *1  ??? [0xffffff8000968bab] 1
             *1  ??? [0xffffff8000872e11] 1
               *1  ??? [0xffffff8000288149] 1
                 *1  ??? [0xffffff80002beded] (running) 1

  Binary Images:
        0x7fff251f2000 -     0x7fff25220fff  libsystem_kernel.dylib (7195.40.65.0.2) <3E3C3209-ADB4-3C9A-B473-04D5222BC09B>  /usr/lib/system/libsystem_kernel.dylib
        0x7fff252ff000 -     0x7fff25339fff  libdyld.dylib (831.1)                   <858A16D5-A205-3A68-BA4E-AF40C8535036>  /usr/lib/system/libdyld.dylib
Model: MacBookPro15,2, BootROM 1554.40.9.0.0, 4 processors, Quad-Core Intel Core i5, 1,8 GHz, 8 GB, SMC 
Graphics: Intel HD Graphics 620, Intel HD Graphics 620, spdisplays_builtin
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR4, 2400 MHz, Ramaxel, RMSA3260MD78HAF-2666
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x623), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1668)
Bluetooth: Version 8.0.0d51, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
PCI Card: Intel HD Graphics 620, VGA compatible controller, Internal@0,2,0
USB Device: USB 3.0 Bus
USB Device: Integrated Camera
USB Device: BCM20702A0
USB Device: Vendor-Specific Device
Thunderbolt Bus: 
 

Link to comment
Share on other sites
Manas Malla
Manas Malla
Posted
Posted

When trying to boot the macOS Big Sur installation media I have created by following the standard procedures and using the opencore i had created to boot off the preinstalled version of macOS Big Sur developer beta few months back.

I have been able to boot that old preinstalled image of dev beta1 but now trying to boot the installer from the usb with same Opencore 0.6.0, i get the following error. Please help me at the earliest. ASAP! 

00:000 00:000 OCC: No compatible mode for 1366x768@0 (max: 0) resolution
00:071 00:071 OC: Changed resolution to 1366x768@0 (max: 0) from 1366x768 - Not Found
70:274 70:202 OCAK: Failed to locate _xcpm_core_scope_msrs - Not Found
70:658 00:384 OCAK: Failed to locate _xcpm_pkg_scope_msrs - Not Found
70:691 00:033 OCAK: Failed to locate _xcpm_SMT_scope_msrs - Not Found
70:791 00:099 OCAK: Failed to locate printKextPanicLists (FFFFFFFFFFFFFFFF) - Not Found
70:816 00:025 OCAK: Failed to locate _cpuid_set_info (FFFFFFFFFFFFFFFF) - Not Found
70:881 00:064 OC: Prelink injection Lilu.kext (Patch engine) - Invalid Parameter
70:914 00:033 OC: Prelink injection VirtualSMC.kext (SMC emulator) - Invalid Parameter
70:939 00:024 OC: Prelink injection WhateverGreen.kext (Video patches) - Invalid Parameter
70:972 00:033 OC: Prelink injection AppleALC.kext (Audio patches) - Invalid Parameter
71:003 00:031 OC: Prelink injection SMCProcessor.kext () - Invalid Parameter
71:028 00:024 OC: Prelink injection USBInjectAll.kext (USB ports injector) - Invalid Parameter
71:050 00:021 OC: Prelink injection RealtekRTL8111.kext (Realtek Ethernet LAN) - Invalid Parameter
71:081 00:030 OC: Prelink injection AirportBrcmFixup.kext (Broadcom WiFi fix up) - Invalid Parameter
71:105 00:024 OC: Prelink injection BT4LEContinuityFixup.kext (Bluetooth fix up) - Invalid Parameter
71:138 00:032 OC: Prelink injection RtWlanU.kext (Wifi USB) - Invalid Parameter
71:170 00:032 OC: Prelink injection RtWlanU1827.kext (Wifi USB Addon) - Invalid Parameter
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
11 minutes ago, Manas Malla said:

When trying to boot the macOS Big Sur installation media I have created by following the standard procedures and using the opencore i had created to boot off the preinstalled version of macOS Big Sur developer beta few months back.

I have been able to boot that old preinstalled image of dev beta1 but now trying to boot the installer from the usb with same Opencore 0.6.0, i get the following error. Please help me at the earliest. ASAP!

 

Update OpenCore 0.6.1 Release version, Lilu and his plugins, update your config.plist: that's the best solution for the moment.

Link to comment
Share on other sites
pop_0098
pop_0098
Posted
Posted
On 8/18/2020 at 7:17 PM, asdesoso said:

I read very carefully your guide in GitHub again, and I saw that FastBoot must be disabled, and I remembered that 2 weeks ago I did a BIOS reset, and I supposed that FastBoot comes enabled by default, so I disabled it, and voila. Here is my 2570P´s Desktop.

Cheers.

Captura de pantalla 2020-08-18 a las 16.43.04.png

ACPI, IGPU, Audio, Ethernet, Sleep are working. WiFi not because I have an Atheros AR9280, I don´t know if it´s supported on Big Sur, but there is no problem, because my 2570P is connected through Ethernet. Bluetooth and SD Card Reader I didn´t tested it, because I didn´t need it.

Cheers.

 

 

Please share your efi folder I also have   notebook 2570p I have

  • Like 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 hour ago, luky35 said:
  Reveal hidden contents

4714888_StartupDisk.png.3c3e81f07648914ed7afca9c15cab4a7.png

Please help, my macOS partition doesn't show up on Startup Disk, only the Windows one.

This was a BS Bug in the first Beta on some systems as well as flickering between Disks if you have a Multi-boot system consisting of Windows. There is a BS volume (at least on my system) that is not mounted at boot (see pic) if you force mount this volume, then the BS Volume appears in the Startup Disk pane. The other way is if you have another OS X disk like Catalina or Mojave etc on line in the system, the BS disk will also appear in Startup Disk.

Spoiler

2087756412_Screenshot2020-09-11at17_16_38.thumb.png.bdd3cfe4e61da7cc5cb523d4527d4ad8.png326998673_Screenshot2020-09-11at17_18_09.png.963f4ab147b20c961b029ae9984940a9.png

 

Link to comment
Share on other sites
luky35
luky35
Posted
Posted
40 minutes ago, eSaF said:

This was a BS Bug in the first Beta on some systems as well as flickering between Disks if you have a Multi-boot system consisting of Windows. There is a BS volume (at least on my system) that is not mounted at boot (see pic) if you force mount this volume, then the BS Volume appears in the Startup Disk pane. The other way is if you have another OS X disk like Catalina or Mojave etc on line in the system, the BS disk will also appear in Startup Disk.

  Reveal hidden contents

2087756412_Screenshot2020-09-11at17_16_38.thumb.png.bdd3cfe4e61da7cc5cb523d4527d4ad8.png326998673_Screenshot2020-09-11at17_18_09.png.963f4ab147b20c961b029ae9984940a9.png

 

 

40 minutes ago, eSaF said:

This was a BS Bug in the first Beta on some systems as well as flickering between Disks if you have a Multi-boot system consisting of Windows. There is a BS volume (at least on my system) that is not mounted at boot (see pic) if you force mount this volume, then the BS Volume appears in the Startup Disk pane. The other way is if you have another OS X disk like Catalina or Mojave etc on line in the system, the BS disk will also appear in Startup Disk.

  Reveal hidden contents

2087756412_Screenshot2020-09-11at17_16_38.thumb.png.bdd3cfe4e61da7cc5cb523d4527d4ad8.png326998673_Screenshot2020-09-11at17_18_09.png.963f4ab147b20c961b029ae9984940a9.png

 

Made after your picture and the disc appeared. You can choose a Macintosh to boot.
It's OK now and thank you.

  • Like 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted

Ok - In one of the BS betas I managed to cure this problem but in this latest Beta the problem is back if I don't have another version (Mojave or Catalina) OS X disk plugged in and I can't remember how I previously cured it plus it's too close to another Beta update due from Apple for me to do a clean install at this stage. So I am contemplating doing a clean install of the coming Beta (next week?) oppose to an update.

Spoiler

 

  • Like 1
Link to comment
Share on other sites
luky35
luky35
Posted
Posted
52 minutes ago, eSaF said:

Ok - In one of the BS betas I managed to cure this problem but in this latest Beta the problem is back if I don't have another version (Mojave or Catalina) OS X disk plugged in and I can't remember how I previously cured it plus it's too close to another Beta update due from Apple for me to do a clean install at this stage. So I am contemplating doing a clean install of the coming Beta (next week?) oppose to an update.

  Reveal hidden contents

 

Screen Recording 2020-09-11 at 18.52.18.mov

 

The same thing happens with me in the Startup disk as in your video.

  • Thanks 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

Can anyone enlighten me where i am going wrong? 

<array>
	<dict>
		<key>Arch</key>
		<string>Any</string>
		<key>BundlePath</key>
		<string>System/Library/Extensions/smbfs.kext</string>
		<key>Comment</key>
		<string>Patch engine</string>
		<key>Enabled</key>
		<true/>
		<key>Identifier</key>
		<string>com.apple.filesystems.smbfs</string>
		<key>ExecutablePath</key>
		<string>Contents/MacOS/smbfs</string>
		<key>MaxKernel</key>
		<string></string>
		<key>MinKernel</key>
		<string></string>
		<key>PlistPath</key>
		<string>Contents/Info.plist</string>
	</dict>
</array>
</plist>

 

Link to comment
Share on other sites
Manas Malla
Manas Malla
Posted
Posted
14 hours ago, Matgen84 said:

 

Update OpenCore 0.6.1 Release version, Lilu and his plugins, update your config.plist: that's the best solution for the moment.

I updated OpenCore to 0.6.1 Release as you said and even updated lilu and plugins and all the kexts and now getting this error 

OCSB: No Suitable signature Security Violation

OCB: Apple security boot prohibits this boot entry, enforcing

OCB: Load image failed- Security Violation

Please help me ASAP!

 

Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
2 hours ago, Manas Malla said:

I updated OpenCore to 0.6.1 Release as you said and even updated lilu and plugins and all the kexts and now getting this error 

OCSB: No Suitable signature Security Violation

OCB: Apple security boot prohibits this boot entry, enforcing

OCB: Load image failed- Security Violation

Please help me ASAP!

 

Maybe a lot easier for someone to help if you post your machine specs and EFI Folder, remove your personal data from config.plist before posting.

  • Like 1
Link to comment
Share on other sites
DocXavier
DocXavier
Posted
Posted (edited)
13 hours ago, eSaF said:

Ok - In one of the BS betas I managed to cure this problem but in this latest Beta the problem is back if I don't have another version (Mojave or Catalina) OS X disk plugged in and I can't remember how I previously cured it plus it's too close to another Beta update due from Apple for me to do a clean install at this stage. So I am contemplating doing a clean install of the coming Beta (next week?) oppose to an update.

  Reveal hidden contents

 

 

It is the same for me from first BS beta but I'm applying a solution that I read in the forum (may be yours??). Mounting BigSur volume, in my case using Hackintool, do it. After that, once you open Startup disk preferences, the disk icons will stay still as they should ... 

This is not a permanent vaccine. You have to repeat it every time you reset Nvram or want to change the startup disk. But I don't care, it's simple and effective ...

Edited by DocXavier
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
2 hours ago, DocXavier said:

It is the same for me from first BS beta but I'm applying a solution that I read in the forum (may be yours??). Mounting BigSur volume, in my case using Hackintool, do it. After that, once you open Startup disk preferences, the disk icons will stay still as they should ... 

This is not a permanent vaccine. You have to repeat it every time you reset Nvram or want to change the startup disk. But I don't care, it's simple and effective ...

Ah yes this is the method I had to adopt to enable BS disk to show up in the startup Disk pane. It is not absolutely crucial for me, it's just annoying to see that flickering, if I want a default Startup Disk I do it at the boot menu (Control+Enter) which is more permanent on every boot until you clean or reset the NVRAM. I don't know if this flickering bug is just affecting Hacks or if we will see an improvement in the coming Betas before the GM or final release but here's to hoping.

  • Like 1
Link to comment
Share on other sites
maxb2000
maxb2000
Posted
Posted
14 hours ago, Stefanalmare said:

Thank you! Jumpstart issue on my HP -> fix it. I can boot with the same settings like on all other hacks.

 

It's fixed in the latest 0.6.2 builds. 

 

https://github.com/dortania/build-repo/releases/download/OpenCorePkg-c72e716/OpenCore-0.6.2-RELEASE.zip

 

The required settings are:

 

GlobalConnect = NO
ConnectDrivers = YES
UnblockFSConnect = YES

  • Thanks 1
Link to comment
Share on other sites
Manas Malla
Manas Malla
Posted
Posted
10 hours ago, eSaF said:

Maybe a lot easier for someone to help if you post your machine specs and EFI Folder, remove your personal data from config.plist before posting.

Thank you for you intrest in helping me @eSaFbut i was able to fix it after adding one key into the config plist which was missing due to recent update of the config plist in 0.6.1 which was SecureBootModel and setting value to false allowed me to boot. Anyway thanks for your effort!

  • Like 1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...