ALSA Upgrade Script

[soundcheck]

If the script fails during the early phases prior to the installation process it won't install anything.

Did you do the reboot?

What does the logfile say? You'll find it under /var/log/Alsa.......

Just edit it and look for strange things.

sudo gedit /var/log/Alsa.....

You can also PM me.

[momist]

Thanks soundcheck,

The relevant bit seems to be this:

Reading package lists...
W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 370054A32DF69BF5
W: You may want to run apt-get update to correct these problems
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
alsa-base is already the newest version.
alsa-oss is already the newest version.
alsa-utils is already the newest version.
alsa-utils set to manually installed.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
build-essential is already the newest version.
libsysfs-dev is already the newest version.
libsysfs-dev set to manually installed.
gettext is already the newest version.
gettext set to manually installed.
linux-headers-2.6.28-11-generic is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
  libavutil-dev: Depends: libavutil49 (= 3:0.svn20090303-1ubuntu6) but it is not going to be installed
E: Broken packages
Problems downloading and installing  the required dependencies...

I tried apt-get update and got the following

Reading package lists... Done
W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 370054A32DF69BF5
W: You may want to run apt-get update to correct these problems

So no help there then.

Ian

[soundcheck]

Try to install libavutil49 manually and then restart the script:

sudo apt-get install libavutil49

[momist]

Thanks soundcheck. That cured the script OK. It took >25 minutes on my machine !

However, no cigar. After the reboot I still have

ian@***:~$ aplay -l
aplay: device_list:223: no soundcards found...
ian@***:~$ cat /proc/asound/versionAdvanced Linux Sound Architecture Driver Version 1.0.21.
Compiled on Sep 16 2009 for kernel 2.6.28-11-generic (SMP).
ian@***:~$

I'll keep looking - but not tonight. Thanks for your efforts, and for the script - I'm sure the sound will be good when I get it back!

Ian

P.S. alsa-info.sh shows this result:
http://www.alsa-project.org/db/?f=8d...6969fd55a53654

[soundcheck]

Ok. The installation seems to be OK now. We'll get there.

Both cards are recognized by the system if you look at the log.

If you type "cat /proc/asound/cards" you'll see both devices. OK.
Both modules are loaded (lsmod | grep snd): OK

snd_intel8x0
snd_usb_audio


Your second card snd-usb-audio is a camera. aplay won't tell you. OK.

Now we need to find out why aplay doesn't see your card.

I googled a bit. Try to run "alsaconf"

[leeelson]

First of all good to see that my new safety anchor worked.
If there is problem with the dependencies the script will drop out.

Hmmh. It seems that there is no alsa-oss in the repo.
Could you please check with synaptic if it is there.

THX

synaptic doesn't show it. Not sure where to get it and the form to use in synaptic. I think I have the Hardy distribution.

[soundcheck]

synaptic doesn't show it. Not sure where to get it and the form to use in synaptic. I think I have the Hardy distribution.

http://packages.ubuntu.com/de/hardy/alsa-oss

[leeelson]

http://packages.ubuntu.com/de/hardy/alsa-oss

I set up synaptic for

dep http://packages.ubuntu.com/hardy/alsa-oss hardy universe

(I used the English version) and got

error message:
Failed to fetch http://packages.ubuntu.com//hardy/al...tion-en_US.bz2 Connection failed
Failed to fetch http://packages.ubuntu.com//hardy/al...a/Packages.bz2 Sub-process bzip2 returned an error code (2)
Some index files failed to download, they have been ignored, or old ones used instead.

If I set the source to be
http://packages.ubuntu.com/hardy/sound/alsa-oss
I get
GPG error: http://packages.ubuntu.com hardy Release: The following signatures were invalid: NODATA 1 NODATA 2Failed to fetch http://packages.ubuntu.com/hardy/sou...a/Packages.bz2 Sub-process bzip2 returned an error code (2)
Some index files failed to download, they have been ignored, or old ones used instead.

This is a read error for bzip2 (bzip2: (stdin) is not a bzip2 file.)



Sorry to be slow, but this is new for me.

[momist]

Ok. The installation seems to be OK now. We'll get there.
<snip>
I googled a bit. Try to run "alsaconf"

Hey thanks, I was going to leave this till tomorrow - but it's still bugging me badly.

If you're still there, thanks again. I ran alsaconf OK and it found the sound card happily, towards the end I got the following output:

         ┌──────────────────────────────────────────────────────────┐
         │                                                          │  
         │                                                          │  
         │      OK, sound driver is configured.                     │  
         │                                                          │  
         │                   ALSA  CONFIGURATOR                     │  
         │                                                          │  
         │           will prepare the card for playing now.         │  
         │                                                          │  
         │      Now I'll run alsasound init script, then I'll use   │  
         │      amixer to raise the default volumes.                │  
         │      You can change the volume later via a mixer         │  
         │      program such as alsamixer or gamix.                 │  
         │                                                          │  
         ├─────────────────────────────────────────────────────92%──┤  
         │                         <  OK  >                         │  
         └──────────────────────────────────────────────────────────┘  
           



Running update-modules...
/usr/sbin/alsaconf: line 929: update-modules: command not found
Setting default volumes...
amixer: Mixer attach default error: No such device
Saving the mixer setup used for this in /etc/asound.state.
/usr/sbin/alsactl: save_state:1502: No soundcards found...



===============================================================================

 Now ALSA is ready to use.
 For adjustment of volumes, use your favorite mixer.

 Have a lot of fun!


ian@***:~$ aplay -l
aplay: device_list:223: no soundcards found...

However, I can't find /etc/asound.state in my file system either by looking (with hidden files shown) or by searching. So does the fault lie with update-modules or with amixer?

Ian

Addendum:
A more careful search reveals that in /var/lib/alsa there is a broken link to asound.state - 17 bytes of type link (broken) - which point nowhere.

[leeelson]

Update:

Never could get the script to work. Could not get alsa-oss via snyaptic. I followed some instructions for downloading and installing lib, utils etc and it worked. My internal mic still is inop . Looks like it may be a codec problem.

Thanks for your help.