No sound with kernel 2.6.27.4 in opensuse 11

I upgraded to kernel 2.6.27.4 from the m4r3k repo listed in webpin to get my wireless drivers working, but the sound doesn’t work at all now. When I type

dmesg | grep "sound"

I get

ALSA sound/pci/hda/hda_codec.c:3047: autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3051:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3055:    hp_outs=1 (0xa/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3056:    mono: mono_out=0x0
ALSA sound/pci/hda/hda_codec.c:3064:    inputs: mic=0xe, fmic=0xb, line=0x0, fline=0x0, cd=0x0, aux=0x0
ALSA sound/pci/hda/hda_generic.c:678: hda_generic: no proper input path found
ALSA sound/pci/hda/hda_generic.c:426: hda_generic: no proper output path found
ALSA sound/pci/hda/hda_generic.c:1021: hda_generic: no PCM found

How do I fix this?

The 2.6.27.1 kernel from the same repo worked perfectly. Is there anyway to get the old version from the repo? Does anyone have a copy?

I can’t find a m4r3k repos with that kernel version … I did a web pin search here for kernel and obtained this hit: Webpin search for kernel

I then looked at

http://download.opensuse.org/repositories/home:/m4r3k:/R-project/openSUSE_11.0

and saw no reference to a kernel module.

Its very common for sound to be broken when one does a kernel update that is as big as the one you did (going from 2.6.26 to 2.6.27). IMHO you were simply lucky it worked i your first 2.6.27.1 efforts. Often the user who creates the custom kernel, will also provide corresponding alsa drivers for their kernel update. I can’t check on that as I do not know where the m4r3k built kernels, that your refer to come from. The webpin search I performed did not help.

Anyway, IMHO you either have to:
a. go back to an older kernel, or
b. find the kernel packagers built alsa drivers (if they build any), or
c. compile the alsa applications yourself against this new kernel.

Index of /repositories/home:/m4r3k:/kernel-backport/openSUSE_11.0

That’s the repo I was talking about. For some reason, webpin only shows it if you search for kernel-pae.

I went from 2.6.25 to 2.6.27, so an even bigger jump. :stuck_out_tongue: Never saw a 2.6.26 version for opensuse. Of course during the RC releases, they had some bad bugs regarding kernel panics because of something weird with GRUB interaction, but I just kept reinstalling. I should have just stopped at 2.6.27.1, but I thought I could go higher. Remind me never to play with the stock market.

I didn’t have to install the ALSA drivers for 2.6.27.1, were they perhaps bundled with the kernel somehow? As far as I know, m4r3k never had alsa packages.

So, what should I do?
1.)Is there a way to enable the intel wifilink 5100 on the old 2.6.25 kernel?
2.)Is there a way to use the buildservice to help me build my own version of 2.6.27.1?
3.)And as a last resort, how do I build alsa packages against my kernel? I don’t even know where to start!

I would try a bit more to get your sound working, then if that fails, custom compile your own alsa. Its actually fairly easy, although the first few times one custom compiles it can be difficult.

But before custom compiling, how about providing some more information ? To provide more information, then with your PC connected to the internet, please copy and paste the following into a gnome-terminal or to a konsole:

wget http://home.cfl.rr.com/infofiles/tsalsa && su -c 'bash ./tsalsa' 

when prompted for a password please enter your root password. Please try to accurately answer the question on the number of plugs/jacks on your PC (for example my PC has 3 i/o plugs/jacks). When the script completes it will pass you a URL. Please post that URL here.

Also, reference your headphone problem, please copy and paste the following, one line at a time, into a gnome-terminal or to a konsole and post the output here.
rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/soundAlso, are you using Gnome? KDE4? or KDE3? I’ll explain about compiling in a separate post.

As noted, this is not difficult, with some experience. The first time will be fun. First of all, you need to install the tools to do this. Go to YAST > SOFTWARE > SOFTWARE MANAGEMENT and change “filter” to “patterns”. Then under “Development” select “Base Developement”. That will install a bunch of applications you need to compile.

Then change “filters” back to “search” and search for “checkinstall” and install that (we will use checkinstall to create some custom rpms). Also ensure you have libtar and tar installed.

Then go to that repository where you obtained your kernel, and install kernel-source. Note kernel-source must match your running kernel.

Then go here, and download the tarballs for each of the following (a tarball has a .tar.bz2 extension in this case) :

  • alsa-driver-1.0.18 (ie alsa-driver-1.0.18.tar.bz2)
  • alsa-lib-1.0.18 … etc …
  • alsa-utils-1.0.18
  • alsa-tools-1.0.18
  • alsa-firmware-1.0.17
  • alsa-plugins-1.0.18
  • alsa-oss-1.0.17
    I don’t know if all need be compiled to get your alsa working, but its possible. But once you get the 1st successful compile, I suspect the others will be easy.

Download those to a directory /home/yourusername/tars or something like that. Uncompress those. I can do this on my kde by selecting the file and right clicking to uncompress.

Then open a gnome-terminal or a konsole and change into the directory where alsa-driver-1.0.18 is uncompressed (when you untar it will create its own directory).

Then read the readme.txt and install.txt for any special instructions. There may or may not be. The type the following in that konsole or gnome-terminal:
./configure
make
su [size=]#enter root password when prompted
checkinstall[/size]

That will create an rpm, and checkinstall will tell you where the rpm is located. You could try installing that rpm now, or you could try making the other rpms and install all at once. Note these rpms are poor quality rpms. They are for use on your pc only and they don’t have all the checks , … etc … that a normal rpm will have.

If “checkinstall” fails, then replace “checkinstall” with the following sequence (ie after ./configure, make, su):
make install
checkinstall
In this later case, “make install” will install alsa on your PC. But by then running checkinstall, it will take the successful “make install” activity and create an rpm. Install that rpm. It will then enter the install information in to your rpm database, making it easier to remove the alsa version later, if so desired.

Then proceed to the other tarballs and do the same.

Do not remove the tar compilation directories, as another method to remove the tarballs (besides the rpm method with checkinstall) is to type “make uninstall”. You can also start an tarball compilation afresh with “make clean”. But you need that directory still in place for “make uninstall” to work.

You can post here any compilation errors you get.

But before you try to compile, I recommend we investigate more about your audio config (hardware/software) in case this is a simple mixer problem.

tsalsa.txt - nopaste.com (beta)

I am using KDE 4.1 from Factory repo by the way.

I hope you have a high resilience to hiccups and pain. :slight_smile: I specifically avoid anything other than the basic KDE (3.5.7 on my openSUSE-10.3 PC and 3.5.9 on my openSUSE-11.0 test PC) and other than the basic kernel. I don’t have the patience for cutting edge desktop/kernels.

There is a risk that some quirk of the 4.1 KDE on your 11.0 could also cause a problem with your sound, and since I avoid those sort of cutting edge updates, its unlikely I’ll be able to help if that is affecting your sound.

I sincerely apologize if I am making the task of helping me more difficult. I have tried reverting to the older kernel with my current version of KDE 4.1 and it works fine, just without wireless. It’s only when I upgrade to 2.6.27.4 does it bork.

My resilience to tech pain is really high. :stuck_out_tongue: I do not have much important data in my Linux partition right now, so reinstalling is not an issue. I only need it for my college CS lab.

Did you find any problems with the tsalsa output?

I was waiting for you to run the other commands in that post.

Your PC’s hardware audio codec is an IDT 92HD71B7X. Thats not all that common.

I have read of Ubuntu users applying this settin to their sound file: options snd-hda-intel enable_msi=1
( I note you your script output it has: snd_hda_intel/parameters/enable_msi:0 ).

In your case that would equate to adding that line at the end of your /etc/modprobe.d/sound file. But to create the syntax for that line, it really helps if one can see the file first, especially to confirm if the syntax from that Ubuntu post is applicable (from a syntax perspective) to open SuSE. Also, if the problem is kernel incompatibility with the alsa driver, then I do not think setting enable_msi=1 will make any difference.

rpm -qa | grep alsa returns:

alsa-oss-1.0.15-48.1
alsa-utils-1.0.16-35.1
alsa-1.0.16-39.1
alsa-plugins-1.0.16-57.1

rpm -qa | grep pulse returns:

libpulse0-0.9.10-26.5

rpm -q libasound2 returns:

libasound2-1.0.16-39.1

uname -a returns:

Linux linux-4qi7 2.6.27.4-10-pae #1 SMP 2008-11-04 09:11:45 +0100 i686 i686 i386 GNU/Linux

cat /etc/modprobe.d/sound returns:

options snd slots=snd-hda-intel
# u1Nb.uI7Vp9nVK5B:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel

That is strange. When I compare that to the script:

where the script gives this:

Alsa driver: 1.0.17        
dpkg path:           
Alsa utils: 1.0.16

the rpms are not consistent with what the script says you have installed. That makes little sense to me, unless you changed your alsa configuration in between. Its risky to make a recommendation when the configuration has changed.

The edit the Ubuntu users applied in openSUSE terms equates to:

options snd slots=snd-hda-intel
# u1Nb.uI7Vp9nVK5B:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
options snd-hda-intel enable_msi=1

If one makes such an edit, it is essential to restart alsa to test it (which can be done by a reboot or other means, such as runnng: su -c ‘rcalsasound restart’

But I suspect this was a kernel incompatibility, in which case I believe that such a change to the /etc/modprobe.d/sound file is not likely to help.

You’re right, changing etc/modprobe.d/sound doesn’t do anything. I think I’d like to try compiling my own kernel 2.6.27.1. Is it possible to do this easily with the buildservice?

There are already rpms built for the latest alsa, for the standard kernels, and I wrote a guide on how to update:
Alsa-update - openSUSE

with the 2 repos for 11.0 here:

http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_11.0/
http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.0_Update/ 

but those are built against specific kernel versions that are not yours.

As to whether one could build other kernel versions via the build service, I don’t know.
I take it then my compilation instructions appear too difficult to follow.

I have switched to Kubuntu 8.10 for now as a temporary solution, but I will switch back to opensuse 11.1 in a month or so.