toleda / audio_CloverALC

macOS Realtek ALC onboard audio with Clover
679 stars 109 forks source link

After couple of restart #88

Open oguz463 opened 7 years ago

oguz463 commented 7 years ago

I have g170 d3h with alc 1150 codec. after renaming to hdef I used alc120 command sound was workingperfect. then couple of restarts just cracking sound actually no sound.

toleda commented 7 years ago

See README/Problem Reporting

dreamcat4 commented 7 years ago

Mine is a very similar model board (the gigabyte z170x gaming 3). But its mostly all the same thing.

Hi @toleda. I'm sorry for my bad explanations below, but I have seen just today a very similar problem as this other user. Please ignore below if you cannot follow it properly. As it does not confirm to your bug reporting process.

Anyway

This is with your SSDT-HDEF+-1.aml file to get it to first regognise / detect at all that there. To install it in the first place. (file still always there in ACPI/PATCHED). + also the realtek kext. As otherwise audio would not work. As described this thread:

https://www.tonymacx86.com/threads/solved-kext-for-alc1150-on-sierra-10-12.203282/

Then I ran you version d installer script, answered y,y,y. Whatever it doesnt tell me what will happen if i say 'n' instead. Of if can use type 1 + HDMI audio together (both). Not option for that it seem. Anyhow thats not the main point here. Your installed worked and patched OK.

Also then copied patched kext back from S/L/E also back in EFI/CLOVER/Kexts/10.12./ folder. Mistly just for safe keeping, and also because i'm paranoid / to prevent not-patched version to be loaded by mistake too early by clover. Like if other noob user take my EFI/ folder and later on adds the wrong (not-patched) original files later on by mistake, thinking its missing.

So I rebooted after your successful toleda kext patching, it worked a couple of times. Then disappeared after another re(boot). Also my GENERIC USB DAC was missing too. Perhaps clue: Which doesnt require any special driver whatsoever and should be universally recognized audio device. When I run the 'check codec' script. It say 'no codec'. Or when i re-run installer script, it says, nothing to do. Like all audio is just not there at all.

Then I have to give up on audio and do some other not-related stuff, session for 12 hours without sound. Mess about with sleep, other USB SSDT aml. Sleep it (fails). Reboot my machine and the audio is back working fine again.

I read you direct users to your troubleshooting. But its information overload and easy to get lost in there. Expecially when cross-referencing to other .pdf file cannot click the hyperlinks doesn even work in github. Sorry thats not meant as a criticism because there is a lot of good information in that.

Just my point with your existing docs is that there is no existing troubleshooting for THIS case when 'audio ok at first, then dissapears after reboots'. Your docs ATM only cover the case of solidly always 'no audio device' at all. Which is different matter. Because we had working device. Then lost it. Then it come back again another reboots.

Anyway to cut a long story shory, still not sure what the heck. Or if its gonna loose again and/or come back again. But same thing happens for my USB DAC... so then where outside (other greater apple audio subsytem) to look for this kind of strange breakage, assuming its not even relating directly to your toleda modification?

Another Question:

Does it matter, or make any difference, if cold boot (from power OFF), or from soft reboot from MacOS, or from soft reboot from windows 10? That the the hardware isnt re-initialized by BIOS? I have not had time to remember / record this situations yet. But does it acutally matter any?

dreamcat4 commented 7 years ago

BTW Another point i forgot to say is that before doing your toleda script. I actually try installing VooDooHDA from a .pkg. The installer said successful. But then could not find any such preferences pane etc. for VooDooHDA or where those installer files were written to my system. I try re-runing the VooDooHDA.pkg 2nd time to uninstall. But the PKG didnt actually offer a software removal option.

And also Lilu.kext because I got totally lost in your docs toleda (before doing properly). And so tried to manually install pieces. Was all confused. Anyhow.

So I still havent a clue how to get rid of them. I don't know if its actually still important to keep Lilu.kext in SLE for your version d patched AppleHDA.kext. I also have the AppleALC.kext too.

Actually I look in S/L/E for VoodooHDA.kext and its not there anyhow. For some reason its in /Backup Extensions/2017-02-27-23h10/VoodooHDA.kext instead.

Was thinking a fresh clean install of MacOS from scratch. To clear everything. But not had time to do that just yet.

dreamcat4 commented 7 years ago

Made fresh clean install, and ran the script [y,y,y], all looked OK for the installation. Will see if problem happens again.