sound blaster live/FC4

ericb · 09-12-2005, 08:50 PM

ok i have already posted this in the hardware section, and another user (Lnx805) referred me to this forum, and i looked up his problem, and didn't help. when i try to run alsaconf, i scroll down to my card, click enter, then i configured that. after that was done, i click no more cards, and then this came up in konsole

Code:

Loading driver:
Starting sound driver: snd-intel8x0 WARNING: Error inserting snd_page_alloc (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd-page-alloc.ko): Invalid module format
WARNING: Error inserting snd (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd.ko): Invalid module format
WARNING: Error inserting snd_timer (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd-timer.ko): Invalid module format
WARNING: Error inserting snd_page_alloc (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd-page-alloc.ko): Invalid module format
WARNING: Error inserting snd (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd.ko): Invalid module format
WARNING: Error inserting snd_timer (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd-timer.ko): Invalid module format
FATAL: Error inserting snd_pcm (/lib/modules/2.6.12-1.1447_FC4/updates/sound/acore/snd-pcm.ko): Invalid module format
WARNING: Error running install command for snd_pcm
WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.12-1.1447_FC4/updates/sound/pci/ac97/snd-ac97-codec.ko): Invalid module format
FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.12-1.1447_FC4/updates/sound/pci/snd-intel8x0.ko): Invalid module format
done
Setting the PCM volume to 100% and the Master output volume to 50%
amixer: Mixer attach default error: No such file or directory
Could not initialize the mixer, the card was probably
not detected correctly.

i disabled the old on-board card in bios. also when i start up the computer, this message comes up

Sound server informational message:
Error while initializing the sound driver:
device /dev/dsp can't be opened (No such file or directory)
The sound server will continue, using the null output device.

keep in mind, i am pretty new to this, so if i say something that doesn't really make any sense, or i did something completely stupid(haha) please do not get pissy at me.

thank you.

farpoint · 09-15-2005, 12:05 PM

Hi. I would suggest posting your problem to the alsa-user list. http://lists.sourceforge.net/lists/listinfo/alsa-user . You will have to register. I have seen quite a few posts to the list about intel8x0 problems, but mainly on laptops. Send them plenty of info as below.
Distro: Obviously FC4
Kernel: uname -r for this
Alsa version: cat /proc/asound/version
Cards: cat /proc/asound/cards . If none shown, output of /sbin/lspci ( as root)
Devices: cat /proc/asound/devices
Output of lsmod for loaded modules: /sbin/lsmod (as root)
And obviously the output you posted to the LQ forum

The message you got when booted up is normal if Alsa hasn't been loaded. Incidentally did the sounds work with the onboard soundcard?
Also. Are you dual booting with Windows. If so did the sounds work ok with the new card? By the way. Linux should work with both
your cards enabled. Windows from my experience is a bit more picky, like, one or the other.

If you are considering using music apps on your machine with Fedora core 1, 2, 3, or 4, planetccrma is the place to go.
http://ccrma.stanford.edu/planetccrma/software . They have kernels specifically setup for music applications, loads of music apps,
and help for setting up problems on they're mailing list. All the best. Nigel. aka farpoint

ericb · 09-16-2005, 11:02 AM

now i finally switched to slackware 10.1 (i was planning on doing that, but i did it alittle sooner than i thought). and i'm getting pretty much the same thing. should i do the same?

farpoint · 09-16-2005, 12:35 PM

Hi. It looks like it is a driver bug, and I'd have thought that FC4 being so up to date, would have had no
problems with the driver if there wasn't a bug. I had some problems setting up Alsa on FC1 and FC2, but FC3
that I've just installed, has set Alsa up with no problems apart from setting volumes on alsamixer. I suppose
I was favoured, having bought an Audigy2 soundblaster using the emu10k1 driver for Win XP, and then finding it
was well supported on Linux. On Slackware 10.0 I initially had problems with no sound. All I got from alsaconf
was a big list of cards, and none of them worked, so I went to audioslack and got a multimedia kernel. Now
when running alsaconf I just got 2 options, my soundcard, and I think the other is something like, configure
your own card. I know from the Alsa list that there are problems with some of the soundblaster live cards.
Creative have such a big range of cards. It is a really good idea to consult, for instance the Alsa list,
to find out if the card you're considering is supported. I would certainly suggest that you post to the Alsa
list giving them all the info, and also ask for suggestions for supported cards. Cards using the emu10k1
driver are well supported. The rest I'm not sure of. At least you've got a PC and can change the card. With
a laptop your stuck with whats installed on the mobo. Regarding Slackware 10.1, I don't know if Alsa support
has improved. You may still have to get a multimedia kernel from audioslack. http://www.audioslack.com .
Luke Yelavich has some good music apps also on the site. If you decide to install the mm kernel, make sure
that you install slapt-get which is the updating program. There is a link on Lukes site for it. This with a
simple, slapt-get --update and then, slapt-get --dist-upgrade will update your slackware install, audioslack,
and also slapt-get & gslapt the GUI for slapt-get. Let me know how you get on. I'll probably see you on the
Alsa-user list. Nigel. aka farpoint.