8 Mar
2005
8 Mar
'05
12:45 a.m.
I am having some very basic problems with my alsa setup on my new Gentoo
installation:
1. I can't make my changes to the mixer settings stick and so I have to
change them manually every time I boot up. This is despite having the line
'SAVE_ON_STOP="yes"' as the only uncommented line in
/etc/conf.d/alsasound.
2. I can't seem to make my Audigy2 soundcard 0 and my on-board audio
soundcard 1, despite having
options snd cards_limit=2
options snd_emu10k1 index=0
options snd_intel8x0 index=1
in my /etc/modules.d/alsa (which is automatically used to
generate /etc/modules.conf).
#2 is just a minor annoyance, but #1 really needs sorting out and any help
would be appreciated.
Many thanks
Robert
--
Robert Persson
"No matter how much ye shake yer peg
The last wee drap rins doon yer leg."
8 Mar
8 Mar
3:12 a.m.
Quoting Robert Persson <ireneshusband(a)yahoo.co.uk>uk>:
1. I can't make my changes to the mixer settings
stick and so I have to
change them manually every time I boot up. This is despite having the line
'SAVE_ON_STOP="yes"' as the only uncommented line in
/etc/conf.d/alsasound.
From what I understand, you have two soundcards, right?
I had the same problem
once, because 'alsactl store' and 'alsactl
restore' only worked on one card,
although it said, that if it's called without a card specified, it should
save/restore the settings of both cards...
You could probably solve it by editing your Alsa-Startup-Script (probably
/etc/init.d/alsasound) and replace the 'alsactl store' with 'alsactl -c 0
store; alsactl -c 1 store' and the same with the restore part.
Well... before doing that, I'd take a look at the help-output of alsactl, I'm
not sure if the above syntax is right, and I can't check it right now, because
I'm writing this mail on a...nother OS...
-Michael
4:17 a.m.
On March 7, 2005 11:11 pm, quoth Michael Wagner:
Quoting Robert Persson
<ireneshusband(a)yahoo.co.uk>uk>:
Thanks very much, Michael. I think you put me on the right track, although it
looks like "alsactl store" ought to work for 2 cards without passing extra
parameters. I ran it from a command line and it produced
an /etc/asound.state as it's supposed to.
I have now discovered that alsasound was not in my default runlevel. I
presume that this was the problem, although I won't believe it until I have
rebooted and found that everything does what it should.
Robert
--
Robert Persson
"No matter how much ye shake yer peg
The last wee drap rins doon yer leg."
1. I can't make my changes to the mixer
settings stick and so I have to
change them manually every time I boot up. This is despite having the
line 'SAVE_ON_STOP="yes"' as the only uncommented line in
/etc/conf.d/alsasound.
From what I understand, you have two soundcards, right? I had the same
problem
once, because 'alsactl store' and 'alsactl restore' only worked on one
card, although it said, that if it's called without a card specified, it
should save/restore the settings of both cards...
You could probably solve it by editing your Alsa-Startup-Script (probably
/etc/init.d/alsasound) and replace the 'alsactl store' with 'alsactl -c 0
store; alsactl -c 1 store' and the same with the restore part.
Well... before doing that, I'd take a look at the help-output of alsactl,
I'm not sure if the above syntax is right, and I can't check it right now,
because I'm writing this mail on a...nother OS...
-Michael
6:07 p.m.
On March 8, 2005 12:17 am, quoth Robert Persson:
I have now discovered that alsasound was not in my
default runlevel. I
presume that this was the problem, although I won't believe it until I have
rebooted and found that everything does what it should.
Robert
Confirmed. Mixer state is now being saved and recalled properly.
--
Robert Persson
"No matter how much ye shake yer peg
The last wee drap rins doon yer leg."
7202
days inactive
7203
days old
linux-audio-user@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
Michael Wagner -
Robert Persson