why is alsa muted at start up, i think we should change that.
Alex Thomsen Leth wrote:
why is alsa muted at start up, i think we should change that.
Where do you discover that Alsa is muted? I can't play gnome system sounds, but other sound works without me doing anything after boot. I would like to find why the system sounds don't work, so please tell me what you check to see that Alsa is muted.
Thanks.
Gerry Tool
run the command alsamixer
i am also intrested in figuring out how to unmute it....i was unable to find anything in the man pages :-\ On Thursday 29 April 2004 16:13, Gerry Tool wrote:
Alex Thomsen Leth wrote:
why is alsa muted at start up, i think we should change that.
Where do you discover that Alsa is muted? I can't play gnome system sounds, but other sound works without me doing anything after boot. I would like to find why the system sounds don't work, so please tell me what you check to see that Alsa is muted.
Thanks.
Gerry Tool
Mike Jensen wrote:
run the command alsamixer
i am also intrested in figuring out how to unmute it....i was unable to find anything in the man pages :-\ On Thursday 29 April 2004 16:13, Gerry Tool wrote:
Alex Thomsen Leth wrote:
why is alsa muted at start up, i think we should change that.
Where do you discover that Alsa is muted? I can't play gnome system sounds, but other sound works without me doing anything after boot. I would like to find why the system sounds don't work, so please tell me what you check to see that Alsa is muted.
I did that, and sound is not muted, and the terminal view of the mixer follows my changes in the menu > Sound and Video > Volume Control gui application. I guess I don't have the muting problem noted at the beginning of this thread.
Gerry tool
I have main volume OK, but PCM slider is set to 0 at every reboot.
Sasha
On Thu, 2004-04-29 at 21:38, Gerry Tool wrote:
Mike Jensen wrote:
run the command alsamixer
i am also intrested in figuring out how to unmute it....i was unable to find anything in the man pages :-\ On Thursday 29 April 2004 16:13, Gerry Tool wrote:
Alex Thomsen Leth wrote:
why is alsa muted at start up, i think we should change that.
Where do you discover that Alsa is muted? I can't play gnome system sounds, but other sound works without me doing anything after boot. I would like to find why the system sounds don't work, so please tell me what you check to see that Alsa is muted.
I did that, and sound is not muted, and the terminal view of the mixer follows my changes in the menu > Sound and Video > Volume Control gui application. I guess I don't have the muting problem noted at the beginning of this thread.
Gerry tool
On Fri, 30 Apr 2004 08:56:55 -0400, Alexander Kirillov wrote:
I have main volume OK, but PCM slider is set to 0 at every reboot.
Please try the following as "root" user:
1. run "alsamixer" and set the sliders correctly, unmute the channels 2. run "alsactl store" 3. run "alsactl restore" 4. run "alsamixer" again
What do you see?
On Fri, 2004-04-30 at 10:30, Michael Schwendt wrote:
On Fri, 30 Apr 2004 08:56:55 -0400, Alexander Kirillov wrote:
I have main volume OK, but PCM slider is set to 0 at every reboot.
Please try the following as "root" user:
- run "alsamixer" and set the sliders correctly, unmute the channels
- run "alsactl store"
- run "alsactl restore"
- run "alsamixer" again
I resolved the "alsa problem" by creating a short script:
alsactl restore gnome-alsamixer alsactl store
And linked it to a launcher on my panel (using the same icon as for the volume control). This makes sure that my levels and settings are always what I expect them to be (and if something screws them up, a single click to bring up the volume control gets them back to my preferred setting).
Ben
On Fri, 30 Apr 2004 10:36:58 -0300, Ben Steeves wrote:
I resolved the "alsa problem" by creating a short script:
What you refer to as "alsa problem" is a potential bug in Fedora Core 1.9x. Rather than creating scripts to work around it, it should be investigated and fixed, so it won't be in Fedora Core 2.
alsactl restore gnome-alsamixer alsactl store
And linked it to a launcher on my panel (using the same icon as for the volume control). This makes sure that my levels and settings are always what I expect them to be (and if something screws them up, a single click to bring up the volume control gets them back to my preferred setting).
The "halt" initscript should store mixer settings with alsactl when you shut down or reboot your system. And /etc/modprobe.conf restores the mixer settings when the ALSA kernel modules are loaded. It should just work.
Do you have the alsactl calls in those files?
On Fri, 2004-04-30 at 10:58, Michael Schwendt wrote:
The "halt" initscript should store mixer settings with alsactl when you shut down or reboot your system. And /etc/modprobe.conf restores the mixer settings when the ALSA kernel modules are loaded. It should just work.
Do you have the alsactl calls in those files?
Yes, but the halt initscript only runs when the system is restarted cleanly. This is my test system and that doesn't always happen :-)
I don't consider my approach to be working around bugs in FC, it's just making the system work the way I want. I don't presume to think that everyone wants things to work the way I do.
Ben
On Fri, 2004-04-30 at 09:30, Michael Schwendt wrote:
On Fri, 30 Apr 2004 08:56:55 -0400, Alexander Kirillov wrote:
I have main volume OK, but PCM slider is set to 0 at every reboot.
Please try the following as "root" user:
- run "alsamixer" and set the sliders correctly, unmute the channels
- run "alsactl store"
- run "alsactl restore"
- run "alsamixer" again
What do you see?
Works fine - that is, PCM slider shows the value I had set. However, after reboot the slider is returned to 0.
And yes, I do have these lines in modprobe.conf
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
Any ideas?
BTW: another oddity is that volume control tool in GNOME shows two mizers. One is identified as Intel 82801DB-ICH4 [Alsa Mixer], another as SigmaTel STAC9750/51, Conexant i[Audio Mixer (OSS)]. I definitely only have 1 audio card, identified by alsamixer as
Card: Intel 82801DB-ICH4 Chip: SigmaTel STAC9750/51,Conexant id 22
So why show 2 different mixers? And their controls are independent: changing PCM slider in one of them does not change the PCM slider in the other. :(
On Fri, 30 Apr 2004 12:22:43 -0400, Alexander Kirillov wrote:
I have main volume OK, but PCM slider is set to 0 at every reboot.
Please try the following as "root" user:
- run "alsamixer" and set the sliders correctly, unmute the channels
- run "alsactl store"
- run "alsactl restore"
- run "alsamixer" again
What do you see?
Works fine - that is, PCM slider shows the value I had set. However, after reboot the slider is returned to 0.
If you run "alsactl restore" directly after reboot, does that restore the PCM slider with value 0 or with a good value?
The values are saved in /etc/asound.state, so if you check the timestamp of that file you can find out when it was written to last time (whether on reboot or earlier).
[I should be querying bugzilla for any ALSA issues with the intel 8x0 chipsets, but I don't have that chipset myself]
And yes, I do have these lines in modprobe.conf
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
Any ideas?
BTW: another oddity is that volume control tool in GNOME shows two mizers. One is identified as Intel 82801DB-ICH4 [Alsa Mixer], another as SigmaTel STAC9750/51, Conexant i[Audio Mixer (OSS)]. I definitely only have 1 audio card, identified by alsamixer as
Card: Intel 82801DB-ICH4 Chip: SigmaTel STAC9750/51,Conexant id 22
So why show 2 different mixers? And their controls are independent: changing PCM slider in one of them does not change the PCM slider in the other. :(
It's a single mixer, but accessible via two differ audio mixer drivers. There is "native ALSA" (devices /dev/snd/* for PCM, mixers, ...) and "ALSA OSS emulation" (devices /dev/dsp, /dev/mixer, ...). The latter provide a compatibility interface for the old OSS/Free audio drivers from the 2.4 kernel series, so many applications don't need to be rewritten for ALSA. I've heard rumours that with some chipsets, the drivers don't route values through between ALSA and ALSA OSS. So when you configure your soundcard mixer with ALSA, the OSS settings can be different. Depending on how much you like to examine this, you could disable the ALSA OSS drivers (they are loaded via /etc/modprobe.dist) and see whether that makes a difference.
On Fri, 2004-04-30 at 13:40, Michael Schwendt wrote:
On Fri, 30 Apr 2004 12:22:43 -0400, Alexander Kirillov wrote:
I have main volume OK, but PCM slider is set to 0 at every reboot.
Please try the following as "root" user:
- run "alsamixer" and set the sliders correctly, unmute the channels
- run "alsactl store"
- run "alsactl restore"
- run "alsamixer" again
What do you see?
Works fine - that is, PCM slider shows the value I had set. However, after reboot the slider is returned to 0.
If you run "alsactl restore" directly after reboot, does that restore the PCM slider with value 0 or with a good value?
The values are saved in /etc/asound.state, so if you check the timestamp of that file you can find out when it was written to last time (whether on reboot or earlier).
[I should be querying bugzilla for any ALSA issues with the intel 8x0 chipsets, but I don't have that chipset myself]
/etc/asound.state is saved at shutdown, and running alsactl restore immediately after login does restore the correct values for PCM and other controls. So the problem seems to be that modprobe didn't run alsactl restore at startup.
And yes, I do have these lines in modprobe.conf
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
Any ideas?
BTW: another oddity is that volume control tool in GNOME shows two mizers. One is identified as Intel 82801DB-ICH4 [Alsa Mixer], another as SigmaTel STAC9750/51, Conexant i[Audio Mixer (OSS)]. I definitely only have 1 audio card, identified by alsamixer as
Card: Intel 82801DB-ICH4 Chip: SigmaTel STAC9750/51,Conexant id 22
So why show 2 different mixers? And their controls are independent: changing PCM slider in one of them does not change the PCM slider in the other. :(
It's a single mixer, but accessible via two differ audio mixer drivers. There is "native ALSA" (devices /dev/snd/* for PCM, mixers, ...) and "ALSA OSS emulation" (devices /dev/dsp, /dev/mixer, ...). The latter provide a compatibility interface for the old OSS/Free audio drivers from the 2.4 kernel series, so many applications don't need to be rewritten for ALSA. I've heard rumours that with some chipsets, the drivers don't route values through between ALSA and ALSA OSS. So when you configure your soundcard mixer with ALSA, the OSS settings can be different. Depending on how much you like to examine this, you could disable the ALSA OSS drivers (they are loaded via /etc/modprobe.dist) and see whether that makes a difference.
Can understand the logic but the result is still ugly. Reasonable thing would be to show only one mixer to the user, even if we have two drivers for compatibility reasons - if it can be done...
On Fri, 2004-04-30 at 13:59, Alexander Kirillov wrote:
/etc/asound.state is saved at shutdown, and running alsactl restore immediately after login does restore the correct values for PCM and other controls. So the problem seems to be that modprobe didn't run alsactl restore at startup.
Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured 49596 usecs Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000 Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command for sound_slot_1 Apr 30 16:18:28 Aristotle last message repeated 2 times Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
Still can't understand why modprobe fails, though
OK, seems that these lines in sys log explain why:
On Fri, 30 Apr 2004 16:31:12 -0400, Alexander Kirillov wrote:
On Fri, 2004-04-30 at 13:59, Alexander Kirillov wrote:
/etc/asound.state is saved at shutdown, and running alsactl restore immediately after login does restore the correct values for PCM and other controls. So the problem seems to be that modprobe didn't run alsactl restore at startup.
Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
That is a modem detection message.
Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured 49596 usecs Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000
That configures your audio chipset to 48 kHz.
Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
sound-slot-1 would be the second soundcard and OSS, sound-slot-0 the first. (/etc/modprobe.conf.dist handles the OSS stuff)
Apr 30 16:18:28 Aristotle last message repeated 2 times Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
Still can't understand why modprobe fails, though
OK, seems that these lines in sys log explain why:
I have a laptop with a Sis chipset Si7012 and a desktop with an Ensoniq. The PCM slider is set to zero after each boot. After saving the settings I just put a "alsactl restore" entry in rc.local to restore my settings. Has (does) this need to be bugzilla'd?
Timothy
On Fri, 2004-04-30 at 17:44, Michael Schwendt wrote:
On Fri, 30 Apr 2004 16:31:12 -0400, Alexander Kirillov wrote:
On Fri, 2004-04-30 at 13:59, Alexander Kirillov wrote:
/etc/asound.state is saved at shutdown, and running alsactl restore immediately after login does restore the correct values for PCM and other controls. So the problem seems to be that modprobe didn't run alsactl restore at startup.
Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
That is a modem detection message.
Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured 49596 usecs Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000
That configures your audio chipset to 48 kHz.
Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
sound-slot-1 would be the second soundcard and OSS, sound-slot-0 the first. (/etc/modprobe.conf.dist handles the OSS stuff)
Apr 30 16:18:28 Aristotle last message repeated 2 times Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
Still can't understand why modprobe fails, though
OK, seems that these lines in sys log explain why:
See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119866 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115932
Sasha
On Wed, 2004-05-05 at 13:09, Timothy wrote:
I have a laptop with a Sis chipset Si7012 and a desktop with an Ensoniq. The PCM slider is set to zero after each boot. After saving the settings I just put a "alsactl restore" entry in rc.local to restore my settings. Has (does) this need to be bugzilla'd?
Timothy
On Fri, 2004-04-30 at 17:44, Michael Schwendt wrote:
On Fri, 30 Apr 2004 16:31:12 -0400, Alexander Kirillov wrote:
On Fri, 2004-04-30 at 13:59, Alexander Kirillov wrote:
/etc/asound.state is saved at shutdown, and running alsactl restore immediately after login does restore the correct values for PCM and other controls. So the problem seems to be that modprobe didn't run alsactl restore at startup.
Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
That is a modem detection message.
Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured 49596 usecs Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000
That configures your audio chipset to 48 kHz.
Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
sound-slot-1 would be the second soundcard and OSS, sound-slot-0 the first. (/etc/modprobe.conf.dist handles the OSS stuff)
Apr 30 16:18:28 Aristotle last message repeated 2 times Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
Still can't understand why modprobe fails, though
OK, seems that these lines in sys log explain why:
Thanks,
Seems it is fixed in modutils-2.4.26-16, but that just hasn't made the developement tree yet.
Timothy
On Wed, 2004-05-05 at 14:00, Alexander Kirillov wrote:
See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119866 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115932
Sasha
On Wed, 2004-05-05 at 13:09, Timothy wrote:
I have a laptop with a Sis chipset Si7012 and a desktop with an Ensoniq. The PCM slider is set to zero after each boot. After saving the settings I just put a "alsactl restore" entry in rc.local to restore my settings. Has (does) this need to be bugzilla'd?
Timothy
On Fri, 2004-04-30 at 17:44, Michael Schwendt wrote:
On Fri, 30 Apr 2004 16:31:12 -0400, Alexander Kirillov wrote:
On Fri, 2004-04-30 at 13:59, Alexander Kirillov wrote:
/etc/asound.state is saved at shutdown, and running alsactl restore immediately after login does restore the correct values for PCM and other controls. So the problem seems to be that modprobe didn't run alsactl restore at startup.
Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
That is a modem detection message.
Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured 49596 usecs Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000
That configures your audio chipset to 48 kHz.
Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
sound-slot-1 would be the second soundcard and OSS, sound-slot-0 the first. (/etc/modprobe.conf.dist handles the OSS stuff)
Apr 30 16:18:28 Aristotle last message repeated 2 times Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
Still can't understand why modprobe fails, though
OK, seems that these lines in sys log explain why:
Alexander Kirillov wrote:
Apr 30 16:15:47 Aristotle kernel: MC'97 1 converters and GPIO not ready (0xff00)
Apr 30 16:15:47 Aristotle kernel: intel8x0_measure_ac97_clock: measured 49596 usecs Apr 30 16:15:47 Aristotle kernel: intel8x0: clocking to 48000 Apr 30 16:15:47 Aristotle modprobe: FATAL: Error running install command for sound_slot_1 Apr 30 16:18:28 Aristotle last message repeated 2 times Apr 30 16:22:01 Aristotle modprobe: FATAL: Error running install command for sound_slot_1
Still can't understand why modprobe fails, though
OK, seems that these lines in sys log explain why:
I get the same message in sys log, however my sound does get restored upon startup. My modprobe.conf file look like:
alias eth0 sis900 alias snd-card-0 snd-intel8x0 install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0 alias usb-controller ohci-hcd
Perhaps something need fixing in modprobe.conf.dist. Has anyone added this to bugzilla?
okay not muted but PCM is not turned up
fre, 2004-04-30 kl. 02:43 skrev Mike Jensen:
run the command alsamixer
i am also intrested in figuring out how to unmute it....i was unable to find anything in the man pages :-\ On Thursday 29 April 2004 16:13, Gerry Tool wrote:
Alex Thomsen Leth wrote:
why is alsa muted at start up, i think we should change that.
Where do you discover that Alsa is muted? I can't play gnome system sounds, but other sound works without me doing anything after boot. I would like to find why the system sounds don't work, so please tell me what you check to see that Alsa is muted.
Thanks.
Gerry Tool
-- Cheers, Mike Jensen jent@spicylemons.com cell@spicylemons.com irc.acidchat.net www.spicylemons.com
-
Alex Thomsen Leth -
Alexander Kirillov -
Ben Steeves -
Demond James -
Gerry Tool -
Michael Schwendt -
Mike Jensen -
Timothy Sandel