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: Code:
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) Code:
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge (rev 80) Code:
Module Size Used by Code:
alsamixer: function snd_ctl_open failed for default: No such device 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? |
Quote:
- 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 |
All times are GMT -5. The time now is 09:42 AM. |