NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio
New Posts  All Forums:Forum Nav:

Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio - Page 2

post #21 of 35
11/18/05 at 11:18am
The alsa-libs package is used by most things to access the alsa drivers I believe, an API for programs to access so yes you do need to load it.

Sorry my best guess without being at your computer right now is that your /dev/ entry isnt being created correctly for some reason, make sure you have everything you need from alsa and check your /dev/snd directory to make sure there are things in there.

Also go through your /proc/asound directory and check things in it, meaning for example make sure you check /proc/asound/modules and make sure you are trying to access the right card number, make sure your card is in there and the like. Other than that I think I would have to be there, sorry.

Seablade
Reply
Reply
post #22 of 35
11/18/05 at 11:35am
Thread Starter 
Quote:
Originally Posted by seablade
The alsa-libs package is used by most things to access the alsa drivers I believe, an API for programs to access so yes you do need to load it.

That was my understanding as well.

Quote:
Sorry my best guess without being at your computer right now is that your /dev/ entry isnt being created correctly for some reason, make sure you have everything you need from alsa and check your /dev/snd directory to make sure there are things in there.

At one point, I thought I'd hit it when I ran snddevices and a long list of things was created. Here's what I have now, opinions sought:

Code:
$ ls
controlC0  hwC2D3    midiC1D2  midiC3D1  pcmC0D4c  pcmC1D3p  pcmC2D3c  pcmC3D2p
controlC1  hwC3D0    midiC1D3  midiC3D2  pcmC0D4p  pcmC1D4c  pcmC2D3p  pcmC3D3c
controlC2  hwC3D1    midiC1D4  midiC3D3  pcmC0D5c  pcmC1D4p  pcmC2D4c  pcmC3D3p
controlC3  hwC3D2    midiC1D5  midiC3D4  pcmC0D5p  pcmC1D5c  pcmC2D4p  pcmC3D4c
hwC0D0     hwC3D3    midiC1D6  midiC3D5  pcmC0D6c  pcmC1D5p  pcmC2D5c  pcmC3D4p
hwC0D1     midiC0D0  midiC1D7  midiC3D6  pcmC0D6p  pcmC1D6c  pcmC2D5p  pcmC3D5c
hwC0D2     midiC0D1  midiC2D0  midiC3D7  pcmC0D7c  pcmC1D6p  pcmC2D6c  pcmC3D5p
hwC0D3     midiC0D2  midiC2D1  pcmC0D0c  pcmC0D7p  pcmC1D7c  pcmC2D6p  pcmC3D6c
hwC1D0     midiC0D3  midiC2D2  pcmC0D0p  pcmC1D0c  pcmC1D7p  pcmC2D7c  pcmC3D6p
hwC1D1     midiC0D4  midiC2D3  pcmC0D1c  pcmC1D0p  pcmC2D0c  pcmC2D7p  pcmC3D7c
hwC1D2     midiC0D5  midiC2D4  pcmC0D1p  pcmC1D1c  pcmC2D0p  pcmC3D0c  pcmC3D7p
hwC1D3     midiC0D6  midiC2D5  pcmC0D2c  pcmC1D1p  pcmC2D1c  pcmC3D0p  seq
hwC2D0     midiC0D7  midiC2D6  pcmC0D2p  pcmC1D2c  pcmC2D1p  pcmC3D1c  timer
hwC2D1     midiC1D0  midiC2D7  pcmC0D3c  pcmC1D2p  pcmC2D2c  pcmC3D1p
hwC2D2     midiC1D1  midiC3D0  pcmC0D3p  pcmC1D3c  pcmC2D2p  pcmC3D2c

They're all 666, so I don't think there's a permissions thing. Oh, and:
Code:
$ ls -l dsp*
lrwxrwxrwx  1 root root      4 Nov 18 09:25 dsp -> dsp0
crw-rw-rw-  1 root root 14,  3 Nov 18 09:24 dsp0
crw-rw-rw-  1 root root 14, 19 Nov 18 09:24 dsp1
crw-rw-rw-  1 root root 14, 35 Nov 18 09:24 dsp2
crw-rw-rw-  1 root root 14, 51 Nov 18 09:24 dsp3

Quote:
Also go through your /proc/asound directory and check things in it, meaning for example make sure you check /proc/asound/modules and make sure you are trying to access the right card number, make sure your card is in there and the like.

I'm not sure exactly what to look for, but things look OK.
Code:
$ ls -l
total 1
dr-xr-xr-x  5 root root 0 Nov 18 09:30 card0/
-r--r--r--  1 root root 0 Nov 18 09:30 cards
-r--r--r--  1 root root 0 Nov 18 09:30 devices
lrwxrwxrwx  1 root root 5 Nov 18 09:30 Intel -> card0/
-r--r--r--  1 root root 0 Nov 18 09:30 modules
dr-xr-xr-x  2 root root 0 Nov 18 09:30 oss/
-r--r--r--  1 root root 0 Nov 18 09:30 pcm
dr-xr-xr-x  2 root root 0 Nov 18 09:30 seq/
-r--r--r--  1 root root 0 Nov 18 09:30 timers
-r--r--r--  1 root root 0 Nov 18 09:30 version

And:

Code:
$ cat cards
0 [Intel          ]: HDA-Intel - HDA Intel
                     HDA Intel at 0x80000000 irq 11

$ cat devices
  1:       : sequencer
 17: [0- 1]: digital audio playback
 16: [0- 0]: digital audio playback
 24: [0- 0]: digital audio capture
  0: [0- 0]: ctl
 33:       : timer

$ cat modules
0 snd_hda_intel

$ cat pcm
00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 2
00-01: ALC880 Digital : ALC880 Digital : playback 1

$ cat timers
G0: system timer : 4000.000us (10000000 ticks)
P0-0-0: PCM playback 0-0-0 : SLAVE
P0-0-1: PCM capture 0-0-1 : SLAVE
P0-0-3: PCM capture 0-0-3 : SLAVE
P0-1-0: PCM playback 0-1-0 : SLAVE

$ cat version
Advanced Linux Sound Architecture Driver Version 1.0.10.
Compiled on Nov 16 2005 for kernel 2.6.13-1.1532_FC4.

I am glad to provide any more info.

Quote:
Other than that I think I would have to be there, sorry.

Hey, 5 mins of work gets you a temporary ssh connection to my machine. If you're willing, I'm able [chip@pcc.com].

Thanks!
Reply
Reply
post #23 of 35
11/18/05 at 7:02pm
Thread Starter 
I THINK I MAY JUMP INTO THE RIVER.

I can't get this to work. I almost beginning to wonder if I have a hardware problem (I'll have to break down and throw XP on or something).

I was so desperate, I tried loading the oss package (from opensound.com). It made my speakers crackle, but that's it. I removed it all.

I tried to clean up everything I could think of - stripped modprobe.conf, uninstalled every rpm and compiled program I could find.

I then re-installed the latest alsa drivers from scratch (1.0.10). At the end, you are supposed to run alsaconf. Here's what happens:

Code:
Loading driver...
Starting sound driver: snd-hda-intel done
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #1 (Invalid argument)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #3 (Invalid argument)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #5 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #6 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #7 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #8 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #15 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #16 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #17 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #18 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #19 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #20 (No such file or directory)
/usr/sbin/alsactl: set_control:873: failed to obtain info for control #27 (No such file or directory)
Setting default volumes...

===============================================================================

 Now ALSA is ready to use.
 For adjustment of volumes, use your favorite mixer.

 Have a lot of fun!


# alsamixer

alsamixer: function snd_mixer_load failed: Invalid argument

...right where I was when I began. Still, no sound.

BTW, google turns up nothing for those errors above.

Can anyone help me?

Thanks.
Reply
Reply
post #24 of 35
11/19/05 at 2:54pm
Quote:
Originally Posted by seablade
The alsa-libs package is used by most things to access the alsa drivers I believe, an API for programs to access so yes you do need to load it.
Seablade
In Gentoo the libs package is not needed. I can't imagine why it should be for anyone really. All of the code required to compile and load the driver (in kernel or as a module) should be included in the kernel sources. The kernel provides the API for the ALSA driver. I currently have ALSA compiled into my kernel, sound works in KDE, and I'm not using any ALSA packages at all. If indeed it is necessary to have the libs installed separately for a system using ALSA provided by the kernel, then it seems to me that this is a proprietary (and strange) requirement.
Reply
Reply
post #25 of 35
11/19/05 at 2:59pm
Quote:
Originally Posted by chiphart
I THINK I MAY JUMP INTO THE RIVER.

I can't get this to work. I almost beginning to wonder if I have a hardware problem (I'll have to break down and throw XP on or something).

Thanks.
Before you buy XP, d/l the latest Knoppix, that should confirm whether or not Linux will work on your machine. In fact, Knoppix might find hardware on your machine you wouldn't have expected to be able to use.
Reply
Reply
post #26 of 35
11/20/05 at 12:32am
Thread Starter 
Quote:
Originally Posted by Starcub
Before you buy XP, d/l the latest Knoppix, that should confirm whether or not Linux will work on your machine. In fact, Knoppix might find hardware on your machine you wouldn't have expected to be able to use.

...well, naturally. My XP comment was more of a threat :-)

I spent some time working with everyone's favorite distro, Ubuntu, and kept running into the hotplug/pcmcia lockup brick wall that others have (Torbo in this thread, iirc). You know, for all the grief RH/Fedora get, I've never had problems until this machine and I've loaded on all kinds of desktops and laptops.

Anyway, back to the point.

I have booted into Knoppix 4.0 [which, btw, is always so cool] and I still have NO SOUND. I do not get the alsa errors when trying to run kmix that I get elsewhere ("alsamixer: function snd_mixer_load failed: Invalid argument") and running xmms makes it look like it should work - just silence.

Yes, I ran alsamixer AND kmix and made sure everything is jacked way up. There's not some mysterious volume control on the front of this thing (like on the CD section) that could affect all this is there?

A brief examination implies that all the configuration files are more-or-less identical (couldn't see anything different). The ONLY thing I see different is in dmesg:
Code:
hda_codec: no AFG node found

I am hoping this lends a clue. I still welcome any comments pointing out my stupidity. At this point, I AM tempted to load XP just to make sure the speakers are working! I'll try a CD, actually.

Thanks.
Reply
Reply
post #27 of 35
11/20/05 at 1:19am
Thread Starter 

Success! Finally!

I GOT IT.

First, if you're looking for answers to ALSA questions, it turns out that using the ALSA bug tracking page is a good source - the search feature was very helpful. (https://bugtrack.alsa-project.org/al...login_page.php)

Second, the answer. Something so simple, so easy.

I decided to read the documentation (alsa-driver-1.0.10/alsa-kernel/Documentation/ALSA-Configuration). In the section for snd_hda_intel, there's a piece about forcing your model into the option line. Although I haven't tested it thoroughly (i.e., does the surround actually work), everything seems hunky-dory.

Thanks for all the help.

Oh, wait, the magic line in modprobe.conf:

Code:
options snd-hda-intel model=3stack
Reply
Reply
post #28 of 35
11/20/05 at 11:14am
Chipart,

I have tested a few different versions of knoppix (I thought I had the latest too), but none worled for me . I'll hafta look for this magic 4.0... I love knoppix it has gotten me outa a few jams in the past. I think I posted how I got Ubuntu to run didn't I? If not let me basically say that for the first run after install you'll need to disable the sound in the bios, then get into it and blacklist the snd_hda_intel driver in the hot plug. seems it locks up the hot plug boot up. once its blacklisted your good to go. Of course I think this basically keeps my sound from working, so to fix that I'll need to do more ground work.
Reply
Reply
post #29 of 35
11/20/05 at 11:22am
Quote:
Originally Posted by chiphart
Oh, wait, the magic line in modprobe.conf:

Code:
options snd-hda-intel model=3stack

Ugh, this makes the module extremely difficult to use. No doubt this will stymie many people. I hope they fix this in future releases. Grats on getting it to work though, you sure tried hard enough ;-).
Reply
Reply
post #30 of 35
11/20/05 at 2:42pm
Congrats on getting it to work.

To answer something else real quick...

Quote:
In Gentoo the libs package is not needed. I can't imagine why it should be for anyone really. All of the code required to compile and load the driver (in kernel or as a module) should be included in the kernel sources. The kernel provides the API for the ALSA driver. I currently have ALSA compiled into my kernel, sound works in KDE, and I'm not using any ALSA packages at all. If indeed it is necessary to have the libs installed separately for a system using ALSA provided by the kernel, then it seems to me that this is a proprietary (and strange) requirement.
You are probably using the Arts daemon in KDE then, not running directly to ALSA which is why your alsa-lib may not be needed. This is just a guess mind you as I dont use Arts as it is not a good idea for me since I do Audio work.

However running software that is designed to use the Alsa libs to interface directly with Alsa that doesnt have the option to use Arts will most likely require the Alsa Libs I believe. And yes there is a good amount of this out there, especially when you get to audio editing software.

Seablade
Reply
Reply
post #31 of 35
11/20/05 at 10:35pm
I'm guessing that you have special requirements that are not met with the in kernel driver. Let me guess... you use the alsa provided packages instead of the included kernel driver? The Gentoo ALSA guide does not assume the use of any particular window manager. Since the Gentoo ALSA guide does not in any place specify that the libs package need be installed, I would expect basic sound services be available using only the in kernel ALSA driver.
Reply
Reply
post #32 of 35
11/21/05 at 12:01am

Possible solution

Having just recently gone through this with my Sager 9860 with Slackware, here's what was tripping me up and what the absurdly simple solution was.

First, I turned off all the kernel-side stuff and made sound support a module. Then I removed all the Alsa packages which came with the distro CD and installed the latest from the Alsa site. Built according to instructions. Doing modprobe of the snd-hda-intel puts all the modules in.

This is where I was stuck: Everything is in the right place in the right way, but no sound. I was getting the no _mixer_ error thingy when trying to get alsamixer to run to turn on the sound.

Solution: Seems one must first run alsactl which returns an errors saying something like "no current state." Use the command "alsactl store" then try to run alsamixer and VOILA, get a mixer, turn on sound and works really nice!

Seems the alsamixer doesn't have any settings to load unless alsactl has run and stored at least once, which also makes the asound.state file in the /etc directory.

Hope this helps you out some. I know I was getting rather frustrated with the whole thing, yikes!

Cheers
Reply
Reply
post #33 of 35
11/21/05 at 12:44am
Quote:
Originally Posted by Starcub
I'm guessing that you have special requirements that are not met with the in kernel driver. Let me guess... you use the alsa provided packages instead of the included kernel driver? The Gentoo ALSA guide does not assume the use of any particular window manager. Since the Gentoo ALSA guide does not in any place specify that the libs package need be installed, I would expect basic sound services be available using only the in kernel ALSA driver.

You would be correct in that I use the packages and not the kernel provided driver. That is the most likely difference there, or at least one of them, another being that you use Arts while I dont. There are others having to deal with specificly how I deal with my audio, so those dont really apply here.

However here is something for reference, I pulled off the agnula documentation...

Quote:
ALSA is an acronym for the Advanced Linux Sound Architecture. The name is most usually encountered when discussing soundcard drivers, but ALSA is much more than a mere collection of modules. The main page at the project's Web site informs us that ALSA's primary characteristics include support for audio and MIDI hardware ranging from consumer-grade to professional-quality, fully modularized drivers for that hardware, a multiprocessor-friendly and thread-safe design, an API (applications programming interface) and a user-space library (libasound) for programmers who want to access the properties and capabilities of the sound system, and full OSS/Free compatibility (OSS/Free is the previous kernel sound system API) for running Linux audio applications that do not explicitly support ALSA. And of course ALSA is completely free and open-source software licensed under the GPL.
Specificly note the line about libasound, and it being an api for programmers to use. This would make it a requirement for any software using it to access alsa in order for it to have sound.

You are correct in that it shoudl be possible to have sound in some circumstances without the lib, but those would be overall not very common and having the lib installed is reccomended by me to avoid confusion when you do hit packages that use it.

Also in the Gentoo Alsa docs you are correct in the alsa-lib is not specified, however alsa-utils I believe are, and I THINK are dependant on alsa-lib, though I cant check right off hand. In which case if they SHOULD automatically install when you emerge alsa-utils. I could be wrong on this, but I think that is what happens, or at least should happen.

Seablade
Reply
Reply
post #34 of 35
11/21/05 at 12:12pm
Thread Starter 

Quick Update

After playing around with things a little bit, let me amend my magic command:

Code:
options snd-hda-intel model=3stack-digout position_fix=2

Thanks again for all the help!
Reply
Reply
post #35 of 35
1/12/06 at 11:14am
Hello You all,

Please dont call me stupid, but i just bought a Promedion M570B which is basicly a Sager 5710. And i have the same problem you all descibed with Kubuntu 5.10 Hoary Hedgehog.
Installation went well but it hang during the bootup.
I disabled de soundcard in the bios and all booted well but of coarse there is no sound.

Can you give me a short explaination what you did to get things working. because I heard so much different things I am completly lost.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux & Other OS's
NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio