hda intel soundcard no sound
I have an hp laptop
hp pavilion dv4-1199ef Here's the info about the sound card detected by the system Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) I can't get any sound at all. Whenever I try to listen to a sound file (*.ogg, *.mp3, *.wav) the app (any) remains silent and doesn't display any error message. I recently built linux-2.6.29.4 with the hda_intel as modules I looked at the doc in the Documentation/sound/alsa of the kernel source tree to try to find the model closest to my laptop I created a file /etc/modprobe.d/alsa-base.conf # cat /etc/modprobe.d/alsa-base.conf alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel options snd-hda-intel model=hp-m4 options snd-hda-intel enable_msi=1 (before that I had tried model=hp, but it didn't work, and in the doc I read it said hp-m4 was for the hp dv laptops) and, there's just one card # cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xdf300000 irq 11 and still no sound |
What version of slackware are you running ? I would make sure of two things: run 'alsaconf' to setup the card, and make sure '/etc/rc.d/rc.alsa' is executable.
I have a similar sound card (rev 02) and it works fine, however it's not an HP laptop. This may also help, possibly: http://www.linuxquestions.org/questi...2/#post3496597 |
vonbiber,
As you seem to know already, the key issue with the snd-hda-intel driver is to select the model=xxxx option to match your computer's audio codec. Unfortunately, I've not been able to find the exact part number of the audio codec used in your hp pavilion dv4-1199ef computer. It's referred to as an "IDT High Definition Audio Codec", but that didn't seem to help me find an appropriate model option for the snd-hda-intel driver. As a practical workaround, you can use USB speakers or headphones for audio. If you choose to do this, it will simplify the ALSA configuration issues with multiple sound devices if you either disable your onboard audio card in the BIOS settings, or blacklist the snd-hda-intel driver. |
Quote:
/etc/rc.d/rc.alsa is executable I even built on another partition (still slackware12.2) linux-2.6.29.4 and checked all these things above. I downloaded archives from the alsa web site (latest version 1.0.20) to look at it. Didn't build the packages. Looking at the docs in alsa-driver archive I noticed there were more models than in the corresponding doc in Documentation/sound/alsa of the kernel source tree There's for instance 'hp-dv5' which could include the dv4 series I didn't try to update my version of alsa (1.0.17) because there might be side effects Hopefully, there's gonna be a fix in a future version of the kernel (perhaps in linux-2.6.30) so I'll keep building new kernels |
Quote:
the docs in the kernel source tree I noticed that in the alsa-driver package there were more models including 'hp-dv5' which could fit the dv4 series as well perhaps it's gonna be included in a future kernel release I had tried the headphones but I didn't disable the audio card I might try that as a last resort |
Did You try to unmute Your sound card channels? By default, all channels are muted and You need to use alsamixer, or any other mixer software to setup the channels responsible for playing what You need, especially PCM (or Master) volume. Try also to setup the volume for front/rear and side channels, or surround channel.
Regards ;) |
Quote:
be set are around 70 one thing that I don't understand is # cat /proc/asound/cards |tail -n2 shows '... irq 11' on my installed slackware while the same command in 2 live linux that I use (slax and grml) shows a different irq value (irq 22) sound doesn't work on these either but in slax this # cd /usr/share/sounds; aplay -vv pop.wav does produce a sound (not grml or slackware) |
Quote:
Quote:
I'm using currently ALSA 1.0.20 with Linux 2.6.29.4 kernel and there is no troubles with the sound, but I use nForce HD-Audio codec... |
Quote:
# alsamixer set PCM to 100%, then # alsactl store I'll seet what happens when I reboot 2. alsa-lib-1.0.17a alsa-oss-1.0.17 alsa-utils-1.0.17 on the partition I'm using right now linux-2.6.29.3 on another partition, same alsa and linux-2.6.29.4 I haven't tried yet to build newer alsa packages (slackware) then replace the current ones because I'm afraid there might be side effects (other packages involved) |
Well, I always try to use newest software and if the software is marked as stable, there is no side efects... Especially with drivers :) Newest driver provide more compatibility...
As for the ALSA software, check alsa-driver first: here is ./configure --help output: Code:
root@service1:/tmp/alsa/alsa-driver-1.0.20# ./configure --help |
[QUOTE=Martinezio;3561606]Well, I always try to use newest software and if the software is marked as stable, there is no side efects... Especially with drivers :) Newest driver provide more compatibility...
As for the ALSA software, check alsa-driver first: here is ./configure --help output: Code:
root@service1:/tmp/alsa/alsa-driver-1.0.20# ./configure --help grep alsa /mnt/dvd/source/FILE_LIST showed the presence of alsa in 4 packages alsa-lib alsa-oss alsa-utils aumix somewhere in there I saw some diff files I don't know if I can figure out the diff part while writing SlackBuild scripts for the newer versions of alsa Besides I didn't see alsa-driver in the slackware packages (I suppose the one used was the one that came with the kernel sources) I might give it a try. I have another partition that I just use for testing. Or wait for eventually there's gonna be a kernel release where this is going to be fixed I already have all the codecs shown above built in the kernel |
Yes, I know, that this package isn't available on Slackware installation disc. This is part of the kernel, but I don't know, what version of alsa-driver is currently joined in linux-2.6.29.4. Before building those drivers from source available at www.alsa-project.org You must have properly configured Your kernel's source in /usr/src/linux folder - build process first jumps into this source, and then build drivers in src of alsa-driver using dynamic path.
Give it a shot in a test environment and see, if this helps You ;) I think, You have nothing to loose :> Regards :) |
All times are GMT -5. The time now is 10:52 AM. |