Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Friends Group
    Friends Group joined the community
  3. LockDown
    Not only in Tahoe. Previous OSs now works too👍
  4. Company Registration Consultancy
    Company Registration Consultancy changed their profile photo
  5. Company Registration Consultancy
    Company Registration Consultancy joined the community
  6. Matgen84
    @MakAsrock and All. I confirm too. Using long time ago, revpatch=sbvmm as Arguments is working fine on my Z390 (Coffee Lake-R) with MacPro7,1 SMBIOS.
  7. open88vwin1
    open88vwin1 joined the community
  8. TAYOPH
    TAYOPH joined the community
  9. dangkybong789 com
    dangkybong789 com joined the community
  10. cityocalplumbing
    cityocalplumbing joined the community
  11. 王柏欣
    王柏欣 joined the community
  12. Today
  13. Amber Torres
    Amber Torres joined the community
  14. Medicaps India
    Medicaps India joined the community
  15. kaoskinkae
    Perfect in OLD2: AppleHDA.kext + Wifi Intel OCLP (OpenCore Legacy Patcher) 😄
  16. SunTew
    SunTew joined the community
  17. miliuco
    @kgp I already mentioned to @fantomas that Golden Gate is clearly more demanding than Tahoe with Gatekeeper, but until now Xattr-remove (sometimes requiring you to select "Re-sign app") or Sentinel (signing the app or disabling Gatekeeper) solved this issue. I'm worried after reading you that Apple has further tightened this system because then... what will we do with all the free, open-source apps that aren't notarized? What a problem! However, I see that @surenmunoo has uploaded a screenshot of ATH with GG beta 3. I haven't downloaded beta 3 yet; I'll do it later and comment.
  18. MakAsrock
    Yes, it works for me.
  19. IPTV Providers
    IPTV Providers changed their profile photo
  20. kaoskinkae
    perfect NEW: AppleHDA + wifi
  21. LockDown
    adding to what @ThriftLoversaid, seems to work with tahoe 😮 Let me try again later... Have to go for now
  22. MakAsrock
    And this is my interpretation:
  23. 世界
    世界 changed their profile photo
  24. surenmunoo
  25. MakAsrock
    Don't ask how it was installed, I didn't do it. The computer does not belong to me: Motherboard: ASRock Z390 Phantom Gaming 6 iGPU: Intel HD Graphics 630 dGPU: Sapphire Pulse Radeon RX 580 8GB GDDR5 RAM: 32GB DDR4-3000 SSD: 128GB WD Green M.2 Audio: Realtek ALC1220 (Onboard) LAN: Intel I219V + Realtek Dragon RTL8125AG (Dual LAN) I/O: USB 3.0 / 3.1 / 3.1 Gen 2 Monitor: Full HD (via HDMI) macOS Big Sur - Everything is installed and works perfectly. macOS Tahoe - With -no_compat_check Bootloop macOS Tahoe - With SMBIS MacPro7,1 (with -no_compat_check and without it) Everything is installed and works perfectly. config.plist.zip
  26. ThriftLover
    To fresh install Big Sur or later using unsupported smbios, I think you need vmm spoof such as revpatch=sbvmm. For an update, you need to be running on Big Sur or later as vmm spoof won't work in Catalina or older. You need both board-id bypass and vmm spoof to install or update when using unsupported smbios.
  27. chuyennhathq5
    chuyennhathq5 changed their profile photo
  28. Nourish Pet Co
    Nourish Pet Co changed their profile photo
  29. LockDown
    Im referring installation in general, as we are not in Tahoe thread. Note: Pic not mine Last time i did a fresh install ( not nessesarily Tahoe). i only mentioned Tahoe to test the "Repaired feature that SMBIOS choosing automatically according to OS version." If i use unsupported smbios WITHOUT -no_compat_check or "Skip board ID Check", i get this (which is obvious) If i use unsupported smbios WITH -no_compat_check or "Skip board ID Check", i get this (disregard whatever OS version is in the pic) I have yet to try in Tahoe if the latter still accuring on a clean install
  30. luxinhaus

    VoodooHDA 3.x

    luxinhaus replied to Slice's topic in VoodooHDA

    Can you add a .xcodeproj for traditional please
  31. CloverLeaf
    I can provide some feedback using it for the last few days. The sound is great and I don't have issues after sleep like some of you, but I observed something interesting. After sleep the sound bar indicates the volume level before the computer goes to sleep. The moment I touch "Volume UP" it does not continue from let's say 25%, it goes all the way up to a 100%. To me this is something I would not even bother "fixing" as I don't know how exactly works on the backend but so far this is probably the best/easiest sound solution we had in a loooong time Thank you again, MaLdon!
  32. LockDown
    used to have the pops on sleep/wake. solved by using codeccommander.
  33. MaLd0n
    Reproduce and extract again. The problem is that the log isn't capturing this type of issue but lets try one more time.
  34. Yesterday
  35. ian mbugua
    ian mbugua changed their profile photo
  36. LockDown
    No. F7 is to test HDA output
  37. Max.1974
    [ 36 ] 2026-07-06 17:26:54 .. 140-42493 .. 27.0.0.26A5378j macOS Golden Gate Beta. https://swdist.apple.com/content/downloads/33/33/140-42493-A_IFDF1D54Q5/t9ynqjz8q72uvzjt9jj0cwkarniw7a2lzc/140-42493.English.dist https://swdist.apple.com/content/downloads/33/33/140-42493-A_IFDF1D54Q5/t9ynqjz8q72uvzjt9jj0cwkarniw7a2lzc/InstallAssistant.pkg
  38. HyperX7
  39. kgp
    Just to make this absolutely clear: I never said or intended to say that the KDK itself has any direct effect on Bluetooth. The important point is that my system had been running flawlessly under macOS 26.5.2 with the AX210 for five consecutive days before the update to macOS 26.6 beta 4, without a single reboot and including proper sleep/wake behaviour. Only after the sequential OTA update to macOS 26.6 beta 4 did the AX210 Bluetooth side immediately fall back to the same broken BCM_4350C2 state that existed before the macOS 26.5 Bluetooth LE fixes by @Vinhts and @Z3c0ld were incorporated into @lshbluesky’s IntelBluetoothFirmware v2.5.1 fork (see https://github.com/OpenIntelWireless/IntelBluetoothFirmware/issues/505). During that earlier recovery attempt, the only working solution for me was to replace the AX210 and then apply the new Bluetooth fixes to the new card. I have now also cleared NVRAM and completely disconnected the system from power for about one hour, but unfortunately neither changed anything. For completeness: I am already using BlueToolFixup 2.7.2 from Dortania together with my SleepWatcher-based Bluetooth reset script after each wake. That exact setup worked perfectly before the 26.6 beta 4 update.
  40. fantomas
    macOS 27 Golden Gate Beta 3 Release Notes
  41. Mirone
    I’m curious now. Did you happen to clear your NVRAM? If not, could you clear your NVRAM, use my BlueWakeFixup kext, and then reboot? The KDK shouldn’t have any effect on Bluetooth. Actually, wait it could be affecting something else indirectly. I need to test that, but I’m currently busy with another project, so I’ll probably only have time to look into it over the weekend.
  42. deeveedee
    Easy update. On this hack, I had used this trick to enroll in Tahoe 26.6 Beta 3. The fix has remained implemented without needing to re-apply it, so I'm still able to apply incremental Tahoe 26.6 Beta Updates with SMBIOS MacMini8,1 (and Booter Patch "Skip Board ID Check"). ... And a smooth update on my HackBookPro16,2 Using HDAUniversal for outstanding audio quality on both platforms.
  43. strangeron
    👍
  44. MakAsrock
    So, I was just trying to test the effect of the -no_compat_check boot argument. The result was negative. I'll try it tomorrow on a different system unit with 10th Gen Intel a UHD630 iGPU and a Radeon RX 560x dGPU. Then I'll write back and tell you what happened.
  1. Load more activity
×
×
  • Create New...