Jump to content
8755 posts in this topic

Recommended Posts

The upgrade to OC0.8.9 on my HackBookPro6,2 has fixed the LegacyBoot bug that prevented loading HfsPlusLegacy.efi.  The OC 0.8.8-0.8.9 upgrade was painless.  As part of the upgrade, I installed OC0.8.9's LegacyBoot (and I also installed OC0.8.9's LogoutHook).

 

Thank you OC developers!!!

Edited by deeveedee
  • Like 1

@eSaF

Yes, MB fixed the overhanging text in a recent commit but there is another related issue that he's working on it and the commits after that have reverted to the verbose text. Hopefully it will be fixed soon. But, yes, it's strange why there are systems without the issue (like mine).

  • Like 1

@eSaF

 

I assume you use a different theme than Acidantera - GoldenGate stock. If this is so, can you try an OpenCore build that produces the verbose lines in the picker screen, but changing PickerVariant to Default (equivalent to Acidanthera/GoldenGate)?
It seems that only those who use a theme other than stock have this issue. I am also going to try but in reverse, changing PickerVariant to a theme to see if those lines are displayed.

  • Like 2

Ventura beta 13.3 killed "enable-backlight-registers-fix" on DeviceProperties (same -igfxblr on Boot argument).
My Dell Vostro 5490 (i5-10210u) after update, is acting like without this Whatevergreen proprieties. Very dim light screen on boot and after some time backlight restore to normal.
Anybody else? Solutions?

 

  • Sad 2

Hi all

 

I can't build OC 0.9.0 commit c6ce045. Any ideas !

 

Spoiler

/Users/mathieu/OC/OpenCorepkg/UDK/Build/OpenCorePkg/DEBUG_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib/OUTPUT/X64/Sha512Avx.iii:25: error: segment name `RODATA_SECTION_NAME' not recognized

make: *** [/Users/mathieu/OC/OpenCorepkg/UDK/Build/OpenCorePkg/DEBUG_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib/OUTPUT/X64/Sha512Avx.obj] Error 1

 

 

build.py...

: error 7000: Failed to execute command

make tbuild [/Users/mathieu/OC/OpenCorepkg/UDK/Build/OpenCorePkg/DEBUG_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib]

 

 

build.py...

: error F002: Failed to build module

/Users/mathieu/OC/OpenCorepkg/UDK/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib.inf [X64, XCODE5, DEBUG]

 

- Failed -

 

  • Like 1
  • Sad 2

@Matgen84

The rodata section name has been changed in a recent build but I don’t know why you get this error. I’ve tried and compiled successfully the release (not debug) version on Ventura. 
 

https://github.com/acidanthera/OpenCorePkg/commit/29274ba613d13fb64f26b2a65708f61f23d489ce

 

Edited by miliuco
  • Like 2
1 hour ago, miliuco said:

@Matgen84

The rodata section name has been changed in a recent build but I don’t know why you get this error. I’ve tried and compiled successfully the release (not debug) version on Ventura. 
 

https://github.com/acidanthera/OpenCorePkg/commit/29274ba613d13fb64f26b2a65708f61f23d489ce

 

 

@miliuco no problem with commit f34a6dd (02/22).

 

But today local UDK directory corrupted. I recreate it, all works fine. 🤣

 

 

 

Edited by Matgen84
  • Like 2
On 2/19/2023 at 3:54 PM, Stefanalmare said:

Ventura beta 13.3 killed "enable-backlight-registers-fix" on DeviceProperties (same -igfxblr on Boot argument).
My Dell Vostro 5490 (i5-10210u) after update, is acting like without this Whatevergreen proprieties. Very dim light screen on boot and after some time backlight restore to normal.
Anybody else? Solutions?

 

 

Hope it will be fixed soon, I reverted back to Monterey 12.6.3 as I need it for my Dell Latitude 7400 :( 

Hey all,

 

Can anyone see in my config why my system will boot perfectly but trying to update to the latest beta results in being stuck at the dreaded EXITBS:START.

Config attached.

OC & Kexts updated today.

config.plist

[mention=1083558]SavageAUS[/mention]
I don't see anything wrong in config.plist. Try SecureBootModel=j160 instead of Default. Is there a difference?

Unfortunately that did not help.
I’ll take any other suggestions.
1d3419bcea9672e6d20ce7be088e2861.jpg


Sent from my iPhone using Tapatalk
  • Like 1
On 3/2/2023 at 11:25 AM, SavageAUS said:

Hey all,

 

Can anyone see in my config why my system will boot perfectly but trying to update to the latest beta results in being stuck at the dreaded EXITBS:START.

Config attached.

OC & Kexts updated today.

config.plist 42.8 kB · 4 downloads

 

Hi @SavageAUS Whate are you talking about: Opencore 0.9.0 Beta or Ventura 13.3 Beta ? As Opencore stops at EXITBS:START. Is not Ventura problem, I think. Do you update all efi files: boot.efi, opencore.efi... or build new commit. Because on your screen shot, OC don't clean verbose on GUI. If I remember well, this problem is solved now.

 

Apple Secure Boot appeared in macOS 10.13 on models with T2 chips. There is a list of vaqlues : configuration.pdf file. For example, j160 --> Macpro7,1 or x86legacy for Macs without T2 chip.

Edited by Matgen84

Having this error when building OC with ...

build -a X64 -b RELEASE -t XCODE5 -p OpenCorePkg/OpenCorePkg.dsc

Thanks.

 

Spoiler

 

/Users/badruzeus/Projects/UDK/Build/OpenCorePkg/RELEASE_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib/OUTPUT/X64/Sha512Avx.iii:25: error: segment name `RODATA_SECTION_NAME' not recognized
make: *** [/Users/badruzeus/Projects/UDK/Build/OpenCorePkg/RELEASE_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib/OUTPUT/X64/Sha512Avx.obj] Error 1

build.py...
 : error 7000: Failed to execute command
make tbuild [/Users/badruzeus/Projects/UDK/Build/OpenCorePkg/RELEASE_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib]

build.py...
 : error F002: Failed to build module
/Users/badruzeus/Projects/UDK/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib.inf [X64, XCODE5, RELEASE]

- Failed -
Build end time: 15:39:58, Mar.04 2023
Build total time: 00:01:29

 

 

  • Sad 1
43 minutes ago, Badruzeus said:

Having this error when building OC with ...

build -a X64 -b RELEASE -t XCODE5 -p OpenCorePkg/OpenCorePkg.dsc

Thanks.

 

  Reveal hidden contents

 

/Users/badruzeus/Projects/UDK/Build/OpenCorePkg/RELEASE_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib/OUTPUT/X64/Sha512Avx.iii:25: error: segment name `RODATA_SECTION_NAME' not recognized
make: *** [/Users/badruzeus/Projects/UDK/Build/OpenCorePkg/RELEASE_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib/OUTPUT/X64/Sha512Avx.obj] Error 1

build.py...
 : error 7000: Failed to execute command
make tbuild [/Users/badruzeus/Projects/UDK/Build/OpenCorePkg/RELEASE_XCODE5/X64/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib]

build.py...
 : error F002: Failed to build module
/Users/badruzeus/Projects/UDK/OpenCorePkg/Library/OcCryptoLib/OcCryptoLib.inf [X64, XCODE5, RELEASE]

- Failed -
Build end time: 15:39:58, Mar.04 2023
Build total time: 00:01:29

 

 

 

Do you try this:

 

cd UDK
. ./edksetup.sh
make -C BaseTools
build -a X64 -b RELEASE -t XCODE5 -p OpenCorePkg/OpenCorePkg.dsc

Then only as usual, for new commit and next build

build -a X64 -b RELEASE -t XCODE5 -p OpenCorePkg/OpenCorePkg.dsc

 

 

Edited by Matgen84
  • Like 1
  • Confused 1
5 hours ago, Matgen84 said:

Do you try this:

cd UDK
. ./edksetup.sh
make -C BaseTools
build -a X64 -b RELEASE -t XCODE5 -p OpenCorePkg/OpenCorePkg.dsc

Then only as usual, for new commit and next build

build -a X64 -b RELEASE -t XCODE5 -p OpenCorePkg/OpenCorePkg.dsc

 

Yeah, I did. That was weird.

Edited by Badruzeus
  • Sad 1
×
×
  • Create New...