Jump to content

Krazubu

Retired
  • Content Count

    697
  • Joined

  • Last visited

About Krazubu

  • Rank
    InsanelyMac Legend

Recent Profile Visitors

10,665 profile views
  1. Krazubu

    ALC892 P8P67 EVO with BIOS 3xxx

    Hi, I had missed this. Still a nice find, this can save from flashing BIOS, and may be patched from clover. I have all the hardware stuff to ruin and restore my ROMs but not everyone does. I wish we both had found these years ago.
  2. Hi, beside the sound problems I never had any issue booting with 3602. You should just check the basics, I don't think BIOS settings much matter either.
  3. Hey, better late than never, I FINALLY FOUND HOW TO GET SOUND WITH APPLE HDA AND LAST BIOS (3602) ! The solution is actually pretty simple : - Get AMIBCP tool somewhere on the web - Run it (you can run it fine in OSX using Wine). - Load your 3602 bios image. - Expand the tree to Advanced / PCI Subsystem Settings / PCH Configuration / PCH Azalia Configuration - Find "Azalia internal HDMI codec" entry in the list on the right - Put settings for "Failsafe" and "Optimal" to disabled. - Save your ROM - Flash - Sound works (considering the rest is properly configured, you should use Layout-ID #1). This is a good thing as 3xxx is a huge update that brings lots of new features and also UEFI compatibility as opposed to previous versions 2xxx that are ony EFI1.1 and have really exotic compatibility with clover and efi modules. It only took 7 years
  4. Krazubu

    AppleALC — dynamic AppleHDA patching

    Hello, here's a tricky one : ASUS P8P67 Pro and its ALC892 codec. An old problem with this mobo and nobody found a solution after years, it's probably a firmware issue but I still hope there's a workaround for it. Basically, HDA works fine with old firmware, but after updating to the latest one the codec vanishes and doesn't work at all in OSX, whatever the method (I think Voodoo HDA is ok though). I could stick with the old but this update is not cosmetic, it brings lots of improvements, like transition from EFI to UEFI and is mandatory for proper Mojave support. Looking in DPCI manager I see 2 codecs, one seems ok, the other one reads "0x00000000" for both codec ID and Revision (see picture). The configuration is ok and working with old firmware. After the update is done, I get this result, without changing any configuration (so it's theoretically still ok). Don't know what to do with this ghost device, maybe finding a way to disable it would be a good start ? Attached a picture of codec with old firmware, and with new. Side question : would you happen to know what module(s) could handle HDA in UEFI ? I'd like to try to bring the old module in the new UEFI, but can't find anything related. I'm afraid this is merged with some critical stuff like PCI lines management.
  5. Krazubu

    AptioMemoryFix

    Nop, same. But I guess there are tons of things that can interfere with this. My ACPI tables are probably pretty messed up considering that I don't feel brave enough to manually patch them. My GFX are AMD RX 580 + NV 9500GT. I think that's not the case anymore, but I remember AMD got trouble with sleep mode for years.
  6. Krazubu

    AptioMemoryFix

    I tried the sleep mode, nothing happens, only the screens go down.
  7. Krazubu

    AptioMemoryFix

    Actually I had already noticed this shell version issue once but had not made the relation with this clover issue, I don't think they are named backward, I never messed with that. About hibernation and sleep I can't test it, it NEVER worked in UEFI (was ok in legacy, depending on the OSX version). The mobo deeply crashes. On wake up it's stuck in a power loop : goes on for a few seconds then off, then on again… indefinitely. Forcing shutdown doesn't help, I must cut power with the back PSU button.
  8. Krazubu

    AptioMemoryFix

    Ok, I launched shell from my BIOS and tried to launch again the shellX64U, it crashed with the same static cursor. Rebooted and tried with shellX64 (no U) and I could run "a shell in my shell" so I removed the U one from Tools\ and voilà, the shell launched fine from clover. I could run memmap and see a quite different memory occupation. In the same move I tried again the Aptiomemoryfix from this thread without slide parameter and it booted fine. So 2 very old problems solved at once, thank you
  9. Krazubu

    AptioMemoryFix

    The shell stopped working years ago, somewhere before builds 2000 of clover. Ok, gonna check all that. Edit : ok the scan option brought it back but it still crashes. I get a fix cursor on the upper left corner. I think it's again a memory issue because it does launch fine from clover in legacy mode.
  10. Krazubu

    AptioMemoryFix

    No I launched the shell from Bios because its the only way I can reach it. It crashes when launched from Clover, since a while the option is not even present anymore. I already tried v3 and aptiofix r10
  11. Krazubu

    AptioMemoryFix

    Yes i did all that. Here is the log with fix2
  12. Krazubu

    AptioMemoryFix

    Hi Apianti, I already tried all the aptio fixes with no succes. I also tried with 105 but I'll try again increasing it more.
  13. Krazubu

    AptioMemoryFix

    Hi, I'm struggling with my mobo which has always been awful regarding memory issues. So far, only the 1st OSXAptiofix version got it to boot, from time to time. It was broken with 10.13.1, ok with 10.13.2, then broken again with 10.13.3. I tried to use the version 2 and calculate a slide value. Here's what I did : Located this area that seemed to be sufficient : available 000000000CF06000-00000000AD737FFF 00000000000A0832 000000000000000F Calculated : CF06000 - 100000 = CE06000 CE06000 / 200000 = 67 Did it backward to verify and noticed I had to increase it to 68. Used slide=104 Problem is stil the same (error allocating blah page blah…) Is there something I miss ?
  14. Krazubu

    AMD Polaris IDs on Sierra / High Sierra

    My board is now working fine in 10.13 DP2
  15. Krazubu

    AMD Polaris IDs on Sierra / High Sierra

    Thank you Matthew82. I tried your ROM, however still no joy. The behavior is identical. So either I'm doing it wrong, or there's something else somewhere that prevents this card from working fine.
×