Updated Uniaud32 build

[TeLLie]

Hi Paul,
Just found time to test you're latest uniaud build.
I have a :
Command line mixer for UNIAUD32. Version 1.1
Detected UNIAUD version 3.01.01
Detected 1 audio adapter(s)
Card info for adapter 0:
  num: 0
  id: PCH
  driver: HDA-Intel
  name: HDA Intel PCH
  longname: HDA Intel PCH at 0x80540000 irq 16
  mixer: Realtek ALC245
  componenets: HDA:10ec0245,103c8a50,00100001

And it's working fine, notice that sound is much louder playing then before.
See no habbits with this build.
Have a nice Eastern ....

If you need more info

           Greetz Tellie

[Paul Smedley]

Thanks Tellie - are you able to post the output of 'copy alsahlp$ alsa.log' with the debug build?

[TeLLie]

Hi Paul.

Will do ASAP, have to change to debug.
As I'm out off town ATM...

[Sigurd Fastenrath]

Interesting, I'm still not sure exactly HOW https://launchpad.net/ubuntu/+source/linux-meta-oem-6.11/6.11.0-1020.20 differs from a standard kernel. I'm struggling to find source patches for it

As playing around with PMUnimix and all those available unimix switches lead to no success, I opend a question on the German Linux Mint Forum:

https://www.linuxmintusers.de/index.php?topic=86025.msg1099397#new

I hope to collect more information about the OEM Kernel and its difference with the "usual" 6.8 or 6.12 Kernel.

[Dave Yeo]

As playing around with PMUnimix and all those available unimix switches lead to no success, I opend a question on the German Linux Mint Forum:

https://www.linuxmintusers.de/index.php?topic=86025.msg1099397#new

I hope to collect more information about the OEM Kernel and its difference with the "usual" 6.8 or 6.12 Kernel.

Hmm, 403 error, guess have to have an account?
Same with https://www.linuxmintusers.de/

[Paul Smedley]

Loads fine from here

[Dave Yeo]

Not here. Tried SeaMonkey, then Dooble-Qt6. Then fell back to my phone where I tried the duckduckgo browser and then Chrome, all give 403 Forbidden, You don't have permission to access this resource. My son also tried Firefox on Win 11. Phone is on a different network from our home, phone is Bell and home is Telus
Geo-blocked?
Edit:

Code Select Expand


H:\tmp>wget https://www.linuxmintusers.de/
--2025-04-19 18:45:35--  https://www.linuxmintusers.de/
Resolving www.linuxmintusers.de (www.linuxmintusers.de)... 85.13.139.169
Connecting to www.linuxmintusers.de (www.linuxmintusers.de)|85.13.139.169|:443..
. connected.
HTTP request sent, awaiting response... 403 Forbidden
2025-04-19 18:45:36 ERROR 403: Forbidden.


[Paul Smedley]

Must be some sort of geo-block - traceroute from my IP below:

Code Select Expand

1  firewalla.inc.lan (192.168.1.254)  0.255 ms  0.317 ms  0.378 ms
2  172.31.0.46 (172.31.0.46)  7.997 ms  12.811 ms  12.719 ms
3  ydc-pe2-v100.sa.leaptel.network (45.249.116.13)  12.583 ms  12.618 ms  12.730 ms
4  223.165.7.26 (223.165.7.26)  12.609 ms  12.509 ms  12.676 ms
5  e50.adl-ccdc3-bb1.globalsecurelayer.com (206.148.24.99)  23.231 ms  23.301 ms  23.384 ms
6  e54.adl-eqxae1-bb4.globalsecurelayer.com (206.148.24.14)  23.189 ms  20.989 ms  20.188 ms
7  po7.per-eqxpe2-bb5.globalsecurelayer.com (206.148.24.162)  39.425 ms  38.965 ms  38.408 ms
8  po6.per-ndcp2-bb7.globalsecurelayer.com (206.148.24.10)  38.669 ms  38.489 ms  38.319 ms
9  po8.sg-eqxsg3-bb2.globalsecurelayer.com (206.148.24.9)  83.978 ms  84.200 ms  84.406 ms
10  e53.mrs-ixmrs2-bb2.globalsecurelayer.com (206.148.26.4)  216.563 ms  216.454 ms  221.047 ms
11  e22.fra-eqxfr5-bb4.globalsecurelayer.com (206.148.26.37)  236.767 ms  236.492 ms  236.613 ms
12  po400.fra-eqxfr5-cr6.globalsecurelayer.com (206.148.26.72)  236.702 ms  236.444 ms  236.539 ms
13  80.81.192.39 (80.81.192.39)  246.045 ms  246.137 ms  246.233 ms
14  dd41708.kasserver.com (85.13.139.169)  244.939 ms  245.305 ms  245.071 ms

[Dave Yeo]

No, at least one German user has the same problem, https://forums.linuxmint.com/viewtopic.php?p=2513872 Someone else after completely powering down and back up started to access. Weird.
Tracerte ends up at the same address,

Code Select Expand


1  192.168.0.1               (192.168.0.1)  0 ms  0 ms  0 ms
2  100.123.16.15             (100.123.16.15)  40 ms  30 ms  20 ms
3  100.123.19.8              (100.123.19.8)  20 ms  20 ms  40 ms
4  100.123.19.16             (100.123.19.16)  30 ms  60 ms  60 ms
5  * * *
6  * * *
7  * * *
8  * * *
9  80.150.170.94             (80.150.170.94)  110 ms  150 ms  280 ms
10  l-ea5-i.L.DE.NET.DTAG.DE  (217.5.68.242)  210 ms  190 ms  190 ms
11  62.157.251.90             (62.157.251.90)  190 ms  190 ms  220 ms
12  dd41708.kasserver.com     (85.13.139.169)  200 ms  190 ms  200 ms


[Sigurd Fastenrath]

May be because I was logged in while copying the Adress.

Here a copy where I am logged out, I hope this may work:

https://www.linuxmintusers.de/index.php?topic=86025.msg1099404

[Paul Smedley]

OK - I did some searching - I think https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/noble/log/?h=oem-6.11-next is the list of checkins to the OEM kernel.

More specifically https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/noble/log/?h=oem-6.11-next&qt=grep&q=asus is checkins which mention asus.

https://smedley.id.au/tmp/uniaud32.sys has a small change taken from the above source.

The other possibility is that the entry 'Cirrus Amp detection not supported on OS/2' could be what's causing the problem. This function had some code that was in the 'too hard' bucket to port when I was getting things building.

Edit: I think the issue is the lack of support for the amp - seems https://forums.gentoo.org/viewtopic-p-8826751.html?sid=022a561d200218c68bbf8e86827faef6 might describe what you're experiencing?

[Sigurd Fastenrath]

Hi Paul,

thank you very much for still working on this!!

The Sound is the same as before, no change at a quick look.

I attach the alsahlp log file with this one.

Just let me know, what else I can provide!

EDIT: I noticed the "Cirrus Amp Detection is not supported on OS/2" line in the logfile.

EDIT 2: Answering your question (sorry for the delay): Yes, you nailed it, it is exactly the problem described in this thread you linked.

And: Happy Eastern to all of you around the globe!!

[TeLLie]

Thanks Tellie - are you able to post the output of 'copy alsahlp$ alsa.log' with the debug build?

Hi Paul,

here the logfile...

[Martin Iturbide]

Hi Paul

Done - https://smedley.id.au/tmp/uniaud32.sys contains:

I tried this one on real hardware, on the Thinkpad T14s. Audio 8086:02C8 (Intel Comet Lake PCH-LP cAVS).
It did not trap and it produce sound normally. Tested with the included .wav files. Volume control is also working.
It seems to be working fine for the moment.

Regards

[Paul Smedley]

Thanks Tellie and Martin - reviewed alsa.log and confirmed all necessary fixups are in place.