alsa, modprobe, lib/modules, and a turtle beach santa cruz sound card equals one confusing problem.

alsa, modprobe, lib/modules, and a turtle beach santa cruz sound card equals one confusing problem.

Post by chester cha » Sun, 29 Sep 2002 09:09:23



- I installed red hat 7.3 with kernel version 2.4.18.  
- I have a turtle beach santa cruz sound card.  
- I could get sound out of the analog/headphone jack by running
sndconfig, the  problem is, I need digital output to use my speakers.
- I ran ./configure, make, make install, snddevices with the alsa
driver 0.9 rc3.
- All of my existing modules were in /lib/modules/2.4.18-3.  More
specifically, the defalt sound modules are in
/lib/modules/2.4.18-3/kernel/drivers/sound.  However, alsa created the
directory /lib/modules/2.4.18 and put its modules in
/lib/modules/2.4.18/misc
- When I do a modprobe or modinfo, it doesn't seem to find any modules
located in the /lib/modules/2.4.18.  I tried copying all of the alsa
modules from their new directory into the default directory, and when
I run a modprobe I get a lot of unresolved symbol errors, probably 30
or so.
- Also, I ran alsaconf and it created a new modules.conf for me, but
in the line "alias snd-card-0 snd-card-cs461x" it refers to a module
snd-card-cs461x which does not exist.  The closest thing to it is
snd-cx46xx.  I tried renaming it but I get the same unresolved symbol
errors.

so:
1) Why does alsa create its modules in /lib/modules/2.4.18 instead of
/lib/modules/2.4.18-3?  Did I do the right thing in copying them to
the default location?
2) What's the deal with snd-card-461x vs. snd-46xx
3) What is the cause of the "unresolved symbol" errors?
4) Is there anything else that I am missing?

I would really appreciate any help anyone can give me.

 
 
 

alsa, modprobe, lib/modules, and a turtle beach santa cruz sound card equals one confusing problem.

Post by Richard A Loug » Sat, 05 Oct 2002 15:40:28



> - I installed red hat 7.3 with kernel version 2.4.18.
> - I have a turtle beach santa cruz sound card.
SNIP
> - Also, I ran alsaconf and it created a new modules.conf for me, but
> in the line "alias snd-card-0 snd-card-cs461x" it refers to a module
> snd-card-cs461x which does not exist.  The closest thing to it is
> snd-cx46xx.  I tried renaming it but I get the same unresolved symbol
> errors.

> so:
> 1) Why does alsa create its modules in /lib/modules/2.4.18 instead of
> /lib/modules/2.4.18-3?  Did I do the right thing in copying them to
> the default location?
> 2) What's the deal with snd-card-461x vs. snd-46xx

I'm guessing that your alsaconf is an old version. That caused the
snd-card-461x to appear. You probably set up your conf file correctly
which should have set up your card ok. The best information I have
found to date on alsa setup is in the mini HOWTO.

HTH

Richard A Lough

 
 
 

alsa, modprobe, lib/modules, and a turtle beach santa cruz sound card equals one confusing problem.

Post by chester cha » Thu, 24 Oct 2002 12:21:13


Why do I get the unresolved symbol errors?

I've followed every instruction in every FAQ, but when I compile the
driver and edit modules.conf, I always get the following unresolved
symbol error:

/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__get_free_pages_Rsmp_4784e424
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
try_inc_mod_count_Rsmp_e6105b23
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
fasync_helper_Rsmp_0f820065
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
strstr_Rsmp_1e6d26a8
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
isa_dma_bridge_buggy_Rsmp_f82abc1d
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
remove_proc_entry_Rsmp_18199406
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__write_lock_failed
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
kill_fasync_Rsmp_f866c12a
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
request_module_Rsmp_27e4dc04
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
proc_root_Rsmp_c79b35f0
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
register_chrdev_Rsmp_10735b95
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
create_proc_entry_Rsmp_9cfe096c
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__generic_copy_to_user_Rsmp_d523fdd3
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
pci_alloc_consistent_Rsmp_d2217097
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
vsnprintf_Rsmp_57a6504e
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
unregister_chrdev_Rsmp_c192d491
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
dma_spin_lock_Rsmp_375c41f8
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__vmalloc_Rsmp_79995c5b
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
xquad_portio
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
unregister_sound_special_Rsmp_99c95fa5
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
sprintf_Rsmp_1d26aa98
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
schedule_timeout_Rsmp_17d59d01
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__read_lock_failed
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__wake_up_Rsmp_127fda83
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
register_sound_special_Rsmp_3a650025
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
printk_Rsmp_1b7d4074
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
kfree_Rsmp_037a0cba
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
free_pages_Rsmp_9941ccb8
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
vfs_readlink_Rsmp_6502d84f
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
vfree_Rsmp_2fd1d81c
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
mem_map_Rsmp_ed75ce01
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
vfs_follow_link_Rsmp_9b5fde49
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
kmalloc_Rsmp_93d4cfe6
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
schedule_Rsmp_4292364c
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
remove_wait_queue_Rsmp_ca8842ea
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
pci_free_consistent_Rsmp_4a863b05
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__generic_copy_from_user_Rsmp_116166aa
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
system_utsname_Rsmp_b12cdfe7
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
add_wait_queue_Rsmp_2fd0ca84
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
__pollwait_Rsmp_4c541ea9
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: insmod
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o failed
/lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: insmod snd-cs46xx
failed

Can anyone explain the cause of this?

Anyone who has gotten a turtle beach santa cruz sound card to work
with red hat 7.x with kernel version 2.4.x, please let me know, I'm
not really sure what do do next.

 
 
 

alsa, modprobe, lib/modules, and a turtle beach santa cruz sound card equals one confusing problem.

Post by zd » Wed, 30 Oct 2002 23:58:34



Quote:> Why do I get the unresolved symbol errors?

> I've followed every instruction in every FAQ, but when I compile the
> driver and edit modules.conf, I always get the following unresolved
> symbol error:

Try moving /lib/modules/2.4.18-3 to a safe place and reinstall the
modules of your kernel. If everything goes fine and you don't get those
unresolved symbols again you might keep those new modules and remove the
old ones.

Regards.

--
Zeles Deree (zeldere)   .zd

 * GNU/Linux - LFS 3.1

 
 
 

alsa, modprobe, lib/modules, and a turtle beach santa cruz sound card equals one confusing problem.

Post by zd » Wed, 30 Oct 2002 23:57:28



Quote:> Why do I get the unresolved symbol errors?

> I've followed every instruction in every FAQ, but when I compile the
> driver and edit modules.conf, I always get the following unresolved
> symbol error:

> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __get_free_pages_Rsmp_4784e424
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> try_inc_mod_count_Rsmp_e6105b23
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> fasync_helper_Rsmp_0f820065
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> strstr_Rsmp_1e6d26a8
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> isa_dma_bridge_buggy_Rsmp_f82abc1d
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> remove_proc_entry_Rsmp_18199406
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __write_lock_failed
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> kill_fasync_Rsmp_f866c12a
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> request_module_Rsmp_27e4dc04
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> proc_root_Rsmp_c79b35f0
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> register_chrdev_Rsmp_10735b95
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> create_proc_entry_Rsmp_9cfe096c
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __generic_copy_to_user_Rsmp_d523fdd3
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> pci_alloc_consistent_Rsmp_d2217097
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> vsnprintf_Rsmp_57a6504e
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> unregister_chrdev_Rsmp_c192d491
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> dma_spin_lock_Rsmp_375c41f8
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __vmalloc_Rsmp_79995c5b
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> xquad_portio
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> unregister_sound_special_Rsmp_99c95fa5
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> sprintf_Rsmp_1d26aa98
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> schedule_timeout_Rsmp_17d59d01
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __read_lock_failed
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __wake_up_Rsmp_127fda83
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> register_sound_special_Rsmp_3a650025
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> printk_Rsmp_1b7d4074
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> kfree_Rsmp_037a0cba
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> free_pages_Rsmp_9941ccb8
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> vfs_readlink_Rsmp_6502d84f
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> vfree_Rsmp_2fd1d81c
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> mem_map_Rsmp_ed75ce01
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> vfs_follow_link_Rsmp_9b5fde49
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> kmalloc_Rsmp_93d4cfe6
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> schedule_Rsmp_4292364c
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> remove_wait_queue_Rsmp_ca8842ea
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> pci_free_consistent_Rsmp_4a863b05
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __generic_copy_from_user_Rsmp_116166aa
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> system_utsname_Rsmp_b12cdfe7
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> add_wait_queue_Rsmp_2fd0ca84
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: unresolved symbol
> __pollwait_Rsmp_4c541ea9
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: insmod
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o failed
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: insmod snd-cs46xx
> failed

> Can anyone explain the cause of this?

> Anyone who has gotten a turtle beach santa cruz sound card to work
> with red hat 7.x with kernel version 2.4.x, please let me know, I'm
> not really sure what do do next.

Try moving /lib/modules/2.4.18-3 to a safe place and reinstall the
modules of your kernel. If everything goes fine and you don't get those
unresolved symbols again you might keep those new modules and remove the
old ones.

Regards.

--
Zeles Deree (zeldere)   .zd

 * GNU/Linux - LFS 3.1

 
 
 

1. Turtle Beach Santa Cruz sound card problem

My fresh install of Mandrake 7.2 did not setup my sound properly (i.e. I
can't hear any sounds).

My sound card is a Turtle Beach Santa Cruz card from Voyetra which uses the
Cirrus Logic CS4630 chipset.

The installation identified my sound card as a Cirrus Logic CS4624.

1) Where can I find a driver for this device? (couldn't find it on ZDNET
site).

2) Will I need to rebuild the kernel?

Sent via Deja.com
http://www.deja.com/

2. From the makers of Outlook, IE and Active-X : Terrarium

3. bad sound with Turtle Beach Santa Cruz (cs46xx)

4. DVD-RAM vs. Iomega REV?

5. Rear Speakers on Turtle Beach Santa Cruz card

6. Why is unix so large ?

7. Voyetra Turtle Beach Santa Cruz driver

8. Subdomains for Analog 1.92beta

9. Turtle Beach Santa Cruz in FreeBSD?

10. Turtle Beach drivers? (Santa Cruz)

11. Turtle Beach Santa Cruz

12. Turtle Beach Santa Cruz in Debian?

13. Turtle Beach Santa Cruz