Alsa fried after attempted alsa upgrade -- help!

English Multimedia
1

Hi,

I’ve been running 10.3/vista dual boot for about 1.5 yrs with no sound problems. A few months
ago I successfully installed an old echo mia card. A few days ago I tried
upgrading alsa from here:

Alsa-update - openSUSE

Since then my audio has been broken, which is a disaster for me as my
work depends on it.

I tried some custom compiling of sources at alsa-sound, which did not help.
I’ve tried uninstalling everything, getting back the old system, and
nothing I’ve tried gets anything. It’s rather certain that I don’t know what I’m doing & I’d greatly appreciate help.

The machine is:

uname -a
Linux presto 2.6.22.19-0.2-default #1 SMP 2008-12-18 10:17:03 +0100 i686 athlon i386 GNU/Linux

This is what I currently have:
rpm -qa | grep alsa
alsa-plugins-maemo-1.0.14-41
alsa-tools-1.0.14-38
alsa-1.0.14-31.2
kalsatools-1.5.0-468
alsa-plugins-samplerate-1.0.14-41
alsa-devel-1.0.14-31.2
alsa-firmware-1.0.14-24
alsa-plugins-1.0.14-41
FA_clalsadrv-1.1.0-80
alsamixergui-0.9.0rc1-644
alsa-oss-1.0.14-23
alsa-tools-gui-1.0.14-38
alsa-docs-1.0.14-31.2
alsa-utils-1.0.14-27
alsa-driver-kmp-default-1.0.20.20090605_2.6.22.19_0.2-3.1

Are these drivers compatible?

alsa-info.sh gives this:
http://www.alsa-project.org/db/?f=3960f1b2763959187853d654c362c29fdda05f8d

the zypper repositories are as follows:
Reading repository ‘Main Update Repository’ cache

  • Reading repository ‘multimedia’ cache
  • Reading repository ‘10.3 - Main Repository (OSS)’ cache

The versions here are not what rpm gives. How do I fix this? After 48 hrs
of futile googling/patching/restarting I’m at the end of my rope & I’d
really appreciate help. thanks!

– eliot

2

No, they are not compatible.

The alsa update guide you quoted states this:

You should send 6 zypper commands to update your alsa (they are given below).
It appears to me you did not. Then later it states:
In addition, to update ALSA driver modules, send the following 3 zypper commands applicable to your kernel version (in the following section). DON’T FORGET THIS.
As near as I can determine, you decided not to update most of the alsa modules and only installed the alsa-driver-kmp-default and for a reason that you have not stated elected to ignore the recommendation of the alsa update guide. I can not figure out why you decided not to follow the guide completely, but decided to only follow part.

You need to send six zypper commands. Not 3 commands. And the six command have to be successful

PLEASE how can I write that guide to stop users making the mistake you just made?

Also, why do you have so many alsa apps installed? Do you have a reason for those extra apps? Do you believe more is better? Its not better. It can be worse. I have not used MS-Windows for over a decade at home, so I don’t know if “more is better” is the way MS-Windows works, but it is NOT the way Linux sound works.

Anyway, here is how you should update and keep all those extra alsa apps that you installed. Please open a konsole or terminal and type ‘su’ (no quotes - enter root password when prompted) and then copy and paste the following six zypper commands, one at time, in sequence, into that console/terminal and execute them:

zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_10.3/ multimedia

zypper install alsa-utils alsa-devel alsa-plugins-maemo alsa-plugins-samplerate alsa-tools alsa-tools-gui alsa-firmware alsa-oss alsa-plugins alsa-docs

zypper rr multimedia

zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_10.3_Update/ multimedia

zypper install alsa-driver-kmp-default

zypper rr multimedia

Its possible the 5th command above will tell you that alsa-driver-kmp-default is already installed at the latest version. In which case still send the 6th command.

Restart and test your PC sound.

3

Well, I did issue all 6 commands.

I did zypper remove on all but the core modules.

I now have this, but still no sound:

rpm -qa | grep alsa
alsa-1.0.14-31.2
alsa-tools-1.0.20-7.3
alsa-utils-1.0.20-9.2
alsa-plugins-samplerate-1.0.20-7.3
alsa-oss-1.0.17-2.10
alsa-driver-kmp-default-1.0.20.20090606_2.6.22.19_0.2-1.1
alsa-firmware-1.0.20-5.1
alsa-plugins-1.0.20-7.3

I ran alsaconf afterwards, which claimed to detect the mia card, but which didn’t
result in sound.

I did get some zypper errors, about various files not being seen on the repository.
When I ran zypper again it found them.

I also get:

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.20-git20090606.
Compiled on Jun 5 2009 for kernel 2.6.22.19-0.2-default (SMP).

thanks to some evidently ill-advised custom compiling. I assume this is not compatible with alsa-1.0.14-31.2 ?

Very many thanks for your help.

4

ok, that looks better :slight_smile:

ok, … what is your criteria for saying “no sound” ??

Please try the 3 sound tests here: SDB:AudioTroubleshooting - openSUSE
Its VERY COMMON for one or two of those tests not to work. Try all 3. The 3rd is the alsa web site test.

next time you get errors, do a print screen to a file, then you can tell us later precisely what they are.

reads like you have a poor internet connection.

Custom compiling typically requires either advanced knowledge or luck, …

The 1.0.14 alsa rpm you have should be compatible with the other rpms that you installed. Please, what is the output URL provided by running this diagnostic script with your PC connected to the Internet:

wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && bash alsa-info.sh
5

ok, … what is your criteria for saying “no sound” ??

I ran all tests. Currently, the soundcard is not detected. When the
card was detected earlier speaker test would run (echoing report) but
with no sound.

Please, what is the output URL provided by running this diagnostic

http://www.alsa-project.org/db/?f=81b2a9e2b4260f3d294b112a0cd2b65f1213c0b9

thanks again

6

If it was the alsa update that broke your sound, why not roll back to your original alsa (on your installation CD / DVD ).

7

I’ve tried that, and in lieu of hanging myself I tried it again. I rolled back to whatever it previously was, and now alsaconf reports
modinfo: could not find module snd
modinfo: could not find module snd
modinfo: could not find module snd

Perhaps this is because I now have no sound drivers and I don;t know
ehere to get them?

rpm -qa | grep alsa
alsa-firmware-1.0.14-24
alsa-1.0.14-31.2
alsa-plugins-samplerate-1.0.14-41
alsa-utils-1.0.14-27
alsa-tools-1.0.14-38
alsa-plugins-1.0.14-41
alsa-oss-1.0.14-23

What I have learned so far is that the current drivers are not compatible with this setup. Where do I find the old ones?

8

From what I can see, you have the old one’s installed.

I think if you wish to make progress on this you will need to write a bug report, and maybe the SuSE-GmbH packager (who is also an alsa developer) can help you: Submitting Bug Reports - openSUSE

9

There seem to be inconsistencies between the versions of alsa here:
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.20-git20090607.
Compiled on Jun 6 2009 for kernel 2.6.22.19-0.2-default (SMP).

and here:

rpm -qa | grep alsa
alsa-firmware-1.0.20-5.1
alsa-1.0.14-31.2
alsa-plugins-samplerate-1.0.14-41
alsa-oss-1.0.17-2.10
alsa-driver-kmp-default-1.0.20.20090607_2.6.22.19_0.2-1.1
alsa-utils-1.0.20-9.2
alsa-tools-1.0.20-7.3
alsa-plugins-1.0.20-7.3

My conclusion is this. I’ll pick up a new machine tomorrow, waste
a few more days configuring that, and then get back to work.

10

You have me confused as to what you have installed. A couple of posts back you posted this:

Did you not have those installed? If not, to roll back, you just insert your installation DVD or CD, go to YaST > Software > Software Management, and select to install the old versions. That will roll back.

Rolling back is a FUNDAMENTAL technique that every linux user should know.

There is no inconsistency that I can see.

Your PC has the kernel 2.6.22.19-0.2-default and the alsa-driver-kmp-default-1.0.20.20090607_2.6.22.19_0.2-1.1 . Those are consistent with each other.

The most current version of alsa-oss is 1.0.17-2.10 and that has been tested and is known to work with the 1.0.20 of alsa. The SuSE-GmbH alsa packagers has adopted an approach where the alsa-1.0.14-31.2 rpm still remains even after the 1.0.20 installation of alsa. If you look at the diagnostic script output that you posted , you will see only mention of 1.0.20 of alsa and no mention of 1.0.18, nor 1.0.17, nor 1.0.14. That indicates there is no inconsistency.

Again, to roll back, just insert your installation CD/DVD and roll back.

If you installed previous from a tarball to do a custom compilation, go to the directory where you installed that, and do a “make uninstall”. And then force the re-installation of your alsa applications.

I had thought you tried all of that already?

Are you certain this sound card you put in actually works?

11

At this point this is just for laughs, because I’ve officially given up,
but here is the whole story.

The card is an echo mia. The machine is suse 10.3 update/vista DB. The card
works fine in vista (ie, same hardware – get it? there is NO DOUBT that the card works).

Under the suse setup, I could not exactly understand how the sliders in alsamixer corresponded to the card. I was getting glitches and
a relatively limited amplitude range. It sounded as if something not
under my control was acting as a filter. So I decided
to “UPGRADE” alsa. Oh, what foolishness.

I followed instructions on the update page, but the result was that
suddenly I had no sound. This is very bad, because I am a composer.

So, notice that “rolling back” would hardly solve my problem, since
I “rolled forward” in an attempt to CORRECT a problem. Of, course,
in retrospect, I would have preferred some sound to no sound.

I experimented for the next few days, with mounting frustration, as
my work, which demands immediate attention, has to be put off until
the sound problem is corrected.

As we all know, when we google for information we never find a primary
documentation source. Rather, we find forums like this one, with
people asking questions and posting reams of information. These posts
mostly go unanswered. We are never sure if the nice-willed people who
extend helping hands know anything themselves.

When we try to figure things out from the Alsa homepage, we are
overwhelmed with low-level information and incomplete, and often
incoherent, wikis written by random people whom we cannot trust.

Someone suggests, “why not recompile alsa?” We attempt this but it does not
help. We make uninstall.

One of the key instabilities in the linux world is the
diostinction between package-based management & those things we
compile from scratch, which the package system never learns about,
and so we wind up with all sorts of incompatibilities. It quickly
becomes a twisted nightmare. Because of these inconsistencies, we can
no longer use yast & friends.

Rolling back is a FUNDAMENTAL technique that every linux user should know.

Yes, and where are the instructions? I started with suse 10.3. I upgraded with yast to 10.3_update. I don’t see where in the 10.3 cd I have any
option to roll back. I can try rolling back in yast (i’ve tried this about 6 times) but this does not correct my problem.

Again, to roll back, just insert your installation CD/DVD and roll back.

Yes, but I have a very complex system which I do not want wiped out and I did not see where to reinstall alsa without destroying my system.

12

If you re-install your original alsa applications by going to YaST > Software > Software management, and select version 1.0.14 of alsa for all of the alsa apps, and also remove the alsa-driver-kmp-default (if it was not already automatically removed) and ensure you force a re-install of the rpm alsa-1.0.14-31.2 you will effect a roll-back.

There is no “menu item” called roll back. Rather “roll back” is what I asked you if you had done.

Now when you state it does not correct your problem, which problem ? I can’t guess which one. I know its painfully obvious to you, but its not to me.

You gave up without writing a bug report?

Sadly, thats what many users do, to the detriment of Linux.

We are fortunate in openSUSE that the SuSE-GmbH packager for alsa is also an alsa developer. Which means by writing a bug report on openSUSE sound, one gets the direct attention of an alsa developer.

Try getting the direct attention of the sound developer in any other OS.

However, most users simply adopt the windoze approach of giving up and moving to something else, in this case moving back to the Windows operating system, instead of providing the input to fix the original problem. Its unfortunately as in the case of openSUSE one can have a direct pipeline into a developer.

Anyway, … I actually DO SYMPATHIZE with your frustration. Best wishes in Vista or what ever OS you end up in.

13

In case you did not know (could not find from a google search) there is information on writing a bug report on openSUSE here: Submitting Bug Reports - openSUSE

14

I plan to stick with linux for computing and whatever works with sound,
which does not happen to be suse 10.3 with a bunch of incompatible patches that no one understands.

15

Just made a phone call. Friend has the same card, I did the install for 10.3, 11.0 and 11.1 and it has always worked. I didn’t even know a card like this could cause so much trouble.
This makes me think you destablized the whole thing. Not on purpose, but trying to get it right.
I also do see your frustration. And hope you indeed stick to linux, I don’t care what distro. I know there are some distro’s and spin-offs that are focussed on audio. But 11.0 and 11.1 should work.

I suddenly notice: you removed the alsa kernel module. Did you do a reinstall of the kernel ? I’m sure you used the built-in kernel module before and that worked. But you installed the module from the repo, then removed it, so now the kernel doesn’t have anything at all !!

16

No, that was not my intention, nor is it what I wanted you to do.

The bug report is for your card not working, NOT for your inability to roll back.

The drivers are on your installation CD/DVD. You just need to install those (which will cause a roll back). Its incredibly simple to do. I state again, the drivers are there on your installation CD/DVD. OK ?

The SuSE-GmbH developers/packagers do not read this forum. For a bug report to be recognized, one has to do more that state “here is my bug report”.

Again, sorry to read of your frustration. Its unfortunate you are on your own not next to a more knowledgeable Linux user, as I am suspicious this is something easy to solve, but without being in front of your keyboard and monitor, its next to impossible to figure out what has happened.