http://bugzilla.novell.com/show_bug.cgi?id=502604
User tiwai@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=502604#c7
--- Comment #7 from Takashi Iwai 2009-05-14 10:53:27 MDT ---
OK, forget about YaST once. The question is whether the volume set up is saved
/ restored properly.
Try the following again:
1. logout once, go to linux console via ctl+alt+F1
2. login as root
3. check the audio via "aplay -Dplughw /usr/share/sounds/alsa/test.wav"
4. if it doesn't work, try to run "set_default_volume -f", then test aplay
again.
5. run "reboot"
6. give "3" to boot option in GRUB boot menu to run in runlevel 3
7. after boot, login as root, test the sound via aplay again
8. if everything is fine, make a backup of /etc/asound.state.
9. run "init 5", then GUI starts up; login to your account there
10. check the mixer status again; if it's fine, run "/usr/sbin/alsa-info.sh
--no-upload" as root, and back the generated file
At this stage, we have some information, /etc/asound.state backup and
alsa-info.sh output. Then, start YaST again. If the volume still shows 0,
it's a YaST problem.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.