Jump to content
Sign in to follow this  
Followers 0
Lord Kamina

HDMI Audio on an XFX HD5570, 1GB DDR3

23 posts in this topic

Recommended Posts

I'm close to giving up on this thing now...

I got an XFX AMD Radeon HD-5570 1GB DDR3 ram. I'm using DSDT injection and GraphicsEnabler=No. I found none of the built-in personalities worked properly for me, so I made a three-port personality from scratch and patched it into Baboon. I've currently got all ports working (HDMI, DVI and VGA), with hot-plug (mostly) working.

 

But, I have been unable to get audio out of my HDMI. As of now, I am using VoodooHDA (I'll switch to AppleHDA eventually) because I want to isolate the problem as much as possible. Voodoo shows me the HDMI device in the audio outputs but no sound comes through it. With my sense-id correctly (0x5) and Uniphy2 for that port I've tried all combinations of links and encoders (DIG5 Link A, DIG5 Dual Link, Dig 6 Link B) and all of them give me video out properly, none of them has audio. I've also tried setting the "Features" byte to both 01 and 71 (as I've seen on different personalities) and the Control Flag I've tried at 0x200 and 0x204, as per different personalities And what's generally known around the net (bcc9 and mucha's threads among others)

 

Has anybody been more successful at this than I? Does anybody have a similar card or can anyone here maybe offer some insight as to what I could be missing?

Share this post


Link to post
Share on other sites
Advertisement

The edit is done correctly. The issue is that you are using VoodooHDA instead of AppleHDA. Remove VoodooHDA from S/L/E and install the kext attached then reboot. Post a new IOreg after restart.

Kext.zip

Share this post


Link to post
Share on other sites

The edit is done correctly. The issue is that you are using VoodooHDA instead of AppleHDA. Remove VoodooHDA from S/L/E and install the kext attached then reboot. Post a new IOreg after restart.

 

Will do right away. In advance, though... I was using AppleHDA at first and switched to Voodoo because AppleHDA wouldn't even show me "HDMI" in the sound outputs.

 

P.S. Yours is a Lion version, no? Should I have been using that instead of the vanilla 10.8.2 version?

 

Ok, there it is.

appleHDA_Tiamat.ioreg.zip

Edited by Lord Kamina

Share this post


Link to post
Share on other sites

It appears that you may have to hex edit AppleHDA to get it working...

 

Install this DSDT I edited and post a new IOreg. If this DSDT does not allow mac os x to boot boot with:

 

DSDT=No

 

Note this is case sensitive

DSDT.aml.zip

Share this post


Link to post
Share on other sites

Will try that. I considered having to edit AppleHDA but Toleda's tutorial said with my device id (60 aa I think?) it was probably not needed. Then again I got to thinking maybe I should try doing the whole shebang of adding it to the HDAPlatform and all that. (haven't gotten around to that yet though, university is a {censored} this week)

 

On that DSDT I see you changed the HDEF layout (BTW I was using 28 before, changed it to 1 to properly test the HDMI audio) and added gfx-onboard to HDEF, anything else?

Share this post


Link to post
Share on other sites

I did not add anything really... I just cleaned up the DSDT and placed the info were it belongs. I also cleaned up a few of your edits.

 

Test the DSDT and then post a new IOreg.

Share this post


Link to post
Share on other sites

You have ALC887 correct?

 

Install this kext for onboard audio.

 

Yes, ALC887. Haven't really done anything to get that working though (yet). I just got my pin config and pathmaps the other day but haven't trubleshooted it at all.

Share this post


Link to post
Share on other sites

Okay, this one gave me audio devices in the system preferences but none of my ports were actually working.

Still, it's definitely an improvement over getting nothing in there, I guess. (also, you can see some Applehdastreams in the IOReg)

 

I suppose I'd have to go over the pin-config with the kext you sent now? (Also, out of curiosity, what was changed in it, other than a patched binary?)

 

P.S. This one did not show HDMI either. Only "digital out" but that should be the on-board SPDIF out, no?

applehda2_Tiamat.ioreg.zip

Share this post


Link to post
Share on other sites

The two layouts for that AppleHDA are:

 

3 Pin:

 

0x1F, 0x01, 0x00, 0x00

 

6 Pin:

 

0x77, 0x03, 0x00, 0x00

 

Only "digital out" but that should be the on-board SPDIF out, no?

 

It is showing the Apple name. It is only cosmetic...

Share this post


Link to post
Share on other sites

 

 

The two layouts for that AppleHDA are:

 

3 Pin:

 

0x1F, 0x01, 0x00, 0x00

 

6 Pin:

 

0x77, 0x03, 0x00, 0x00

 

I'll try the other layout tomorrow and report back.

 

Only "digital out" but that should be the on-board SPDIF out, no?

 

 

It is showing the Apple name. It is only cosmetic...

 

 

I know, what I meant is... there's no chance that was actually HDMI, right? I didn't test that option because I don't really have the S/PDIF add-on bracket.

Share this post


Link to post
Share on other sites

If you were to hex edit the AppleHDA you should have no issues.

 

We could also try another AppleHDA that is from ML but some people have reported popping

Share this post


Link to post
Share on other sites

Status update: I tried the 0887 layout and I still cannot get audio out of any port (they still show on my devices, mind you.) Additionally, I did one further modification to your DSDT edit: In the HDEF section you'd added hda-gfx: onboard-2, I corrected that to onboard-1 and while I still don't get audio, the TV is now shown on the devices selection (and identified correctly as SAMSUNG TV)

 

I would say this definitely narrows it down to two separate problems. On one side I gotta troubleshoot/review the on-board layout you posted and separate from that, it's becoming clear that the problem with the HDMI audio is on the side of the GFX card itself or the framebuffer configuration.

 

Anyway, I feel we're actually making progress here.

 

P.S. New IOReg.

dsdt_onboard-1_Tiamat.ioreg.zip

Share this post


Link to post
Share on other sites

The last IOreg shows onboard audio working and HDMI audio working...

 

Only they aren't, not really.

Like I said, I could select them in devices, but there was no sound through either.

Share this post


Link to post
Share on other sites

... it appears the on-board audio has "died.", I use the quotes because I have experienced similar issues with my Ethernet (which are so far always fixed by resetting the CMOS and/or leaving the rig disconnected from the AC for a while, hoping this is the case with the audio too)

 

If not, I guess I'll have to RMA it. Have you heard about something like this ever happening with Asus boards?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By noisegate
      Hi,
       
      I use AppleALC v1.3.5, I can see the device in system info but no sound. Any idea?
       
      Thanks!
       
    • By karthiksh1989
      can somebody walkthrough with the mojave installation guide?
      i have a mac high sierra 13.6 version on my macbook pro and want to install mojave on my desktop
      Exact config is Gigabyte gaming wifi 7 motherboard amy ryzen 7 2nd gen 2700X processor Gigabyte G1 8GB grapgic card VEGA 64
      running 2 nvme Samsung 256gb cards and 1 intel 180gb ssd internal and 1tb WD HDD, with 64 GB 3200Mhz Ram
       
      https://wa.me/919611736534 (whatsapp)
    • By Fede1132
      Hi guys i have a problem install macOs Mojave on my PC, I have this configuration:

      CPU: Ryzen 7 2700X;
      GPU1: GTX 970 Strix(For game rendering and 144Hz Monitor);
      GPU2: GTX 750ti Strix(For 2nd monitor rendering to get 100% performances from 1st 144Hz Monitor);
      MotherBoard: MSI x470 GAMING PLUS
      Hard Disk 1 (Windows 10): Samsung EVO M.2;
      Hard Disk 2 (For Storage): RAID (1) between two hard disks;
      Hard Disk 3 (For Mojave): Kingston SSD 120GB;

      I have created my USB with this:
       
      Create Bootable USB Code: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB -- /Applications/Install\ macOS\ Mojave.app -- nointeract && say Done. Clover Settings: Boot: Verbose; dart=0; nv_disable=0; kext-dev-mode=1; GraphicsEnabler=No; XMPDetection = No. Cpu: C6. Devices: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Inject (Full Enabled); Add ClockID (Full Enabled); FixOwnership (Full Enabled); Gui: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Enabled (Full Enabled); Screen Resolution: 1920x1080; Kernel and Kext Patches: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Apple RTC (Full Enabled); KernelPm (Full Enabled); SMBIOS: iMac(18,3); System Parameters: Inject Kexts = Yes; Inject System ID; Used Kexts: FakeSMC FakePCIID NVIDIA WEB LILU BIOS: VT-d = Disabled; XHCI Hand-Off = Enabled; Legacy USB Support: Enabled; Hard Disk: AHCI Mode; Selection Mode: Legacy + EUFI; Clover Install Log:
      Full Error Log:
       
    • By grisno
      Hi people,
       
      Installer to activate the sound card REALTEK ALC282-v2 (10ec:0282) with LayoutID 1 or 3 in MacOS. This installer does not contain AppleHDA patched Kext. To work properly, it must be installed over vanilla AppleHDA.kext.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      Speakers : OK Headphones : OK HDMI Audio : OK (Intel HD4K Tested) LineIn : N/A (Model Without LineIn) MicInt : OK MicIntNoiseReduction : OK MicExt : N/A (Model Without MicExt) AutoDetectLineIn : N/A (Model Without LineIn) Sleep : OK WakeUp : OK AutoSleep : OK Hibernate : OK Siri : OK   Tested Laptops:
       
      - HP Pavillion 15-D002SS
       
      Coming Soon:
       
      - Unified installer for the different supported operating systems.
      - Support model with LineIn jack.
       
      Modified Verbs:
      01271C20 01271D00 01271EA0 01271F90 01471C10 01471D00 01471E17 01471F90 01871CF0 01871D00 01871E00 01871F40 01E71CF0 01E71D00 01E71E00 01E71F40 02171C30 02171D10 02171E21 02171F00 01470C02   DSDT:
       
      Patch to apply with MaciASL in your DSDT
      ######################################### HDEF v1.00######################################## into method label _DSM parent_label HDEF remove_entry;into device label HDEF insertbeginMethod (_DSM, 4, NotSerialized)\n{\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "layout-id", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n //"layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 },\n "hda-gfx", Buffer() { "onboard-1" },\n "PinConfigurations", Buffer() { },\n })\n}\nend;  
    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



×