Intel sound fails in openSUSE 11.1 RC1

English Hardware
#1

Laptop: Dell Precision M4400
openSUSE version: 11.1 RC1
Audio device: Intel Corp 82801I (ICH9 Family)
Audio codec: IDT 92HD71B7X
“The audio playback device HDA Intel (STAC92xx Analog) does not work. Falling back to default.”

I have installed the latest ALSA scripts, firmware, tools, etc. available as of 2008-12-14. When I try to install the ALSA drivers via YaST2 and zypper, I get the following failure messages:

YaST2 Warning: “nothing provides kernel(default:kernel) = 804b868b3ec81a71 needed by alsa-driver-kmp-default-1.0.18.20081212_2.6.27.7_9.1-2.1.x86_64”

D7BFKQH1:~ # zypper install alsa-driver-kmp-default
Building repository ‘ALSA driver kernel modules (openSUSE_11.1)’ cache [done]
Loading repository data…
Reading installed packages…
Resolving package dependencies…

Problem: nothing provides kernel(default:kernel_irq) = df201a335477d689 needed by alsa-driver-kmp-default-1.0.18.20081212_2.6.27.7_9.1-2.1.i586
Solution 1: do not ask to install a solvable providing alsa-driver-kmp-default

(Not sure why zypper is trying to install the i586 version; perhaps a command switch I failed to provide?)

I tried to compile the ALSA kernel module drivers manually, but that was unproductive as well. ‘./configure’ appears to run successfully, but ‘make’ fails almost immediately.

In order to provide more useful detail, have run some commands that appear in other threads on this forum; the output appears below. In addition, I have run the ‘bash alsa-info.sh’ script; output may be found at the following address:

http://www.alsa-project.org/db/?f=5e0d9a40e8a594efec8e7dc33eb7fbcd0533c2be

D7BFKQH1:~ # rpm -qa | grep alsa
alsa-1.0.18.git20081212-1.1
alsa-devel-1.0.18.git20081212-1.1
alsa-firmware-1.0.17.git20081202-2.3
alsa-tools-1.0.18.git20081201-1.5
alsa-oss-1.0.17.git20080715-2.7
alsa-oss-32bit-1.0.17.git20080715-2.7
alsa-plugins-1.0.18.git20081122-1.9
alsa-plugins-pulse-1.0.18.git20081122-1.9
alsa-tools-devel-1.0.18.git20081201-1.5
alsa-tools-gui-1.0.18.git20081201-1.5
alsa-utils-1.0.18.git20081122-1.7

D7BFKQH1:~ # rpm -qa | grep pulse
alsa-plugins-pulse-1.0.18.git20081122-1.9
libpulse0-0.9.12-8.6
libpulsecore4-0.9.12-8.6
libpulse-browse0-0.9.12-8.6
libpulse-mainloop-glib0-0.9.12-8.6
libxine1-pulse-1.1.15-44.pm.2
pulseaudio-0.9.12-8.6
pulseaudio-esound-compat-0.9.12-8.6
pulseaudio-utils-0.9.12-8.6
vlc-beta-aout-pulse-1.0.0-2008121001.1

D7BFKQH1:~ # rpm -q libasound2
libasound2-1.0.18.git20081212-1.1

D7BFKQH1:~ # uname -a
Linux D7BFKQH1 2.6.27.7-4-default #1 SMP 2008-11-25 00:02:37 +0100 x86_64 x86_64 x86_64 GNU/Linux

D7BFKQH1:~ # cat /etc/modprobe.d/sound
options snd-hda-intel model=dell-m4-1 enable=1 index=0

Intel Corporation 82801H (ICH9 Family) HD Audio Controller

alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel

I can try to provide additional information, if needed. I’m also willing to try additional procedures not already covered at SDB:AudioTroubleshooting.

Thanks much for any assistance that can be rendered.

#2

Thanks for that. Your hardware is not detected by alsa.

Reference the IDT 92HD71B7X I note this in the ALSA-Configuration.txt file:

	STAC92HD71B*
	  ref		Reference board
	  dell-m4-1	Dell desktops
	  dell-m4-2	Dell desktops

and I see you tried this in your /etc/modprobe.d/sound file:

options snd-hda-intel model=dell-m4-1 enable=1 index=0
# Intel Corporation 82801H (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel

Can you try a different syntax? Run alsaconf (with root permissions) to try configure your sound. Then, assuming that does not work, but it will change your /etc/modprobe.d/sound file, with that modified file, add the following line at the end, as a separate line:

options snd-hda-intel model=dell-m4-1

Note if dell-m4-1 does not work, you can try dell-m4-2 . Don’t forget to restart alsa each time (either via a reboot or via “rcalsasound restart” with root permissions.

Those warnings puzzle me a bit … but I do note that an alsa-driver-kmp-default has NOT been created yet for 11.1 RC1 … which might explain those messages.

Still, I am a bit worried that your efforts to sort this might have caused more problems. Can you reboot your PC, and provide the output of:dmesg > dmesg.txt && curl -F file=@dmesg.txt nopaste.com/a
and then post the URL that you are given.

Then roll back to the version of alsa that comes with openSUSE-11.1 RC1.

But, having suggested a roll back, also note, before you spend too much time on this, the final released version of 11.1 will be released on 18-Dec (just a handful of days away) and you may wish instead to wait for that and then install that version.

#3

Thank you for your suggestions. I’ll have an opportunity to try them out this evening.

#4

Thanks again. As you speculated, all my mucking about seems to have really knocked things out of kilter.

alsaconf reports, “No supported PnP or PCI card found,” and then offers to probe for legacy ISA devices. Out of curiosity I issued a restart command and got this response:

D7BFKQH1:~ # rcalsasound restart
Starting sound driver: hda-intel
WARNING: Could not open ‘/lib/modules/2.6.27.7-4-default/kernel/sound/core/snd.ko’: No such file or directory
WARNING: Could not open ‘/lib/modules/2.6.27.7-4-default/kernel/sound/core/snd-hwdep.ko’: No such file or directory
WARNING: Could not open ‘/lib/modules/2.6.27.7-4-default/kernel/sound/core/snd-page-alloc.ko’: No such file or directory
WARNING: Could not open ‘/lib/modules/2.6.27.7-4-default/kernel/sound/core/snd-timer.ko’: No such file or directory
WARNING: Could not open ‘/lib/modules/2.6.27.7-4-default/kernel/sound/core/snd-pcm.ko’: No such file or directory
FATAL: Could not open ‘/lib/modules/2.6.27.7-4-default/kernel/sound/pci/hda/snd-hda-intel.ko’: No such file or directory

Not so good.

As you requested, I rebooted and issued the ‘dmesg’ command. The resulting URL is dmesg.txt - nopaste.com (beta), if you care to have a look; but I caution you that it may be time wasted.

I will echo your observation that final release of 11.1 is just days away. I could restore the system from last Friday’s snapshot and begin the process all over, but that probably doesn’t make a lot of sense.

You see, I bought this laptop to replace my desktop system, which has an internal storage array. All the data must now be migrated to an external RAID5, which isn’t supported by the laptop’s native Intel controller. So I had to purchase an ExpressCard/34 controller. The rush to install RC1 was driven by my desire to make certain the whole thing would work (it does!) before time ran out on my opportunity to return the card.

Having configured the RAID5 successfully, I figured I would tackle the sound problem next. Since it has become somewhat intractable, I think it makes more sense to spend the next couple of days encrypting the RAID and then migrating data. I can revisit the sound situation with a fresh install of 11.1 final. Thank you again for your assistance. With luck, 11.1 will be wired for sound.

#5

I think/hope this may be easily fixed with 11.1 GM. So I think waiting is a good idea.

#6

Finished install/config of 11.1 GM earlier today. Sound works out of the box. We be rockin’!

#7

Congratulations.

Thank you for the post, so that we know you had a successful resolution in the end.

#8

Hello! I have the same hardware, and installing 11.1 (64bit) did not enable me to hear sound from the laptop’s speaker.

I do get a Phonon popup that something is wrong, but it vanishes to quickly in order for me to write the message down.

I do not understand much of the above, but under Hardware Information, I see “Intel 82801l (ICH9 Family)” and Device Identifier (spec) “66128” and Device Identifier “76094”. I also have a Dell M4400.

So what should I try on the freshly installed system? Thanks!

#9

There is the possibility that the audio on your Dell M4400 is different than the audio hardware of milehigh. Hence I need more information from you in order to provide a recommendation.

First, which desktop? KDE3 ? KDE4 ? Gnome? XFCE ? other ?

Second, do you get sound from your headphones?

Third, I need to see the output of your running a diagnostic script. With your PC connected to the internet please running the following command in a gnome-terminal or a kde konsole:/usr/sbin/alsa-info.shthat will give you a URL. Please post that URL here.

Fourth, please copy and paste the following commands one at a time into a gnome-terminal or a kde konsole and post here the output: rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound

With the information from those 4 requests I should be able to make a recommendation.

#10

Thanks! Should I open I new thread instead then?

Anyway, here is the requested information:

  1. KDE 4
    (I fear this is a big mistake, given all my other troubles…)
  2. Normal Headphones
    are just as dead. (I have not yet tried a USB headphone, but I think those should work independently, right?)
  3. Your ALSA information is located at http://www.alsa-project.org/db/?f=570728c72a0bee9c810b8f33c8ae1b7293968
    (Is it normal that this link does not show anything in a normal browser? I ran it again, see link in code window.)
Your ALSA information is located at http://www.alsa-project.org/db/?f=6665105ff138a1b761be9a91512a971aa2e2ad73                                                                                              

Please inform the person helping you.


linux-1m4d:/root # rpm -qa | grep alsa
alsa-plugins-pulse-1.0.18-6.13             
alsa-plugins-1.0.18-6.13                   
alsa-oss-1.0.17-1.43                       
alsa-oss-32bit-1.0.17-1.37                 
alsa-1.0.18-8.9                            
alsa-utils-1.0.18-6.4                      
java-1_6_0-sun-alsa-1.6.0.u7-20.3 

         
linux-1m4d:/root # rpm -qa | grep pulse
libpulse0-0.9.12-9.5                        
alsa-plugins-pulse-1.0.18-6.13              
libpulse-browse0-0.9.12-9.5                 
pulseaudio-utils-0.9.12-9.5                 
pulseaudio-module-x11-0.9.12-9.5            
pulseaudio-module-lirc-0.9.12-9.5           
pulseaudio-esound-compat-0.9.12-9.5         
libpulse-mainloop-glib0-0.9.12-9.5
pulseaudio-0.9.12-9.5
pulseaudio-module-zeroconf-0.9.12-9.5
pulseaudio-module-jack-0.9.12-9.5
libpulsecore4-0.9.12-9.5
libxine1-pulse-1.1.15-20.8
pulseaudio-module-bluetooth-0.9.12-9.5


linux-1m4d:/root # rpm -q libasound2
libasound2-1.0.18-8.9


linux-1m4d:/root # uname -a
Linux linux-1m4d 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux


linux-1m4d:/root # cat /etc/modprobe.d/sound

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


linux-1m4d:/root #

Thanks for having a look! It’s a fresh install of 11.1, but I did add some community repositories and the multimedia package from the opensuse-community, but I am very sure that sound did not work right after the initial installation (I did not add/change anything after the installation was finsihed.)

#11

You gave me two links. One works, one does not. I’ll assume you made a mistake on the first, and corrected it on the second.

I do not see alsa-firmware. Please install that. I do not know if you need to upload custom firmware, but it does not hurt to install the application.

OK, this has me very concerned. I see /root # … Are you running your desktop as user root. If so, please do not. I won’t support users who do that. If you are running your desktop as a regular user, but had the konsole open with root permissions, for the commands I gave you, there was no need. You could have run them with regular user permissions. If you need root permissions, I will endeavor to tell you.

Reference your mixer, I note this:
Card hw:0 ‘Intel’/‘HDA Intel at 0xf6fdc000 irq 21’
Mixer name : ‘IDT 92HD71B7X’
Simple mixer control ‘Master’,0
Mono: Playback 88 [69%] -29.25dB] [on]
Simple mixer control ‘Front’,0
Front Left: Playback 88 [69%] -29.25dB] [on]
Front Right: Playback 88 [69%] -29.25dB] [on]
Simple mixer control ‘Analog Loopback’,0
Mono: Playback [off]
Simple mixer control ‘Analog Loopback’,1
Mono: Playback [off]I note your Master and Front volumes are at 69%. That is the level I nominally put them at, but in case your sound is not linear, move them up to 95% for these tests. Once you have sound, you can move them back to 69% or to a more optimal level. Also play with your analog loopback. I think it should be OFF, but I had one user tell me their sound only worked when it was ON (although I’m from Missouri on that).

If you look carefully, you will see milehigh updated his alsa to a more current version than what you have installed. I recommend you also update your alsa. Send the following six commands from a konsole (this time with root permissions :slight_smile: … lol … ) with your PC connected to the internet. My reference for this is here: Alsa-update - openSUSE

zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_11.0/ multimedia 

zypper install alsa alsa-utils alsa-tools alsa-firmware libasound2  

zypper rr multimedia 

zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.1/ multimedia 

zypper install alsa-driver-kmp-default 

zypper rr multimedia

Then restart your PC, and test your audio.

Use this sound test (try as a regular user, and also with root permissions) to test your audio: speaker-test -c2 -l5 -twav

#12

No, I ran it twice and posted both links, neither working for me. However, now the latter one does.

I do not see alsa-firmware. Please install that.

Done.

OK, this has me very concerned. I see /root # … You could have run them with regular user permissions. If you need root permissions, I will endeavor to tell you.

No, I run as a normal user, but issued “su” before running the commands you gave me, because I was not sure. Not everyone specifies that.

Furthermore, with an editor I searched and replaced “/home/login #” with “/root #”. First to tell you that I used a root-console, second to avoid posting my real name, which happens to be my login.

After doing the first two steps, i.e. installing alsa-firmware and increasing the volume to maximum, I had sound both in the headphones and the speakers! :slight_smile: Thanks!

However, neither the laptop’s internal microphone nor the headset’s microphone worked (I use the headset on my old machine often, so it works and the mic is NOT muted, checked.)

So I executed the commands from your previous posts and rebooted the machine.

No change, except for a small shock: No audio! I had reset the volume, but apparently I hear nothing when it is below 80%. At 100%, the sound is just ok (both speakers and headset). My hearing is not exceptional, but I am usually not considered deaf. :wink:

Also play with your analog loopback.
I have no idea what you mean by that? I only click on the sound symbol in the KDE panel, which only offers a PCM slider. Right-clicking, brings a single Tab labelled HDA Intel, having two front sliders, PCM, Headphones and Digital. Unlike the previous Kmix windows in earlier Suse versions, there is no tab for recording, nor a tab with all kinds of buttons (in 10.3, e.g. there are buttons for Mix or MicBoost, etc.). There are no usueful options under “Settings” either.

#13

PS: I found the Kmix “Select Channels” now, and I offers me a lot more buttons and sliders.

I checked all “Capture”-checkboxes and moved all sliders up, but still neither microphone works. :frowning: (Note: Hardware works fine under Windows.)

There are hooks at “Analog Loopback” and “Analog Loopback2”. If I click either of them away, all falls silent. So I leave them, for whatever that means.

Also, I clicked on YAST->Sound->Other->PulseAudio. There was a checkbox for “Enable Pulse Audio”. When I clicked it and rebooted, all was silent again, so unchecked it again.

#14

Congratulations !

I had read of a user with the same hardware audio codec as you having that problem. Thats why I suggested you try 95%. Still, it may be possible to go to YaST > Hardware > Sound > Other and move the volume level up there, so you can back OFF from the 95%.

I also recommend you raise a bug report on the alsa driver and openSUSE in that the volume scale is not linear for your hardware with the alsa driver.

In the KDE4 mixer, you have an menu item that will let you add the extra channels. I would have to log out and log back in to KDE4 to tell you what that menu item is, but I’m sure you can figure it out (if it is offered). It might be called channels ? … Explore your mixer a bit.

I find this can be difficult. I note many new laptops (including mine) have an internal mic that is non-functional under Linux (and in the case of mine works very poorly under Vista).

There are a few possibilities here for getting an external mic to work and why it does not work:
a. the wrong model option is specified specified in your /etc/modprobe.d/sound file, or
b. there is a bug in the alsa sound driver, or
c. your PC’s mixer is set wrong.

I took a look at your mixer settings for recording sound from the previous script, and from what I can see, based on that, there is a high probability with those settings, your sound is munted. (again, note you can possibly expand your mixer settings via appropriate menu selection).

I note this:
!!Amixer output
!!-------------

!!-------Mixer controls for card 0 [Intel]
Simple mixer control ‘Capture’,0
Capabilities: cvolume cswitch
Front Left: Capture 3 [20%] [4.50dB] [off]
Front Right: Capture 3 [20%] [4.50dB] [off]
Simple mixer control ‘Capture’,1
Capabilities: cvolume cswitch
Front Left: Capture 0 [0%] [0.00dB] [off]
Front Right: Capture 0 [0%] [0.00dB] [off]
Simple mixer control ‘Analog Loopback’,0
Capabilities: pswitch pswitch-joined
Mono: Playback [off]
Simple mixer control ‘Analog Loopback’,1
Capabilities: pswitch pswitch-joined
Mono: Playback [off]
Simple mixer control ‘DAC0’,0
Capabilities: cvolume cswitch
Front Left: Capture 23 [74%] [0.00dB] [off]
Front Right: Capture 23 [74%] [0.00dB] [off]
Simple mixer control ‘DAC1’,0
Capabilities: cvolume cswitch
Front Left: Capture 23 [74%] [0.00dB] [off]
Front Right: Capture 23 [74%] [0.00dB] [off]
Simple mixer control ‘Digital’,0
Capabilities: cvolume
Front Left: Capture 0 [0%] -30.00dB]
Front Right: Capture 0 [0%] -30.00dB]
Simple mixer control ‘Import0 Mux’,0
Capabilities: cvolume cswitch
Front Left: Capture 23 [74%] [0.00dB] [off]
Front Right: Capture 23 74%] [0.00dB] [off[/COLOR]]
Simple mixer control ‘Import1 Mux’,0
Capabilities: cvolume cswitch
Front Left: Capture 23 [74%] [0.00dB] [off]
Front Right: Capture 23 [74%] [0.00dB] [off]
Simple mixer control ‘Input Source’,0
Items: ‘Mic’ ‘Front Mic’
Item0: ‘Mic’
Simple mixer control ‘Input Source’,1
Items: ‘Mic’ ‘Front Mic’
Item0: ‘Mic’
Simple mixer control ‘Mux’,0
Capabilities: cvolume
Front Left: Capture 0 [0%] [0.00dB]
Front Right: Capture 0 [0%] [0.00dB]
Simple mixer control ‘Mux’,1
Capabilities: cvolume
Front Left: Capture 0 [0%] [0.00dB]
Front Right: Capture 0 [0%] [0.00dB]I posted in read every item that I think you need to check. Note 74% “may” not be enough to capture, if the capture scale is not linear. I don’t have your hardware so I can not state which one is blocking your sound, but from what I can see, those settings are not good for recording sound. And do not forget to try and add extra controls to your mixer.

Also, what are you doing for a recording test. We do not want the misconfiguration of some application confusing the test results. Hence I recommend you use the basic arecord command.

I typically use: arecord -d 10 myrecording.wav where the “10” specifies the length of the recording. I then a play back “myrecording.wav” with a nominal player.

#15

[QUOTE=oldcpu;1913545]Still, it may be possible to go to YaST > Hardware > Sound > Other and move the volume level up there, so you can back OFF from the 95%.

No, those levels are identical to the one I set in the mixer.

[quote]I also recommend you raise a bug report on the alsa driver and openSUSE in that the volume scale is not linear for your hardware with the alsa driver.
I will do that!

In the KDE4 mixer, you have an menu item that will let you add the extra channels.
Thanks! Found them, as I wrote in my PS (I posted twice, since I could not edit the previous post upon the discovery.)

I find this can be difficult. I note many new laptops (including mine) have an internal mic that is non-functional under Linux (and in the case of mine works very poorly under Vista).
Oh, this is surprising: On my 4 year old HP notebook, the internal mic worked very well for video conferencing. I took that for granted by now. This would be a true killer for me, as I use my notebook now very often for video calls. :frowning: (…and I was so happy that the internal webcam was one of the few things that worked out of the box.)

Altering the mixer settings had some effect, but all that is recorded (with arecord) is static and electrical interference (like holding a mobile near a radio.)

I do manage to hear myself amidst all the static noise on the external mic only, though. However, this is not useable at all for VoIP. :frowning:

I will try more to alter all the settings that you have highlighted. Thanks again!

#16

Added another comment to Bug 461660

Microphone not working. No luck with a USB Headset either.

#17

Your problem is completely different than the bug in that thread.

If you want this fixed, I recommend you start a new bug report. I seriously doubt you will get much work done here if you try to tag on to someone else’s report that is completely different from yours.

#18

Hmm, I thought it was related and one is always reminded to search the database before submitting…

…and still my bugs are then marked as duplicates. Well, if you say so, I will open a new one then.
EDIT: Done, Bug 462007

#19

Some news:

I played around in the mixer while “arecord -d 60 | aplay” was active. With an attached analog headset microphone, I discovered that I get a clear and noise free echo of myself when deslecting Analog Loopback 1 and selecting Analog Loopback 2. I hear myself crystal clear.

However, then arecord fails to record anything in this situation, so this is useless, or does this tell anyone anything? In order to record, I need both Loopback to be checked in kmix. Playing around with the sliders labelled Digital, ImportMux0 and Mux helps to reduce the static, but there is still a lot of static noise. :frowning: Strangely, the test call via skype works fine without any static noise after that fiddling. Is Skype filtering noise? Or is arecord/aplay somehow flawed? I am happily puzzled!

Uninstalling all “pulse”-stuff (except one lib that has far too many dependencies) did not change anything for me. Even worse, I do hear tiny “blib” every few minutes now.

#20

It suggests to me either:
a. you had your mixer still setup wrong, or
b. there is a bug in alsa.

I still would be inclined to take a serious look at “a”.

If you setup your mixer exactly how you think it should be working with your mic, and then run the diagnostic script and post the output here, I will take a look again at your mic settings.