OpenCore General Discussion

[STLVNUB]

16 minutes ago, STLVNUB said:

What The Fn Hell Is Up With Copying Files To USB< Don't WORK!! FROM MONTEREY AND VENTURA(HIGHWAY)

S L O W  A S A WET WIG  

Using Sudo cp ETC Doesn't Work Either

2 minutes ago, STLVNUB said:

Using Sudo cp ETC Doesn't Work Either

disabling Spotlight For The USB Works, Cp Files Fast

Edit, Mods Feel Free To Transfer My Posts About USB issues By All Means Do So.

[STLVNUB]

1 hour ago, eSaF said:

Hiya - I've tinkered with both the EFI Folders, EFI-ACPI and EFI-PANIC you uploaded by changing this Setting Kernel/Quirks/RtcChecksum that was set to 'Yes', I set that to 'No' plus updating all files and kexts. I cannot guarantee that the changes will solve the problem, but try both EFI Folder and hopefully fingers crossed the problem will be fixed. Good luck.

Archive.zip 35.88 MB · 0 downloads

Thank You

Will Test And Get Back To You, I'm Using My Script PlistTool To Transfer  SMBIOS Data

Will Report Back soon

 

edit: Geeze can't copy any files to HDD/USB, Man this u\is crazy

 

Edited January 26, 2023 by STLVNUB
copying files to destination

[STLVNUB]

Geez It's Trying To Copy 16.9 MB To Usb, File Info Says Kext Folder is 12.8MB

But My Kext Folder are 29.2MB This sucks BIG TIME☹️

 

Edited January 26, 2023 by STLVNUB

[STLVNUB]

7 minutes ago, eSaF said:

I don't know what to say!!! That's crazy you shouldn't be having such a torrid time with such a simple task like copying files. Something is seriously wrong Bro.

I will ask the obvious question, you are formatting the Drive with the correct Format and using the inbuilt Format tool in Disk Utility oppose to a third party app.

Yeah, Formatted as Fat32, the Girl Is My Girlfriend, I WISH, Look Deeply into those eye it's uncanny

One Another Note, I Have Discovered A Bug In OC OR Apple 

Do This With Caution, As You MAY Not Be Unable To Revert It.

 

Try -x as boot argument

You Will NOT be able To Boot

Comes Up With Screen About Startup contact apple

 

On Another Note, You CAN Revert It By Booting With -v

Crazy stuff going on here

 

 

[STLVNUB]

5 minutes ago, eSaF said:

If you're installing any version of OS X surely the Drive should be Formatted as 'Mac OS Extended (Journaled)' or am I missing what you're trying to do?

 

PS - I think that also goes for Drives to be used and recognised on a Mac machine. FAT32 is more pertained on a Windows PC??!!

Iy Clover Is Dead Slow, about 5 odd minutes,

Trying OC To Improve my boot times and re-install Ventura

5 minutes ago, eSaF said:

If you're installing any version of OS X surely the Drive should be Formatted as 'Mac OS Extended (Journaled)' or am I missing what you're trying to do?

 

PS - I think that also goes for Drives to be used and recognised on a Mac machine. FAT32 is more pertained on a Windows PC??!!

That's what the EFI Folder is for on HDD, doing all this on Monterey

Edited January 26, 2023 by STLVNUB

[STLVNUB]

Fixed My USB Problem, USB 2.0 Socket Was Too Loose

[STLVNUB]

6 hours ago, eSaF said:

Hiya - I've tinkered with both the EFI Folders, EFI-ACPI and EFI-PANIC you uploaded by changing this Setting Kernel/Quirks/RtcChecksum that was set to 'Yes', I set that to 'No' plus updating all files and kexts. I cannot guarantee that the changes will solve the problem, but try both EFI Folder and hopefully fingers crossed the problem will be fixed. Good luck.

Archive.zip 35.88 MB · 2 downloads

Weird KP one Still Does KP

Acpi does  same thing

Edited January 26, 2023 by STLVNUB

[deeveedee]

@STLVNUB I just saw you in the CLOVER credits here.  I know this is way off topic, but I had no idea I was in the presence of one of the CLOVER developers.  Very cool!  Whatever your contribution to CLOVER - thank you!

[STLVNUB]

1 hour ago, eSaF said:

Sorry man I am stumped as why the KP is still happening even after all the tinkering. This is a stab in the dark, have you tried to Default the BIOS Settings just to see what result you get and note if the KP is reading the same as before?

I'll Give It A Go

49 minutes ago, deeveedee said:

@STLVNUB I just saw you in the CLOVER credits here.  I know this is way off topic, but I had no idea I was in the presence of one of the CLOVER developers.  Very cool!  Whatever your contribution to CLOVER - thank you!

That was a LONG Tim ago ,😉 Thanks

My Contribution Was A Script File To Assemble Clover😊

It Was Called CloverGrower

CloverGrower-master.zipYou Can See The Magic, It Was Only Way To Compile Clover Easily

May Resurrect It To Compile Latest Clover

Edited January 26, 2023 by STLVNUB

[ANTIKO]

7 hours ago, STLVNUB said:

Weird KP one Still Does KP

Acpi does  same thing

Are you formatting the disk in "Mac OS extended (journaled)?" I also had a panic at a similar installation. I formatted it in APFS (GUID partition scheme) - and the installation went. Try it, maybe you have such a problem?

Edited January 27, 2023 by ANTIKO

[STLVNUB]

3 hours ago, ANTIKO said:

Are you formatting the disk in "Mac OS extended (journaled)?" I also had a panic at a similar installation. I formatted it in APFS (GUID partition scheme) - and the installation went. Try it, maybe you have such a problem?

Can't Get It To Boot Let Alone Format Mac OS extended (journaled)

[ANTIKO]

1 hour ago, STLVNUB said:

Can't Get It To Boot Let Alone Format Mac OS extended (journaled)

I apologize for my poor English, I mean that the installation went after formatting the disk in APFS.

[STLVNUB]

1 hour ago, ANTIKO said:

I apologize for my poor English, I mean that the installation went after formatting the disk in APFS.

Doesn't get that far,

either Kernel Panic and No Boot

[STLVNUB]

Yeah, something wrong with the board its fussy about ram, reboot loop if using duel channel

also rtc goes bezerk one minute its fine next boot will show date as 2017, sometimes 2035

 

Calendar Comes Up With My Sons 54 year Birthday Some Times

Maybe related with my problem trying to boot OC

 

resetting back to defaults need to disable secure boot otherwise only windows 11 shows up

 

on a side note, Clover was taking a hell of a long time to get to desktop (around 5 minute)

Put Monterey onto its own 250GB NVME Drive

Will Run Ventura from usb ssd 

Now Clover Loads In Under A Minute

 

Windows Is On A 1TB NVME Drive

 Also copying files to usb requires terminal, as drag and drop 

or Copy Paste Don't Work

 

Ok Enough Off Topic for now

 

 

Edited January 27, 2023 by STLVNUB

[STLVNUB]

20 minutes ago, eSaF said:

Bro be very careful here because that can be a mis-diagnosis, The reason I am erring on the side of caution, I had a problem which I thought was the RAM, would not run with more than one or two sticks anymore and it would not post, so bought 4 new sticks, same problem. Turned out to be the bloody PSU even though it was a 850 so had to buy a 1000 and all was well. If you're sure the fault is with the board, then by all means. Ok man Good luck.

Power supply is ok, it's modular, 

Have other MSI MB in my other system with 32 gig ram 9th gen i5

it beeps a couple of times if ram has changed then boots

 

[STLVNUB]

20 hours ago, STLVNUB said:

Fixed My USB Problem, USB 2.0 Socket Was Too Loose

May Have Been A Bit Premature,

copy from anywhere to usb is Still S L O W Or Dose N O T  A T  A LL

 

 

 

Edited January 27, 2023 by STLVNUB

[deeveedee]

On 10/20/2022 at 9:25 AM, Stefanalmare said:

Are you using Duet (LegacyBoot) to boot your computer? If yes, read this:

"Recommended configuration settings for this driver:

• OpenVariableRuntimeDxe.efi loaded using LoadEarly=true. OpenDuet users should not load this driver, as it

is included in OpenDuet.

• OpenRuntime.efi specified after OpenVariableRuntimeDxe.efi (when applicable), also loaded using LoadEarly=true"

I never used OpenVariableRuntimeDxe.efi in my legacy rig and I had no problems with USB, Ps2 mouse/keyboard in picker.

I just discovered that I do not need LoadEarly = True for OpenRuntime.efi.  This may be what you were trying to explain to me before, but I didn't understand.  With LegacyBoot (OpenDuet) installed on my Legacy Hack, I do not need LoadEarly = True for any UEFI > Drivers.

 

EDIT: I am booting with OpenCore 0.8.8 while still using LegacyBoot from OC 0.8.7.

 

EDIT2: It may be that I don't need OpenRuntime.efi > LoadEarly = True because I have UEFI > Quirks > RequestBootVarRouting = False.  I'm not sure.  The more I learn, the more I realize that I know very little.

 

Edited January 28, 2023 by deeveedee

[joevt]

On 1/22/2023 at 11:54 AM, miliuco said:

@aben @deeveedee

 

This is a new world for me, I still thought that the Portable Executable format is Windows specific even though I have read in the past that there are ways to use them on Unix systems as well.
I have to learn more things 🙂

UEFI uses PE images and also TE (Terse Executable) images which contains less info than PE images. You can convert TE to PE if you have a disassembler that doesn't know how to deal with TE. Usually TE is used for PEI which is stuff that happens before Open Core loads (except Open Core Legacy needs to do PEI and everything for PCs that don't have UEFI).

 

On 1/21/2023 at 3:57 PM, deeveedee said:

I can read the comments associated with new HfsPlus.efi and HfsPlusLegacy.efi here, but I don't understand.  What does "Fix W^X for firmware drivers for ExFat and HFS+" mean and what specifically do these new drivers fix?  Thank you.

W = write

X = execute

^ = exclusive or operator

 

A PE image has different sections.

Code sections are executable.

Data sections can be read only or writable.

Sections are usually not allowed to be both writable and executable. W^X is false if both W and X are true.

 

It seems the changed drivers are removing the execute flag from writable sections?

https://github.com/acidanthera/OpenCorePkg/commit/652e5c643ed1b4e9f2f67e1fc97a30747b1a37cc

 

[deeveedee]

I was having a problem with my HackBookPro6,2 (OpenCore 0.8.8, Open Core Legacy Patcher 0.6.1) where I could only boot Ventura with the -v boot-arg.  Without -v boot-arg, Ventura booting would always freeze at the Apple Logo (with no progress).  With the -v boot-arg, Ventura always boots.  Thanks to @FirstTimeCustomac who solved this problem.  His recommendation here to switch from VirtualSMC.kext to FakeSMC.kext fixed my hack's boot issue.  My HackBookPro6,2 now boots Ventura without the -v boot-arg.

 

EDIT: I was also experiencing intermittent Monterey boot problems on my HackBookPro6,2.  Replacing VirtualSMC with FakeSMC has fixed the Monterey issues, too.

 

EDIT2: I forgot how much I loved HWMonitor to view sensor data.  Now that I have switched from VirtualSMC back to FakeSMC (still booting with OpenCore), HWMonitor works great!  Thank you to Slice and all the FakeSMC developers for maintaining this kext.

Edited January 30, 2023 by deeveedee

[deeveedee]

Why is OpenCore DeviceProperties able to define new device properties for unnamed devices (devices that don't have ACPI names), but it can't overwrite existing device properties for unnamed devices?  This seems like an OpenCore coding issue that should be changed.  Details below...

 

For my HackBookPro6,2 (Dell Latitude E6410) which is using OpenCore 0.8.8 to boot High Sierra, Big Sur, Monterey and Ventura, Vit9696 advised me to set the class-code of my Nvidia dGPU audio device (Device at pci10de,be3) to <FF FF FF FF> to prevent AppleHDA from trying to initialize and enable the audio device.  Without changing the class-code to <FF FF FF FF>, AppleHDA would unsuccessfully try to initialize my dGPU audio which resulted in a very long boot delay.  More details here.  After changing class-code to <FF FF FF FF>, AppleHDA does not try to initialize my dGPU audio and my hack boots quickly without the AppleHDA delay.

 

Since my audio device already has a defined class-code, I needed to overwrite the existing class-code.  I first attempted to overwrite the class-code using OpenCore DeviceProperties, but OC would not overwrite the existing class-code because, according to Vit9696, OC will not overwrite a device property for a Device that does not have an ACPI name (e.g., my audio device is detected at pci10de,be3, but the unpatched ACPI does not define a device name like "HDAU").

 

To overcome the OpenCore DeviceProperties limitation, I needed to create an SSDT (attached) that names my device and overwrites class-code.  This SSDT overwrites the existing class-code property.

 

Using OpenCore DeviceProperties in config.plist, OpenCore is able to define new device properties (properties not already defined) for unnamed devices, but it is not able to overwrite existing device properties for unnamed devices.

 

Does anyone understand why OpenCore DeviceProperties has this limitation? Namely, why is OC DeviceProperties able to define new properties for unnamed devices, but it is not able to overwrite existing properties for unnamed devices?

 

Thank you.

SSDT-HDAU.aml.zip

[deeveedee]

Just saw this SDHC kext appear in the Acidanthera GitHub repo.  Interesting.

Edited February 2, 2023 by deeveedee

[SavageAUS]

I was having a problem with my HackBookPro6,2 (OpenCore 0.8.8, Open Core Legacy Patcher 0.6.1) where I could only boot Ventura with the -v boot-arg.  Without -v boot-arg, Ventura booting would always freeze at the Apple Logo (with no progress).  With the -v boot-arg, Ventura always boots.  Thanks to [mention=2422360]FirstTimeCustomac[/mention] who solved this problem.  His recommendation here to switch from VirtualSMC.kext to FakeSMC.kext fixed my hack's boot issue.  My HackBookPro6,2 now boots Ventura without the -v boot-arg.
 
EDIT: I was also experiencing intermittent Monterey boot problems on my HackBookPro6,2.  Replacing VirtualSMC with FakeSMC has fixed the Monterey issues, too.
 
EDIT2: I forgot how much I loved HWMonitor to view sensor data.  Now that I have switched from VirtualSMC back to FakeSMC (still booting with OpenCore), HWMonitor works great!  Thank you to Slice and all the FakeSMC developers for maintaining this kext.

I am also having to boot Ventura with latest OC in verbose mode or else it doesn’t boot all the way visibly but I can VNC in. I might give fakesmc a try and see if that helps me too. I am not using the legacy patcher though so I’ll see how I go.

Also I just updated my OC and a EFI partition is visible in the picker again, why?

Sent from my iPhone using Tapatalk

[deeveedee]

@SavageAUS Antuneddu was kind enough to explain it here.

[SavageAUS]

Ok I’m not sure where to share this but I’m having a real issue with my hackbook. I have tried a fresh install and as the video shows I cannot login, I just get looped to the black screen.

Latest OC and Kexts as of today. Sorry if the video is bad.


Sent from my iPhone using Tapatalk

[Matgen84]

8 hours ago, SavageAUS said:

Ok I’m not sure where to share this but I’m having a real issue with my hackbook. I have tried a fresh install and as the video shows I cannot login, I just get looped to the black screen.

 

Latest OC and Kexts as of today. Sorry if the video is bad.


Sent from my iPhone using Tapatalk

 

 

Can you upload horizontal video, please 

Edited February 12, 2023 by Matgen84