Audigy LS Anyone?

[DSwain]

Well, I am trying to get my new sound to work in Linux (well, not with OSS, prefeerably ALSA) and i just wanted to know if anybody got it to work, and maybe give me some advice on the config file editing, installing the stuff, etc.

[bandwidth_pig]

Hi Swain. I have a Audigy myself. And, I also use ALSA. I just recompiled the kernel with the emu10k1 module and the support for ALSA, changed the permissions for /dev/dsp (I'm sure you know the routine). Then you will need to unmute the mixer as it will be muted by default. I use aumix for this. After that, she should work like a champ.

[DSwain]

well, i could probably figure out the user permission, but how would i go about recompiling the kernel? I know how to compile the 2.6 kernel, but i don't know how to go and recompile the kernel i already have installed. I'll take a look around here maybe...

[bandwidth_pig]

Ahhh. Thats an easy one. If you kept the sources, just change over to the directory where you had compiled the kernel originally. Your config will still be there. I don't know if you run menuconfig or what your preference is...I like menuconfig myself. But just go in and make "your preferred method" and select the emu10k1 driver and your ALSA support and then do the usual (make bzImage, make modules, make modules_install). For permissions:

chmod ugo+rwx /dev/dsp
chmod ugo+rwx /dev/mixer

It's not so much you are recompiling a kenrel you have already installed, as you are using the same options you had setup previously (saving yourself some time) and compiling a new kernel with the same info + some changes for your sound card. :cool:

[DSwain]

i see, thanks for the permission help, but the thing of it is, i should have said i CAN and HAVE compiled a kernel myself (2.6.0) but i'm not running it at the moment...so, is there a way to do it with a kernel thats previously been installed (or a stock kernel in this case, Mandrake 9.2)

[bandwidth_pig]

Ahhh. Sorry about that. Misunderstood you there. It is possible that you may have the config you are currently running under /usr/src/linux. Possible. Sounds like you don't want to recompile another kernel? That would be the easiest route IMHO.

[DSwain]

no i don't really mind, but with MDK 9.2 you can't just compile straight from the source, and i don't know what you need to do it either. maybe i'll give RH9 a run again.

[bandwidth_pig]

You can't? I can't imagine that. Are you sure? I never used Mandy long enough to find out (ran to damn slow for me). Is it possible you might come over to the dark side and try Debian or Gentoo or Slackware?

[DSwain]

i've done Slack before. Tried Gentoo, but very complex. Tried Debian, but it failed on me. I may try Debian again sometime, maybe i'll give Slack a shot tonight, though.

[DSwain]

well just as an update, i installed Slack 9.1, and compiled the 2.6.1 kernel. running pretty well, i just gotta try out the permission thing you told me to do. i'll be back if it doesn't work out.

[JamminJoeyB]

DSwain, Slack 9.1 uses ALSA as the default. About 2 weeks ago I bought an Audigy 2 ZS and installed. I rebooted and slackware found the card and loaded all the right modules and I never had to change anything. It was a real no brainer. I was ready to have to change a bunch of config files and that was not the case. Should be the same on your system.

I'm not running a 2.6 kernel, but I am sure the Slackware guys will probably have one out here shortly. I have 2.6 running on my testing partician. Not like I have booted there much lately as I have needed a stable platform to do a lot of work.

[DSwain]

yes, i was hoping that was the case, but it isn't. My card (Audigy LS) is not supported out of the box, and OSS and stuff only has beta drivers. I wish it was just like that.

[JamminJoeyB]

That is strange. Why would the LS have such a different chipset that the LS would not be supported.

I'm gonna have to do some reading on the specs of the cards. It just doesn't make sense that Slack9.1 on my machine would pick the card up and go like it did, but the LS is causing so much trouble.

***edit

I looked over the specs of both cards at the creative site. They pretty much support the same basic standards. The audigy 2 ZS just supports more and has a few more features.

Odd that Slackware didnt just pick this card up like the ZS. Did you disable PNP OS in your bios? I don't think anyone asked that question yet.

[DSwain]

well, it isn't just slack- its every distro, Red Hat 9, Fedora Core 1, Mandrake 9.2/Cooker Alpha's on. Didn't try PnP, but i guess i could try it...

as for not finding it, though, it does seem to be able to find it. when i boot of something, say Knoppix, it shows the card as an unsupported device. And, i had it working once, after i used OSS a little bit, but it wasn't very good, and i think it'd be better to use ALSA. And, finally for the permission, i was about to try, but then of course i decided i should try and get new video drivers installed..... of course i must have messed something up on the X config file, so that went away....

oh, and i know what you mean. all the Audigy's (except the LS) have pretty much full support for Linux. Odd, very odd since they're generally the same. SOO, i guess i'll reinstall Slack and then try to get sound again with the 2.6.1 Kernel

and, one last thing, isn't Slack suppost to come with built-in support for the RTL8139? i thought it was, but i guess not. Oh well, it works fine after compiling the new kernel, so its all good.

[JamminJoeyB]

Well if pnp op is enabled in the bios that would cause problems. Linux doesn't use pnp. If you have it enabled disable it.

This may have been causing the problem all along.

[DSwain]

i'll be glad to give it a shot, but i've read its unsupported. its worth a try, though.

[bandwidth_pig]

It's important to remember guys, it isn't a question of weather slackware will detect the card or not, as it has nothing to do with slackware itself. It's all about the Kernel. So in your case JoeyB, I suspect you had never recompiled or installed a new kernel on your Slackware machine and the kernel you were using just happened to have support already compiled in. It's not unusual for stock kernels to have quite a few loadable modules.

As long as the card uses the same module (emu10k1) then it's a done deal. It's either compiled in as a loadable module in the kernel (again I suspect the case with JoeyB), or compiled straight in . If neither, it's not going to work. Make sense? Now in some cases, a tweak has had to be made to a module to support hardware...and emu10k1 is no exception...where a new piece of hardware has come out and the mod needs a little tweaking...so sometimes you have to compile the source for the module and then insert it on your own, or download a new kernel that contains a newer version of the module. Like 2.4.22 would not support my Audigy. I don't care how many times I tried. 2.6.0 did no problem.

[DSwain]

alright, well now i have the 2.6.1 kernel compiled with emu10k1, and i've done the permissions, but i don't really seem to have any luck with that... do i need to start alsa somehow?

[mdwatts]

If all the required modules are being loaded (lsmod) and sound is still not working, then it's usually permissions or volume levels and/or muting in the sound mixer.

[DSwain]

i just tried lsmod, and it shows no modules being loaded. and, of course, i forget if i compiled it directly into the kernel or as a module. should i recompile it as a module? also, under "Infocenter" for Sound Devices, this is what it lists-

Sound Driver: 2.8.1a-980706 (ALSA v0.9.7 emulation code)
Installed drivers:
Type 10: ALSA emulation

Card Config:
--- no soundcards ---

and all the mixers and devices are not enabled in the config (because there isn't one, i would think)

[bandwidth_pig]

As long as you know you compiled it in it doesn't matter. Mine is compiled right into the kernel. To find out if you compiled it in, you could just go back to the directory where you compiled the kernel and run makemenuconfig and go under the sound area. What you selected will still be there. Just exit out when you are done and don't save the kernel. Also, if your curious if your card is being seen, just take a look at dmesg. Take a look at messages too. I'm curious if your getting any error messages when booting up.

[DSwain]

i looked at dmesg like you said, and heres what i got for sound error wise-

Advanced Linux Sound Architecture Driver Version 0.9.7 (Thu Sep 25 19:16:36 2003 UTC).
request_module: failed /sbin/modprobe -- snd-card-0. error = -16
ALSA device list:
No soundcards found.

request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- snd-card-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256

well, some of that is for net-pf (i'm assuming my network card, which is working fine BTW) so i'm not sure... i don't know what error 256 is either.

[mdwatts]

And you have disabled PnP OS in the bios as was previously suggested?

What does

lsmod

show?

Did you compile sound support as modules or into the kernel?

[DSwain]

lsmod shows- nothing. actually, it says-

Module Size Used by

and thats it. PnP, well I can give it a shot, but i had sound working once with OSS (it was pretty poor, though) so i dunno if that'd do it. Plus i didn't see 1 specific setting for enable or disable PnP in my BIOS. And i compiled sound directly into the kernel. like i said, if i need to recompile it as a module i will, not that big of a problem for me. i'll take a look at PnP again now.

[mdwatts]

Did you compile anything as a module (besides sound) as it's strange that you do not have any modules loaded.

Did you enable 'module' support while compiling the kernel?

[bandwidth_pig]

Hmmm. At this stage, I would recompile your kernel. Do not compile in emu10k1 in directly and instead compile it in as a module. Then try inserting it and see if you get any errors. I can tell you that emu10k1 is without a doubt the correct driver for the Audigy. I use it for mine.

[DSwain]

i'm pretty sure i didn't compile anything else as a module, other than some network card dummy which i didn't tell it to do, so i guess i'll go with bandwidth pig and recompile with it as a module.

[bandwidth_pig]

You could save yourself a lot of time by reusing the config you already have. Just change emu10k1 to module. :D

[DSwain]

alright, yeah i tried doing that but it didn't go over well, but all is well now. here's what i've got so far-

recompiled the kernel, made the EMU10k1 a module, and here's what lsmod gave me (i made other stuff modules too)

Module Size Used by
soundcore 6976 0
ide_scsi 12356 0
vfat 12160 0
fat 42080 1 vfat
ntfs 111316 0
8139too 19584 0
mii 4096 1 8139too
crc32 3840 1 8139too

so i see soundcore their, i'm guessing that means better than where i was, any ideas on what to do from here? sorry if this is newbish of me, but i'd like to figure this out, so i keep asking what to do next. so thanks for the help guys.

also, heres dmesg, or what i found from it-
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
NTFS volume version 3.1.
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- net-pf-10. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256
request_module: failed /sbin/modprobe -- sound-slot-0. error = 256

and yes, the card does work.

[bandwidth_pig]

Thats interesting. I'm not seeing emu10k1 listed in your lsmod output. Did you insert it? Even if it loads at boot, it should still be listed.

[DSwain]

yeah, i did insert it, i am positive (as a module also) and i did (during the compile)-

make modules
make modules install

so i'm pretty sure that should have worked.

[mdwatts]

Originally posted by DSwain
yeah, i did insert it, i am positive (as a module also) and i did (during the compile)-

make modules
make modules install

so i'm pretty sure that should have worked.

I'm sure bandwidth_pig meant by inserting ...

insmod emu10k1

or

modprobe emu10k1

So PnP OS is now disabled in the bios?

It certainly helped in this thread (http://justlinux.com/forum/showthread.php?s=&threadid=120514) just down from yours.

[bandwidth_pig]

Exactly mdwatts. If you insert the module manually and you don't get any error messages, then we should see the module listed in the lsmod output....ie insmod emu10k1. If you have no error messages, and the module is listed when you issue the lsmod command, then we know the card is working. It will only be a matter of removing the default mute status of the mixer. Based upon the information you have given, it appears that if you did insert the module in the manner described, that it was not taken. But I would think you would have noticed the error messages.

[DSwain]

oh alright, sorry i didn't know the command to insert a module (i never had to do it manually before) so i'll try that. also, the card is working, I am positive of that. As for the PnP in the BIOS, my problem is there is no specific setting that says "PnP BIOS" there is a whole menu for it, and there is no just enabling, or disabling. And I had it working once with OSS, but I never could seem to resimulate the same setup. I will take another look for PnP in the BIOS though.

[DSwain]

well, here's what i've tried as of now-

root@MSHOME:~# insmod emu10k1
insmod: can't read 'emu10k1': No such file or directory
root@MSHOME:~# modprobe emu10k1
FATAL: Module emu10k1 not found.

and i'm positive that i have it inserted as a module. I'll go take a look at PnP....

[mdwatts]

Are you positive that you selected 'emu10k1' to be compiled as a module? Have a look in /lib/modules/<kernel version>/.

If you did select it as a module and the module is not somewhere in the above directory, then the kernel compile must have failed at some point.

[DSwain]

yeah, i found it. it is under /lib/modules/2.6.1/kernel/sound/pci/emu10k1
and the files are-
snd-emu10k1-synth.ko
snd-emu10k1.ko
maybe i should try snd-emu10k1 as the module? or, move the files into /lib/modules/2.6.1/kernel ?

[mdwatts]

Originally posted by DSwain

snd-emu10k1.ko

maybe i should try snd-emu10k1 as the module? or, move the files into /lib/modules/2.6.1/kernel ?

That would be correct. As root

modprobe snd-emu10k1

Leave those modules where they are or dependencies will be broken as the supporting modules will not be found.

As long as modules.dep (in /lib/modules/2.6.1) is up to date, all modules in there should be found when loading.

depmod -ae (as root to update that file)

[DSwain]

OK, well that definitly did something. after modprobe snd-emu10k1, it didn't generate an error, and lsmod shows-
snd_emu10k1 90884 0
snd_rawmidi 20928 1 snd_emu10k1
snd_pcm 88064 1 snd_emu10k1
snd_timer 22144 1 snd_pcm
snd_seq_device 6788 2 snd_emu10k1,snd_rawmidi
snd_ac97_codec 52228 1 snd_emu10k1
snd_page_alloc 9220 2 snd_emu10k1,snd_pcm
snd_util_mem 3392 1 snd_emu10k1
snd_hwdep 7680 1 snd_emu10k1
snd 45060 8 snd_emu10k1,snd_rawmidi,snd_pcm,snd_timer,snd_seq_ device,snd_ac97_codec,snd_util_mem,snd_hwdep
soundcore 6976 1 snd

now, i'm going to try the permissions again...

ok, well i tried permissions, and it didn't do it, soo is there some form of a config file i need to take a look at here? or, do i need to give permission to something else? it doesn't seem like i should cause i'm using root right now, but i would like to know (so sound starts going)

[mdwatts]

Originally posted by DSwain

now, i'm going to try the permissions again...

ok, well i tried permissions, and it didn't do it, soo is there some form of a config file i need to take a look at here? or, do i need to give permission to something else? it doesn't seem like i should cause i'm using root right now, but i would like to know (so sound starts going)

The successful soundcard module loading is a good sign.

So what permissions did you try and what is it complaining about?

Just in case... we do have loads of previous threads on soundcard device permissions. :)

[DSwain]

i tried what bandwidth_pig told me to try a while back-

chmod ugo+rwx /dev/dsp
chmod ugo+rwx /dev/mixer

which, i'll be honest, makes about 0 sense to me (at least the ugo+rwx part) so, maybe you could explain what the permissions?

[mdwatts]

Read the chmod manpage (man chmod) and also search around (Google for Linux) for 'linux file permissions' as you should find lots of tutorials/guides on the subject. Better than one of us (especially myself) trying to explain.

So what errors are you now getting for whatever you are attempting to do?

[DSwain]

well i'm working off the man page now, and its tough, but i've figured out what some of the letters mean (read, write, execute) so i tried "chmod rwx /dev/mixer" but that didn't work, i think i need to make it "chmod +rwx /dev/mixer"

ok, now i'm doing "chmod a+rwx /dev/mixer" and that seems to work, but i can't execute it, nor am i getting any sound still. are there other devices i need to change permission for?

[mdwatts]

The main one (it seems to be here at JL) is /dev/dsp.

/dev/dsp

/dev/mixer

/dev/audio

[DSwain]

ok, i've done all of those, and still no luck.... is there anything else i have to do? also, under Info Center, there is no soundcard listed, nor is their any under XMMS settings, or Kmix.

according to this-
http://alsa-project.org/alsa-doc/doc-php/template.php?company=Creative+Labs&card=Soundblaster+Audigy+Digital+Entertainment&chip=Audigy&module=emu10k1
it seems that there is more i need to do, so i may try that later/another time, unless anyone else can think of another idea to toss out.

[JamminJoeyB]

OK looks like you have gotten a step or two closer since I have been away. BTW FL was really nice this weekend (Sorry mdwatts I know it's freezing where you are at).

You have the modules loaded and no errors are generated. Now you have to make sure you un mute. I don't remember them, but they are in the docs and I know they have been posted on this board a number of times.

My lsmod for my slack9.1 install looks like this.

Module Size Used by Tainted: P
nvidia 1628576 11 (autoclean)
snd-pcm-oss 37252 1
snd-mixer-oss 11992 2 [snd-pcm-oss]
uhci 24496 0 (unused)
ehci-hcd 16872 0 (unused)
usbcore 58400 1 [uhci ehci-hcd]
natsemi 16288 1
snd-emu10k1 60212 3
snd-pcm 55904 0 [snd-pcm-oss snd-emu10k1]
snd-timer 13252 0 [snd-pcm]
snd-hwdep 4672 0 [snd-emu10k1]
snd-util-mem 1136 0 [snd-emu10k1]
snd-page-alloc 6004 0 [snd-emu10k1 snd-pcm]
snd-rawmidi 12512 0 [snd-emu10k1]
snd-seq-device 3920 0 [snd-emu10k1 snd-rawmidi]
snd-ac97-codec 37240 0 [snd-emu10k1]
snd 27460 0 [snd-pcm-oss snd-mixer-oss snd-emu10k1 snd-pcm snd-timer snd-hwdep snd-util-mem snd-rawmidi snd-seq-device snd-ac97-codec]
soundcore 3332 8 [snd]
emu10k1-gp 1352 0 (unused)
gameport 1452 0 [emu10k1-gp]
ohci1394 24200 0 (unused)
ieee1394 42436 0 [ohci1394]
ide-scsi 9424 0
agpgart 39576 3
bash-2.05b$


My XMMS is using the oss Driver so I am making the assumption here that my system is running ALSA and using the oss emulation. You could try changing the driver in alsa to see if it will play under a different driver. Just remember to unmute first.

[DSwain]

yeah, but i can't get to any mixer settings. it just won't show me any, and under KMIX it just acts as if there is no soundcard.

[DSwain]

for /dev/mixer, that one is their, and there is also mixer 0, mixer 1, mixer 2, and mixer 3. here's my lsmod (when i do modprobe snd-emu10k1)

Module Size Used by
snd_emu10k1 90884 0
snd_rawmidi 20928 1 snd_emu10k1
snd_pcm 88064 1 snd_emu10k1
snd_timer 22144 1 snd_pcm
snd_seq_device 6788 2 snd_emu10k1,snd_rawmidi
snd_ac97_codec 52228 1 snd_emu10k1
snd_page_alloc 9220 2 snd_emu10k1,snd_pcm
snd_util_mem 3392 1 snd_emu10k1
snd_hwdep 7680 1 snd_emu10k1
snd 45060 8 snd_emu10k1,snd_rawmidi,snd_pcm,snd_timer,snd_seq_ device,snd_ac97_codec,snd_util_mem,snd_hwdep
soundcore 6976 1 snd
ide_scsi 12356 0
vfat 12160 0
fat 42080 1 vfat
8139too 19584 0
mii 4096 1 8139too
crc32 3840 1 8139too
ntfs 111316 1

[bandwidth_pig]

Originally posted by DSwain
i tried what bandwidth_pig told me to try a while back-

chmod ugo+rwx /dev/dsp
chmod ugo+rwx /dev/mixer

which, i'll be honest, makes about 0 sense to me (at least the ugo+rwx part) so, maybe you could explain what the permissions?

Sure. ugo = user, group, and owner
rwx = read, write, and execute.

Did you ever try aumix?

[DSwain]

yeah, when i run aumix it just shows me nothing at all.

and yeah, i read the man pages, so i learned that one. god bless those man pages (now that i understand them better now) but i still REALLY don't know what to do. as far as i know, the only working driver for the Audigy LS is with OSS which isn't great quality, so i'm stumped. and none of the utilites in KDE are picking up on the card, any mixers, etc.... i don't know, maybe i'll take OSS for another swing...

[bandwidth_pig]

Frankly I'm scratching my head on this one too. Don't know what to say.

[JamminJoeyB]

Ok I found the commands I was looking for. I knew they were on this board.

amixer set Master 100 unmute
amixer set PCM 100 unmute


After you load your modules these will unmute the sound.

Did you do this after you modprobed?

If not open a terminal and give it a go. I think you need to be root to do this.

I also noticed that you weren't sure if pnp os was enabled in your bios. Any chance you could post you mobo specs. Maybe we can figure out what needs to be set to disable pnp os. Most mobos have it enabled by default.

[DSwain]

as i said, in the BIOS there is a menu "PCI & PnP Configuration" or something along those lines, but no setting that just enables or disables the settings. My mobo is the Soltek SL-75FRN2-RL (http://www.soltek.com.tw/soltek/product/products_all.php?isbn_st=SL-75FRN2-RL%2FSL-75FRN2-L) motherboard, nforce2 chipset, and the specs says AWARD BIOS, but i could have sworn it was Phonix, but lets go with specs and say AWARD.

oh, and no, i did not try those commands at all, i will give them a shot right away though.

here are the results for the command you reccomended-

root@MSHOME:~# modprobe snd-emu10k1
root@MSHOME:~# amixer set Master 100 unmute
amixer: Mixer attach default error: No such device
root@MSHOME:~# amixer set PCM 100 unmute
amixer: Mixer attach default error: No such device

i wonder if i'm missing a module that i have to load or something.

and for about my 5th edit of this post- i just gave the OSS beta a spin, and sound is working (at least on XMMS) so i'm glad for that much, but i'd rather not to have to deal with this poor licencing.

[JamminJoeyB]

Well I did some searching on your errors and only came up with a couple of posts around the net that reference them. They all point to another sound system being loaded.

Here is the search I did.

http://www.google.com/linux?hl=en&lr=&ie=ISO-8859-1&q=Mixer+attach+default+error%3A+No+such+device+

Not sure if this is going to be any help.

I also looked at your motherboad manual. The pnp area in the bios is either auto controled by the bios or manual. Have you tried setting the bios to manual? I'm about out of ideas here. Maybe another JLC member will have a better idea about your error.

[DSwain]

well, that just sparked an idea!

another sound module being loaded? i have onboard sound, actually, and for some reason it keeps trying to load itself when i compile the kernel, and i have it disabled on the system board.... as for that, i guess i can set it all to manual, but i'm tell ya, it works with OSS, just terribly, so I don't really see how it'll help. anythings worth a shot, though.

well, I'm really not sure. I sent out an email to Creative, asking about when an official driver will be released by them/if ever. hopefully, yes.

[JamminJoeyB]

Are you running the nforce driver from the nvidia web site?

I know that has a sound driver that comes with it. Maybe something in nforce driver is loading the nforce audio driver and that is why you audigy is not working under ALSA.

[DSwain]

well, no i never installed the nforce drivers with my board (it is an nforce chipset, though) and Creative that the only working Audigy LS driver at the moment is from OSS, and there are no planned official Creative drivers to be released.

[JamminJoeyB]

Ok, well I did spot something in the readme on nvidia's site about pnp.

System BIOS Configuration
Since the audio and network drivers work on the nForce chipset, these devices along with other motherboard devices are controlled by the System BIOS. If the installed drivers don't recognize hardware on your system, the problem may be your System BIOS's plug and play configuration. If your system BIOS expects the operating system to configure hardware devices, and your Linux kernel doesn't support ACPI-style configuration, you'll need to change your BIOS settings.

To view or change an Award-style system BIOS, reboot the machine, and press the Delete key. When you get a configuration screen, select "PnP/PCI Configurations" in that screen if "PNP OS Installed []" Has "Yes" choosen, change the selection to "No".

If your BIOS is Phoenix-style, use the F2 key instead of Delete, and scroll through the menus to find OS Type, and chose "Other". The exact details of System BIOS configuration vary with BIOS vendor, so the screens may not be exactly the same.

Warning: You should write down the original configuration of the BIOS before changing it. Changing your system BIOS configuration may adversely affect the operation of the system, and even make it unbootable.

Your board has the award bios according the link you posted earlier in the thread. So if this information is correct it should be easy to find and set.

[mdwatts]

Originally posted by DSwain
The only working Audigy LS driver at the moment is from OSS, and there are no planned official Creative drivers to be released.

I did a bit of searching around and it seems you are correct as the only drivers available are the OSS beta, so I would say you are out of luck for the time being.

Keep an eye on http://opensource.creative.com/ to see if they add LS support and with ALSA.