|
Bugzilla – Full Text Bug Listing |
| Summary: | Volume in yast2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Forgotten User d8u6e9Lt6y <forgotten_d8u6e9Lt6y> |
| Component: | YaST2 | Assignee: | Takashi Iwai <tiwai> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_w4XUsT47_R, lslezak, wiki.melancholie |
| Version: | Alpha 0 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
wief of yast2+kmix
alsa-info asound.state |
||
|
Description
Forgotten User d8u6e9Lt6y
2009-05-11 05:42:14 UTC
Takashi, any idea what might be wrong? The volume should be saved/restored by RC alsa scripts shouldn't it? Yes. But kmix & co might restore its own value at login and can override the current value. Is it the case? sorry for the delay..... kmix for me is ok.... only yast2 have a prblem!!! si a pic! Created attachment 292075 [details]
wief of yast2+kmix
You cannot use yast2-sound setup and kmix at the same time. This screws up. Anyway, after setting up the volume, try to run "alsactl store" as root. Logout once, then go to linux console via ctl+alt+F1. Login as root there, run "alsactl restore". Then try to reboot and check the problem again. [Also, please don't forget to reset NEEDINFO flag after providing the requested information. Thanks.] You cannot use yast2-sound setup and kmix at the same time. This screws up. I did so just to show you the situation in the picture Logout once, then go to linux console via ctl+alt+F1. Login as root there, run "alsactl restore". Then try to reboot and check the problem again. I did as you said, but the problem remains. 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. I did as I have said, but the problem remains. But now (maybe) I have more information if i set volume = 88% (for example) when i reboot the system return to find the following things: root--> 63% (volume) user -->0% but that's not all I saw that if I enter init3 and give the command "aplay -Dplughw......" in user I hear the sound.... but i go i kde4 (startx) i find the volume (in yast) 0% Created attachment 292548 [details]
alsa-info
Created attachment 292549 [details]
asound.state
Me having the same problem the other way round (100%), after installing the PuleAudio 0.9.15-1.3 patch some days ago. After any reboot my volume is suddenly always at 100%. I am only using KMix, not yast2 for adjusting the volume (but doesn't matter, the effect/problem is the same). That wouldn't be that bad, but my audio card is clipping enormously with 100% set (way too loud, very very much too loud, even with 30% it seems to still clip a little bit; btw can only use XMMS (ALSA)), so it's damaging hardware in my case! I think it's an PulseAudio and/or KMix issue. My specs: See http://www.smolts.org/client/show/pub_5fe28ef2-ec4f-4cb6-b03d-7c924a8cde1e L Kernel: 2.6.27.23-0.1-default (i686) L VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (snd_via82xx) L PuleAudio 0.9.15-1.3 L KDE 4.2.3 Oh, just saw that this is for product openSUSE 11.2, but I am using openSUSE 11.1 (with many factory packages tough ;-) Fully updated my system and upgraded to KDE 4.2.90 (4.3b2) and my sound system was broken for all audio players (yast2 test sound was ok); then re-installed phonon, alsa, xine etc. But what have been successful to get my sound system working again was installing alsa-driver-unstable-kmp-pae, I think. It seems that with those (partially factory) upgrades the 'reset' phenomenon that occured with PuleAudio 0.9.15-1.3 has disappeared on my system. unfortunately for now I have no other information. I can not install opensuse11.2 milseton2 on acer 5920 (kernel panic error) I have the same issue on a Dell D410 notebook. Every time I restart the volume is back to 0%. When I use the applet on increase the volume I can hear the music, so the audio system works. I am using openSuSE 11.2 milestone 5 with Gnome. Below is the output from LSPCI 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) The 0% volume after boot is already fixed (as in bug 499445). yess! in opensuse11.2 the volume is ok! good! |