LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-02-2006, 07:06 AM   #1
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Rep: Reputation: 39
can not get sound to work, nor alsa mixer... on a CMedia on board chip


Hello everyone,
i have slackware 10.2 and at this point i have twice installed it in different computers (a very old pII and a rather speedy p5 (so to speak) at 3GHz... completely different systems, yet with the basic kernel 2.4.31 the sound is non existent... and i have made my own kernels too based on the 2.6.17.3 version...
i have gone Very thoroughly through the options to make sure i haven't forgot to add STRAIGHT to the kernel (no modules) all the bits of the kernel that are sound related... ie anything that is alsa and oss related (even though i don't exactly know, is alsa basically the next step after oss or am i wrong?
anyhow all these options (ask me for a hard copy of the config file ifyou need it ) i have included..
if i try to play an mp3 with mpg321 i get:

Code:
ALSA lib confmisc.c:560:(snd_determine_driver) could not open control for card 0
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_card_driver returned error: Permission denied
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_concat returned error: Permission denied
ALSA lib confmisc.c:955:(snd_func_refer) error evaluating name
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_refer returned error: Permission denied
ALSA lib conf.c:3948:(snd_config_expand) Evaluate error: Permission denied
ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
No default libao driver available.
if i do 'alsamixer' i get

alsamixer: function snd_ctl_open failed for default: No such device

I really don't know where to start from to fix things.

I have the onboard sound card of Asus - P5GD2 motherboard.. its a C-Media chip..

when i do 'lspci' i get the following concerning the audio controller:
00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)


and i have included in kernel support for C-Media 8738 and 8338, Intel/sis/nvidia/amd/ali AC97 controller, and SB Audigy (just in case they are compatible) under device driver->sound-> A.L.S.A -> pci devices.
also a few options from the O.S.S. submenu under 'sound'..

Please help me!
Thank you in advance
nass
 
Old 08-02-2006, 07:16 AM   #2
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Original Poster
Rep: Reputation: 39
ok scratch what i said about mpg321... i was using it wrongly..
i don't get all this error msg i wrote.. it says 'playing the file at 44.1kHz' etcetc. but i do not hear any sound.. then again that might be because the sound is muted.. but i can not get to alsa mixer...
so the question still stands... how should i start approaching this problem with the alsa mixer?
thank you
nass
 
Old 08-02-2006, 07:25 AM   #3
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Original Poster
Rep: Reputation: 39
more info:

when i do 'slapt-get --installed | grep alsa' i get:

alsa-utils-1.0.9a-i486-2 [inst=yes]: alsa-utils (Advanced Linux Sound Architecture utilities)
alsa-driver-1.0.9b_2.4.31-i486-1 [inst=yes]: alsa-driver (Advanced Linux Sound Architecture drivers)
alsa-lib-1.0.9-i486-1 [inst=yes]: alsa-lib (Advanced Linux Sound Architecture library)
alsa-oss-1.0.9-i486-1 [inst=yes]: alsa-oss (library/wrapper to use OSS programs with ALSA)

and when i do slapt-get --installed | grep oss' i get:

alsa-oss-1.0.9-i486-1 [inst=yes]: alsa-oss (library/wrapper to use OSS programs with ALSA)

so packages seem to be installed... still don't know and still looking.
 
Old 08-02-2006, 07:43 AM   #4
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
I think you've got two conflicting ideas working at the moment ...

If you use a stock kernel, then the alsa-drivers will be provided for you in a separate package (alsa-driver-<version>-<kernel version built against>). If you rebuild your kernel then you need to a) rebuild the alsa-driver package against your new kernel or b) make sure you build the modules relating to your sound in your new kernel.

You've built everything into your kernel, but, your kernel doesn't know what to use - you should build these things as modules and then run alsaconf and let your system sort it out!

It's been a while since i've used a 2.4 kernel and alsa, but I recall making new alsa-driver packages using the slackbuild script and the alsa-driver source, you may wish to do the same.

Once you've sorted access to alsa-mixer, have a read of this thread http://www.linux-on-laptops.com/foru...php/t-165.html regarding (what I assume is) your audio chip to see if you can avoid the common pitfalls they found.

Let us know what happens!
- Piete.
 
Old 08-02-2006, 09:14 AM   #5
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,940

Rep: Reputation: 129Reputation: 129
You shouldn't use slapt-get in the first place. ALSA is included with the default
Slackware-10.2 installation. And when you compile a 2.6.x.y kernel you enable
ALSA in the kernel.

[rant]
Using a third party package manager such as slapt-get or swaret, etc. is just
asking for trouble. Use official Slackware packages or compile from source and
make your own Slackpacks with makepkg, checkinstall, or SlackBuild scripts.
[/rant]

This ALSA bugtrack probably has your answer:
http://sourceforge.net/mailarchive/f...&forum_id=1752

Try the "snd-hda-intel" module and see if that one works.

http://www.alsa-project.org/alsa-doc...dule=hda-intel
(so you might try "snd-hda-intel" by issuing as root
"modprobe snd-hda-intel;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss")

If that doesn't work, then you'll need to recompile your kernel with these options:
Code:
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_VERBOSE_PROCFS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
After that the above modprobe command line should work.

Last edited by Bruce Hill; 08-03-2006 at 08:49 AM.
 
Old 08-02-2006, 09:54 AM   #6
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Original Poster
Rep: Reputation: 39
Finally,
managed to get sound playing using the snd_hda_intel module..
i run alsaconf and it found the audio device.. so far so good.
thank you for your help.
but the problem is not over yet..
i have install the lastest alsa driver, lib and utils a while ago (ie before the last kernel compile) but i still can not get into alsamixer.. it gives me that same msg as before.
also from inside KDE the Kmix mixer is just an empty window ie no mixer is present there either... how should i tackle this?

if i lsmod i get:
Code:
Module                  Size  Used by
snd_pcm_oss            48384  0
snd_mixer_oss          18560  1 snd_pcm_oss
ipv6                  241120  12
snd_mpu401              8744  0
snd_mpu401_uart         7936  1 snd_mpu401
snd_rawmidi            25600  1 snd_mpu401_uart
snd_seq_device          8844  1 snd_rawmidi
pcspkr                  2944  0
intel_agp              21916  1
snd_hda_intel          19604  0
snd_hda_codec         150576  1 snd_hda_intel
snd_pcm                92680  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              24452  1 snd_pcm
snd                    56452  10 snd_pcm_oss,snd_mixer_oss,snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
soundcore               9696  1 snd
snd_page_alloc         10760  2 snd_hda_intel,snd_pcm
ide_scsi               16388  0
so the snd_mixer_oss module IS loaded... or am i wrong?
any ideas?
 
Old 08-02-2006, 10:23 AM   #7
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,940

Rep: Reputation: 129Reputation: 129
Your alsa* packages are NOT all the same version. Why?

I highly recommend using what comes with Slackware (officially),
or compiling ALSA on your own from the source at their website.

Until you get proper packages, it seems a waste of time to go on.

Your loaded sound modules are:
Code:
snd                    56452  10 snd_pcm_oss,snd_mixer_oss,snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
 
Old 08-02-2006, 11:33 AM   #8
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Original Poster
Rep: Reputation: 39
hey, where did you figure out that there is a version mismatch? i did install the alsa 1.0.11 driver , lib and utils (without deleting anything first - don't don;t quite know how to perform an unistall yet - enlighten me if you can). and i figured that should work.. it doesn't what modules should i unload or what else you think i should do..?
thank you
nass
 
Old 08-02-2006, 12:02 PM   #9
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,940

Rep: Reputation: 129Reputation: 129
Quote:
Originally posted by nass
when i do 'slapt-get --installed | grep alsa' i get:

alsa-utils-1.0.9a-i486-2 [inst=yes]: alsa-utils (Advanced Linux Sound Architecture utilities)
alsa-driver-1.0.9b_2.4.31-i486-1 [inst=yes]: alsa-driver (Advanced Linux Sound Architecture drivers)
alsa-lib-1.0.9-i486-1 [inst=yes]: alsa-lib (Advanced Linux Sound Architecture library)
alsa-oss-1.0.9-i486-1 [inst=yes]: alsa-oss (library/wrapper to use OSS programs with ALSA)
Please disregard that -- those are the packages in Slackware-10.2. I guess the a and b doesn't matter.

In Slackware it's best to use Slackware packages and "upgradepkg <package-name>" so that you let the pkgtool app remove the old and install the new. If you're going to compile from source rather than using a package, then use "removepkg <package-name>" for the already installed version first, so that you don't create entropy in your system.

How to remove installed software? You should check it's INSTALL or README file which came with the source. That's why in Slackware the best method is to build Slackpackages and use pkgtool. Issue "man pkgtool" and read to familiarize yourself.

There is no need to upgrade the ALSA packages when you build a new kernel. You simply choose the modules that I previously posted to you; because ALSA is in the 2.6 kernel.
 
Old 08-02-2006, 12:44 PM   #10
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Original Poster
Rep: Reputation: 39
i see what you mean..
however i have already got the source 1.0.11 and installed it as root in the pc.
and an update if i run alsamixer as root the alsamixer window appears where everything is muted apart from the pc speak volume... if i unmute any of the other (ie PCM, Surround, Center, LFE, side, IEC958) i get the '00' in place of 'MM' but i can not increase of decrease the sliders. thats not normal behaviour is it?

if i run alsamixer as a user i get the aforementioned error, even though the alsamixer attrib are -rwxr-xr-x ...

hm whats funny is that know slapt-get -installed gives me still the 1.0.9 version... the alsamixer version is of course 1.0.11..

finally i don't seem to have the utilities upgradepkg nor removepkg, even though i have carried out my linux installeation enabling all packages to be installed..
still looking into it
nass
 
Old 08-02-2006, 05:22 PM   #11
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,940

Rep: Reputation: 129Reputation: 129
Originally posted by nass
Quote:
got the source 1.0.11 and installed it as root in the pc
Something seems to be wrong with your install. My best advice is, once
again, quit using slapt-get and only use official Slackware packages
using pkgtools.
Quote:
if i run alsamixer as root
You shouldn't run "alsamixer" as root; run it as a normal user.
Quote:
i get the '00' in place of 'MM' but i can not increase of decrease the sliders. thats not normal behaviour is it?
It is not normal behavior.
Quote:
the alsamixer attrib are -rwxr-xr-x
Those permissions are correct.
Quote:
slapt-get -installed gives me still the 1.0.9 version
What does "ls -l /var/log/packages/alsa*" output?
Quote:
i don't seem to have the utilities upgradepkg nor removepkg
What does "ls -l /var/log/packages/pkgtools*" output?

Now for the good news...

Slackware Linux is recoverable when other OSes would be fubar.
 
Old 08-02-2006, 10:14 PM   #12
davidsrsb
Member
 
Registered: Oct 2003
Location: Kuala Lumpur, Malaysia
Distribution: Slackware 13.37 current
Posts: 770

Rep: Reputation: 33
I use swaret, but alsa is in my excludes list along with kernel packages.
Kernel sets plus matching alsa-driver should ALWAYS be carefully manually installed, making sure that lilo is run.
 
Old 08-03-2006, 12:04 AM   #13
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,940

Rep: Reputation: 129Reputation: 129
Just to add a bit of clarity, in case that last post confuses you.

If you compile your own 2.6 series kernel, you do NOT need to get
another ALSA driver, lib, or utils. I believe David is referring to
a case where someone installs a Slackware kernel package ONLY.
 
Old 08-03-2006, 03:28 AM   #14
nass
Member
 
Registered: Apr 2006
Location: Athens, Greece
Distribution: slackware, debian, ubuntu
Posts: 666

Original Poster
Rep: Reputation: 39
but how is slackware recoverable?
the thing is i have compiled the 1.0.11 source of alsa... and it has been installed on the pc (somewhere) and at this point, when i do:

Code:
root@meditSea:/var/log/packages# ls -l | grep alsa
-rw-r--r--  1 root root  16321 2006-07-05 15:22 alsa-driver-1.0.9b_2.4.31-i486-1
-rw-r--r--  1 root root   4584 2006-07-05 15:22 alsa-lib-1.0.9-i486-1
-rw-r--r--  1 root root   1089 2006-07-05 15:22 alsa-oss-1.0.9-i486-1
-rw-r--r--  1 root root   2498 2006-07-05 15:20 alsa-utils-1.0.9a-i486-2
ie only the alsapackage that came with the installation. so i can not do removepkg alsa-1.0.11...
i can however removepkg alsa-1.0.9 and then built an alsa-1.0.11 slackware package... i wonder though if it will work since in the alsa installation manual it nowhere states explicitly to built a package for slackware.. so i had assumed and simple ./configure;make;make install would have sufficed...
nass
 
Old 08-03-2006, 03:45 AM   #15
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,940

Rep: Reputation: 129Reputation: 129
Look in the source of the alsa-1.0.11 files you installed, and perhaps there
is an INSTALL, README, or similar file which tells you how to uninstall.

There is also the possibility that you could use "removepkg alsa-*" to get rid
of the original Slackware packages. Would it then be clean?

You could also use Pat Volkerding's SlackBuild scripts to build Slackpacks of
those new versions.

My first choice would be to remove the ones you installed from source, then check
your kernel for the modules I previously posted to you.

A simple "./configure;make;make install" installed new versions of packages that
were already in your system. What new files did it install to where? What old files
did that overwrite?

What does "ls -l /var/log/packages/pkgtools*" output?

What is your present "lsmod" output now that sound works?

What is the output of "uname -a" ?

What is the output of "cat /location/of/your/present/kernel/.config | grep -i snd" ?

What is the error when you run "alsamixer" in a terminal as a user (not root)?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
no output/input Logitech 350 usb with cmi 8738 chip set sound board installed marvinudy Linux - Hardware 0 05-08-2006 04:27 PM
debian alsa CMedia 8738 chip doobiean Linux - Hardware 3 10-24-2004 07:16 AM
mute sound alsa mixer - used to work TroelsSmit Linux - Newbie 4 09-02-2004 12:39 PM
ALSA CMedia 8738 Mixer problems LavaDevil94 Linux - Hardware 0 06-13-2004 09:23 PM
on board sound chip ES1887 fig Linux - Hardware 1 07-18-2003 01:36 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration