UCM for sof-rt5682
Describe the bug Support for rt5682 on Todo list
Boardname Lindlar - Tiger Lake, MaxxAudio
Logs It's still on the Todo list, can I help to get it done?
Todo list?
The list here: https://github.com/WeirdTreeThing/alsa-ucm-conf-cros
Ah that. That's just upstreaming status. Did you try running the script to install the downstream ucm?
Thanks actually not, I'm on NixOS and was looking for the configuration parameters. Nevertheless, got it running with pipewire and alsa after installing pavucontrol. Why the last is necessary, is not really obvious to me, but it does the trick. Without it, my system always falls back to 'dummy output' even though the driver are installed and the sound card is recognized.
Are you using pro audio?
Hm, no - I don't
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
From: WeirdTreeThing @.> Sent: Friday, April 11, 2025 6:38:51 PM To: WeirdTreeThing/chromebook-linux-audio @.> Cc: Torsten Boettjer @.>; Author @.> Subject: Re: [WeirdTreeThing/chromebook-linux-audio] UCM for sof-rt5682 (Issue #270)
Are you using pro audio?
— Reply to this email directly, view it on GitHubhttps://github.com/WeirdTreeThing/chromebook-linux-audio/issues/270#issuecomment-2797430581, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANWRIRM2DSMXPC2DLYSLCUD2Y7VZXAVCNFSM6AAAAAB2RRBJS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJXGQZTANJYGE. You are receiving this because you authored the thread.Message ID: @.***>
[https://avatars.githubusercontent.com/u/46109425?s=20&v=4]WeirdTreeThing left a comment (WeirdTreeThing/chromebook-linux-audio#270)https://github.com/WeirdTreeThing/chromebook-linux-audio/issues/270#issuecomment-2797430581
Are you using pro audio?
— Reply to this email directly, view it on GitHubhttps://github.com/WeirdTreeThing/chromebook-linux-audio/issues/270#issuecomment-2797430581, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANWRIRM2DSMXPC2DLYSLCUD2Y7VZXAVCNFSM6AAAAAB2RRBJS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJXGQZTANJYGE. You are receiving this because you authored the thread.Message ID: @.***>