Re: Creative SoundBlaster Live! - how to get it working?
robin wrote:
> michael wrote:
>
>> robin wrote:
>>
>>> michael wrote:
>>>
>>>> robin wrote:
>>>>
>>>>> michael wrote:
>>>>>
>>>>>> michael wrote:
>>>>>>
>>>>>>> robin wrote:
>>>>>>>
>>>>>>>> michael wrote:
>>>>>>>>
>>>>>>>>> I've looked but can't find anything that definitely explains
this, so...
>>>>>>>>>
>>>>>>>>> I have a new Creative SoundBlaster Live! 24 bit sound card in
my machine (dual Xeon box). The card works - heard it when booted WinXP.
However, I can make no headway on getting sounds from it when I boot in
to my Linux
>>>>>>>>> partition. I have done a 'apt-get install alsa' but that
doesn't seem to have changed anything. All solutions are most welcome!
And here's what I
>>>>>>>>> believe is sufficient information for people to answer this
for me! TIA.
>>>>>>>>>
>>>>>>>>> michael@ratty:~$ uname -a;sudo lsmod
>>>>>>>>> Linux ratty 2.4.27-1-686-smp #1 SMP Fri Sep 3 06:34:36 UTC
2004 i686 GNU/Linux
>>>>>>>>> Module Size Used by Not tainted
>>>>>>>>> floppy 52184 0 (autoclean)
>>>>>>>>> soundcore 4420 0 (autoclean)
>>>>>>>>> input 3872 0 (autoclean)
>>>>>>>>> lp 6916 0
>>>>>>>>> parport 27944 0 [lp]
>>>>>>>>> af_packet 14472 1 (autoclean)
>>>>>>>>> uhci 27100 0 (unused)
>>>>>>>>> hw_random 2876 0 (unused)
>>>>>>>>> i810_rng 2788 0 (unused)
>>>>>>>>> ehci-hcd 18924 0 (unused)
>>>>>>>>> usbcore 65804 1 [uhci ehci-hcd]
>>>>>>>>> ide-scsi 10192 0
>>>>>>>>> scsi_mod 97732 1 [ide-scsi]
>>>>>>>>> e1000 68844 1
>>>>>>>>> ide-cd 31328 0
>>>>>>>>> cdrom 30080 0 [ide-cd]
>>>>>>>>> rtc 7112 0 (autoclean)
>>>>>>>>> ext3 84748 7 (autoclean)
>>>>>>>>> jbd 46200 7 (autoclean) [ext3]
>>>>>>>>> ide-detect 288 0 (autoclean) (unused)
>>>>>>>>> piix 9128 2 (autoclean)
>>>>>>>>> ide-disk 16960 8 (autoclean)
>>>>>>>>> ide-core 112184 8 (autoclean) [ide-scsi
ide-cd ide-detect piix ide-disk]
>>>>>>>>> unix 16784 221 (autoclean)
>>>>>>>>> michael@ratty:~$
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Try running alsaconf to set up the alsa sound modules.
>>>>>>>>
>>>>>>>> Robin
>>>>>>>>
>>>>>>>>
>>>>>>> That comes up with:
>>>>>>> No supported PnP or PCI card found.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I should also have said the console gets the message:
>>>>>> chael@ratty:/usr/src$ sudo alsaconf
>>>>>> modinfo: snd: no module by that name found
>>>>>> modinfo: snd: no module by that name found
>>>>>> modinfo: snd: no module by that name found
>>>>>>
>>>>>>
>>>>> Not sure which module it is so check
http://www.alsa-project.org/alsa-doc/ soundcard matrix and then
>>>>> e.g.
>>>>>
>>>>> modprobe snd-ens1371
>>>>>
>>>>> replacing, if necessary, snd-ens1371 with the correct module.
>>>>> If there are any error messages post them here.
>>>>> Also which kernel version are you running as there was an issue
with some 2.6 kernels with OSS grabbing the sound card before Alsa.
>>>>>
>>>>
>>>> Okay, it seems to be module emu10k1 that I require but I get:
>>>>
>>>> michael@ratty:/usr/src$ sudo modprobe emu10k1
>>>>
/lib/modules/2.4.27-1-686-smp/kernel/drivers/sound/emu10k1/emu10k1.o:
init_module: No such device
>>>> Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
>>>> You may find more information in syslog or the output from dmesg
>>>>
/lib/modules/2.4.27-1-686-smp/kernel/drivers/sound/emu10k1/emu10k1.o:
insmod
/lib/modules/2.4.27-1-686-smp/kernel/drivers/sound/emu10k1/emu10k1.o failed
>>>>
/lib/modules/2.4.27-1-686-smp/kernel/drivers/sound/emu10k1/emu10k1.o:
insmod emu10k1 failed
>>>>
>>>> michael@ratty:/usr/src$ dmesg|tail
>>>> Floppy drive(s): fd0 is 1.44M
>>>> FDC 0 is a National Semiconductor PC87306
>>>> Creative EMU10K1 PCI Audio Driver, version 0.20, 06:37:07 Sep 3 2004
>>>> isapnp: Scanning for PnP cards...
>>>> isapnp: No Plug & Play device found
>>>> isapnp: Scanning for PnP cards...
>>>> isapnp: No Plug & Play device found
>>>> isapnp: Scanning for PnP cards...
>>>> isapnp: No Plug & Play device found
>>>> Creative EMU10K1 PCI Audio Driver, version 0.20, 06:37:07 Sep 3 2004
>>>> michael@ratty:/usr/src$ uname -a
>>>> Linux ratty 2.4.27-1-686-smp #1 SMP Fri Sep 3 06:34:36 UTC 2004
i686 GNU/Linux
>>>> michael@ratty:/usr/src$
>>>>
>>>>
>>>> Thanks for helping me through this!
>>>> Michael
>>>>
>>>>
>>> See
http://www.mail-archive.com/debian-user@lists.debian.org/msg120316.html
for 2.6 details.
>>> Do you have alsa-modules-2.4.27-1-686-smp installed?
>>>
>>
>> It's been a long day (that's my excuse & it also means I can go
shortly!) but
>>
>> a) isn't "2.6 details" irrelevant to me since I'm using 2.4.27?
>> b) err, how do I find what modules I have installed? Do you mean
using 'lsmod'? There's no alsa there
>>
>> Michael
>>
>>
> Sorry I meant the alsa-modules-2.4.27-1-686-smp deb package
installed. It is separate from the alsa-base package.
> Run
>
> dpkg -S alsa-mod*
> alsa-modules-2.4.25-1-multimedia-k7:
/usr/share/doc/alsa-modules-2.4.25-1-multimedia-k7
> alsa-modules-2.4.27-1-multimedia-k7:
/usr/share/doc/alsa-modules-2.4.27-1-multimedia-k7
>
> means I have 2 modules packages installed to match my installed kernels.
> Do you use synaptic or aptitude or apt-get to load new packages? If
apt-get then
>
> apt-get install alsa-modules-2.4.27-1-686-smp
>
> should do the biz. Either it will install the package or say it is
already installed.
I didn't have it installed, but got ''unresolved symbols'' error when
tried to install it, viz:
michael@ratty:~/src$ sudo apt-get install alsa-modules-2.4.27-1-686-smp
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
kernel-pcmcia-modules-2.4.27-1-686-smp
The following NEW packages will be installed:
alsa-modules-2.4.27-1-686-smp
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1239kB of archives.
After unpacking 3453kB of additional disk space will be used.
Get:1 http://ftp.uk.debian.org testing/main
alsa-modules-2.4.27-1-686-smp 1.0.6a +5 [1239kB]
Fetched 1239kB in 4s (271kB/s)
Selecting previously deselected package alsa-modules-2.4.27-1-686-smp.
(Reading database ... 96662 files and directories currently installed.)
Unpacking alsa-modules-2.4.27-1-686-smp (from
.../alsa-modules-2.4.27-1-686-smp_ 1.0.6a+5_i386.deb) ...
Setting up alsa-modules-2.4.27-1-686-smp (1.0.6a+5) ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686-smp/updates/alsa/snd -pdaudiocf.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686-smp/updates/alsa/snd -vx-cs.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686-smp/updates/alsa/snd -vxp440.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-1-686-smp/updates/alsa/snd -vxpocket.o
> Can we carry on tomorrow as the matchsticks propping up my eyelids
are starting to split:)
That's no problem - it's very good of you to help so much!
Michael
Reply to: