Heh Paul!
_______________
| It would be interesting if others with realtek hardware could test, which would help determine if this issue is | unique to your hardware or more generic.
_______________
I resemble that remark about Realtek (Tested it today on my Hyperfire system with Realtek ALC892) using the 14/4/2025 release today
I had an interesting problem with the new release (I currently had the build from 29/10/2021installed).
Rebooting after installing the new files, the system hard locked (needed a manual reboot by pressing the reset switch on the tower.) The lock occurred after running STARTUP.CMD.
You (and others) may not remember, but I needed to add the statement unimix.exe -id20 -val0=0 to STARTUP.CMD, to get sound enabled with your drivers on that system. This was due to a software switch present seemingly in all the RealTek hardware which enables a feature called AUTO-MUTE by default.
IOW I needed to disable that switch to get sound with your drivers installed on a system with Realtek audio installed. As it is instance specific, it needs to be re-enabled after ever boot, whether hard or soft in nature, so the easiest way to do that was through placing the statement in STARTUP.CMD.
Anybody else who may want to try that will need to run unimix -list first to see what ID the switch is on your Realtek system. In my case it is at ID20 (hence the -ID20 in the unimix statement), but yours may be at a different ID. Substituting your ID for the one I have in the statement above may work, if AUTO-MUTE is the reason you can't get sound, even though the driver installed correctly.
However, the problem I ran into with the new build is that, after installing the 14/4/2025 version of the driver, the partition booted up, ran correctly up to the STARTUP.CMD (startup.cmd prompt window displayed) but hard locked there, and stopped the boot.
I then disabled the STARTUP.CMD, rebooted and the boot went normally and the new version of UNIAUD32 seemed to be installed, but no sound. Opening a prompt window, and running the unimix.exe -id20 -val0=0 command manually, again hard locked the system at the prompt window (doing it that way has enabled sound in the past, but only until you reboot, if the statement is not in STARTUP.CMD.
Reverting back to the 29/10/2021 build and the problems went away.
So, Paul, I haven't read the entire follow-on thread about this build, (was out in Ottawa stamping out fires for the politicians up to this weekend) but I suspect SOME problem may affect the Realtek code in the UNIAUD drivers.
Best Sir as always!
Mark
This section probably explains the failure:
hda_codec_cleanup_stream: NID=0x6
hda_codec_cleanup_stream: NID=0x3
Period size min=2f0 max=2f0
Error -22 second time.. Bailing
U16: StartStream: ConfigDev failed!!
It would be interesting if others with realtek hardware could test, which would help determine if this issue is unique to your hardware or more generic. Worst case, I should be able to test on Thursday afternoon or Friday when I'm back at home.
Meanwhile I'll search the code to see where this is coming from.
Edit: it's from here - https://trac.netlabs.org/uniaud/browser/GPL/branches/uniaud32-next/lib32/sound.c#L1025
Edit2: the other interesting thing would be to try playing audio using an app that uses libkai (eg VLC). I think that error is from uniaud16 trying to configure MMPM audio.