Contribute
Register

AppleHDA HDMI Audio [Guide]

Set config.plist/ACPI/DSDT/Fixes/NO
Restart, reply with new files

Here. Although as I said in a previous post, FixDisplay is needed in order to make the graphics card work. Without it, I'm left with 7MB of video memory.
 

Attachments

  • report6.zip
    3.5 MB · Views: 55
FixDisplay is needed in order to make the graphics card work
Actually, Oland framebuffer loads, however, no acceleration.
Clover/FixDisplay and WhateverGreen do the same thing and may cause a conflict
Experiment
a. remove WhateverGreen.kext
b. set config.plist/ACPI/DSDT/Fixes/Yes
c. install EFI/CLOVER/ACPI/patched/ssdt_hdmi-amd-default-P0P1.zip
d. add anything else required for recognized graphics

Restart and reply with files.
 
Actually, Oland framebuffer loads, however, no acceleration.
Clover/FixDisplay and WhateverGreen do the same thing and may cause a conflict
Experiment
a. remove WhateverGreen.kext
b. set config.plist/ACPI/DSDT/Fixes/Yes
c. install EFI/CLOVER/ACPI/patched/ssdt_hdmi-amd-default-P0P1.zip
d. add anything else required for recognized graphics

Restart and reply with files.

Here you go.
Graphics card now shows as "ATI Radeon HD 7xxx 2048 MB", acceleration is enabled.

ALSO, ran the touch command, here is the unexpected new output:

Code:
Bernardos-iMac:~ bernardo$ sudo touch /System/Library/Extensions && sudo kextcache -u /
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Lilu.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_GPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleALC.kext
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.
AppleDataSetManagement.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.
KernelCache ID: 3BA8184F7DB8C8F70E0CA1E7A28C71F9

something is apparently wrong now, maybe due to all the ACPI fixes being off (except FixDisplay obviously)?
 

Attachments

  • report7.zip
    3.7 MB · Views: 66
Graphics card now shows as "ATI Radeon HD 7xxx 2048 MB"
config.plist/Graphics/FBName/Oland does not exist in AMD7000Controller.kext, remove
something is apparently wrong now, maybe due to all the ACPI fixes being off
Feel free to do the tests to figure out which is required, unlikely the cause
AppleDataSetManagement.kext
trimforce? Search works

Fix config.plist, restart, reply with new files
 
trimforce?

Yes, enabled trimforce. So that's what causes the message...
But more importantly:
config.plist/Graphics/FBName/Oland does not exist in AMD7000Controller.kext, remove
Removed, got a black screen upon restart.
Changed config.plist again using another computer, restored Oland > still black screen, can't get to the desktop.

Puzzled.
 
Changed config.plist again using another computer, restored Oland > still black screen, can't get to the desktop.
Missed: Post #1/I. Before You Install HDMI Audio/Spoiler: Prerequisites/1. Make a bootable backup
Removing an invalid argument does not cause boot failure and restoring an invalid argument does not solve a boot problem
Boot your High Sierra USB installer
 
Missed: Post #1/I. Before You Install HDMI Audio/Spoiler: Prerequisites/1. Make a bootable backup
Removing an invalid argument does not cause boot failure and restoring an invalid argument does not solve a boot problem
Boot your High Sierra USB installer
Yeah I'm not concerned, and I didn't ignore that recommendation. Just puzzled!

I could edit out the FakeID which I'm sure would let me get to the desktop with the unknown display adapter with 7MB. What would I do after booting the installer anyway?

I'm very grateful for all the help!!
I'll report back soon. I'm on Sierra btw
 
Last edited:
So all along, the last black screen problem seemed like it was just the graphic card that couldn't be initialized, or maybe the HDMI port- it all went blank after "DSMOS has arrived", but it didn't look like the system had froze or the boot had hung.
Turns out, rebooting with a monitor attached (DVI) gets me to the desktop just fine. Even the actual gfx card model is recognized.
Connecting the HDMI cable makes the DVI monitor resolution change to 1080p, as the preferences are set to "mirroring", but no signal is sent through it to the HDMI TV. Needless to say, no HDMI audio interface is present.

Files are attached.

Remark:
- I see in the last stages of the bootlog that the video port number is set to 5, while the graphics card has 3 (DVI, HDMI, VGA)...
 

Attachments

  • report8.zip
    3.8 MB · Views: 70
Turns out, rebooting with a monitor attached (DVI) gets me to the desktop just fine. Even the actual gfx card model is recognized.
Expected, config.plist/Devices/FakeID/ATI/0x67981002 is working and the Futomaki framebuffer is loading, likely, Clover default:
Code:
Futomaki (4) @ 0xebf90
DP, DP, DVI-D, HDMI
000400000403000000010101000000001204040100000000
000400000403000000010201000000002205050200000000
040000001402000000010300000000000000060600000000
000800000402000000010400000000001102010300000000

Motherboard HDMI connector is not natively supported by the framebuffer HDMI connector (0008)
Motherboard DVI connector is supported by a framebuffer DP connector (0004)
AMD/DVI connector does not support HDMI audio
See Post #1/VII. AMD Radeon Graphics/1. AMD .../2. AMDxxxxController .../1. Guide ...
 
Expected, config.plist/Devices/FakeID/ATI/0x67981002 is working and the Futomaki framebuffer is loading, likely, Clover default:
Code:
Futomaki (4) @ 0xebf90
DP, DP, DVI-D, HDMI
000400000403000000010101000000001204040100000000
000400000403000000010201000000002205050200000000
040000001402000000010300000000000000060600000000
000800000402000000010400000000001102010300000000

Motherboard HDMI connector is not natively supported by the framebuffer HDMI connector (0008)
Motherboard DVI connector is supported by a framebuffer DP connector (0004)
AMD/DVI connector does not support HDMI audio
See Post #1/VII. AMD Radeon Graphics/1. AMD .../2. AMDxxxxController .../1. Guide ...
I don't know if I understand correctly, but you're saying that there's a chance I can make it work by following one of the guides to patch the framebuffer?
I'll try again from scratch then, the last thing I tried to do before coming to get help was following the first of the three guides mentioned in the first post.

NOTE: editing framebuffer name in Clover back to the "invalid argument" Oland makes the HDMI port work again. Can this be relevant in any way?
 
Back
Top