[Bug 526127] New: [Goblin Bug] Sound volume is incorrectly set at 1st boot
http://bugzilla.novell.com/show_bug.cgi?id=526127 Summary: [Goblin Bug] Sound volume is incorrectly set at 1st boot Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: awafaa@opensuse.org QAContact: qa@suse.de Found By: --- Created an attachment (id=308640) --> (http://bugzilla.novell.com/attachment.cgi?id=308640) Soundcard error from yast sound module. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.12) Gecko/2009071200 SUSE/3.0.12-0.1.2 Firefox/3.0.12 It looks like the autoconfig aspect of 1st boot incorrectly sets the output volume to 60% and not 100%. As far as the volume applet is concerned the volume is at 100% which is incorrect. I have verified this by doing a net install and de-selecting auto-config, and when it comes to the soundcard I go to edit it and the output is set to 60, i manually change it to 100 and continue. When trying to reconfigure the soundcard on my Asus eeePC 1000HE I get an error about the module for my soundcard is missing. I confirmed with Greg K-H that the module is actually part of the kernel. When I enter the sound module in yast it says the soundcard isnt configured and when i try to configure it it gives the rrror message attached. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
Andrew Wafaa
http://bugzilla.novell.com/show_bug.cgi?id=526127
User tiwai@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c1
Takashi Iwai
It looks like the autoconfig aspect of 1st boot incorrectly sets the output volume to 60% and not 100%.
Yes, this is the correct behavior.
As far as the volume applet is concerned the volume is at 100% which is incorrect.
What do you mean here?
When trying to reconfigure the soundcard on my Asus eeePC 1000HE I get an error about the module for my soundcard is missing. I confirmed with Greg K-H that the module is actually part of the kernel. When I enter the sound module in yast it says the soundcard isnt configured and when i try to configure it it gives the rrror message attached.
Yes, this is a known problem by built-in driver. The sound configuration doesn't work with Moblin kernel (at least for HD-audio). -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
User awafaa@opensuse.org added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c2
Andrew Wafaa
(In reply to comment #0)
It looks like the autoconfig aspect of 1st boot incorrectly sets the output volume to 60% and not 100%.
Yes, this is the correct behavior.
Really? Why is that so? It is far too low a setting surely the hardware should be at maximum and then the user decides what they like?
As far as the volume applet is concerned the volume is at 100% which is incorrect.
What do you mean here?
The method that a regular user would change the volume of their machine whether it is by the hardware volume controls or the volume applet in the top right (or bottom right if using stock GNOME/KDE). This should be how users control their volume and if they whish to have the volume at 60% then they set it at 60% not openSUSE
When trying to reconfigure the soundcard on my Asus eeePC 1000HE I get an error about the module for my soundcard is missing. I confirmed with Greg K-H that the module is actually part of the kernel. When I enter the sound module in yast it says the soundcard isnt configured and when i try to configure it it gives the rrror message attached.
Yes, this is a known problem by built-in driver. The sound configuration doesn't work with Moblin kernel (at least for HD-audio).
Is there any other way of changing the setting? The system default is too low. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
User tiwai@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c3
Takashi Iwai
(In reply to comment #1)
(In reply to comment #0)
It looks like the autoconfig aspect of 1st boot incorrectly sets the output volume to 60% and not 100%.
Yes, this is the correct behavior.
Really? Why is that so? It is far too low a setting surely the hardware should be at maximum and then the user decides what they like?
No, it should *NOT* be maximum at the very first time. It can easily blow your speaker box if connected. The question of the loudness is rather a matter of taste. It could be higher, but 100% is definitely a wrong value from the safety POV. (Note that here I'm arguing about the very initial volume, not the second boot after user has set up.)
As far as the volume applet is concerned the volume is at 100% which is incorrect.
What do you mean here?
The method that a regular user would change the volume of their machine whether it is by the hardware volume controls or the volume applet in the top right (or bottom right if using stock GNOME/KDE). This should be how users control their volume and if they whish to have the volume at 60% then they set it at 60% not openSUSE
Still not clear what do you mean. What did you do exactly, what was the expected result, and what was the actual result?
When trying to reconfigure the soundcard on my Asus eeePC 1000HE I get an error about the module for my soundcard is missing. I confirmed with Greg K-H that the module is actually part of the kernel. When I enter the sound module in yast it says the soundcard isnt configured and when i try to configure it it gives the rrror message attached.
Yes, this is a known problem by built-in driver. The sound configuration doesn't work with Moblin kernel (at least for HD-audio).
Is there any other way of changing the setting? The system default is too low.
If the volume isn't recovered at the next reboot, it's another bug. The volume has to be restored from the previous setting. Is this the 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
User awafaa@opensuse.org added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c4
Andrew Wafaa
(In reply to comment #2)
(In reply to comment #1)
(In reply to comment #0)
It looks like the autoconfig aspect of 1st boot incorrectly sets the output volume to 60% and not 100%.
Yes, this is the correct behavior.
Really? Why is that so? It is far too low a setting surely the hardware should be at maximum and then the user decides what they like?
No, it should *NOT* be maximum at the very first time. It can easily blow your speaker box if connected.
The question of the loudness is rather a matter of taste. It could be higher, but 100% is definitely a wrong value from the safety POV.
(Note that here I'm arguing about the very initial volume, not the second boot after user has set up.)
OK that makes sense, I'm arguing about the second boot after I'm logged in. The volume is far too low and no matter what I do I can't increase it as the tools available insist that the volume is at max. This is either the on screen display when I use the hardware buttons or the volume control applet in the top right (the speaker icon).
As far as the volume applet is concerned the volume is at 100% which is incorrect.
What do you mean here?
The method that a regular user would change the volume of their machine whether it is by the hardware volume controls or the volume applet in the top right (or bottom right if using stock GNOME/KDE). This should be how users control their volume and if they whish to have the volume at 60% then they set it at 60% not openSUSE
Still not clear what do you mean. What did you do exactly, what was the expected result, and what was the actual result?
The expected result was to increase the volume to 100%, and the actual result is the volume did not change and 100% volume is displayed.
When trying to reconfigure the soundcard on my Asus eeePC 1000HE I get an error about the module for my soundcard is missing. I confirmed with Greg K-H that the module is actually part of the kernel. When I enter the sound module in yast it says the soundcard isnt configured and when i try to configure it it gives the rrror message attached.
Yes, this is a known problem by built-in driver. The sound configuration doesn't work with Moblin kernel (at least for HD-audio).
Is there any other way of changing the setting? The system default is too low.
If the volume isn't recovered at the next reboot, it's another bug. The volume has to be restored from the previous setting. Is this the problem?
Yes the problem is that the volume is too low, and there is no way to increase it. It's almost like hardcoding the volume to 60% so after you log in the system thinks it's at 100% but is actually only at 60% so you can only go down. If I go by the user volume controls and change to 50% I'm actually dropping it to 30%. Does this make sense? -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
User tiwai@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c5
Takashi Iwai
The volume is far too low and no matter what I do I can't increase it as the tools available insist that the volume is at max. This is either the on screen display when I use the hardware buttons or the volume control applet in the top right (the speaker icon).
Run "alsamixer -c0" on a terminal. Do you see other volumes?
As far as the volume applet is concerned the volume is at 100% which is incorrect.
What do you mean here?
The method that a regular user would change the volume of their machine whether it is by the hardware volume controls or the volume applet in the top right (or bottom right if using stock GNOME/KDE). This should be how users control their volume and if they whish to have the volume at 60% then they set it at 60% not openSUSE
Still not clear what do you mean. What did you do exactly, what was the expected result, and what was the actual result?
The expected result was to increase the volume to 100%, and the actual result is the volume did not change and 100% volume is displayed.
Which app did you use? Does alsamixer -c0 show also 100% on all outupt volumes? The pulseaudio volume applet picks up only the master volume, and alsamixer (without -c0) is also routed to pulseaudio. That's why you see only 100% there, I guess. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
User awafaa@opensuse.org added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c6
Andrew Wafaa
Run "alsamixer -c0" on a terminal. Do you see other volumes?
OK running that, alsa shows PCM at 100, Line Out at 59, Mic Boost at 0, Capture at 59.
Which app did you use? Does alsamixer -c0 show also 100% on all outupt volumes?
I just used whatever comes on the system (I think it's pulseaudio)
The pulseaudio volume applet picks up only the master volume, and alsamixer (without -c0) is also routed to pulseaudio. That's why you see only 100% there, I guess.
Very strange thing, when running "alsamixer -c0" I dropped and then returned PCM to 100 and exited. After doing that audio is indeed at 100 with a huge improvement in volume. Not sure what to do with the bug, my issue is fixed, but the fact that I have to run "alsamixer -c0" and fiddle to resolve is a bit of a pain and not something normal user should have to do. Any ideas? -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=526127
User tiwai@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c7
Takashi Iwai
http://bugzilla.novell.com/show_bug.cgi?id=526127
User awafaa@opensuse.org added comment
http://bugzilla.novell.com/show_bug.cgi?id=526127#c8
Andrew Wafaa
participants (1)
-
bugzilla_noreply＠novell.com