Greetings, fellow linux users.

I was running sound apps with no problems under mandrake 9.2
I couldn't wait to try out KDE 3.2 and kernel 2.6 so I upgraded to mandrake 10.0 beta 2

Now I no longer have sound. The only error I've seen was related to KDE startup and it mentioned something about no /dev/dsp existig. I tried searching out some leads on that and discovered an empty file (says 0k in Konkeror) called /dev/sound/dsp.

I checked Harddrake and saw the card properly recognized as an Audigy, however, I think the system may be trying to load an emu10k1 driver and this is an emu10k2 card. Are the drivers one and the same for both SB Live! and SB Audigy cards?

Anyway, poking around a bit more led me to /etc/modules.conf which contains exactly the following lines:

probeall usb-interface usb-uhci
options bttv radio=1 gbuffers=4
above snd-emu10k1 snd-pcm-oss
alias sound-slot-0 audigy

so, it seems maybe it is supposed to use the emu10k1 driver for an Audigy card?
at any rate, I am not getting sound, even with this. I have been trying to find out what modules are and aren't loading but I keep forgetting the commands to use. I know there's modinfo and I ran modinfo soundcore and saw that was fine.

Ok, so I just ran
[root@localhost bin]# modinfo emu10k1
author: Bertrand Lee, Cai Ying. (Email to: emu10k1-devel@lists.sourceforge.net)
description: Creative EMU10K1 PCI Audio Driver v0.20a
Copyright (C) 1999 Creative Technology Ltd.
license: GPL
vermagic: 2.6.2-0.rc3.1mdk 586 gcc-3.3
depends: soundcore,ac97_codec
alias: pci:v00001102d00000002sv*sd*bc*sc*i*
alias: pci:v00001102d00000004sv*sd*bc*sc*i*

maybe that is helpful...

It followed instructions at alsa-project.org (if you choose audigy gamer card, that is closest to what I have...same hardware without gamer software for windoze) to create an .asoundrc in my /home/username directory

I appreciate any help you folks can provide. Gaming with no sound bites!

Before you attempt a solution, check three more things. First, check that your mixer is not muted (main and pcm). Sounds dumb, but usually the culprit. Second, see if you get sound as root (you'll have to re-add your user account to group audio, if that is so). Third, see if the module for your card actually loads. If thereare emu10k1 or 2 entries, you've got the wrong module. The kernel gets confused sometimes. If no module got loaded, likely ifplug is crapping on it. Force it by adding the modules to /etc/modprobe.preload file (unless you dumped the 2.6 kernel for the 2.4). If its wrong, try putting in the right one with the hardware module of the mandrake control center or download sndconfig and run it. Pick the emu10k2 and see if you get sound

Ok, Vectordrake...
I checked my mixer and I did see some volume levels pretty low, so I moved everything at least to the middle (using kmix). Now, I ran lsmod to see what I got:

[root@localhost nick]# lsmod
Module Size Used by
raw 7616 0
udf 94660 0
8139too 22560 0
mii 4992 1 8139too
sg 37528 0
st 38328 0
sr_mod 16964 0
sd_mod 16672 0
scsi_mod 114712 4 sg,st,sr_mod,sd_mod
autofs4 14656 2
parport_pc 34924 1
lp 12200 0
parport 40648 2 parport_pc,lp
agpgart 31080 0
md5 3872 1
ipv6 233664 8
snd-seq-midi 8160 0
snd-emu10k1-synth 6816 0
snd-emux-synth 36384 1 snd-emu10k1-synth
snd-seq-virmidi 6912 1 snd-emux-synth
snd-seq-midi-emul 7776 1 snd-emux-synth
snd-seq-oss 31264 0
snd-seq-midi-event 7552 3 snd-seq-midi,snd-seq-virmidi,snd-seq-oss
snd-seq 51248 8 snd-seq-midi,snd-emux-synth,snd-seq-virmidi,snd-seq-midi-emul,snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 51812 0
snd-mixer-oss 17824 1 snd-pcm-oss
snd-emu10k1 84836 2 snd-emu10k1-synth
snd-rawmidi 23616 3 snd-seq-midi,snd-seq-virmidi,snd-emu10k1
snd-pcm 93220 2 snd-pcm-oss,snd-emu10k1
snd-timer 24516 2 snd-seq,snd-pcm
snd-seq-device 8008 7 snd-seq-midi,snd-emu10k1-synth,snd-emux-synth,snd-seq-oss,snd-seq,snd-emu10k1,snd-rawmidi
snd-ac97-codec 57540 1 snd-emu10k1
snd-page-alloc 11972 2 snd-emu10k1,snd-pcm
snd-util-mem 4448 2 snd-emux-synth,snd-emu10k1
snd-hwdep 8928 2 snd-emux-synth,snd-emu10k1
snd 52548 18 snd-seq-midi,snd-emux-synth,snd-seq-virmidi,snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-emu10k1,snd-rawmidi,snd-pcm,snd-timer,snd-seq-device,snd-ac97-codec,snd-util-mem,snd-hwdep
af_packet 20552 2
floppy 59348 0
ipt_TOS 2240 12
ipt_REJECT 6464 4
ipt_LOG 5312 6
ipt_state 1728 20
ipt_multiport 1856 0
ipt_conntrack 2304 0
iptable_filter 2624 1
iptable_mangle 2624 1
iptable_nat 23116 0
ip_conntrack 31120 3 ipt_state,ipt_conntrack,iptable_nat
ip_tables 16704 9 ipt_TOS,ipt_REJECT,ipt_LOG,ipt_state,ipt_multiport,ipt_conntrack,iptable_filter,iptable_mangle,iptab le_nat
ntfs 85900 1
nls_iso8859-1 3904 2
nls_cp850 4736 1
supermount 37876 2
vfat 13760 1
fat 45120 1 vfat
ide-floppy 18528 0
ide-tape 51376 0
ide-cd 39972 0
cdrom 37056 2 sr_mod,ide-cd
nvidia 2068232 22
tuner 17260 0
tvaudio 21324 0
bttv 146700 1
video-buf 20388 1 bttv
i2c-algo-bit 9512 1 bttv
v4l2-common 6144 1 bttv
btcx-risc 4712 1 bttv
i2c-core 23044 4 tuner,tvaudio,bttv,i2c-algo-bit
videodev 9536 2 bttv
soundcore 9248 2 snd,bttv
usblp 12288 0
uhci-hcd 29584 0
usbcore 99324 4 usblp,uhci-hcd
rtc 11576 0
ext3 110344 2
jbd 54328 1 ext3

...it appears to be loading emu10k1 drivers (which after further researching I found to be the correct driver for both SB Live! and Audigy cards). I also checked the contents of my /etc/modprobe.preload and it contains:

# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules

bttv

...do you still think I should add an entry below bttv (my brooktree tv card module) for emu10k1? Or is that what you even meant?

By the way, I am running the default mandrake 10 beta 2 2.6 kernel. I don't think there is any emu10k2 driver.

Any other ideas?

From your lsmod, its obvious that the driver loaded. I thin kyou might want to try the audigy2 driver. The first way to try is to use alsaconf. As root, type that (it works like that kewl redhat tool - sndconfig). Try to configure your card with it. It may give you a choice of which module to use for your card. An alternative is to do it from the Mandrake Control center, through the hardware module. I have a feeling that yours is a 2nd gen card and the newer driver will work. Sometimes the kernel gets confused. BTW what does lspci tell you the card actually is?

vectordrake,

Thanks for taking the time to help me!
I have tried to run that alsaconf tool from a terminal (su'd to root) and I get "command not found." On a hunch, I tried urpmi alsaconfig and it found no packages matching that name (my urpmi is properly configured for main, contrib and plf servers). I remember the oldskool redhat sndconfig tool - I used it back in the redhat 6.0 days when I was first learning linux. Also, I tried to run lspci and got a "command not found" for that too.
Maybe I have something wierd with Alsa installation? Urpmi said "everything already installed" when I typed urpmi alsa on a hunch.
Ugh...
So - I go to "configure your computer" from my kde menu and get into my mandrake control center. One thing that seems kinda wierd to me is that it says "Mandrake Control Center 9.2" at the top instead of 10.0 beta 2. Not sure why.

Oh yeah....Mandrake has their own version of lspci...I got this:
root@localhost temp# lspcidrake -v | fgrep AUDIO
audigy : Creative Labs|EMU10K2 Audigy Audio Processor [MULTIMEDIA_AUDIO] (vendor:1102 device:0004 subv:1102 subd:0053)

I switched the driver choice between the 3 in Harddrake configuration and none worked. I can choose from "snd-emu10k1", "audigy" and "emu10k1".

The installation default was on "audigy", which is of course my card.

I still think there is something to this not having any /dev/dsp
I am not sure what creates that file...is it kind of like a windows device driver or .vxd?

Sort of.

Do you have a source for updates set up? I didn't know where to go since I haven't joined mandrakeclub (although I keep coming back, so I think I'd better ), so I pointed towards cooker sources. I got pointed to the 2.6.2 final kernel. Perhaps if you install it, you may have a better chance at getting the emu10k2 driver loaded.

A thought. Why don't you manually unload the emu10k1 driver and load the emu10k2 driver. See if it works. /dev/dsp will show up if your driver actually connects with the hardware its supposed to communicate with.

You seem to not have certain tools available to you that I do. lspci should be available to root every time. How are you accessing it? sudo? or su?

Yes, I am using sunet.se for my main and contribs and I have a plf source, but I have not had any success adding an update media since my upgrade to 10.0b2

Do you have an ftp or rsync (or whatever) path for a cooker update mirror? I would really appreciate that because I haven't been able to update any packages.

It sounds like you are on to something with manually unloading the 10k1 driver and trying the 10k2 driver (I didn't realize there WAS a 10k2 driver!). That makes sense about the /dev/dsp showing up when everything is working correctly.

As for root tools - I have just been using su. I forgot all about sudo and the difference...must be time for me to hit the man pages again.

My problem is that I've been "experimenting" with linux since redhat 6.0 but haven't stuck with it due to frustrations. It seems to me that there are really no reasons for me personally not to stick with it and eliminate windows use altogether now that I've found out that DVD shrink 3.0beta versions work under wine. All my favorite games are either ported to linux natively or work acceptably under wine, (except maybe counterstrike 1.6, but I have heard things about that lately).

If I can get this problem fixed and my xawtv config file to be read on startup, I'll be able to do my video capture and then I can REALLY let go of windows.

I feel a world of legal and free software is open to me and just waiting for me to learn how to use it all!

Maybe I should just see what happens after beta 3 of mandrake 10 comes out. Its likely to have the updated kernel release and some bugfixes too.

Here's the mirror I use. From where I am, in New Brunswick (eastern Canada), it seems to be the best and fastest for me: ftp://ftp.rpmfind.net/linux/Mandrake.../Mandrake/RPMS

I also use the same mirror for the RPMS2 and RPMS3 folders as wel. So, I have 6 entries in my sources file. 3 for the cds and 3 for the ftp server. After I added them, things went well. A few things were broken with 10, but after a quick upgrade, I was ok. Tonights upgrade resolved a few KDE things. I had no packages held back. They plan to release the stable 10 in March, so they must be plugging foreward. If you upgrade to 2.6.2mdk you'll likely be happy with the results. Perhaps that's where the emu10k2 comes in. Here's a 'slocate alsa' from my system:

/etc/sysconfig/alsa
/etc/rc.d/init.d/alsa
/etc/rc.d/rc0.d/K70alsa
/etc/rc.d/rc1.d/K70alsa
/etc/rc.d/rc2.d/S17alsa
/etc/rc.d/rc3.d/S17alsa
/etc/rc.d/rc4.d/S17alsa
/etc/rc.d/rc5.d/S17alsa
/etc/rc.d/rc6.d/K70alsa
/etc/rc.d/rc.alsa_default
/etc/netprofile/profiles/default/services/alsa
/var/lib/alsa
/var/lib/alsa/dev
/var/lib/alsa/dev/snd
/var/lib/alsa/dev/snd/hwC0D2
/var/lib/alsa/dev/snd/midiC0D1
/var/lib/alsa/dev/snd/midiC0D2
/var/lib/alsa/dev/snd/seq
/var/lib/alsa/dev/sound
/var/lib/alsa/dev/sound/admmidi
/var/lib/alsa/dev/sound/amidi
/var/lib/alsa/dev/sound/sequencer
/var/lib/alsa/dev/sound/sequencer2
/usr/share/man/man8/alsaconf.8.bz2
/usr/share/man/man1/alsactl.1.bz2
/usr/share/man/man1/alsamixer.1.bz2
/usr/share/doc/libalsa2-1.0.2
/usr/share/doc/libalsa2-1.0.2/COPYING
/usr/share/doc/libalsa-data-1.0.2
/usr/share/doc/libalsa-data-1.0.2/COPYING
/usr/share/doc/alsa-utils-1.0.2
/usr/share/doc/alsa-utils-1.0.2/COPYING
/usr/share/doc/alsa-utils-1.0.2/INSTALL
/usr/share/doc/alsa-utils-1.0.2/README
/usr/share/doc/alsa-utils-1.0.2/TODO
/usr/share/doc/xmms-alsa-1.2.9
/usr/share/doc/xmms-alsa-1.2.9/COPYING
/usr/share/locale/en_GB/LC_MESSAGES/alsaplayerui.mo
/usr/share/alsa
/usr/share/alsa/cards
/usr/share/alsa/cards/Audigy2.conf
/usr/share/alsa/cards/AU8810.conf
/usr/share/alsa/cards/AU8820.conf
/usr/share/alsa/cards/AU8830.conf
/usr/share/alsa/cards/Audigy.conf
/usr/share/alsa/cards/CMI8738-MC6.conf
/usr/share/alsa/cards/CMI8338.conf
/usr/share/alsa/cards/EMU10K1.conf
/usr/share/alsa/cards/CS46xx.conf
/usr/share/alsa/cards/SI7018
/usr/share/alsa/cards/SI7018/sndoc-mixer.alisp
/usr/share/alsa/cards/SI7018/sndop-mixer.alisp
/usr/share/alsa/cards/ENS1370.conf
/usr/share/alsa/cards/ENS1371.conf
/usr/share/alsa/cards/FM801.conf
/usr/share/alsa/cards/GUS.conf
/usr/share/alsa/cards/ICE1712.conf
/usr/share/alsa/cards/ICE1724.conf
/usr/share/alsa/cards/ICH.conf
/usr/share/alsa/cards/NFORCE.conf
/usr/share/alsa/cards/RME9636.conf
/usr/share/alsa/cards/RME9652.conf
/usr/share/alsa/cards/TRID4DWAVENX.conf
/usr/share/alsa/cards/SI7018.conf
/usr/share/alsa/cards/VXPocket440.conf
/usr/share/alsa/cards/VIA8233.conf
/usr/share/alsa/cards/VIA8233A.conf
/usr/share/alsa/cards/VX222.conf
/usr/share/alsa/cards/VXPocket.conf
/usr/share/alsa/cards/aliases.alisp
/usr/share/alsa/cards/YMF744.conf
/usr/share/alsa/cards/aliases.conf
/usr/share/alsa/pcm
/usr/share/alsa/pcm/center_lfe.conf
/usr/share/alsa/pcm/front.conf
/usr/share/alsa/pcm/iec958.conf
/usr/share/alsa/pcm/rear.conf
/usr/share/alsa/pcm/surround40.conf
/usr/share/alsa/pcm/surround41.conf
/usr/share/alsa/pcm/surround50.conf
/usr/share/alsa/pcm/surround51.conf
/usr/share/alsa/alsa-utils
/usr/share/alsa/alsa.conf
/usr/share/alsa/sndo-mixer.alisp
/usr/share/zoneinfo/Asia/Choibalsan
/usr/share/apps/kappfinder/apps/Internet/balsa.desktop
/usr/bin/alsamixer
/usr/lib/ao/plugins-2/libalsa09.la
/usr/lib/ao/plugins-2/libalsa09.so
/usr/lib/xine/plugins/1.0.0/xineplug_ao_out_alsa.so
/usr/sbin/alsaconf
/usr/sbin/alsactl
/usr/java/j2re1.5.0/lib/i386/libjsoundalsa.so
/usr/java/j2re1.5.0/lib/zi/Asia/Choibalsan


I have a sb live! gamer. Notice that I have entries for the emu10k2?

Your card will produce sound!!!!!! We will make it so!
There a re a few bindings from 9.2 that are different. The 2.4 kernel from 9.2 would have looked to /etc/modules for forced modules, as one would suspect. The 2.6 would look at the /etc/modprobe.preloadfile for the same things. Times change. I do think that with MDK, you've got a better chance for support for anything new you buy.

Awesome...your update source is good.
I'm going to run an update for all packages available tonight and then I'll mess around with my configuration for the sound card after work tommorow.

I can't thank you enough for all the help!

vectordrake -
did you update your kernel from that updates source you gave me?
The closest thing I could find was a 2.6.2-3mdk kernel source that I didn't have installed on my machine. Did you download and compile your own kernel or something? I haven't done that in years and I remember it involving a bunch of steps to configure lilo to find the new one, etc. I would need to read up on that for a bit before I felt comfortable compiling a custom kernel (although that is eventually exactly what I want to do to optimize my system performance.)

If you updated to a newer kernel than the beta 2 release included from that mirror, then I am having an issue with my mandrake update software as well since it detected that I needed absolutely no updates! And I haven't updated since installing this beta!

The kernel is there as well. Yes, I did update the kernel with the update tool. That's the one I am running. I got the source too, since I was pretty close to compiling that damn ethernet module right into the kernel, but that config file find saved me from messing with it (although I still may have to. my Nero burns aren't readable as anything under Linux - might not have Joliet extensions enabled).

Add all three folders to your source list: RPMS RPMS2 RPMS3
That will give you everything available, as far as I can tell. BTW, good news. A few KDE packages were being held back because of dependancy issues until last night. I selected the update module of the package manager (GUI) and changed the view from "Mandrake choices" to "select from...." and chose by updateability, or whatever (I'm using Win right now to finish a Shareaza bittorrent download, so I can't check exactly). I selected the checkbox by "upgradable" (as in all of them), and they all upgraded successfully. Stability will be around the corner...not that mine is unstable, but you know what I mean.

Wow. This is so wierd.
Good news: MY SOUND IS WORKING!!!!
I have sound using xawtv for my tv capture card and I have sound for video games. Strangely enough, though on KDE startup, I get an error about being unable to open the device for sound. I can now find a /dev/dsp and /dev/dsp1 entry on my system. Something we tweaked worked, I think it was a change I made in hard drake from "audigy" to "emu10k1" and after rebooting, I guess that restarted the sound server with the correct parameters for the kernel to be happy.

Now, the part that is genuinely strange is that lately, I have to go to hard drake and reconfigure my network card so that I can connect through my cable modem again. I can't understand why it started to do this. In addition, just since adding that update server mirror, when I try to run any package app (from mandrakesoft) such as the "mandrake update", I get to the point where it checks the remote server and then says "please wait, finding packages" and then the thing disappears and I never get the chance to update. Something is corrupted somewhere.

At any rate, vectordrake, I really appreciate all the help. It is so nice to have one less reason to ever boot windows. I am weaning myself off for good! And soon, I'm going to get a mandrakeclub membership to support my favorite distro.

I think that you'll find that if you update your media before you check for updated packages, you'll get better results. Mandrake's cooker is aflurry with activity, and I think it recieves updated packages all day long. Your problem is probably stemming from the fact that you're "looking" for a package that has been replaced by a newer one. Its quite close to the bleeding edge, I find. That is why I didn't take to any development distros before I left dialup, as I'd never get an update before the packages I was looking for got updated.

BTW, I don't think that Mandrake update'll do you any good until 10 becomes stable. I couldn't get any security sites to resolve for me either (not that they could keep up with the development of the packages we are loading up.) No worries. I have the most fresh rpms that mandrake can cook.

If your ethernet card won't load on boot, enter the name of the module in /etc/modprobe.preload and it'll likely fire up then. I think its a bug in the PCI hotplugging program that loads up modules. That's what I had to do, which led me to the solution that is sort of working for you.

That sounds about right, Vectordrake. (regarding the pci hotplugging proggie).

I just started using bittorrent to get Mandrake 10 rc1.
Details are at distrowatch.com if you want to pick it up yourself.
Since its so new, I'm getting only about 11 or 12k download rates....pleh!

And I know what you mean, this is my first time messing with a pre-release version of any distro. It hasn't been all that bad, truthfully. I would certainly not recommend it to any true linux noobs, but it is pretty fun to get to use KDE 3.2 and the MUCH faster safari-enhanced konqueror. I don't know if you noticed, but when I browse windows ntfs volumes, it is lightning fast now when I used to have several seconds pause before in mandrake 9.2