Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,888 posts in this topic

Recommended Posts

D-an-W
D-an-W
Posted
Posted

Good evening folks, can I please just ask if the OpenCore boot chime is now known to work over HDMI or not?

 

I have it working from the audio jacks at the rear but currently don't have speakers on this build so was trying to enable it over HDMI.

 

HDMI audio works well once macOS Ventura, Sonoma and Windows 11 are booted.

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
Good evening folks, can I please just ask if the OpenCore boot chime is now known to work over HDMI or not?
 
I have it working from the audio jacks at the rear but currently don't have speakers on this build so was trying to enable it over HDMI.
 
HDMI audio works well once macOS Ventura, Sonoma and Windows 11 are booted.

I don’t know if it works or not but did you put the pci address of the device in the audio section on your config?


Sent from my iPhone using Tapatalk
  • Thanks 1
Link to comment
Share on other sites
D-an-W
D-an-W
Posted
Posted
9 hours ago, SavageAUS said:


I don’t know if it works or not but did you put the pci address of the device in the audio section on your config?


Sent from my iPhone using Tapatalk

 

I did thanks, this is what is shown for it... 

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x1)

 

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
20 hours ago, D-an-W said:

Good evening folks, can I please just ask if the OpenCore boot chime is now known to work over HDMI or not?

 

I have it working from the audio jacks at the rear but currently don't have speakers on this build so was trying to enable it over HDMI.

 

HDMI audio works well once macOS Ventura, Sonoma and Windows 11 are booted.

For me HDMI audio works in Ventura but not at boot time with AudioDxe connected to AMD RX570.

AFAIK the driver AudioDxe can't work with AMD HDMI audio.

May be it will work with Intel or Nvidia HDMI audio. 

  • Like 4
  • Thanks 1
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted
On 8/17/2023 at 1:02 AM, Slice said:

For me HDMI audio works in Ventura but not at boot time with AudioDxe connected to AMD RX570.

AFAIK the driver AudioDxe can't work with AMD HDMI audio.

May be it will work with Intel or Nvidia HDMI audio. 

Hi, Slice:

I need convert Clover's Graphics>RadeonDeInit function to OpenCore, but according to https://dortania.github.io/OpenCore-Install-Guide/clover-conversion/Clover-config.html

this SSDT method seems not working in my M5A(FX-6300) Hackintosh.

I have posted my IOReg & 2 SSDT.aml for your reference.

Do you have any correct way to fix it ?

Screenshot 2023-08-19 at 14.42.17.png

Jin-Shin’s iMac.ioreg SSDT-GFX0.aml SSDT-Radeon-DeInit.aml

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

How can I stop OpenCore messing with the audio in ArchLinux? If I boot with F12 menu into Arch sound works, if I use OpenCore I get no output devices. I DO NOT want to use the F12 menu every time, defeats the purpose.
I have been troubleshooting this for days on the ArchLinux forums etc only to find out today that it’s OpenCore.
In my config.plist I have this set or else I do not get the boot chime.
UEFI > Driver > AudioDxe.efi > Arguments > —force-device=PciRoot(device path) device path is the actual path. Could this be causing the problem?


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites
cankiulascmnfye
cankiulascmnfye
Posted
Posted (edited)
On 8/10/2023 at 5:25 PM, deeveedee said:

Is there another entry in addition to "PlatformInfo > Generic > SystemProductName" in Open Core's config.plist that defines the Mac Model name?  I ask, because when I run Open Core Legacy Patcher, it detects my hack as "Latitude E6410" even though my SystemProductName is defined as "MacBookPro6,2" in OC's config.plist.

 

If possible, I'd like to be able to configure something in my OC config.plist that makes OCLP detect the Mac Model name and not my laptop's actual model name.

 

I'm looking through OCLP source code now to figure this out, but if someone knows already, it would be a big time saver.  Thank you.

 

I executed the following commands in terminal and don't see why OCLP wouldn't detect my Mac Model:

  

ioreg -lp IOService | grep model   
    |   "model" = <"MacBookPro6,2">
ioreg -lp IOService | grep board-id
    |   "board-id" = <"Mac-F22586C8">

 

 

That's what the "OCLP-Model" NVRAM entry is for. But iit has to be present in NVRAM/Delete as well so that it can be written:

 

Bildschirmfoto2023-08-19um16_51_19.png.c8ade3487c355f9fece5e2bd2b07b1b7.png

8 hours ago, jsl2000 said:

Hi, Slice:

I need convert Clover's Graphics>RadeonDeInit function to OpenCore, but according to https://dortania.github.io/OpenCore-Install-Guide/clover-conversion/Clover-config.html

this SSDT method seems not working in my M5A(FX-6300) Hackintosh.

I have posted my IOReg & 2 SSDT.aml for your reference.

Do you have any correct way to fix it ?

Screenshot 2023-08-19 at 14.42.17.png

Jin-Shin’s iMac.ioreg 4.96 MB · 0 downloads SSDT-GFX0.aml 306 B · 1 download SSDT-Radeon-DeInit.aml 306 B · 1 download

 

@jsl2000 If you are using Whatevergreen and DeInit is not working in OC and if it is also not working with the SSDT, create an issue report so this can be fixed.

Edited by cankiulascmnfye
  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
44 minutes ago, cankiulascmnfye said:

 

That's what the "OCLP-Model" NVRAM entry is for. But iit has to be present in NVRAM/Delete as well so that it can be written:

 

Bildschirmfoto2023-08-19um16_51_19.png.c8ade3487c355f9fece5e2bd2b07b1b7.png

 

Thanks. Where I can find more documentation about these keys and values. Please.

Link to comment
Share on other sites
  • 4 weeks later...
  • 4 weeks later...
joevt
joevt
Posted
Posted

My Mac Pro 2008 (Penryn era?) recently died so I moved all my disks containing all Intel macOS versions (Mac OS X 10.4.11 Tiger to macOS 13.4.1 Ventura) to my 2016 Skylake Hackintosh.

 

I made disk images of the partitions to use in VMs because the VMs don't support very well using actual disk partitions.
Mac OS X 10.5.8 Leopard and later boot in Parallels Desktop for Mac 19 on the Skylake Hackintosh.

Mac OS X 10.4.11 Tiger boots in VirtualBox 7.0.10 after modifying some CPUID information. https://github.com/ranma42/TigerOnVBox

 

I know there's been some work done in OpenCore to support early Mac OS X versions but I haven't read posts from users or developers about that.

For each processor, Skylake included, Dortania's OpenCore Install Guide has a section regarding configuration options for early Mac OS X versions including 10.4. Does that mean 10.4 can work on SkyLake?

 

If OpenCore can't modify CPUID like VirtualBox, then maybe it can patch the kernel sufficiently enough? Do the required patches exist already?

 

The OCLP project deals with running newer macOS versions on older Macs. I would like to go in the other direction and use older macOS versions on newer Macs/PCs.

 

  • Like 1
Link to comment
Share on other sites
  • 3 weeks later...
mrmacdi2
mrmacdi2
Posted
Posted

Hi,

 

Can somebody explain how LegacySchema works? I've read Configuration.pdf, but it's purpose and way of work is unclear to me: there are only keys, without any values.

For example, I have NVRAM - ADD - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - bluetoothInternalControllerInfo key with data, at the same time I see in NVRAM - LegacySchema - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - 7 (key number) and value bluetoothInternalControllerInfo without any data.

Link to comment
Share on other sites
cankiulascmnfye
cankiulascmnfye
Posted
Posted
1 hour ago, mrmacdi2 said:

Hi,

 

Can somebody explain how LegacySchema works? I've read Configuration.pdf, but it's purpose and way of work is unclear to me: there are only keys, without any values.

For example, I have NVRAM - ADD - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - bluetoothInternalControllerInfo key with data, at the same time I see in NVRAM - LegacySchema - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - 7 (key number) and value bluetoothInternalControllerInfo without any data.

 

I think this sections for systems without NVRAM which require emulated NVRAM. But I don't have any systems that old so I never worked with the LegacySchema

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

@mrmacdi2

 

LegacySchema is a set of NVRAM variables and OpenCore compares these to the variables present in nvram.plist so it is not necessary when we have native NVRAM. It’s required only for emulated NVRAM. 
 

If we have LegacyEnable=False and LegacyOverwrite=False, LegacySchema is not used by OpenCore. And macOS boots perfectly without the LegacySchema keys. We can even delete the  LegacySchema whole part if we have native NVRAM.

 

What is always recommended is to have WriteFlash=True.

 

Edited by miliuco
  • Like 2
Link to comment
Share on other sites
Stefanalmare
Stefanalmare
Posted
Posted
5 hours ago, mrmacdi2 said:

Hi,

 

Can somebody explain how LegacySchema works? I've read Configuration.pdf, but it's purpose and way of work is unclear to me: there are only keys, without any values.

For example, I have NVRAM - ADD - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - bluetoothInternalControllerInfo key with data, at the same time I see in NVRAM - LegacySchema - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - 7 (key number) and value bluetoothInternalControllerInfo without any data.

For Legacy (non UEFI):

1. Download OpenCore: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

2. Install LegacyBoot (first on USB installer, after on boot drive). .../OpenCore-0/Utilities/LegacyBoot

3. Install OS

4. Run LogoutHook for emulated NVRAM: ..../OpenCore-0/Utilities/LogoutHook

I use this type of OC config for legacy:

1.thumb.png.5e2d8af4a3a46a57e3af2fbd8e09d2f2.png

Like you see I use "*" for every UUID. And it is working like a dream.

You should insert normal values to NVRAM -> Add/Delete

 

If you have another question about legacy (and you'll have 😇), shot!

  • Like 1
Link to comment
Share on other sites
mrmacdi2
mrmacdi2
Posted
Posted
3 hours ago, miliuco said:

@mrmacdi2

 

LegacySchema is a set of NVRAM variables and OpenCore compares these to the variables present in nvram.plist so it is not necessary when we have native NVRAM. It’s required only for emulated NVRAM. 
 

If we have LegacyEnable=False and LegacyOverwrite=False, LegacySchema is not used by OpenCore. And macOS boots perfectly without the LegacySchema keys. We can even delete the  LegacySchema whole part if we have native NVRAM.

 

What is always recommended is to have WriteFlash=True.

 

Thanks, still unclear. I have legacy systems without hardware NVRAM and I’ve always used the regular way: put items in NVRAM - Add/Delete, without touching anything in LegacySchema.

Link to comment
Share on other sites
miliuco
miliuco
Posted
Posted
35 minutes ago, mrmacdi2 said:

I have legacy systems without hardware NVRAM and I’ve always used the regular way: put items in NVRAM - Add/Delete, without touching anything in LegacySchema.

But without native NVRAM, motherboard doesn’t save those values. Maybe you have a kind of partially emulated NVRAM. 

Link to comment
Share on other sites
mrmacdi2
mrmacdi2
Posted
Posted
29 minutes ago, Stefanalmare said:

Now I'm sorry for my time.

I have emulated NVRAM, but I have never touched LegacySchema, not before I had have turned NVRAM emulation on, not after that.

3 minutes ago, miliuco said:

But without native NVRAM, motherboard doesn’t save those values. Maybe you have a kind of partially emulated NVRAM. 

But how then LegacySchema works if it has no values, but keys only?

Link to comment
Share on other sites
Stefanalmare
Stefanalmare
Posted
Posted (edited)
2 hours ago, miliuco said:

But without native NVRAM, motherboard doesn’t save those values. Maybe you have a kind of partially emulated NVRAM. 

Config.plist from one of my legacy rigs. Core2, NVRAM emulated running latest Sonoma beta. This config is a backup, not the latest. I'm not at home.

config.plist

 

Like I said above, for having full emulated NVRAM you must install LogoutHook. This and the NVRAM config.plist make all working. Even when upgrade OS, the installer become the default boot. That good emulated NVRAM work!

Edited by Stefanalmare
  • Like 3
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
On 10/26/2023 at 1:18 AM, Stefanalmare said:

Config.plist from one of my legacy rigs. Core2, NVRAM emulated running latest Sonoma beta. This config is a backup, not the latest. I'm not at home.

config.plist 84.88 kB · 5 downloads

 

Like I said above, for having full emulated NVRAM you must install LogoutHook. This and the NVRAM config.plist make all working. Even when upgrade OS, the installer become the default boot. That good emulated NVRAM work!

Hello friend, can I have your EFI file please? I have a board model GA-H61M-D2-B3 (rev. 1.0) rev. 1.1 CPU i3 2100 RAM 4GB graphics card GT-640 2GB and would like to try installing it. This is a model that does not support UEFI mode.

Link to comment
Share on other sites
  • 1 month later...
makk
makk
Posted
Posted

I imagine at some point, when Apple drops all past Intel and AMD rigs from their list in future MacOS's that we all end up using Legacy everything and have very slim pickings if we continue to use as close as possible all Apple.

 

The idea of running MacOS on a PC was to patch all the kexts and everything else where, it is possible to run.

 

However, over the years, the development as stated in the first sentence has led to being a Mac as close as possible.  Imitation.

 

The idea of running MacOS on PC is then really detracted a bit in my thought.

 

A hack is to hack and use what is there.   Taking advantage of what is in place, not becoming it.  If you follow my thought here.

If you want a Mac buy one.

 

If you want to hack it, that is different. 

 

Back in the day, when I started this, the 'hackers' of those days, hacked and made use.

 

Any one can make a kext if they know how and what specs are needed to make it work for their piece of hardware.  I used to write scripts in UNIX many many years ago.  oops tells my age..

 

However, a hacker knows already what they are looking to do and then dive in and with their skills and intelligence see how far they can go.

 

So as long as you want to have mac on your pc exactly like a mac, then, the idea of hackintosh is lost.  Follow my thought here?

 

patching is what hackers start out by doing to find the core where all is then taken in control.  Data control and having it do precisely what is intended.
All I hear is that is not possible Mac is this and that. Well tell that to the hacker who made it possible.

 

All data.  Language is one: 1 0 1 0 1 1 0.  This is how a true hacker gains control.  the hardware is then theirs for the taking.

 

the history of data begins with those creating it and they were able to make it happen thus we are living in their work progressed through time.

 

 

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