public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hoël Bézier" <hoelbezier@riseup.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: alsamixer - no sound
Date: Sun, 17 Dec 2023 11:39:27 +0100	[thread overview]
Message-ID: <ZX7P4ODJvEPPHzCC@sparta> (raw)
In-Reply-To: <ff098391-3a29-4414-9ce0-959d59df2b5b@sys-concept.com>

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

>If I remember correctly, running
>alsamixer - allows you select certain cards, ESC exits
>
>alsactl store  - would write the setting to a file, under user it would be ~/.asoundrc   (I could be wrong).  But in my case "alsactl store" doesn't do anything, It opens "master" setting single bar setting.

 From `man 1 alsactl`:

```
	store <card>
		This command saves the current driver state for the selected soundcard 
		to the configuration file.
[…]
FILES
	/var/lib/alsa/asound.state (or whatever file you specify with the -f flag) 
	is used to store current settings for your soundcards. The settings include 
	all the usual soundcard mixer settings.
```

~/.asoundrc is your hand-edited card configuration (including which one is your 
primary soundcard, and /var/lib/alsa/asound.state contains the mixer settings 
for your cards, i.e. the volume levels. The latter is written by `alsactl 
store` and is owned by root, so your user has nothing to do with it. It’s 
usually read once at startup and written at shutdown to preserve sound volume 
between reboots.

This is most likely not the file you want to edit, and `alsactl store` is not 
the command you want to run, unless I misunderstood your issue.

Hoël

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-17 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-16 20:19 [gentoo-user] alsamixer - no sound thelma
2023-12-16 20:57 ` thelma
2023-12-16 21:11   ` Jude DaShiell
2023-12-16 21:25     ` thelma
2023-12-16 22:02 ` Vít Smolík
2023-12-16 22:23   ` thelma
2023-12-16 23:03 ` Jigme Datse
2023-12-16 23:16   ` thelma
2023-12-16 23:33 ` [gentoo-user] " Nuno Silva
2023-12-16 23:54   ` thelma
2023-12-17  3:00     ` Nikos Chantziaras
2023-12-17  3:31       ` thelma
2023-12-17 10:39         ` Hoël Bézier [this message]
2023-12-17  0:05   ` thelma

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=ZX7P4ODJvEPPHzCC@sparta \
    --to=hoelbezier@riseup.net \
    --cc=gentoo-user@lists.gentoo.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