http://bugzilla.kernel.org/show_bug.cgi?id=10300
------- Comment #14 from [EMAIL PROTECTED] 2008-04-16 06:24 -------
Takashi,
I did what you suggested. I started the laptop (resuming from suspend to ram,
but the behaviour is more or less the same), opened the gnome volume control
and take a screenshot of it, and immediately after I took a "alsactl -f
start_state.txt store" data.
After that, I gave the volume wheel a "shot" down. The result is in
one_jot_down.{txt,jpg}. Notice the status assumed by the PCM control. The
channels went unjoined, and after that whatever thing I do with the wheel they
stayed so.
You have more data, with 5 more shots down, then 4 up, then 6 more up. Whatever
I do, the volumes of the PCM never went back to maximum. They go up and down in
an apparently random way, sometime going up, sometime down, every time I use
the wheel.
The only way to have the two (left and right)controls to the max togheter is to
put them there, independently, with the mouse, and then joining them.
After that, with the mouse all is ok, but if I hit the "zero" value, they
unjoin again, and I have to rejoin the two channel manually.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
