Donny S Beatz
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Donny S Beatz
-
-
18 hours ago, ghost82 said:
Now you are doing it correctly.
Yes, and ioreg is reporting "a correct value", but not that of the device properties, it seems it still applies the boot-arg value (?), or you didn't reboot the vm (?).
Assuming the screenshot comes from a reboot of the vm (you see the changes in ioreg only after you applied the device property in the config.plist and only after a reboot, it doesn't happen "on the fly"), in device properties you have layout id 11, in ioreg you have layout id 7.
If this happens (even after applying the device property and after a reboot of the vm), check in a terminal of the vm:
nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args1. Check that the layout-id variable is not there
2. Check in config.plist that you have an entry for 7C436110-AB2A-4BBB-A880-FE41995C9F82 in the Delete tab for boot-args
3. Check that WriteFlash is enabled
Thank you again for the reply and help, I greatly appreciate it!
Correct, after each change I make, I save, unmount and reboot the VM.
When I run that nvram command I get an error that data was not found. From what I Google that seems normal?
I searched the config.plist and found 3 entries.
I enabled WriteFlash and rebooted but still nothing. I'm just not sure where that IORegistry is pulling that layout-id from.
-
10 hours ago, ghost82 said:
Ok, sorry, I need to describe it again if you use opencore configurator (I don't like it at all!!!)
1. OK
2. OK
3. OK
4. OK
5. OK
6. OK
7. No, sorry, here opencore configurator behavior is not standard in my opinion: it is asking for DATA type, but you need to input HEX data, that HEX data are written in base64 to the config.plist (what a mess!!!)
So, look at this example:
Layout n. 17 --> 17 0 0 0 (decimal)
Converted to HEX: 11 00 00 00 --> 11000000
11000000 is the value that you input into opencore configurator (type DATA):
If you save the config.plist and you open it with a text editor they are saved as base64 automatically:
So, new values to input into opencore configurator:
Layout 1: 01000000
Layout 100: 64000000
Layout 11: 0B000000
Layout 13: 0D000000
Layout 15: 0F000000
Layout 16: 10000000
Layout 17: 11000000
Layout 2: 02000000
Layout 21: 15000000
Layout 27: 1B000000
Layout 28: 1C000000
Layout 29: 1D000000
Layout 3: 03000000
Layout 30: 1E000000
Layout 34: 22000000
8. OK, check type is DATA
9. OK
10. OK
11. OK
You can check the right value is applied with ioregistry explorer (this is my layout for layout-id=7 decimal):
Values are correctly applied if you read it in <HEX>
So I went through each layout you converted for me (thank you so much, btw!) but still no dice.
I changed out the layout-id in OpenCore Configurator, verified in the config.plist that the conversion is right but in IORegistryExplorer the layout-id is not right.
If the layout # works under boot-args it should work for the layout-id value right?
-
8 hours ago, ghost82 said:
You are not converting correctly from decimal to base64, I explained that.
Don't use hexadecimal, dortania is saying AppleALC could accept hexadecimal values, not opencore.
in your screenshot you applied a layout id of 0CAAAA00 -->
(layout 12?? don't know how you converted it 
...anyway not converted correctly)
Correct values (type DATA):
Layout 1: AQAAAA==
Layout 100: ZAAAAA==
Layout 11: CwAAAA==
Layout 13: DQAAAA==
Layout 15: DwAAAA==
Layout 16: EAAAAA==
Layout 17: EQAAAA==
Layout 2: AgAAAA==
Layout 21: FQAAAA==
Layout 27: GwAAAA==
Layout 28: HAAAAA==
Layout 29: HQAAAA==
Layout 3: AwAAAA==
Layout 30: HgAAAA==
Layout 34: IgAAAA==
Layout 35: IwAAAA==
Layout 5: BQAAAA==
Layout 7: BwAAAA==
Layout 98: YgAAAA==
Layout 99: YwAAAA==
Thank you for your prompt reply again!
This is where my confusion comes into play.
I converted each of these when I tested them with the website you gave me. I noticed after a reboot I went back into check the string and that's where it is getting converted to that "0CAAAAA00" or whatever value. Is there something that could be causing this.
Just so I'm not missing a step.
- Boot up macOS
- Launch OpenCore Configurator
- Tools > Mount EFI > Mount disk
- Open config.plist from OC folder
- Go to "Device Properties"
- Add/edit "layout-id" field
- Convert layout ID i.e "11 0 0 0" to Base64
- Input in "Value" field
- Save
- Unmount EFI
- Reboot
After a reboot, I check sound preferences and don't see any device so I go back and mount the EFI/config and check the value and that's where I see that "0CAAAA00".
Sorry I forgot to mention that last night, it was well past midnight and I was ready for bed. 😅
-
10 hours ago, ghost82 said:
<data>CwAAAA==</data>
I would try all the layouts available if line in doesn't work.
https://github.com/acidanthera/AppleALC/tree/master/Resources/ALC1220
Check all the files named layoutXXX.xml and try all that listed XXX as layout-id until you find the one working for you.
I'm not entirely sure what i'm doing wrong.
I tested the different layout IDs and went through each one on the list but still can't seem to get audio to work when applying it via Device Properties.
If i do the boot-args method it will work.
Am I missing something?
-
1 hour ago, ghost82 said:
Probably yes if it works with boot-arg but not by injecting the layout
To correctly apply layout id:
0. Make sure audio is on bus 0x00 in your xml
1. Find the correct device path with hackintool (in this example PciRoot(0x0)/Pci(0x2,0x0)):
2. Mount the efi and open the config.plist with a text editor; in "DeviceProperties --> Add" add your layout-id:
<key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>layout-id</key> <data>BwAAAA==</data> </dict> .... ....
Use an integer (decimal) to base64 converter, for example:
https://v2.cryptii.com/decimal/base64
In this example BwAAAA== base64 means 7 0 0 0 decimal (7<space>0<space>0<space>0), so in that site if layout is 7 input 7 0 0 0 and convert it.
For a 2 digits layout, for example 13, input it like 13 0 0 0 (13<space>0<space>0<space>0).
3. Remove the layout id boot arg
You may want to read also this, related to audio and device path:
I was using that in the past, but switched to AppleALC since it has better quality.
About the line-in are you sure you are using the correct layout?What's your codec/motherboard?
Thank you for the reply! I will take a look at this later tonight.
The motherboard is a Gigabyte B450 AORS PRO WIFI - which has the same Realtek ALC1220 used in the article.
Just to clarify I should remove the boot-arg, then in the Device Properties add a layout-id value of "11 0 0 0" and that should work?
Also thank you for linking the thread, I will go through that as well.
-
Hi all,
Had a question for those who had to configure audio in their VM.
I was able to get an install of macOS Monterey going. I was able to get Apple services, GPU pass thru, network, etc.
I followed this article for audio: https://dortania.github.io/OpenCore-Post-Install/universal/audio.html#testing-your-layout
I was working on audio last night using OpenCore Configurator and it will work if I have the boot-arg in the NVRAM section. But, if I add the layout-id via Device Properties and remove the boot-arg as stated it doesn't appear to work.
Am I doing something incorrectly?
Also, does anyone use VoodooHDA instead? I'm curious to see if that will get my line-in for mic to work but it's not a deal breaker as I may just opt to use a USB audio interface since I'm planning to utilize this VM more for music production.
Thanks in advance!
(layout 12?? don't know how you converted it 
...anyway not converted correctly)
[Support] SpaceinvaderOne - Macinabox
in Docker Containers
Posted
I removed the layout-id but IORegistry still pulls that <07 00 00 00>
Sounds good. I'll shoot you a message.
I appreciate all the help!