I see your HP DV-5 has a Codec: IDT 92HD71B7X codec, and you are running the latest 2.6.27.19-3.2-default kernel. The 2.6.27.19 kernel update broke the sound for the 92HD71B7X (and some other recent hardware) on openSUSE-11.1 and so the openSUSE/alsa dev created some rpms to install to fix the problem.
But before I recommend the zypper commands to send to update (via rpm) your alsa version can you tell me what rpms you have installed now? What is the output of:
rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
OK, thanks for that. Lets update the alsa version to 1.0.19 in your PC to be consistent with the 2.6.27.19 kernel.
You can update alsa for your laptop by opening a konsole or a terminal, and type ‘su’ (no quotes - enter root password when prompted) and with your PC connected to the internet, copy and paste and execute, one at a time, in sequence, the following six zypper commands:
zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_11.1/ multimedia
zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.1_Update/ multimedia
zypper install alsa-driver-kmp-default
zypper rr multimedia
After that is complete, open your PC’s /etc/modprobe.d/sound file with root permissions and edit it by adding the following line at the front of the file:
"options snd-hda-intel model=hp-m4 enable_msi=1 " such that the file looks like:
options snd-hda-intel model=hp-m4 enable_msi=1
options snd slots=snd-hda-intel,snd-hda-intel
# 5Dex.DVex+nmP8+5:SBx00 Azalia (Intel HDA)
alias snd-card-0 snd-hda-intel
# NXNs.HS4OKn_IlZ0:RV620 Audio device [Radeon HD 34xx Series]
alias snd-card-1 snd-hda-intel
To edit with root permissions, if using KDE, you may need to open an editor by typing “kdesu kwrite /etc/modprobe.d/sound” or if using gnome type “gnomesu gedit /etc/modprobe.d/sound file”.
Save the change, reboot your PC (to reload the new alsa sound drivers and the changed /etc/modprobe.d/sound file) , and test your sound. Pay careful attention to your mixer settings. When testing your sound, I recommend you use one of the following two sound tests (one of the two should work): open a konsole or xterm, and type (it may be easier to copy and paste this into your konsole/xterm): speaker-test -Dplug:front -c2 -l5 -twavNote Linux is case sensitive, and “D” is not the same as “d”. To stop the above test, while the konsole/xterm has the mouse focus, press <CTRL><C> on the keyboard. Note you should check your mixer settings (kmix if using KDE, and alsamixer if using Gnome) to ensure that PCM and Master Volume are set around 95% (once basic sound is established you can back off to 75% or so). Note the test for surround sound is different.
If that test yields errors, try instead this more simple test: speaker-test -c2 -l5 -twav and ideally you should hear a lady’s voice saying ‘FRONT LEFT’,‘FRONT RIGHT’ five times. Its only necessary for one of those 2 tests to work to prove you have basic sound functioning.
Dear oldcpu,
Unfortunately, what you told me to do has had no result (apparently).
Please, if you need anything more information, ask to me.
Thanks again!
I’ll likely propose a further edit to your /etc/modprobe.d/sound file. … But first, I would like to do a quality check on what you have done. Please, can you do that by running the diagnostic script again, by typing in a terminal or konsole (with your PC connected to the internet):/usr/sbin/alsa-info.shand post here the URL that you are provided. Just the URL.
Also run the following commands in a konsole and post here the output, so I can check your rpms installed and the syntax of your file edits:
rpm -qa | grep alsa
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound
The installed rpms look correct. The syntax in the /etc/modprobe.d/sound file also look correct.
Reference your mixer settings, I have one area I think you need fix (highlighted in RED BOLD, and some to consider (in ORANGE)).
!!Amixer output
!!-------------
!!-------Mixer controls for card 0 [SB]
Card hw:0 ‘SB’/‘HDA ATI SB at 0xd2400000 irq 16’
Mixer name : ‘IDT 92HD71B7X’
Simple mixer control ‘Headphone’,0
Front Left: Playback 28 [44%] -27.00dB] [on]
Front Right: Playback 28 [44%] -27.00dB] [on]
Simple mixer control ‘IEC958’,0
Mono: Playback [off]
Simple mixer control ‘IEC958 Default PCM’,0
Mono: Playback [on]
Simple mixer control ‘Speaker’,0
Front Left: Playback 32 50%] -24.00dB] [on]
Front Right: Playback 32 50%] -24.00dB] [on]Note your speaker mixer control is a 50%. Please move that up to 95% for the two speaker-tests. Also, in one place you have digital audio (iec958) OFF, and in another you have it ON. What is your intention there?
In addition to try both sound tests, as a regular user, and also with root permissions, please also test your sound with and without, your headset plugged in.
You could also try this test with enable_msi=1 not applied. After making the change, restart your alsa sound driver when testing that, by typing su -c ‘rcalsasound restart’ and enter root password when prompted. Restart your mixer.Test your sound. Check your mixer.
For your hardware audio codec, the model options are listed here for 1.0.19 of alsa from the HD-Audio-Models.txt file:
STAC92HD71B*
============
ref Reference board
dell-m4-1 Dell desktops
dell-m4-2 Dell desktops
dell-m4-3 Dell desktops
hp-m4 HP dv laptops
So in the /etc/modprobe.d/sound file, replace “hp-m4” with “dell-m4-1” and restart your alsa sound driver when testing that, by typing su -c ‘rcalsasound restart’ and enter root password when prompted and restart your mixer. Test your sound. Check your mixer.
Note to try that with and without enable_msi=1
If that does not work, try “dell-m4-2”, … then “dell-m4-3”, and also “ref” using the same method as above.
Don’t forget to listen also with your headphones plugged in and also removed.
Hi oldcpu,
Before your last post, I’ve test the sound again, and it works properly now.
I’ve rebooted my laptop before that (twice) and I don’t know what happened, but whatever it was, the problem is fixed now.
Thanks again for your willingness to help.
Regards,
Beto.
I confess I was surprised when your first assessment was it did not work the first time, as many other HP Pavilion dv5 users who I have helped found that those settings worked (update alsa and then apply the “model=hp-m4” and “enable_mis=1” ) … but when it comes to hardware, one never knows. :\
I also have a dv5-1135la with the same issue than betoceli however I’m new with Linux. I compared his alsa URL report with mine and I believe we do not share the same version of the kernel, so I’m affraid I need some assistance.
PLEASE start a new thread on this. If betocei’s problem re-appears and he resumes this thread, it will be come very confusing. I struggle when I have to bounce back and forth and back and forth in one thread between more than one, and between different users, to try figure out their different symptoms (often spread across many posts) and what they tried and did not try (also often spread across many posts). For example, typically I need the content of the /etc/modprobe.d/sound file, and you did not include that (in your case I will GUESS - I dislike guessing when not necessary ) . I don’t always recall what users tried in a thread, so I always have to re-read the post. When there are multiple problems in one post it becomes very difficult for me as I have to re-read multiple users problems to help only one user.
Fixing sound problems is already difficult enough. Please, don’t make it any more difficult for me.
But, also we do not want to waste your time. So, before you repost and start a new thread, update your alsa by opening a gnome terminal or a kde konsole and type “su” (no quotes - enter root password) to get root permissions, and with your laptop connected to the Internet send the following six zypper commands, one at a time in sequence:
zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_11.1/ multimedia
I think it is too much to open a new threat just for thank you for your help taking into account you are a kind of LINUX GOD trying to help everybody and your time is money. I realize that is easier for you if I open a new threat and I will in the future.
I think you are that kind of people that really make the difference. Thanks a lot for your help! lol!
I have almost the same laptop: “hp dv5 1120 eh”. No sound, yet.
At the part when I had to hit the “zypper install alsa-driver-kmp-pae” command into the terminal an error occured…that some packages are needed, but they can’t be installed. They are: glibc-2.9-2.10.1.x86_64[repo-update]
glibc-2.9-2.11.1.x86_64[repo-update]
And libc.so.6()(64bit) is needed by: rpm-4.4.2.3-20.3.x86_64
At the part when I had to hit the “zypper install alsa-driver-kmp-pae” command into the terminal an error occured…that some packages are needed, but they can’t be installed. They are: glibc-2.9-2.10.1.x86_64[repo-update]
glibc-2.9-2.11.1.x86_64[repo-update]
And libc.so.6()(64bit) is needed by: rpm-4.4.2.3-20.3.x86_64
PLEASE start a new thread on this. If betocei’s or jfandino’s problems re-appear and they resume this thread, it will be come very confusing. I struggle when I have to bounce back and forth and back and forth in one thread between more than one, and between different users, to try figure out their different symptoms (often spread across many posts) and what they tried and did not try (also often spread across many posts). For example, typically I need the content of the /etc/modprobe.d/sound file, and you did not include that. I also need to know what alsa rpms you have installed. You did not include that. I don’t always recall what users tried in a thread, so I always have to re-read the post. When there are multiple problems in one post it becomes very difficult for me as I have to re-read multiple users problems to help only one user.
As noted, I’m reluctant to reply because this will just confuse the entire thread.
So when you start a new thread, please provide the output of
rpm -qa | grep alsa
rpm -qa | grep pulse
uname -a
cat /etc/modprobe.d/sound
In the new thread, please also reference this error message, and provide the output of:zypper lras it appears you may have your repos setup incorrectly.
