New Soundblaster Live Card... Help needed!
 

Hi all,

Up until now i've been using the onboard sound on my motherboard. A friend (who isn't around at the mo) helped me set it all up and my music was playing fine with the ALSA drivers.
I bought a new soundblaster live 5.1 digital card today and have installed it in my box, but am so far having no luck getting any sound through it.
I uninstalled the alsa drivers, alsa lib and alsa utils, configured, compiled and installed all 3 again, following the instructions on this page: http :// www . alsa-project. org / alsa-doc/doc-php/template.php?company=Creative+Labs&card=Soundblaster+Live&chip=EMU10K1&module=emu10k1 (sorry i had to put spaces in that url but it wouldn't let me post it because i have less than 5 posts. :( )
using the configure line: ./configure --with-cards=emu10k1 --with-sequencer=yes

I then ran alsaconf, which picked up my onboard legacy sound and my new emu10k1 soundblaster card, so i let it update my /etc/modules.conf file and it said that my new soundcard was ready to use.

But, when i run alsamixer, it still says:

Card: VIA 8235
Chip: C-Media Electronics CMI9738
Item: Master

at the top and i get no sound when i try and play anything.

Any ideas what i might need to do?

Thanks a lot!

Sam Holman.

Can you disable the onboard sound in the BIOS?

true you neeed to first probably disable the onboard sound, then when configuring alsa i think you might need to specify that it is a 5.1 card?, if u cant disable onboard sound u will need to probably specify all the irq addresses for the sb live, i dont know the commands but look in the docs. but the simpilist is to diable the on board sound to prevent the alsa drivers from detecting the cmi 9738.

it works cause i also have the cmi 9738 on my k7s5a that i have disabled and am using a sb live card. also remember to diable the gameport and midi parts of the onboard sound too, although i though i read somewhere that full midi support isn't yet offered for the emu10k1 driver.

Hi again, i hadn't thought of disabling it in the bios, will probably have a look later out of interest.
But, it started working after a reboot, so something must have gone through and set it right on startup. Would have been nice to know what script it was which sorted it, but never mind.