Bug 105272

Summary: alsa not really started
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Jan Engelhardt <jengelh>
Component: SoundAssignee: Takashi Iwai <tiwai>
Status: VERIFIED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 1   
Target Milestone: ---   
Hardware: x86   
OS: Linux   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jan Engelhardt 2005-08-17 17:05:13 UTC
I found that my mixer controls are all muted. If I look into
/etc/init.d/alsasound I seem to not need to guess to say why:

case "$1" in
  start)
        if [ -d /proc/asound ]; then
            start_rest
        fi
        ;;

start_rest() {
  load_sequencer
  if [ x"$LOAD_OSS_EMUL_MODULES" = xyes ]; then
    /sbin/modprobe snd-pcm-oss
    # test x"$LOAD_SEQUENCER" = xyes && /sbin/modprobe snd-seq-oss 
  fi
}

So that's everything executed. Only the stop) procedure has a call to $alsactl
for storing the values.
Comment 1 Takashi Iwai 2005-08-17 17:10:41 UTC
The new system loads all modules via hwcfg-* stuff.  alsactl is called via udev.
It's a bug of yast2-sound that didn't unmute the default mixer set-up.
Comment 2 Jan Engelhardt 2005-08-17 19:03:25 UTC
>It's a bug of yast2-sound that didn't unmute the default mixer set-up.

The last time I called the sound module of yast2 was when I did the initial
install, which was well at 8.2. I just ran rpm -Uhv newalsapackes* and now I
find that the volumes don't get set up upon boot.

I got some /etc/sysconfig/hardware/hwcfg-* files:
hwcfg-bus-pci-0000:00:04.0 (ethernet)
hwcfg-bus-pci-0000:00:0b.0 (ethernet)
hwcfg-vpid-4153-1862-4121-6152
hwcfg-vpid-4153-2
hwcfg-vpid-4153-22
hwcfg-vpid-4153-2403
hwcfg-vpid-57689-1-41127-1
hwcfg-vpid-57689-1-57511-1

All non-ethernet files are almost empty, containing only:
STARTMODE='auto'
MODULE=''

The sound modules are loaded, just no vol.
Comment 3 Takashi Iwai 2005-08-18 09:48:47 UTC
Regardless you reinstall the alsa package, the mixer setting is kept from the
first configuration (yast2 set up).  Since yast2 saved the mixer state with all
mutes, you'll get still such a state unless reconfiguring the sound card or
adjust volume manually once and stores the setting.
Comment 4 Jan Engelhardt 2005-08-18 09:50:47 UTC
So how do I get the 9.3 behavior back where the volume is stored upon shutdown
and reloaded upon boot?
Comment 5 Takashi Iwai 2005-08-18 09:57:52 UTC
The volume is restored via udev.  It calls "alsactl restore" when the driver is
activated.  You likely have a wrong mixer setting in /etc/asound.state.

Anyway, you should reconfigure the sound when you updated from the version older
than 9.3 to put hwcfg stuff for the sound device.  And try beta2 :)
Comment 6 Jan Engelhardt 2005-08-18 10:00:36 UTC
What file in /etc/udev? I have not yet completely upgraded to beta because of
some unsatisfied dependencies...
Comment 7 Takashi Iwai 2005-08-18 10:03:53 UTC
/etc/udev/rules.d/50-udev.rules
Comment 8 Jan Engelhardt 2005-08-18 10:04:49 UTC
Some specific line?
Comment 9 Takashi Iwai 2005-08-18 10:07:06 UTC
Look for ALSA and read 50 lines.
Comment 10 Jan Engelhardt 2005-08-18 10:09:13 UTC
12:08 pri:/etc/udev/rules.d # grep -i alsa 50-udev.rules | wc -l
1
12:08 pri:/etc/udev/rules.d # grep -i alsa 50-udev.rules
# alsa devices

Hm oh ok, file belongs to "udev" which I didnot update yet.