Sound Card Problems: Unknown Symbols

Hello,

I've recently compiled the 2.6.11 kernel for use on my computer. I previously used 2.4.22 (I still have it here just in case). Anyway, I can't get my sound card (SB Live) to work with ALSA. I know there have been plenty of posts about this but I couldn't find this specific problem anywhere. I followed the instructions on the ALSA site, yet when I run "modprobe snd-emu10k1;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss" I get:

WARNING: Error inserting snd_hwdep (/lib/modules/2.6.11-C/kernel/sound/acore/snd-hwdep.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.11-C/kernel/sound/pci/ac97/snd-ac97-codec.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_seq_device (/lib/modules/2.6.11-C/kernel/sound/acore/seq/snd-seq-device.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_rawmidi (/lib/modules/2.6.11-C/kernel/sound/acore/snd-rawmidi.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_emu10k1 (/lib/modules/2.6.11-C/kernel/sound/pci/emu10k1/snd-emu10k1.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Module snd_pcm_oss already in kernel.
FATAL: Module snd_mixer_oss already in kernel.
WARNING: Error inserting snd_seq_device (/lib/modules/2.6.11-C/kernel/sound/acore/seq/snd-seq-device.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_seq (/lib/modules/2.6.11-C/kernel/sound/acore/seq/snd-seq.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_seq_midi_event (/lib/modules/2.6.11-C/kernel/sound/acore/seq/snd-seq-midi-event.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_seq_oss (/lib/modules/2.6.11-C/kernel/sound/acore/seq/oss/snd-seq-oss.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Here is the output of lspci:

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
00:0b.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a)
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4150
01:00.1 Display controller: ATI Technologies Inc: Unknown device 4170

As you can see, the card is there. Here's lsmod:

Module                  Size  Used by
snd_util_mem            3328  0
ppp_deflate             4928  0
zlib_deflate           21144  1 ppp_deflate
snd_pcm_oss            48416  0
snd_pcm                83940  1 snd_pcm_oss
snd_timer              21828  1 snd_pcm
snd_page_alloc          7620  1 snd_pcm
snd_mixer_oss          17664  1 snd_pcm_oss
snd                    46884  4 snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
binfmt_misc             8904  1
md5                     3712  1
ipv6                  245184  8
parport_pc             25092  1
lp                      9480  0
parport                33032  2 parport_pc,lp
autofs                 13312  0
8139too                22848  0
mii                     4032  1 8139too
ipt_state               1536  2
iptable_filter          2304  1
ipt_MASQUERADE          2752  1
iptable_nat            20380  2 ipt_MASQUERADE
ip_conntrack           39052  3 ipt_state,ipt_MASQUERADE,iptable_nat
ip_tables              20352  4 ipt_state,iptable_filter,ipt_MASQUERADE,iptable_nat
agpgart                28648  0

I installed all the 4 ALSA tar files (lib, utils, drivers, oss) and they all seemed to work fine. Running alsamixer produces:

alsamixer: function snd_ctl_open failed for default: No such device

EDIT - Forgot to mention: I compiled ALSA stuff as modules in xconfig, and sound card support straight into the kernel. I left out OSS.

Anybody know what I can do to fix this? Any advice greatly appreciated.

Cheers

Ovalteen

Alright, I just tried running alsaconf again, and now it works. Alsamixer too. In XMMS, it still only has OSS listed in output plugins. Should it also have ALSA, or is that not supported? And what was with all that symbols stuff anyway?

Thanks for any advice.

Cheers

Ovalteen

When I get Unknown symbol errors, it's usually because something was compiled against a different version of the kernel than what is running. I would check that you have everything for the new kernel set up correctly.

Did you compile the 2.6.x kernel or load a package with it? If it's a package, did you get the proper modules package also? If you did a compile, did you do make modules and make modules_install? Are there any symlinks in /boot (ls -l /boot) pointing to old kernel settings? Do you have a /lib/modules/2.6.11 directory?

Originally posted by Darin When I get Unknown symbol errors, it's usually because something was compiled against a different version of the kernel than what is running. I would check that you have everything for the new kernel set up correctly. Did you compile the 2.6.x kernel or load a package with it? If it's a package, did you get the proper modules package also? If you did a compile, did you do make modules and make modules_install? Are there any symlinks in /boot (ls -l /boot) pointing to old kernel settings? Do you have a /lib/modules/2.6.11 directory?

- Compiled
- Did make modules_install, but not make modules.
- A few symlinks, one of which points to /lib/modules/2.4.x. Doesn't seem to be an equivalent for 2.6.11
- /lib/modules/2.6.11 directory is present.

Everything works as advertised. I've tried networking (verified iptables and all adapters functional), sound, display (need to do the ATI drivers again though), mounting and unmounting. I can't think of anything else to test. If I do a symlink in /boot, will that tidy things up a bit, or is it not necessary?

Thanks for the advice.

Cheers

Ovalteen

I haven't done enough 2.6.x kernel compiles to say for sure but I assume you were either following a guide or have compiled a working kernel in the past. I think the make modules step from 2.4.x kernels is integrated into another step now.

You shouldn't have to make new symlinks in /boot AFAIK. I don't think they are needed by anything, but since you were having problems that point to a kernel issue it won't hurt to eliminate them as a possible cause of future problems. For me it's that unknown factor, do all the 'optional' steps just in case I run into the one oddball in the lot that needs some of it.

As for the other questions, I don't have answers about the XXMS and OSS schtuff but unless I misread you have it working now?

Sorry for the late reply Darin,

Yes, I was following a guide (or two) to building the 2.6.x kernel, the main one didn't mention anything about symlinks so I hadn't thought to include them. I've also done it once or twice before and without them. It seems to be working just fine without them though so I'll leave it that way. All the other XMMS/OSS/ALSA stuff is also working OK.

Thanks for the advice.

Cheers

Ovalteen