Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Having problems getting sound to work with Asus P5LD2-SE HDA-Intel, ADI1986A 6-channel CODEC setup.
I had the problem when I first tried Ubuntu and now have it with Sabayon.
On Ubuntu the sound only worked at all every few boots.
On Sabayon it works to some extent every boot, but before I play anything I have to run alsaconf.
When something is playing if I touch the volume control either on the application or the Gnome panel volume control or the volume control panel the sound vanishes and I'm back to re-running aslaconf.
When it does play, the sound only comes from the right speaker - crystal clear, not particularly high volume (compared to my other computer with AC'97 also running Sabayon where sound is as expected).
A high-pitched sound in the left speaker was fixed by adding:
options snd-hda-intel position_fix=1 model=3stack
to /etc/modules.conf
Kernel: 2.16.18-r2
ALSA: 1.0.13
If I could just find out why the sound vanishes when I try to adjust the level, maybe I will be on the way to finding out how the sound is controlled and a solution also for the one-channel problem I have.
Most grateful if anyone could throw any light on the situation.
At first glance, I can't tell if your particular board is directy supported by the alsa driver. The Codec is supported, quite well in fact (I have the same codec in my Asus Z62F Laptop). What is the subsystem id of the sound device? You can get this with 'lspci -s 0:1b -vn'.
Also, until this system gets added in, try adding "model=6stack to your /etc/modprobe.conf file. To test if this works, you can try unloading the snd-hda-intel driver, then reloading it with "modprobe snd-hda-intel model=6stack".
Also, what version of alsa-driver is it? Try 'cat/proc/asound/version' to find out.
do seem to have the sound working with this motherboard.
# lspci -s 0:1b -vn
00:1b.0 0403: 8086:27d8 (rev 01)
Subsystem: 1043:817f
Flags: bus master, fast devsel, latency 0, IRQ 66
Memory at bdcf8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable+
Capabilities: [70] Express Unknown type IRQ 0
I have model=3stack in my /etc/modules.conf file and had also tried model=6stack and a couple of other values there before posting here. I'm not sure I understand what you mean by "unloading the snd-hda-intel driver".
Upgrading from the 2.6.17 with the built-in ALSA 1.0.12 drivers to 2.6.18 (which I also need to do to get my onboard NIC to work) I deselected ALSA so that it compiled without it. I then emerged alsa-driver 1.0.13.
I also tried uninstalling the ebuild alsa-driver, downloading ALSA 1.0.10 directly from the ALSA site, applying the patch at:
However I got a compilation error with "make" failing.
I suppose I could try putting the patch in the ALSA site 1.0.13 and trying again but I'm not too hopeful and I'm not sure I know how to uninstall if it is not successful and I want to install ALSA 1.0.14 some time in the future.
Hence currently:
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.13.
Compiled on Nov 11 2006 for kernel 2.6.18-gentoo-r2 (SMP).
I have the same motherboard model and my sound on Suse 10.2 works only with the model=3stack option, eventhough the motherboard specifications are:
...
Audio
ADI1986A 6-ch Audio CODEC
Jack Sensing and Enumeration
S/PDIF out interface
...
which means that the "model" option must be set to "6stack" = no success to me.
My sound is working perfectly in ALL applications but my microphone is totally out to again ALL applications i am trying to use. In skype (skype test call) when i try to hear my voice back i maxed up the volume and hear br-brbr-br-br-br-br-br-br-br-br-br-br as it is very very far and it is very quiet also. It records something for sure but does output it back. F**k.
The headphones with integrated mic I use are working perfectly on Windows 2003 Server Enterprise.
I changed them and... viola!! Mic is working but only when plugged on the back. That I know - 3stack means 3 channels and the front 2 aren`t available softwarely.
I tried Suse 10.0, 10.1, 10.2, Fedora 5, Fedora 6 Zod, Ubuntu 6.10 all these with both Gnome and KDE and absolutely the same effect.
I installed Fedora Core 6 about two months ago and after setting model=3stack my sound worked perfectly. I don't use a microphone input so afraid I can't comment on that.
I have the same motherboard model and my sound on Suse 10.2 works only with the model=3stack option, eventhough the motherboard specifications are:
...
Audio
ADI1986A 6-ch Audio CODEC
Jack Sensing and Enumeration
S/PDIF out interface
...
which means that the "model" option must be set to "6stack" = no success to me.
That I know - 3stack means 3 channels and the front 2 aren`t available softwarely.
Actually, 3-stack & 6-stack refers to the number of audio plugs on the back of the motherboard, not the number of channels. A 6 stack board usually has one port for each function (Front, Rear, Center/LFE, Line-in/Side out, Mic, S/PDIF), whereas a 3-stack board has 3 plugs that are function sharing (Front, Rear/Mic, Center/LFE/Line-in).
If you have a board with 3 plugs, and you load with model=6-stack, most of the plugs will be incorrectly mapped.
Actually, 3-stack & 6-stack refers to the number of audio plugs on the back of the motherboard, not the number of channels. A 6 stack board usually has one port for each function (Front, Rear, Center/LFE, Line-in/Side out, Mic, S/PDIF), whereas a 3-stack board has 3 plugs that are function sharing (Front, Rear/Mic, Center/LFE/Line-in).
If you have a board with 3 plugs, and you load with model=6-stack, most of the plugs will be incorrectly mapped.
Ok, so that is why it does not work on 6stack, but in /alsa-driver-1.0.13/alsa-kernel/Documentation/ALSA-Configuration.txt is written:
...
Module snd-hda-intel
--------------------
Module for Intel HD Audio (ICH6, ICH6M, ESB2, ICH7, ICH8),
ATI SB450, SB600, RS600,
VIA VT8251/VT8237A,
SIS966, ULI M5461
model - force the model name
position_fix - Fix DMA pointer (0 = auto, 1 = none, 2 = POSBUF, 3 = FIFO size)
single_cmd - Use single immediate commands to communicate with
codecs (for debugging only)
disable_msi - Disable Message Signaled Interrupt (MSI)
This module supports one card and autoprobe.
Each codec may have a model table for different configurations.
If your machine isn't listed there, the default (usually minimal)
configuration is set up. You can pass "model=<name>" option to
specify a certain model in such a case. There are different
models depending on the codec chip.
...
...
AD1986A
6stack 6-jack, separate surrounds (default)
3stack 3-stack, shared surrounds
laptop 2-channel only (FSC V2060, Samsung M50)
laptop-eapd 2-channel with EAPD (Samsung R65, ASUS A6J)
...
,which is my model by specifications - the default is 6stack.
???
What tha **** does this mean? By default my sound card will not work, actually it wasn`t till i changed to 3stack...
As I said earlier, your board is a 3-stack audio board (even according to the manual, which I'm reading now). If a board's subsystem ID (in your case 1043:817f) is not recognized, the driver will use the default settings (6-stack for the AD1986A codec). Your subsystem ID was added after alsa 1.0.13 was released, and it is listed there as a 3-stack system. If you would like, download alsa-driver-1.0.14rc2 from alsa-project.org.
As I said earlier, your board is a 3-stack audio board (even according to the manual, which I'm reading now). If a board's subsystem ID (in your case 1043:817f) is not recognized, the driver will use the default settings (6-stack for the AD1986A codec). Your subsystem ID was added after alsa 1.0.13 was released, and it is listed there as a 3-stack system. If you would like, download alsa-driver-1.0.14rc2 from alsa-project.org.
Tobin
I have 3 "holes" on the back of my mboard which means that I had to set it to 3stack and it is the right option. Or?
What means that "(in your case 1043:817f)" and where is this written? How can I recognize my board subsystem ID? And where in the alsa drivers are given the available IDs?
Beside that i could never manage to "replace" any driver in linux when installing the new driver from source... I just do not know the right order of things to do to replace from 1.0.13 to 1.0.14rc2...
I have 3 "holes" on the back of my mboard which means that I had to set it to 3stack and it is the right option. Or?
yes, that is the deffinition of a "3-stack" audio. There are 3 stereo jacks stacked one on top of the other on the motherboard (if you were to lay the motherboard flat).
Quote:
What means that "(in your case 1043:817f)" and where is this written? How can I recognize my board subsystem ID? And where in the alsa drivers are given the available IDs?
This is from the output of lspci -s 0:1b -vn from an earlier post by r-t. You stated that you had the same motherboard. If lspci -s 0:1b -vn produces a different value for Subsystem, let me know.
Quote:
Beside that i could never manage to "replace" any driver in linux when installing the new driver from source... I just do not know the right order of things to do to replace from 1.0.13 to 1.0.14rc2...
Why not? It's not rocket science. Just go to alsa-project.org, download the alsa-driver-1.0.14rc2.tar.bz2 file to a directory you can work in, then follow these simple instructions:
First, make sure you have the kernel source for the kernel you are running. Check your package manager utility. You will also need to install gcc, which is the compiler used to build the kernel and drivers.
cd <work directory> # where <work directory> is where you downloaded the file to
tar -jxvf alsa-driver-1.0.14rc2.tar.bz2
cd alsa-driver-1.0.14rc2
./configure
make
That will build the drivers. Next, close all audio programs, sound mixers, etc., and login as root. Type "su" and enter the root password, then type:
make install
modprobe -r snd-hda-intel
lsmod | fgrep snd
If the last command above returns a list of snd_ modules, unload them by typing "rmmod <module name>" (where <module name will be in the first column). Now you can load the new drivers:
modprobe snd-hda-intel
And that is it. To verify that it installed and loaded correctly, type "cat /proc/asound/version".
If you still need help, send me an email. I have an rpm package that can be rebuild for suse.
drop:~ # lspci -s 0:1b -vn
00:1b.0 Class 0403: 8086:27d8 (rev 01)
Subsystem: 1043:817f
Flags: bus master, fast devsel, latency 0, IRQ 177
Memory at dfdf8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Unknown type IRQ 0
....
That is the output.
Thanks for the instructions...
The things to do that I did not know are:
Quote:
Originally Posted by GrueMaster
modprobe -r snd-hda-intel
lsmod | fgrep snd
If the last command above returns a list of snd_ modules, unload them by typing "rmmod <module name>" (where <module name will be in the first column). Now you can load the new drivers:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.