Hi James et al, 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.
Do we know how this gets in a failed state to begin with? I read the headlines of them most recent 100 bugs with "sound" in them and I didn't see anything that would cause this. I only saw 3 old, closed bugs with "alsactl" in them. If we have an ideas on why or how this happens, let's file a bug and I can track it for 9.1. Thanks, Greg S ***************** Date: Tue, 30 Dec 2008 20:46:39 +1100 From: qu...@laptop.org Subject: Re: XOs with no sound To: Philipp Kocher <philipp.koc...@gmx.net> Cc: firstname.lastname@example.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. 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 /etc/asound.state /home/olpc/asound.state.orig 3. obtain a copy of /etc/asound.state from a working XO, or from a reinstalled XO, and place it in /etc/asound.state on the failed XO, 4. restore the settings from the file, alsactl restore 5. test that sound now works. Note: there is a possibility that the build 767 ALSA saved state file is in some other place. I've not checked. I found out where the file was on Joyride 2612 using a command: strace -e open alsactl restore -- James Cameron mailto:qu...@us.netrek.org http://quozl.netrek.org/ _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel