Message-ID:

[FORTRAN] will persist for some time -- probably for at least the next decade. -- T. Cheatham

computers / alt.os.linux.slackware / Re: problem with /etc/rc.d/rc.alsa

problem with /etc/rc.d/rc.alsa

<stecbm$moa$1@dont-email.me>

https://www.rocksolidbbs.com/computers/article-flat.php?id=944&group=alt.os.linux.slackware#944

copy link Newsgroups: alt.os.linux.slackware

Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: problem with /etc/rc.d/rc.alsa
Date: Wed, 2 Feb 2022 16:43:35 -0000 (UTC)
Organization: Linux Advocacy
Lines: 16
Message-ID: <stecbm$moa$1@dont-email.me>
Injection-Date: Wed, 2 Feb 2022 16:43:35 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="9d8359b8b8be72270e29fcbc0e77f406";
logging-data="23306"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/eo4YaSl9KeFsZNsuY/5tEowk+LkoJi9Q="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:zSweBABHRQlZiGfK2aBG6nJ5+YU=
Mail-Copies-To: nobody

by: root - Wed, 2 Feb 2022 16:43 UTC

I get an error message when starting rc.alsa:

Loading ALSA mixer settings: /usr/sbin/alsactl restore
ALSA lib conf.c:1179:(parse_def) value is not a compound
ALSA lib conf.c:1697:(snd_config_load1) _toplevel_:1141:25:Unexpected char
/usr/sbin/alsactl: load_state:1674: snd_config_load error: Invalid argument

My guess is that "ALSA lib" refers to alsa-lib, but I can't
find any conf.c file. If this error message means anything
to you can you, please tell me where to look for the
offending file?

Whatever the error, it seems to eliminate all alsa devices.

Thanks.

Re: problem with /etc/rc.d/rc.alsa

<steqc3$a3l$1@posie.signal11.org.uk>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=946&group=alt.os.linux.slackware#946

copy link Newsgroups: alt.os.linux.slackware

Path: i2pn2.org!i2pn.org!aioe.org!DGjWzfH4KkkUpRm673S1gA.user.46.165.242.75.POSTED!not-for-mail
From: mjb@signal11.invalid (Mike)
Newsgroups: alt.os.linux.slackware
Subject: Re: problem with /etc/rc.d/rc.alsa
Date: Wed, 2 Feb 2022 20:42:43 +0000 (GMT)
Organization: Signal11 (www.signal11.org.uk)
Lines: 28
Message-ID: <steqc3$a3l$1@posie.signal11.org.uk>
References: <stecbm$moa$1@dont-email.me>
Reply-To: mjb@signal11.org.uk
Injection-Info: gioia.aioe.org; logging-data="13648"; posting-host="DGjWzfH4KkkUpRm673S1gA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-Notice: Filtered by postfilter v. 0.9.2

by: Mike - Wed, 2 Feb 2022 20:42 UTC

In article <stecbm$moa$1@dont-email.me>, root <NoEMail@home.org> wrote:
>I get an error message when starting rc.alsa:
>
>Loading ALSA mixer settings: /usr/sbin/alsactl restore
>ALSA lib conf.c:1179:(parse_def) value is not a compound
>ALSA lib conf.c:1697:(snd_config_load1) _toplevel_:1141:25:Unexpected char
>/usr/sbin/alsactl: load_state:1674: snd_config_load error: Invalid argument
>
>
>My guess is that "ALSA lib" refers to alsa-lib, but I can't
>find any conf.c file. If this error message means anything
>to you can you, please tell me where to look for the
>offending file?
>
>Whatever the error, it seems to eliminate all alsa devices.
>

I took a look at "/etc/rc.d/rc.alsa" to remind me what "alsactl restore"
exactly does in there.

Maybe look in /var/lib/alsa/asound.state (assuming it hasn't moved!),
it sounds like the contents of that file may be corrupt or incompatible?

It also hints that if you "touch /var/lib/alsa/no.asound.state" then
it won't load that file, and instead set some defaults up.
--
--------------------------------------+------------------------------------
Mike Brown: mjb[-at-]signal11.org.uk | http://www.signal11.org.uk

Re: problem with /etc/rc.d/rc.alsa

<sthekb$qo0$1@dont-email.me>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=949&group=alt.os.linux.slackware#949

copy link Newsgroups: alt.os.linux.slackware

Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: Re: problem with /etc/rc.d/rc.alsa
Date: Thu, 3 Feb 2022 20:40:44 -0000 (UTC)
Organization: Linux Advocacy
Lines: 22
Message-ID: <sthekb$qo0$1@dont-email.me>
References: <stecbm$moa$1@dont-email.me> <steqc3$a3l$1@posie.signal11.org.uk>
Injection-Date: Thu, 3 Feb 2022 20:40:44 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="8137c300f913c029c7065bbe23d88f29";
logging-data="27392"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Exe+mzewzy3aKw6/fZ64mzjYGhxnbvR8="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:HaHXUE5BMMYHI/MoQ60lTLpmz9A=

by: root - Thu, 3 Feb 2022 20:40 UTC

Mike <mjb@signal11.invalid> wrote:
>
> I took a look at "/etc/rc.d/rc.alsa" to remind me what "alsactl restore"
> exactly does in there.
>
> Maybe look in /var/lib/alsa/asound.state (assuming it hasn't moved!),
> it sounds like the contents of that file may be corrupt or incompatible?
>
> It also hints that if you "touch /var/lib/alsa/no.asound.state" then
> it won't load that file, and instead set some defaults up.

Thanks for responding. The date on the file /var/lib/alsa/asound.state
corresponds to the last time I booted into the machine. At that
time I had no file /etc/asound.conf and the asound.state file reflects
the correct state of my machine beginning with state NVIDIA.

I take that as what happens when no.asound.state was touched.
I know that nothing I could put in /etc/asound.conf worked for me.

In the old days we used to have to create an xorg.conf. Now it
is best left missing and X starts up correctly be default. It
seems now that sound may do the same. All the better for us.

Subject	Author
problem with /etc/rc.d/rc.alsa	root
Re: problem with /etc/rc.d/rc.alsa	Mike
Re: problem with /etc/rc.d/rc.alsa	root