Sblive+kernel 2.6.12 no sound

chuckler · 03-22-2006, 03:57 PM

..i recently compiled a 2.6.12 kernel and it has alsa already in it apparently...
my sound card is a creative SB live! 5.1... i have used the emu10k1 module and it had worked like a charm in the previous kernel 2.4.26, slackware 10.0
i currently use slackware 10.0 with 2.6.12.

lsmod gives just the following uotput which looks a little sparse to me.

Module Size Used by
nvidia_agp 6428 1
amd74xx 12380 0 [permanent]
emu10k1_gp 3136 0
gameport 12744 2 emu10k1_gp
nvidia 4085872 12

alsactl --v
alsactl version 1.0.11rc2

i am unable to modprobe emu10k1... says module not found.

lspci gives the following about the card

01:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
Subsystem: Creative Labs SBLive! 5.1 Digital Model SB0220
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d000 [size=32]
Capabilities: [dc] Power Management version 1

cat /proc/pci | grep EMU10k1
Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 10).

..been googling and Lq.org-ing from sometime... can't find an answer anywhere..

any help gladly appreciated.

Brian1 · 03-22-2006, 04:49 PM

Just to make sure you have included emu10k1 as a module and not compiled in the kernel.
Run the command alsamixer and see if it displays volume levels and make sure volume levels for main and pcm are up and also that they are not muted. There will be a MM if muted.

Brian1

chuckler · 03-22-2006, 07:28 PM

when i run alsamixer i get
alsamixer: function snd_ctl_open failed for default: No such device

what does this mean?

MannyNix · 03-22-2006, 09:25 PM

Hello, i also had this problem, can't remember how i solved it but here's part of my kernel and configs in hope it helps somehow
uname -r 2.6.15.4
lsmod:

Code:

snd_emu10k1            93092  1
snd_rawmidi            17568  1 snd_emu10k1
snd_ac97_codec         80032  1 snd_emu10k1
snd_pcm                67720  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer              18052  2 snd_emu10k1,snd_pcm
snd_ac97_bus            2048  1 snd_ac97_codec
snd_page_alloc          8072  2 snd_emu10k1,snd_pcm
snd_util_mem            3456  1 snd_emu10k1
snd_hwdep               6688  1 snd_emu10k1
snd                    39908  10 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
soundcore               6880  1 snd
emu10k1_gp              2944  0
gameport               10760  2 emu10k1_gp

alsactl version 1.0.9a
lspci:

Code:

02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
02:02.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 06)

kernel config:

Code:

CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=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_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

Code:

# PCI devices
#
# 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_CS46XX is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set

rickh · 03-22-2006, 09:29 PM

Is it insulting to suggest that a Slackware person might not have run alsaconf?

chuckler · 03-23-2006, 10:16 AM

well i thought i mentioned it but looks like i didn't... alsaconf does not detect my card either. but lspci does.
had compiled this kernel long back could not use it due to stability issues with nvidia drivers.

cwwilson721 · 03-23-2006, 10:19 AM

Quote:

Originally Posted by chuckler

well i thought i mentioned it but looks like i didn't... alsaconf does not detect my card either. but lspci does.
had compiled this kernel long back could not use it due to stability issues with nvidia drivers.

Sounds more like you forgot to include the sound card modules in your compile

jong357 · 03-23-2006, 10:32 AM

I'm pretty sure Pat used to compile sound modules directly from the kernel at one point in time but then switched to using alsa-driver... IMO, your best bet is to ditch ALL sound related things from the kernel except for the VERY top level option which will be "<M> Sound card support".. Leave it as a module. recompile your kernel and then boot into it.

Download and compile alsa-driver yourself. Make sure the version matches your alsa-{lib,utils,oss} packages. Configure alsa-driver with:

Code:

./configure --with-cards=emu10k1 --with-sequencer=yes
make
make install

After that, move your alsa-driver source directory to /usr/src
then:

Code:

alsaconf
alsamixer (adjust levels then press ESC)
alsactl store

Now it should work. These forums were plauged by kernel/sound related issues for the longest time. I think Pat got the hint and started using alsa-driver and ever since, these kind of posts have pretty much dissapeared...

chuckler · 03-23-2006, 11:42 AM

hah finally solved it... on a whim recompiled the kernel with

as root:
cd /usr/src/linux
make menuconfig
make dep clean modules modules_install bzImage

then
depmod -a

then it loaded automatically on the reboot.. now sound works flawlessly..
looks like i had forgotten to compile the kernel module for the sound..
there was the exact emu10k1 module listed for sblive! in menuconfig..

everything went like clockwork.

thanks everyone...
the replies were quick.

chuckler · 03-23-2006, 11:44 AM

jong357: your method looks a lot better since the kernel image would be far less bloated i suppose.. so is it better to have the drivers a module in the kernel or load it later?

jong357 · 03-23-2006, 11:17 PM

Well, it's really the same no matter how you work it. The only way your kernel would be more 'bloated' is if you were to start building sound options into the kernel verses using a module.. ie- <*> instead of <M>.... If you are using all modules in the kernel for the sound section, then they are near identical to the ones that will be installed from the alsa-driver package and there is no extra size on your kernel. The modules live in the same /lib/modules/$(uname -r) directory regardless of whether they are from the kernel or alsa-driver.

If you look at your first post, the alsa version in your kernel is 1.0.11rc2 whereas Pat is using version 1.0.9 (I believe) with regards to alsa-{lib,utils,oss}... Probably not a big deal and as you've said, it works... I just like consistency with version numbers and all alsa packages.

If you do it like I suggested, anytime you compile a new kernel of the same version, you can just cd into /usr/src/alsa-driver-123 and do a 'make install' again. No fuss.

Pat uses alsa-driver on slack so one might suggest it's the proper way to do it. However you want. However, if you install a slackware alsa-driver package on top of your custom compiled kernel, all your hard work with the sound section gets wiped anyway...

Might as well just stick with the alsa-driver package...

EDIT: Wow.. Just checked the changelog. Pat is getting wild and crazy with alsa-driver-1.0.11rc3... A release canidate... I find that odd..