Jump to content
8755 posts in this topic

Recommended Posts

8 minutes ago, Mike Ranger said:

 

Well.... then if HDMI Audio is not supported please add it to the documentation.

To me that is a crucial feature, because ideally you have audio from your monitor... my monitor only supports HDMI audio.

For Notebooks this is a different situation, but I guess most users here use Desktop machines.

Is it technically feasible to have HDMI audio as well?

Another thought.... there might be users who just want the chime without the other audio support... something to consider.

 

Thanks

 

 

Ask https://github.com/Goldfish64

Guys, I'm having lots of problems trying to install Catalina (with OpenCore 0.55) in this computer:

CPU: intel i7-2600 (Sandy Bridge)
MAINBOARD: Gigabyte GA-P67A-D3-B3 (rev. 1.0) bios F7
GPU: ASUS GT640-2GD3 (Kepler)

I've carefully followed this guide, using Legacy Emulated NVRAM settings:
https://khronokernel.github.io/Opencore-Vanilla-Desktop-Guide/config.plist/ivy-bridge.html

But the computer hangs at the Apple Logo, and I noticed that all my BIOS settings are reset to factory defaults!!

This mainboard unfortunately has the dreaded "Gigabyte Hybrid EFI" bios, and I'm guessing that's the source of my suffering :( Is there anything I can do?

This computer is able to boot with Clover (using legacy boot), but I'd really like to migrate to OpenCore

Realtek ALC1220 on AMD MSI mobo, somewhat works. It only plays the boot chime sound 1/3 of the length though.

 

OCAU: Matching PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000)
OCAU: 1/2 PciRoot(0x0)/Pci(0x3,0x1)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x1)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (6 outputs) - Success
OCAU: 2/2 PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (5 outputs) - Success

 

Edited by Pavo
Just now, telepati said:

Guys finally I got this and saying Audio connection failed.

 

272255879_ScreenShot2020-02-29at17_52_11.thumb.png.a878d0b07e21b3672158d0255fe10dae.png

 

I set up this way but still saying Audio Connection Failed;

 

491771208_ScreenShot2020-02-29at18_14_56.thumb.png.794891b35b1c05671870102871142e69.png

Your AudioCodec and AudioOut is wrong, AudioCodec should be 0 and AudioOut looks like it is 0 or 2.

  • Like 1
  • Thanks 1
2 hours ago, vit9696 said:

either your audio card is unsupported, or your AudioOut is not correct, try to bruteforce all the values from 0 to N-1 outputs.

In the same environment, using bootchimecfg of goldfish, test playing the built-in ChimeData is completely normal, but it cannot be played under OC!

image.png.cc1ef88d01be8b5d51bde46599b3c8e4.png

7 hours ago, Download-Fritz said:

 

@n.d.k Your GUI seems to not handle entry hiding properly with VoiceOver (it takes 3 for 4, etc)

I moved the playaudio function call  on VoiceOver Auxiliary entry switch to after Entries and Icons displayed process are done on version 0.1.5.   Let me know if problem still exists. 

  • Like 1

Regarding audio support.

 

1. AudioDxe in AppleSupportPkg is functionally not different from https://github.com/Goldfish64/AudioPkg, and it only contains bugfixes. Therefore every sound card that originally worked with AudioDxe will work with our version too. We expect that AudioDxe may later migrate to OpenCorePkg with AudioPkg being deprecated. If the particular HDMI audio worked with the original AudioDxe, it will still work fine (as far as I know they do not though).

 

2. BootChimeCfg is not compatible with OpenCore, but it is writing exactly the same values we have in AudioDevice/AudioCodec/AudioOut to NVRAM. Therefore if you can get your audio to work with BootChimeCfg and cannot with OpenCore it is because you have borked configuration somewhere. Reading is hard, but you have a pdf with a decent amount of details.

 

3. Different audio cards support different audio formats, and unsupported message in the log means that either the port you tried to output to cannot play audio at all or you have your boot chime in an incompatible format. In the latter case you can always consult to the specification of your audio codec and e.g. reencode the chime wav into some other format e.g. 48 KHz, mono, etc.

Hi,

 

I recently install Catalina 10.15.3 using OpenCore, on a X570 3950X machine with 5700 XT. Everything working seemingly at first. However I noticed the machine will automatically restart after shutdown, sometime immediate, sometime a few minutes later.

 

- This do not happen if I shut down in Windows or Linux.

- The motherboard is ITX and each USB controller is well within 15 ports. I have also tried to create USB Mapping DSDT to rename XCI0/XCI1 to other names, and also map each port correctly.

- I have unplugged everything (other than onboard Broadcom wifi)

- There is no kernel panic or error report on restart

- I disable everything related to sleep or wake on LAN

- I have clean reinstall macOS and rebuild EFI

 

Now I'm running out of idea and don't sure where to look at. It would be great if I can get some pointer on how to diagnostic this issue.

 

Edited by siuying
1 hour ago, Andres ZeroCross said:


Where (how) did you see this information??? 

nvram -p command and hackintool shows this. As far as I know "sudo nvram StartupMute=%00" activate Startup Chime on newer mac "sudo nvram StartupMute=%01" re-activating it. 

 

739635749_ScreenShot2020-03-01at00_20_14.thumb.png.216002b099ba84df56e5b139788b2750.png

675753059_ScreenShot2020-03-01at00_20_31.thumb.png.ba15796d1c1efc20bea502281fb61e93.png

Edited by telepati
47 minutes ago, telepati said:

nvram -p command and hackintool shows this. As far as I know "sudo nvram StartupMute=%00" activate Startup Chime on newer mac "sudo nvram StartupMute=%01" re-activating it. 

 

739635749_ScreenShot2020-03-01at00_20_14.thumb.png.216002b099ba84df56e5b139788b2750.png

675753059_ScreenShot2020-03-01at00_20_31.thumb.png.ba15796d1c1efc20bea502281fb61e93.png

 

I don't have that in my NVRAM,did you manually inject it from terminal????


image.thumb.png.dcce3525e460b350c6fd4d80ed887c3f.png

54 minutes ago, telepati said:

nvram -p command and hackintool shows this. As far as I know "sudo nvram StartupMute=%00" activate Startup Chime on newer mac "sudo nvram StartupMute=%01" re-activating it. 

 

739635749_ScreenShot2020-03-01at00_20_14.thumb.png.216002b099ba84df56e5b139788b2750.png

675753059_ScreenShot2020-03-01at00_20_31.thumb.png.ba15796d1c1efc20bea502281fb61e93.png

 

 

Check your NVRAM Properties in config.plist. I don't add it. Or maybe just add "StartupMute = 0"

However i didn't use this properties for my NVRAM because i didn't see it in SampleFull.plist
image.thumb.png.45149a3ecf0f2824db99b60f6e35d92e.png

1 hour ago, Andres ZeroCross said:

 

 

Check your NVRAM Properties in config.plist. I don't add it. Or maybe just add "StartupMute = 0"

However i didn't use this properties for my NVRAM because i didn't see it in SampleFull.plist
image.thumb.png.45149a3ecf0f2824db99b60f6e35d92e.png

How is your StartupMute showing with nvram -p command? is it shows <00> or <01>?

9 hours ago, telepati said:

How is your StartupMute showing with nvram -p command? is it shows <00> or <01>?

I didn't have "StartupMute" properties in my NVRAM when i run "nvram -P"

  • Thanks 1

I have a question about Debug. I used Debug version then back to Release version, disabled watchdog settings clean the NVRAM but every restart OpenCore create an empty .txt file in EFI root. is it possible to tell OpenCore to stop creating a .txt file?

Edited by telepati
31 minutes ago, telepati said:

I have a question about Debug. I used Debug version then back to Release version, disabled watchdog settings clean the NVRAM but every restart OpenCore create an empty .txt file in EFI root. is it possible to tell OpenCore to stop creating a .txt file?


Set Target=0

  • Thanks 1

I have been trying to get the correct layout id for my audio codec(ALC1220)

https://github.com/acidanthera/AppleALC/wiki/Supported-codecs

I have tried editing DeviceProperties>Add>PciRoot(0x0)/Pci(0x1f,0x3)>layout-id

I made sure to put the number in as a hexadecimal

according to some people I "layout-id" needs to be "Layout-id"

I still can't manage to get it working

I now have renamed HDAS to HDEF and still need to try out the layout id's with the rename

apparently you can use the alcid=xxx boot arg but I don't know where to place it 

does it go under DeviceProperties>Add>PciRoot(0x0)/Pci(0x1f,0x3) or NVRAM>7C436110-AB2A-4BBB-A880-FE41995C9F82>boot-args

I also need to keep the npci=0x2000 boot arg under NVRAM>7C436110-AB2A-4BBB-A880-FE41995C9F82>boot-args or my Hackintosh won't boot

 

 

if you could tell me where to add the alcid=xxx boot arg or tell me if me any other error it would help alot

 

my config.plist is linked below

config.plist

Edited by Hector van der Aa
×
×
  • Create New...