From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Low volume with chtmax98090 (Toshiba Chromebook 2/Swanky)
Date: Mon, 10 Aug 2020 06:26:29 +0200 (CEST) [thread overview]
Message-ID: <20200810042629.583F0F8022B@alsa1.perex.cz> (raw)
In-Reply-To: <1597033583603136063-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #45 was opened from reanimus:
It looks like the UCM configuration for this board is the Chromebook Asus C300 one, but the volume levels set by default are far too low. It looks like when Pulseaudio loads on my system, it follows the initialization steps and results in a really low volume, as the Speaker is set to 27/100 and one must manually set the alsamixer levels to fix it. I could have a periodic task reload the volume state, but I find it better to override the UCM configuration manually and tell my package manager to ignore changes to that file during upgrade.
Naturally, this is a bit of a nasty solution. It'd be nice to have an upstream fix in case other stuff is changed for this.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/45
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2020-08-10 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1597033583603136063-webhooks-bot@alsa-project.org>
2020-08-10 4:26 ` GitHub issues - opened [this message]
[not found] <1597034008999078035-webhooks-bot@alsa-project.org>
2020-08-10 4:33 ` Low volume with chtmax98090 (Toshiba Chromebook 2/Swanky) GitHub issues - edited
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200810042629.583F0F8022B@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).