Compaq Presario v6030
Fedora Core 6 x86_64

The story:
FC6 comes with Alsa-1.0.12. After much fiddling around, I finally managed to get both my headphones and mic working with Alsa 1.0.13 by adding the following "disable_msi=1" in the modprobe.conf

options snd-hda-intel index=0 disable_msi=1

This gave me seperate controls for my mic/headphone jack, and although a minor annoyance that I had seperate controls, all was fine and dandy... until...

Now I've upgraded my kernel and find that there is no alsa-kmdl 1.0.13 for the latest kernel. There is only a 1.0.14. Having previous problems with 1.0.14 I've dreaded this for a while, but I installed it and booted the machine. Now here's the problem:

Without the "disable_msi=1":
Headphone jack works as it's supposed to, but no matter how I fiddle with the mic/capture, I can't get it to record any sound.

With the "disable_msi=1":
I get some fatal error on start up that flies by too quickly for me to be able to tell what it is.

I don't know what they changed, but now I'm basically stuck without a Mic. Here are my files:

alsa-driver.x86_64 1.0.14-57_rc2.fc6.at installed
alsa-kmdl-2.6.19-1.2895.fc6.x86_64 1.0.14-57_rc2.fc6.at installed
alsa-lib.i386 1.0.14-0.2.rc2.fc7 installed
alsa-lib.x86_64 1.0.14-0.2.rc2.fc7 installed
alsa-lib-devel.x86_64 1.0.14-0.2.rc2.fc7 installed
alsa-oss.i386 1.0.12-3.fc6 installed
alsa-utils.x86_64 1.0.14-0.3.rc2.fc7 installed

Anyone have any ideas?
(The alsa-oss i386 is not a mistake. This is so that i can run 32-bit apps (TeamSpeak) that only have oss).

Using 64-bit libraries with 32-bit programs will create some problems. Also mixing 32-bit and 64-bit libraries will create even more problems. Either use 32-bit libraries and modules (drivers) or forget using TeamSpeak and use 64-bit.

I recommend using 64-bit OS only when the system is going to process multimedia files. If it is not, a 32-bit OS should be used to be compatible with majority of programs.

Do you have the alsaconf file installed ? It will setup your sound card(chip) then use alsamixer to turn on and set your microphone.
Scott

Been about a week, but time to sit down and get this working. There is no alsaconf for Fedora. Fedora comes only with system-config-soundcard. I considered grabbing it and manually compiling it, but didn't know if it would make a diff. Basically, I have mic controls, but there is no mic. It might be due to poor redirection to the mic plug and perhaps is only using my onboard one?

1.0.13:
Seperate Controls for each plug using msi_disable=1
Mute actually worked.

1.0.14:
1 control for mic, 1 control for speaker.
Plugging in headphones redirects speaker to headphones.
Mute *ONLY* works when headphones are plugged in, has no effect to onboard speaker.
Mic does not work at all. Perhaps unplugging it and yelling into my screen (where the interal mic is located) might have more effect.

Out of curiousity, which file is it that controls how the hardware works, is it the "kmdl" file, or the "driver" file. I will have to play around with whichever it is to find the workaround for the HP/Compaq issue.

And another question to follow that up. If it is the "driver" is it possible to have the 1.0.14 kmdl with the 1.0.13 driver? Obviously something in 1.0.13 worked and I would *LOVE* to go back to it.

Ok, I tried to install the 1.0.13 driver with the 1.0.14 kmdl and there were dependency errors. I could have tried to do a --force, but chose not to screw up my system farther. I also found out that there is no "disable_msi" option with 1.0.14 as they turned it off by default and added an "enable_msi" option. What has this left me with?

1) 1.0.14rc2 does not work on a compaq 6030 (and possibly other HP brands with nvidia chipsets)
2) In order to get working microphone/headphone support (yes, you *could* get a somewhat working headphone with just 1.0.14rc2) you must roll back to the 2.6.18 kernel so you can use the 1.0.13 kmdl. Also, you need to have "disable_msi=1" to make this work with this hardware.

It's sad that they forced an RC with a kernel upgrade, but they did, and now I can not use the new kernel because of it.

If you did not include ALSA in the kernel which is actually a waste of compile time, ALSA version 1.0.13 should work with the latest kernel version. ALSA version 1.0.14 right now is an experimental release, so it may or may not work. I normally do not include either OSS and ALSA for the kernel, but I do include sound core which is require for both OSS and ALSA. This gives me a choice to use either OSS or ALSA and upgrade either of them when I need to, but I have to do it because ALSA ebuild file in Gentoo requires me to not include either OSS and ALSA in the kernel.

If you want to use Linux with out any trouble, build your own computer. Compaq/HP, Dell, Gateway makes their computers, so they may not work as expected because of proprietary software that they wrote in the BIOS or for Windows.

I still don't recompile my kernel for optimization due to the fact that in the old days this seemed to break my system every single time (in fact, I don't think I ever got a custom compiled kernel working). I use Fedora with Kernel Modules. In theory, if there *WAS* a 1.0.13 module for my kernel (the 2.6.19) then there would be no issue and this would work. However, it doesn't exist. Fedora does not supply a 2.6.19 kmdl for alsa 1.0.13. (I don't know how or why these integrate, which is why not having any provided pretty much stops me). This means, either fedora has to provide an "alsa-kmdl-2.6.19-1.2895.fc6-1.0.13.x86_64.rpm" *OR* they have to fix the 1.0.14 version to work with my hardware.

Post for no 1.0.13: http://lists.atrpms.net/pipermail/at...ry/006708.html

As for the hardware in question, it's a laptop. This limits me in what I can "customize". A lot of people in my situation have bought a pcmcia sb card, but I'm still holding out that the built in one will work... and it does with 1.0.13. Which is why I'm quite shocked at the big leap backwards with 1.0.14.

I think you need to learn how to configure, compile, and install the kernel. It is not hard. Then your troubles will go away or be minimized. I suggest trying Gentoo to know more about Linux.

I do not compile the kernel to optimize it. I compile it because I have to and it provides freedom.

I recently posted steps to configure, compile, and install the kernel. I also include additional steps to create an initrd file that includes require modules if need to. Go to http://www.linuxquestions.org/questi...d.php?t=525628 and scroll to the bottom.