Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,888 posts in this topic

Recommended Posts

STLVNUB
STLVNUB
Posted
Posted
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

  • Like 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 hour ago, STLVNUB said:

Doesn't get that far,

either Kernel Panic and No Boot

Bro, can I ask is this board running any thing at all i.e Windows, Ubuntu. At the moment I am running a MSI Tomahawk albeit an Intel Z490 and it is running sweet multi-booting 3 OS X Versions including Ventura along with Windows 11. There is a back story to this though, I did have the Z490 Mag to start with but unfortunately it did not support integrated and dedicated Graphics running in tandem as I like to run my machines in Headless Mode so I swopped it out for the Tomahawk and never looked back.

 

In saying all of that, after all the trials and failures you had with this board, on a personal note, I would have got rid of it for a more Hack friendly board and move on. MSI did have a reputation for not being the ideal board for a Hackintosh unlike Gigabyte but I bit the bullet and went with them after many Hack years with Gigabyte and struggling with their atrocious Z590 Board ditched them and went MSI. Have a word with your friendly neighbourhood p/c provider and swop it out for something more malleable. 

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

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 by STLVNUB
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 minute ago, STLVNUB said:

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

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.

  • Like 1
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted
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

 

  • Like 2
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted (edited)
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 by STLVNUB
  • Sad 1
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)
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 by deeveedee
Link to comment
Share on other sites
joevt
joevt
Posted
Posted
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

 

  • Like 4
  • Thanks 1
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)

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 by deeveedee
  • Like 3
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted

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

Link to comment
Share on other sites
  • 2 weeks later...
SavageAUS
SavageAUS
Posted
Posted
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
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

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
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
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 by Matgen84
Link to comment
Share on other sites
deeveedee
deeveedee
Posted
Posted (edited)

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 2
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted (edited)

Guys - A word of caution for those of us that had the Verbose Text overhang on the Boot Menu. I just updated to the latest OC version 0.9.0 (494733F) and the Verbose text is back on the Boot Menu.

I reverted to the EFI I built from 'OCAfterBootCompactLib: Avoid Verbose Boot overwriting Graphics Mode'

Spoiler

16165718.thumb.png.e05c672d3715104ec68e18c44f3bcb55.png16170407.thumb.png.1d7fc418f910c1d7a3cf80560243a80a.png

(XCODE5 Artifacts) package and it's gone (see attached)

 

PS - I put in a Bug Report hopefully it will be fixed, meanwhile I will stick with the one I built.

Edited by eSaF
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
45 minutes ago, miliuco said:

@eSaF

I don’t have this issue. You can see how Mike Beaton is working on it, my coding skills are far from understanding all what he’s doing 🥴

https://github.com/acidanthera/OpenCorePkg/pull/426

It's amazing some machines are not affected by this Bug and yet others are including my MSI Z490. I got quite excited by the latest OC released which was available a few hours ago that the Bug was fixed only to be disappointed by the outcome. Good job I am in the habit of backing up my current EFI Folder.

I will obviously continue to watch the progress of future release to see if the Text overhang is solved.

What I am surprised at is Mike Beaton got rid of it in the XCODE5 Artifact prebuild, you'd think the edits would have been implemented in this latest release, but hey what do I know or understand, I am not a Coder or programmer, I am just grateful for all the work they are doing and have done in the past.

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

@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
Link to comment
Share on other sites
miliuco
miliuco
Posted
Posted

@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
  • Thanks 1
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
57 minutes ago, miliuco said:

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

Ok Bro - will try the Default stock theme and report finding.

  • Like 2
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
1 hour ago, miliuco said:

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

Sorry Man even with the Default Theme the Text overhang is there( See attached)

@antuneddu - It makes no difference Wallpaper or not.

Spoiler

16211556.thumb.png.32f8a1b41a4c9369baf72c24db43fefe.png1142010262_Screenshot2023-02-16at21_26_54.png.8852ce6843356a313b56285f3e89dd91.png

 

  • Like 4
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...