Comment 8 for bug 130397

Sound worked with Windows, does not work with Linux Ubuntu, installed July '07, accept once with an up-date down load from you. The sound worked until I shut the machine off. Upon starting the machine up the next day, no sound, and no sound the past two months since installation. I've plated with System/Preferences/Sound but I can't make sense of those settings.
Thanks for your help on this.
Mike
ProblemType: Bug
Architecture: i386
Date: Sat Jul 21 17:34:34 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.18.1-0ubuntu3.1
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/mike
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux c-71-232-240-212Mike 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

#We couldnt find a suitable wget, so tell the user to upload manually.
else
 if [[ -z $DIALOG ]]
 then
  echo ""
  echo "Could not automatically upload output to http://www.pastebin.ca"
  echo "Possible reasons are:"
  echo " 1. Couldnt find 'wget' in your PATH"
  echo " 2. Your version of wget is less than 1.8.2"
  echo ""

 echo "Please manually upload $FILE to http://www.pastebin.ca/upload.php and submit your post."
  echo ""
 fi
 if [[ -n $DIALOG ]]
 then
  dialog --backtitle "$BGTITLE" --msgbox "Could not automatically upload output to http://www.pastebin.ca.\nPossible reasons are:\n\n 1. Couldn't find 'wget' in your PATH\n 2. Your version of wget is less than 1.8.2\n\nPlease manually upload $FILE to http://www.pastebin.ca/upload.php and submit your post." 25 100
 fi
fi
#Clean up the temp files
if [ -z $KEEP_FILES ]
then
 cleanup
fi

1. tail -2 /proc/asound/oss/sndstat
The above command lists the codecs involved. The output from this command is vital. Different codecs pushing the same driver (say, intel8x0, emu10k1, or hda-intel) exhibit a huge variation in errata.

2. amixer
It is imperative that you include the amixer output from your preferred (the one that's giving problems) audio device. The community has spent years documenting known mixer issues on http://alsa.opensrc.org/ (see drivers). For instance, many of the codecs driving cs46xx, emu10k1, and intel8x0 require multiple elements to be selected, unmuted, and raised to audible levels.

3. lspci -nv
The actual {sub,}{vendor,device} IDs are important. That's how we track whether something exists as a quirk or needs to be added/modified.

4. asoundconf list
This script command (which is really just filtered cat /proc/asound/cards) lists the enumerated sound devices on your system.

5.cat /etc/asound.conf ~/.asoundrc*
We need to know if you've modified any runtime configuration files that affect how alsa-lib interacts with your sound devices. The nonexistence of the above files is not a problem.

6. dmesg
Many codecs and drivers, upon initialization, will spit something via printk() into the kernel ring buffer. Any diagnostic messages will appear in this output.

7. cat /proc/interrupts
Sound devices require resources. We need to see if those resources are properly assigned, the above command lists interrupts used.

8.Manual sound configuration collection
You can use aplay to get a list of soundcards configured by alsa
$ aplay --list-devices
aplay: device_list:200: no soundcards found...
The following commands can help to figure out what sound card (chip set) you have (Look for lines that contain 'Multimedia audio controller')
$ lspci -v
$ lspnp -v

Mike Dudley
_________________________________________________________________
Windows Live Hotmail and Microsoft Office Outlook – together at last.  Get it now.
http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033