Unix Technical Forum

Problems with sound/ALSA

This is a discussion on Problems with sound/ALSA within the Gentoo Linux Support forums, part of the Unix Operating Systems category; --> Hi, I have recently installed Gentoo with relative success :-) But - of cause - sound doesn't work. I'm ...


Go Back   Unix Technical Forum > Unix Operating Systems > Gentoo Linux Support

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-21-2008, 07:09 AM
Jakob Rohde
 
Posts: n/a
Default Problems with sound/ALSA

Hi,

I have recently installed Gentoo with relative success :-) But - of cause
- sound doesn't work.

I'm using SoundBlaster Live 1024 and kernel 2.6.5 on AMD Athlon XP with
ALSA and I thought I had done what the installation manual said.

Below is the output from DMESG - can you help me in the right direction?

BTW, what is a "tainted" kernel? Can I ignore the nVidia stuff?

TIA,

Jakob

nvidia: no version magic, tainting kernel.
nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4496 /
Wed Jul 16 19:03:09 PDT 2003 NTFS volume version 3.1.
unable to register native major device number 116 unable to register timer
device (-16) Unable to handle kernel paging request at virtual address
306d64a4
printing eip:
c0338a0f
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c0338a0f>] Tainted: PF EFLAGS: 00010282
(2.6.5-gentoo-r1)
EIP is at snd_info_create_card_entry+0x1d/0x3a eax: edfe5180 ebx:
306d6370 ecx: 00000000 edx: edfe5180 esi: ee028980 edi: ee0289d4
ebp: 00000000 esp: ee779e4c ds: 007b es: 007b ss: 0068
Process modprobe (pid: 5038, threadinfo=ee778000 task=ee7cd2e0) Stack:
c044de76 ee028980 c034c9dc 306d6370 c044de76 00000001 ee744000 ee027e58
f0932f58 ee028980 00010000 00010000 00010000 00010000 ee779e88
ee027e00 efbb8400 00000000 00000001 efedf400 f092e0fb ee744000
00000000 00000000
Call Trace:
[<c034c9dc>] snd_pcm_lib_preallocate_pages1+0x60/0xbc [<f0932f58>]
snd_emu10k1_pcm+0x156/0x172 [snd_emu10k1] [<f092e0fb>]
snd_card_emu10k1_probe+0xfb/0x38a [snd_emu10k1] [<c0226bcb>]
pci_device_probe_static+0x52/0x61 [<c0226c15>]
__pci_device_probe+0x3b/0x4e [<c0226c54>] pci_device_probe+0x2c/0x4a
[<c0286b61>] bus_match+0x3f/0x6a
[<c0286c73>] driver_attach+0x56/0x80
[<c0286f45>] bus_add_driver+0x9f/0xb1 [<c0287345>]
driver_register+0x2f/0x33 [<c0226e10>] pci_register_driver+0x5c/0x84
[<f08b6013>] alsa_card_emu10k1_init+0x13/0x3b [snd_emu10k1] [<c0130ff1>]
sys_init_module+0x147/0x221 [<c010727f>] syscall_call+0x7/0xb

Code: 8b 83 34 01 00 00 89 5a 24 89 42 28 8b 44 24 14 89 42 20 89
<3>unable to register native major device number 116
Debug: sleeping function called from invalid context at mm/slab.c:1931
in_atomic():1, irqs_disabled():0
Call Trace:
[<c011994a>] __might_sleep+0xab/0xc9
[<c013b5d7>] kmem_cache_alloc+0x6e/0x70
[<c01499c0>] __get_vm_area+0x24/0xf3
[<c0149ac1>] get_vm_area+0x32/0x36
[<c0116e10>] __ioremap+0xb7/0x104
[<c0138043>] buffered_rmqueue+0xf0/0x1bd
[<c0116e88>] ioremap_nocache+0x2b/0xad
[<f0a4e4a4>] os_map_kernel_space+0x68/0x6c [nvidia]
[<f0a60a97>] __nvsym00568+0x1f/0x2c [nvidia]
[<f0a62bb6>] __nvsym00775+0x6e/0xe0 [nvidia]
[<f0a62c46>] __nvsym00781+0x1e/0x190 [nvidia]
[<c015ca3f>] link_path_walk+0x638/0x953
[<f0a646cc>] rm_init_adapter+0xc/0x10 [nvidia]
[<f0a4aed7>] nv_kern_open+0xf3/0x228 [nvidia]
[<f0a4ade4>] nv_kern_open+0x0/0x228 [nvidia]
[<c0157d4c>] chrdev_open+0xb3/0x1be
[<c014e3da>] dentry_open+0x106/0x15e
[<c014e2d2>] filp_open+0x62/0x64
[<c014e698>] sys_open+0x5b/0x8b
[<c010727f>] syscall_call+0x7/0xb

Debug: sleeping function called from invalid context at mm/slab.c:1931
in_atomic():1, irqs_disabled():0
Call Trace:
[<c011994a>] __might_sleep+0xab/0xc9
[<c013b5d7>] kmem_cache_alloc+0x6e/0x70
[<c01499c0>] __get_vm_area+0x24/0xf3
[<c0149ac1>] get_vm_area+0x32/0x36
[<c0116e10>] __ioremap+0xb7/0x104
[<c0138043>] buffered_rmqueue+0xf0/0x1bd
[<c0116e88>] ioremap_nocache+0x2b/0xad
[<f0a4e4a4>] os_map_kernel_space+0x68/0x6c [nvidia]
[<f0a60a97>] __nvsym00568+0x1f/0x2c [nvidia]
[<f0a62bb6>] __nvsym00775+0x6e/0xe0 [nvidia]
[<f0a62c46>] __nvsym00781+0x1e/0x190 [nvidia]
[<c015ca3f>] link_path_walk+0x638/0x953
[<f0a646cc>] rm_init_adapter+0xc/0x10 [nvidia]
[<f0a4aed7>] nv_kern_open+0xf3/0x228 [nvidia]
[<f0a4ade4>] nv_kern_open+0x0/0x228 [nvidia]
[<c0157d4c>] chrdev_open+0xb3/0x1be
[<c014e3da>] dentry_open+0x106/0x15e
[<c014e2d2>] filp_open+0x62/0x64
[<c014e698>] sys_open+0x5b/0x8b
[<c010727f>] syscall_call+0x7/0xb

0: NVRM: AGPGART: unable to retrieve symbol table
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-21-2008, 07:09 AM
Ric de France
 
Posts: n/a
Default Re: Problems with sound/ALSA

Jakob Rohde wrote:

> BTW, what is a "tainted" kernel? Can I ignore the nVidia stuff?


From my understanding, if you're installing the nVidia proprietary
drivers, they're really sliding a non-kernel module into the kernel
space, therefore taiting the kernel. It's a way nVidia can give you a
kernel module without having to reveal the source code to their drivers.

Overall, I don't think it's a bad thing. Just have to be aware if you
recompile your kernel, you've got to "emerge nvidia-kernel" again.

....Ric
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-21-2008, 07:09 AM
Anno v. Heimburg
 
Posts: n/a
Default Re: Problems with sound/ALSA

Jakob Rohde wrote:
> BTW, what is a "tainted" kernel? Can I ignore the nVidia stuff?


The main point of a tainted kernel is to allow the kernel developers to
better deal with binary-only drivers. For these drivers, the source code is
not available, making it practically impossible for somebody not working
for the driver company to debug errors. Furthermore, binary-only drivers
have a history of producing a faire share of kernel errors / oopses.

The "tainted" thing is there to alert the user to the fact that the module
just loaded might seriously decrease the kernel's stability. Furthermore,
the tainted status is recorded in the "oops" error output when the kernel
goes belly up. The kernel developers can then immediately see from the
error that there's a binary-only driver loaded and tell the user to talk to
the driver manufacturer instead, since they probably won't be able to do
anything about it.

Anno.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-21-2008, 07:09 AM
Phil Clayton
 
Posts: n/a
Default Re: Problems with sound/ALSA

Jakob Rohde wrote:

> I have recently installed Gentoo with relative success :-) But - of cause
> - sound doesn't work.
>
> I'm using SoundBlaster Live 1024 and kernel 2.6.5 on AMD Athlon XP with
> ALSA and I thought I had done what the installation manual said.


Have you seen this?
http://www.gentoo.org/doc/en/alsa-guide.xml

Regards,
Phil
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-21-2008, 07:09 AM
Jakob Rohde
 
Posts: n/a
Default Re: Problems with sound/ALSA

On Sun, 02 May 2004 09:56:39 +1000, Phil Clayton wrote:

> Have you seen this?
> http://www.gentoo.org/doc/en/alsa-guide.xml


Yes, and I thought I did what it said...

Jakob
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 02-21-2008, 07:09 AM
Percival Bartlebooth
 
Posts: n/a
Default Re: Problems with sound/ALSA

Jakob Rohde <jakob.rohde@nal-net.dk> wrote in
newsan.2004.05.01.07.27.30.941033@nal-net.dk:

> Hi,
>
> I have recently installed Gentoo with relative success :-) But - of
> cause - sound doesn't work.
>
> I'm using SoundBlaster Live 1024 and kernel 2.6.5 on AMD Athlon XP
> with ALSA and I thought I had done what the installation manual said.
>
> Below is the output from DMESG - can you help me in the right
> direction?
>


I've also tried to get alsa working on my laptop, using the 2.6.5
kernel. I finally gave it up, and used oss instead. It may be considered
as a defeat, but I have sound at last, and that's what counts.

maybe you can have a try ?

Bartlebooth
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 12:05 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com