Updating Suse 11.1 to Kernel 2.6.27.48… and then updating alsa-driver-kmp (from multimedia:/audio:KMP/openSUSE_11.1_Update) completely broke my sound system.
Alsa is up-to-date from multimedia:/libs/openSUSE_11.1 and my sound chip is HDA_Intel on a Toshiba laptop. The system worked with all previous kernel and Alsa-KMP updates.
boot.msg gives the following:
<6>HDA Intel 0000:00:14.2: PCI INT A → GSI 16 (level, low) → IRQ 16
…
<3>ALSA hda_intel.c:1451: no codecs initialized
<6>HDA Intel 0000:00:14.2: PCI INT A disabled
for reference, boot.msg gives the following when the sound system is working:
<6>HDA Intel 0000:00:14.2: PCI INT A → GSI 16 (level, low) → IRQ 16
…
<6>hda_codec: Unknown model for ALC268, trying auto-probe from BIOS…
<7>ALSA sound/pci/hda/hda_codec.c:3281: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0)
<7>ALSA sound/pci/hda/hda_codec.c:3285: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
<7>ALSA sound/pci/hda/hda_codec.c:3289: hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
<7>ALSA sound/pci/hda/hda_codec.c:3290: mono: mono_out=0x0
<7>ALSA sound/pci/hda/hda_codec.c:3298: inputs: mic=0x18, fmic=0x0, line=0x1a, fline=0x0, cd=0x0, aux=0x0
Removing the KMP drivers will allow the sound system to partially work again.
Any ideas of what happened? - is there any way to notify the Alsa packager that there is a problem? - Any help is much appreciated.
Thanks.
P.S. - Thanks to ATI (who made my graphics chip a legacy chip one year after buying my laptop), I cannot upgrade to 11.2 or 11.3.
Thanks oldcpu, but I have made all the correct updates. after updating to kernel-pae 2.6.27.48- alsa still worked fine. But updating to alsa-driver-kmp for 2.6.27.48- broke the system. All alsa files and libasound are all updated from multimedia repository as stated above.
For some reason, the codec for the hda_intel chip will not get loaded with the latest alsa-driver-kmp update.
Typically when updating alsa, you need more than just the kmp. You need all the other updated alsa packages (on a one-on-one to what you have currently installed) also. For example, if you have alsa-oss, alsa-utils, alsa-plugins, alsa-oss-32bit, alsa-plugins-32bit, alsa-devel, alsa-docs
alsa installed, you also need to update those from here:
Maybe thats what you did, but it is not clear to me it is.
Also, I have had many users claim they have actually done that, but when I asked them to run:
rpm -qa '*alsa*'
and post the output, it was clear they did NOT do the update, even though they had mistakenly thought they had done the update. So care is needed here.
I checked those version numbers, and they look ok.
what you could do, if you have time, is write a bug report on openSUSE component “sound” on openSUSE-11.1.
Attach (don’t copy and paste, but attach) to the bug report the text file from running:
/usr/sbin/alsa-info.sh --no-upload
and that will create the file /tmp/alsa-info.txt which can be added as an attachment. That has bunch of technical info that may show the alsa dev what is wrong with the alsa driver, IF you also describe the audio symptoms.
Note the SuSE-GmbH packager for sound is also an alsa developer, and if he fixes this, the fix gets sent upstream and ALL Linux distributions will benefit from your efforts with him.
There is guidance here for raising bug reports: Submitting Bug Reports - openSUSE … The alsa developer/openSUSE packager, may ask that you try a few different alsa versions, and hence if your schedule is too busy for such support (and I definitely know what that can be like) then its probably best NOT to write such a bug report.
Don’t reference this thread, as the SuSE-GmbH packager refuses to read forum threads. Its important the bug report has all the salient information.
Thanks oldcpu - unfortunately, I have just downloaded and compiled the drivers from the Alsa-project website. Everything seems to be working again. If I have a few minutes, I will re-install the KMP drivers, and see if it fails, then send in a bug report as you described.
Thank you very much for you time and help.
Cheers.
Good luck. I forgot to mention above, but its in the guide I quoted, and I think it pretty obvious, after installing the updated alsa rpms, a reboot IS necessary.
