6 Feb
2005
6 Feb
'05
4:17 p.m.
I have a soundblaster live 24-bit card and am following the directions
at http://www.alsa-project.org/alsa-doc/doc-php/template.php?
company=Creative+Labs&card=Sound+Blaster+Live
+Value.&chip=emu10k1&module=emu10k1
I get to the last final command: Now insert the modules into the kernel.
modprobe snd-emu10k1;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss
and I get this error below. I do not have a /etc/modules.conf
or /etc/conf.modules. I do have a /etc/modprobe.conf file. I am brand
new to linux and am at a serious loss. I am not even sure if this is
the module I am really supposed to be installing for sb live 24-bit.
You help would be greatly appreciated.
Sincerely and without sound,
Angela
modprobe snd-card-emu10k1
FATAL: Module snd_card_emu10k1 not found.
[root@localhost services]# modprobe snd-emu10k1
WARNING: Error inserting snd_ac97_codec
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_ac97_codec
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_emu10k1
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/emu10k1/snd-emu10k1.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error running install command for snd_emu10k1
6 Feb
6 Feb
4:28 p.m.
Angela Day wrote:
Unknown symbol in module, or unknown parameter (see
dmesg)
The part in the '()' might be helpful?
--
Our enemies are innovative and resourceful - and so are we
They never stop thinking about new ways to harm our country and our people - and neither
do we.
-- George W. Bush
5:06 p.m.
OK, I found the dmesg file, but I did not see any error messages in it
or anything that referenced snd. What should I be looking for?
Thanks,
Angela
On Sun, 2005-02-06 at 14:59 -0600, Angela Day wrote:
Showing my ignorance, I didn't know what they
meant by dmesg. Could you
help me out there?
Thanks,
Angela
On Sun, 2005-02-06 at 12:26 -0800, Noah Roberts wrote:
Angela Day wrote:
Unknown symbol in module, or unknown parameter
(see dmesg)
The part in the '()' might be helpful?
5:16 p.m.
On Sunday 06 February 2005 22:06, Angela Day wrote:
OK, I found the dmesg file, but I did not see any
error messages in it
or anything that referenced snd. What should I be looking for?
dmesg isn't a file, at least not in the traditional way. It's a program
showing you a history of kernel-messages.
Just enter "dmesg" in a console and send the output...
Arnold
--
There is a theory which states that if ever anyone discovers exactly what the
Universe is for and why it is here, it will instantly disappear and be
replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.
-- Douglas Adams, The Restaurant at the End of the Universe
5:50 p.m.
This is what dmesg produced:
snd_seq: Unknown symbol snd_timer_open
snd_seq: disagrees about version of symbol snd_timer_start
snd_seq: Unknown symbol snd_timer_start
snd_seq: disagrees about version of symbol snd_timer_resolution
snd_seq: Unknown symbol snd_timer_resolution
snd_seq: disagrees about version of symbol snd_timer_pause
snd_seq: Unknown symbol snd_timer_pause
snd_seq: disagrees about version of symbol snd_unregister_device
snd_seq: Unknown symbol snd_unregister_device
snd_seq: disagrees about version of symbol snd_info_unregister
snd_seq: Unknown symbol snd_info_unregister
snd_seq: disagrees about version of symbol snd_register_device
snd_seq: Unknown symbol snd_register_device
snd_seq_midi_event: Unknown symbol snd_seq_expand_var_event
snd_seq_oss: Unknown symbol snd_seq_kernel_client_enqueue
snd_seq_oss: disagrees about version of symbol snd_info_register
snd_seq_oss: Unknown symbol snd_info_register
snd_seq_oss: Unknown symbol snd_seq_set_queue_tempo
snd_seq_oss: disagrees about version of symbol
snd_info_create_module_entry
snd_seq_oss: Unknown symbol snd_info_create_module_entry
snd_seq_oss: Unknown symbol snd_seq_delete_kernel_client
snd_seq_oss: Unknown symbol snd_seq_kernel_client_dispatch
snd_seq_oss: disagrees about version of symbol snd_info_free_entry
snd_seq_oss: Unknown symbol snd_info_free_entry
snd_seq_oss: disagrees about version of symbol snd_seq_root
snd_seq_oss: Unknown symbol snd_seq_root
snd_seq_oss: Unknown symbol snd_seq_kernel_client_enqueue_blocking
snd_seq_oss: disagrees about version of symbol snd_unregister_oss_device
snd_seq_oss: Unknown symbol snd_unregister_oss_device
snd_seq_oss: Unknown symbol snd_verbose_printk
snd_seq_oss: disagrees about version of symbol snd_register_oss_device
snd_seq_oss: Unknown symbol snd_register_oss_device
snd_seq_oss: disagrees about version of symbol
snd_seq_device_register_driver
snd_seq_oss: Unknown symbol snd_seq_device_register_driver
snd_seq_oss: Unknown symbol snd_midi_event_free
snd_seq_oss: Unknown symbol snd_midi_event_no_status
snd_seq_oss: Unknown symbol snd_seq_event_port_detach
...
snd_emu10k1: Unknown symbol snd_ctl_new1
snd_emu10k1: disagrees about version of symbol snd_ctl_remove_id
snd_emu10k1: Unknown symbol snd_ctl_remove_id
snd_emu10k1: disagrees about version of symbol snd_card_new
snd_emu10k1: Unknown symbol snd_card_new
snd_emu10k1: disagrees about version of symbol snd_pcm_lib_malloc_pages
snd_emu10k1: Unknown symbol snd_pcm_lib_malloc_pages
snd_emu10k1: disagrees about version of symbol snd_pcm_lib_ioctl
snd_emu10k1: Unknown symbol snd_pcm_lib_ioctl
snd_emu10k1: disagrees about version of symbol snd_pcm_lib_free_pages
snd_emu10k1: Unknown symbol snd_pcm_lib_free_pages
snd_emu10k1: disagrees about version of symbol snd_hwdep_new
snd_emu10k1: Unknown symbol snd_hwdep_new
snd_emu10k1: disagrees about version of symbol snd_ctl_notify
snd_emu10k1: Unknown symbol snd_ctl_notify
snd_emu10k1: disagrees about version of symbol snd_pcm_set_ops
snd_emu10k1: Unknown symbol snd_pcm_set_ops
snd_emu10k1: disagrees about version of symbol snd_timer_new
snd_emu10k1: Unknown symbol snd_timer_new
snd_emu10k1: disagrees about version of symbol
snd_pcm_hw_constraint_list
snd_emu10k1: Unknown symbol snd_pcm_hw_constraint_list
snd_emu10k1: disagrees about version of symbol snd_device_new
snd_emu10k1: Unknown symbol snd_device_new
snd_emu10k1: disagrees about version of symbol snd_pcm_sgbuf_ops_page
snd_emu10k1: Unknown symbol snd_pcm_sgbuf_ops_page
snd_emu10k1: disagrees about version of symbol snd_rawmidi_new
snd_emu10k1: Unknown symbol snd_rawmidi_new
snd_emu10k1: disagrees about version of symbol
snd_pcm_hw_constraint_integer
snd_emu10k1: Unknown symbol snd_pcm_hw_constraint_integer
snd_emu10k1: disagrees about version of symbol snd_rawmidi_set_ops
snd_emu10k1: Unknown symbol snd_rawmidi_set_ops
snd_emu10k1: disagrees about version of symbol
snd_pcm_lib_preallocate_pages
snd_emu10k1: Unknown symbol snd_pcm_lib_preallocate_pages
snd_emu10k1: disagrees about version of symbol
snd_pcm_lib_preallocate_free_for_all
snd_emu10k1: Unknown symbol snd_pcm_lib_preallocate_free_for_all
snd_emu10k1: disagrees about version of symbol snd_pcm_period_elapsed
snd_emu10k1: Unknown symbol snd_pcm_period_elapsed
snd_emu10k1: Unknown symbol snd_ac97_write
I have no idea how to respond to this information. Any help would be
greatly appreciated.
Angela
On Sun, 2005-02-06 at 22:16 +0100, Arnold Krille wrote:
On Sunday 06 February 2005 22:06, Angela Day wrote:
OK, I found the dmesg file, but I did not see any
error messages in it
or anything that referenced snd. What should I be looking for?
dmesg isn't a file, at least not in the traditional way. It's a program
showing you a history of kernel-messages.
Just enter "dmesg" in a console and send the output...
Arnold
6:03 p.m.
On Sunday 06 February 2005 22:50, Angela Day wrote:
This is what dmesg produced:
<snip>
snd_emu10k1: disagrees about version of symbol
snd_pcm_period_elapsed
snd_emu10k1: Unknown symbol snd_pcm_period_elapsed
snd_emu10k1: Unknown symbol snd_ac97_write
I have no idea how to respond to this information. Any help would be
greatly appreciated.
This seems to me (I am not an alsa expert) as if the version of the running
kernel and the version of the kernel these modules where build for doesn't
match.
If you compiled the alsa-driver-modules yourself, are you sure /usr/src/linux
pointed to the sources of the running kernel?
Arnold
--
There is a theory which states that if ever anyone discovers exactly what the
Universe is for and why it is here, it will instantly disappear and be
replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.
-- Douglas Adams, The Restaurant at the End of the Universe
6:50 p.m.
I did not compile them myself. The instructions said that if I had
soundcore then I did not need to recompile my kernel. Did I
misunderstand the instructions? The instructions only said to unpack
the packages, not recompile them. I followed the instructions verbatim.
Should I have picked a different version of the packages?
Thanks,
Angela
On Sun, 2005-02-06 at 23:03 +0100, Arnold Krille wrote:
If you compiled the alsa-driver-modules yourself, are
you
sure /usr/src/linux
pointed to the sources of the running kernel?
6:53 p.m.
You are right. I did compile them with /configure;make;make install
I wrote before I thought. How do I see if /usr/src/linux pointed to the
sources of the running kernel?
Thanks,
Angela
On Sun, 2005-02-06 at 23:03 +0100, Arnold Krille wrote:
On Sunday 06 February 2005 22:50, Angela Day wrote:
This is what dmesg produced:
<snip>
snd_emu10k1: disagrees about version of symbol
snd_pcm_period_elapsed
snd_emu10k1: Unknown symbol snd_pcm_period_elapsed
snd_emu10k1: Unknown symbol snd_ac97_write
I have no idea how to respond to this information. Any help would be
greatly appreciated.
This seems to me (I am not an alsa expert) as if the version of the running
kernel and the version of the kernel these modules where build for doesn't
match.
If you compiled the alsa-driver-modules yourself, are you sure /usr/src/linux
pointed to the sources of the running kernel?
Arnold 
7:06 p.m.
Angela Day schrieb:
I have a soundblaster live 24-bit card and am following
the directions
at http://www.alsa-project.org/alsa-doc/doc-php/template.php?
company=Creative+Labs&card=Sound+Blaster+Live
+Value.&chip=emu10k1&module=emu10k1
i had this soundcard (sound blaster live 24 bit).
this card is _NOT_ based on the emu10k1 chipset,
like the original sb live.
it is based on a chip thats like the one found on the audigy LS cards.
you may have some success with latest alsa cvs, whith an driver
called somethin like ca0106
you may also look at http://www.alsa-project.org/~james/alsa-driver/
and wait for lee revell.
he seems to be an expert on this topic.
-tom
I get to the last final command: Now insert the modules
into the kernel.
modprobe snd-emu10k1;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss
and I get this error below. I do not have a /etc/modules.conf
or /etc/conf.modules. I do have a /etc/modprobe.conf file. I am brand
new to linux and am at a serious loss. I am not even sure if this is
the module I am really supposed to be installing for sb live 24-bit.
You help would be greatly appreciated.
Sincerely and without sound,
Angela
modprobe snd-card-emu10k1
FATAL: Module snd_card_emu10k1 not found.
[root@localhost services]# modprobe snd-emu10k1
WARNING: Error inserting snd_ac97_codec
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_ac97_codec
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_emu10k1
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/emu10k1/snd-emu10k1.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error running install command for snd_emu10k1
7:27 p.m.
On Mon, 2005-02-07 at 00:06 +0100, tommy wrote:
you may also look at
http://www.alsa-project.org/~james/alsa-driver/
and wait for lee revell.
<rant>
Please, please, file a Fedora bug report. We are really being inundated
with support requests from FC3 users whose sound doesn't work for a
variety of stupid reasons. This is 2005, inexperienced Linux users
should not still have to be building drivers from source to get their
sound to work. I guarantee you if Red Hat made the user experience vis
a vis sound a priority then these problems would magically go away
overnight. For example I can't remember the last time a SuSE user
showed up on LAU with inexplicably non working sound.
</rant>
On a more useful note maybe you can get newer ALSA RPMS from rawhide or
something. You do need the ca0106 driver for the 24 bit SB live.
Lee
11:06 p.m.
Lee,
Thanks, I agree completely. People complain about microsoft, but,
please... No casual user should be expected to traverse this mess just
to install a SB card in Linux. I am not a hardware person or a linux
administrator, as you can tell :)
I will look into the rawhide and ca0106. Wish me lots of luck.
Angela
On Sun, 2005-02-06 at 18:26 -0500, Lee Revell wrote:
On Mon, 2005-02-07 at 00:06 +0100, tommy wrote:
you may also look at
http://www.alsa-project.org/~james/alsa-driver/
and wait for lee revell.
<rant>
Please, please, file a Fedora bug report. We are really being inundated
with support requests from FC3 users whose sound doesn't work for a
variety of stupid reasons. This is 2005, inexperienced Linux users
should not still have to be building drivers from source to get their
sound to work. I guarantee you if Red Hat made the user experience vis
a vis sound a priority then these problems would magically go away
overnight. For example I can't remember the last time a SuSE user
showed up on LAU with inexplicably non working sound.
</rant>
On a more useful note maybe you can get newer ALSA RPMS from rawhide or
something. You do need the ca0106 driver for the 24 bit SB live.
Lee
9:40 p.m.
On Mon, 2005-02-07 at 00:06 +0100, tommy wrote:
you may also look at
http://www.alsa-project.org/~james/alsa-driver/
and wait for lee revell.
he seems to be an expert on this topic.
Actually James is the expert on the ca0106. I don't know much about it,
other than that James did a remarkable job reverse engineering it.
I really don't know what Creative is thinking with this crap. The #1
killer app for the emu10k1/audigy was the hardware accelerated 3d audio
aspect. Remember how mind blowing the original sblive was compared to
the previous generation of sound cards? Compare the sound in Doom to an
EAX game from a year or two later. Ever since they have been selling
bazillions of them to gamers. The ca0106 looks like a winmodem or
something, where they took the emu10k1 and gutted it and left the bare
minimum of (cheap!) hardware so they can implement all the emu10k1/2
features in software.
Considering how much can be done with the relatively feeble DSP in the
original emu10k1, if Moore's Law applied to DSPs then we should all be
able to buy $50 sound cards with multiple outboard DSP cores and run 100
reverbs and harmonizers and real time pitch correction at the same time.
I still maintain there's a lot of money to be made by someone who
designs a soundcard with the exact right balance of outboard DSP
horsepower, decent quality codecs, price point and of course open
architecture.
Who knows, maybe if the open source video card project succeeds then
someone will step up to fund the open sound card project...
Lee
10:58 p.m.
Tom,
Thanks for pointing me in the right direction.
Angela
On Mon, 2005-02-07 at 00:06 +0100, tommy wrote:
Angela Day schrieb:
I have a soundblaster live 24-bit card and am
following the directions
at http://www.alsa-project.org/alsa-doc/doc-php/template.php?
company=Creative+Labs&card=Sound+Blaster+Live
+Value.&chip=emu10k1&module=emu10k1
i had this soundcard (sound blaster live 24 bit).
this card is _NOT_ based on the emu10k1 chipset,
like the original sb live.
it is based on a chip thats like the one found on the audigy LS cards.
you may have some success with latest alsa cvs, whith an driver
called somethin like ca0106
you may also look at http://www.alsa-project.org/~james/alsa-driver/
and wait for lee revell.
he seems to be an expert on this topic.
-tom
I get to the last final command: Now insert the
modules into the kernel.
modprobe snd-emu10k1;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss
and I get this error below. I do not have a /etc/modules.conf
or /etc/conf.modules. I do have a /etc/modprobe.conf file. I am brand
new to linux and am at a serious loss. I am not even sure if this is
the module I am really supposed to be installing for sb live 24-bit.
You help would be greatly appreciated.
Sincerely and without sound,
Angela
modprobe snd-card-emu10k1
FATAL: Module snd_card_emu10k1 not found.
[root@localhost services]# modprobe snd-emu10k1
WARNING: Error inserting snd_ac97_codec
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_ac97_codec
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_emu10k1
(/lib/modules/2.6.10-1.760_FC3/kernel/sound/pci/emu10k1/snd-emu10k1.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error running install command for snd_emu10k1
7322
days inactive
7322
days old
linux-audio-user@lists.linuxaudio.org
13 comments
5 participants
participants (5)
-
Angela Day -
Arnold Krille -
Lee Revell -
Noah Roberts -
tommy