Happy New Year.
We don't use the Measure Activity.
Here are the most frequently used Activities using sound:
- Scratch version 11 (with resume sound problem, ticket #6201)
- Record version 59
- Browse version 98 with Adobe flash plugin version 10.0.12.36 (gnash
deinstalled) for a flash based
Alsa keeps the values in memory and writes it into the
/etc/alsa/asound.state file during shutdown. The file has a new
timestamp, so someone is writing into it at least.
Sorry my master asound.state file was working but not standard. I have
now 5 values that are different between a standard XO
On Wed, Dec 31, 2008 at 03:52:05PM +0700, Philipp Kocher wrote:
Alsa keeps the values in memory and writes it into the
/etc/alsa/asound.state file during shutdown. The file has a new
timestamp, so someone is writing into it at least.
Okay, that must be a build 767 thing. Recent
I have seen this problem when the alsamixer settings have become
messed up. Seems like there are one or 2 processes that occasionally
write to the alsamixer config file.
You can alter the settings by running the graphical program /usr/bin/
alsamixer from the terminal. There is also a
How to fix no sound caused by operating system.
1. obtain the root prompt, e.g. by starting the Terminal activity and
clicking on become root button,
2. if you wish to find out in which way the settings have been
corrupted, copy the file /etc/asound.state before proceeding,
cp
...@laptop.org
Subject: Re: XOs with no sound
To: Philipp Kocher philipp.koc...@gmx.net
Cc: devel@lists.laptop.org
Message-ID: 20081230094639.ga12...@us.netrek.org
Content-Type: text/plain; charset=us-ascii
How to fix no sound caused by operating system.
1. obtain the root prompt, e.g
On Tue, Dec 30, 2008 at 09:32:38AM -0500, Greg Smith wrote:
That's great debugging and repair info. I especially like the use of the
stack trace command! That's a great trick for hunting down which process
is calling what files.
Actually, it's a system call tracing command. It can be used
What is the ticket number for that problem?
It seems like always the same 7 values are wrong.
There is a shorter solution:
1. Copy /etc/alsa/asound.state of a healthy XO to USB flash drive
2. Type alsactl -f /media/{flash_dirve_name}/asound.state restore on
the XO with no sound
Thanks
On Wed, Dec 31, 2008 at 09:22:17AM +0700, Philipp Kocher wrote:
It seems like always the same 7 values are wrong.
Which 7 values?
1. Copy /etc/alsa/asound.state of a healthy XO to USB flash drive
Okay, so it is in /etc/alsa on those builds? Are you sure that file is
in use? On the build I'm
