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.