OpenCore General Discussion

[Slice]

Orange disk icon appeared due to a bug in SATA controller firmware. It can't be corrected.

But we can patch the driver "External" -> "Internal" string inside  or just replace orange icon by metallic one.

[miliuco]

@fusion71au

I don't have the orange disk icons issue, all is working as before. Now on OpenCore 0.9.1. But the hardware is very different.

[Ellybz]

@fusion71au

Same story here. No such odd behaviors are reported on X299.

Everything works as intended. And yes I know, I use lots  of drives .

 

Spoiler

 

 

[fusion71au]

Thanks guys, for all your inputs.  

 

The orange disk icons issue is merely cosmetic and TBH I am not too fussed about it.  The main annoyance is the boot slowdown and AHCI error spamming due, I assume, to some incompatibility of my old DVD-RW drive with the new AHCI drivers in 13.3+.  This probably won't affect all DVD drives or SATA controllers, but I am hoping that maybe an OC patch can suppress error logging (funnily enough, I can still play movies in 13.3 on my DVD drive).

 

16 hours ago, Slice said:

Orange disk icon appeared due to a bug in SATA controller firmware. It can't be corrected.

But we can patch the driver "External" -> "Internal" string inside  or just replace orange icon by metallic one.

 

I have read that there is a bug in Gigabyte's BIOS for my ancient P55A motherboard that is the main cause of the orange icons.  Nevertheless, enabling the External Icons patch for AppleAHCIPort.kext in Clover or OC quirk worked (changing the "External" string to "Internal". string) in older macOS up to 13.2.1 but not 13.3 for my system.

 

The manual custom disk icon method still works (copy/pasting the Internal.icns file from IOStorageFamily.kext/Contents/Resources in Finder-->creates hidden ".VolumeIcon.icns" file on root of volume) - 

Spoiler

 

 

9 hours ago, eSaF said:

@fusion71au Hi I've had think about your orange Icon (Internal/External Disk) glitch. It may be a bit far fetch and clutching at straws but did you at any time alter or made an entry into the Info.plist of the NVMe.kext?

The reason I came up with this assumption, I was trying to solve the 'Unknown Connection' in 'Disk Utility' for my M.2 drives and made a few alterations to the NVMe.kext Info.plist to correct it and got the result you described (see attached) with some of my disks reading as External which is wrong.

  Reveal hidden contents

 

 

Besides root patching with OCLP 0.6.2 for non-metal AMD Terascale 2 graphics, I have not modified any kexts (including NVMe.kext) manually.

[SavageAUS]

Hope this is the right place for this.

I am working on the "cosmetic" side on my Dell Latitude 3410, GUI & Boot Chime.

I cannot for the life of me get the boot chime to work.

I have the resources folder and the sounds in the audio folder.

I believe config is correct, just get no startup chime.

Archive.zip

[FirstCustomac]

3 hours ago, SavageAUS said:

Hope this is the right place for this.

I am working on the "cosmetic" side on my Dell Latitude 3410, GUI & Boot Chime.

I cannot for the life of me get the boot chime to work.

I have the resources folder and the sounds in the audio folder.

I believe config is correct, just get no startup chime.

Archive.zip 916.16 kB · 3 downloads

It might be helpful to look at your debug log. If OC finds your audio device, perhaps, this may help you to troubleshoot.

Edited April 6, 2023 by FirstTimeCustomac

[feartech]

1 hour ago, eSaF said:

Hi - I had a look at your config.plist and found a few errors (see attached including my working examples).

You need to find the correct Codec Value for your system and insert this into the config.plist (Dortania has an extensive list of Codec examples that you can try until you find the correct one for your system) again, see my examples attached. Good luck.

  Hide contents

 

you could also add your Layout-ID in your audio section and remove the boot argument

[miliuco]

@SavageAUS

Did you follow the guide? I’ll check your config when I’ll come back to home. 
 

https://dortania.github.io/OpenCore-Post-Install/cosmetic/gui.html#setting-up-boot-chime-with-audiodxe

[SavageAUS]

Yeah I followed the guide. I have boot chime working on my AMD hack and my other laptop the one in my signature but not this one.
The problem is the guide doesn’t match up to what is in OC anymore. It needs updating but I’ll continue to read and use OC debug.


Sent from my iPhone using Tapatalk

[SavageAUS]

Just to add more information.

I have working native nvram.

gfutil output = 00:1f.3 8086:02c8 /PCI0@0/HDEF@1F,3 = PciRoot(0x0)/Pci(0x1F,0x3)

ioreg IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/HDEF@1F,3/AppleHDAController@1F,3/IOHDACodecDevice@1F,3,0

Config, debug log and ioreg attached.

Spoiler

 

 

Archive.zip

[miliuco]

@SavageAUS

I’m pretty sure that the guide is not outdated. It was updated by myself a few months ago. No changes in that OpenCore section after that. 

 Audio chipset model of the motherboard?

[SavageAUS]

[mention=1083558]SavageAUS[/mention]
I’m pretty sure that the guide is not outdated. It was updated by myself a few months ago. No changes in that OpenCore section after that. 
 Audio chipset model of the motherboard?

ALC236 is what I have found mine to be.


Sent from my iPhone using Tapatalk

[Alpha22]

Question: wanted to ask to have SIP enabled but not completely is it possible

[SavageAUS]

Now you just have to find the Lay-out ID relevant for that Codec. You'll be be presented with a potential list of numbers i.e 1,2,3,4,5,7,9,10,11 and probably upwards, unfortunately you'll have to try each one until your speakers are working and Headphones are also working and recognised when plugged in.
Good luck and keep us posted on progress.
 
PS - This is what I found: 

Realtek

ALC236

0x100001, 0x100002, layout 3, 11, 12, 13, 14, 15, 16, 17, 18, 23, 36, 54, 55, 99

13 (10.9)

With the layout I am using (15) and have audio working fine. No mic but that’s intel sst or something and will never work.
I have tested different layout ids and they all produce sound in the os but not the startup chime.


Sent from my iPhone using Tapatalk

[FirstCustomac]

10 hours ago, SavageAUS said:

Just to add more information.

I have working native nvram.

gfutil output = 00:1f.3 8086:02c8 /PCI0@0/HDEF@1F,3 = PciRoot(0x0)/Pci(0x1F,0x3)

ioreg IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/HDEF@1F,3/AppleHDAController@1F,3/IOHDACodecDevice@1F,3,0

Config, debug log and ioreg attached.

 

In your log,

 

 

Try adding --force-device=PciRoot(0x0)/Pci(0x1f,0x3) in AudioDXE arguments

 

[pkdesign]

1 hour ago, Alpha22 said:

Question: wanted to ask to have SIP enabled but not completely is it possible

Absolutely. I do not have SIP completely enabled in order to run some software and I have never had any issues.

[Alpha22]

2 minutes ago, pkdesign said:

Absolutely. I do not have SIP completely enabled in order to run some software and I have never had any issues.

what I would like, can you advise me what to set in csr-active-config

[Slice]

3 hours ago, SavageAUS said:

With the layout I am using (15) and have audio working fine. No mic but that’s intel sst or something and will never work.
I have tested different layout ids and they all produce sound in the os but not the startup chime.

Don't mix sound in macOS (AppleHDA.kext with several layouts) with startup chime produces by AudioDxe.efi working before the system starts.

[miliuco]

As @Slice says, layout-id has nothing to do with boot chime.

 

Try this config.plist, only 3 changes:

• 2 keys aded in NVRAM >> Add >> 7C436110-AB2A-4BBB-A880-FE41995C9F82 (StartupMute = 00 and SystemAudioVolumeDB = E2)
• UEFI >> Audio >> AudioOutMask changed to -1.

Sure the answer is yes but do you have OCEFIAudio_VoiceOver_Boot.mp3 in Resources/Audio?

 

config.plist

Edited April 7, 2023 by miliuco

[SavageAUS]

10 hours ago, FirstTimeCustomac said:

 

In your log,

 

 

Try adding --force-device=PciRoot(0x0)/Pci(0x1f,0x3) in AudioDXE arguments

 

I am not sure where to add AudioDXE arguments?

 

5 hours ago, miliuco said:

As @Slice says, layout-id has nothing to do with boot chime.

 

Try this config.plist, only 3 changes:

• 2 keys aded in NVRAM >> Add >> 7C436110-AB2A-4BBB-A880-FE41995C9F82 (StartupMute = 00 and SystemAudioVolumeDB = E2)
• UEFI >> Audio >> AudioOutMask changed to -1.

Sure the answer is yes but do you have OCEFIAudio_VoiceOver_Boot.mp3 in Resources/Audio?

 

config.plist 47.46 kB · 1 download

 

Yes I have all the audio files in the resources > audio folder.

I made the changes you suggest with no luck unfortunately. I did reset nvram in between to be sure.

Perhaps as per the guide mine os one of the devices that needs the file changed? Mines a Dell Latitude 3410.

Spoiler

Attached new files,

Archive.zip

[FirstCustomac]

26 minutes ago, SavageAUS said:

I am not sure where to add AudioDXE arguments?

[SavageAUS]

7 hours ago, FirstTimeCustomac said:

This has solved the issue. Seems like a bandaid though.

The device is there so not sure why it would need to be forced.

Hoping a dev can take a look and see what's up.

 

Now onto the rest of the cosmetics.

 

Thanks to all that helped.

Archive.zip

[gorans]

Hi,

Updated to 0.9.1 and ResetNVRAM afterwards. Now my hack boots with "You shut down Your computer because of a problem" message after every restart, and boot is much slower.

There is "shutdown_stall_2023-******_iMac.shutdownStall" file created in DiagnosticReports after every restart. I tried deleting it but nothing changed.
I don't know if it's relevant, but there are Diagnostics Reporter Error accessing <private>. <private> and Invalid launch errors in console.

 

Thanks,

G

 

 

[FirstCustomac]

4 hours ago, SavageAUS said:

This has solved the issue. Seems like a bandaid though.

The device is there so not sure why it would need to be forced.

Hoping a dev can take a look and see what's up.

 

Now onto the rest of the cosmetics.

 

Thanks to all that helped.

Archive.zip 930.99 kB · 0 downloads

The answer to your question can be found in OpenCore's Configuration.pdf or in acidanthera/bugtracker#740 

[SavageAUS]

The answer to your question can be found in OpenCore's Configuration.pdf or in acidanthera/bugtracker#740 

Thank you for pointing me to that. It does seem the devs are aware of this and forcing the device is the “fix”. Hey it works so I’m happy.


Sent from my iPhone using Tapatalk