Paul Talacko wrote:
----Original Message----
I've got a problem or two with a recompiled kernel, modules and sound.
I recently installed Suse 6.1 (kernel 2.2.7) on a Sony Vaio F-150. Installation went like a breeze, neomagic X servers available from NeoMagic went straight in and everything is working beautifully, except sound, that is.
The laptop uses the NM256 sound chip. This is available as a module in kernel 2.2.13, where it clicks after playing CDs apparently, and 2.2.14 where it works well. Thinking I was being really smart I downloaded the 2.2.14 from www.kernel.org.
make xconfig wasn't working properly. This morning I managed to configure the kernel properly with 'make config'. make dep clean bzImage worked. make modules; make modules_install also seemed to work.
However, the new kernel was installed under root (/) and not /boot/ where SuSe puts its kernel. I thought I could fix this by updating lilo.conf.
Did you move the kernel to /boot or alter lilo.conf to reflect the kernel's location? To get the kernel to install into /boot, you need to uncomment the appropriate line in the kernel Makefile.
But it's all gone pear-shaped. I now have modules in /lib/modules/2.2.7 /lib/modules/2.0.36 and /lib/modules/2.2.14. The new kernel does not seem to recognise anything in the older directories. I have two sound.o and soundcore.o files one each in /lib/modules/2.2.7/misc/ and /lib/modules/2.2.14/misc/, but only one nm256 module in /lib/modules/2.2.14/misc/. PCMCIA support is now broken so is serial support.
If you're running 2.2.14, all other module directories are ignored, so don't expect it to recognise anything in the older kernel directories. PCMCIA support needs to be compiled separately, and the serial appears to be compiled into the kernel, so you can do the following in /etc/conf.modules: alias char-major-4 off
----Later Messages----
There is more stuff wrong than just the pcmcia and serial being broken. At boot time I get a whole series of messages saying 'symbol not found'.
My boot.msg directory has the following entries: Symbol table has incorrect version number. Inspecting /System.map Loaded 6565 symbols from /System.map Symbols match kernel version 2.2.14 Loaded 2 symbols from 2 modules.
You could try copying both vmlinuz and System.map to the /boot directory and altering lilo.conf as appropriate.
I can't find where all the messages about 'can't locate module', but basically the new kernel can't see any of the modules that aare in /lib/modules/2.2.7/ The pcmcia modules are there. Why didn't make compile ALL the modules and put them in /lib/modules/2.2.14/ rather than only putting the new stuff in there (specifically the sound and nm256 modules)?
Maybe you didn't compile them as modules? The compile shouldn't touch any directory other than /lib/modules/2.2.14 - all the kernel modules should be there, with the exception of PCMCIA modules, as you appear to have found out.
I installed the pcmcia sources from the Suse install disks. make config runs fine, but after running make all I get:
<bunch of PCMCIA stuff snipped>
What does all this mean anyone?
Nothing to me ;-) However, you do need to compile the PCMCIA modules separately, as you are doing.
When I boot from my old kernel in /boot/ which has its own System.map in /boot everything works as it used to, but no sound of course :-) I can't believe I'm going to so much trouble just to make the computer beep - but now I can't get it to work, I just can't rest.
I know that feeling - in fact, I'm helping a friend in exactly the same situation at the moment (sound works in 2.2.14, and PCMCIA works in 2.2.13 ;-) ). I don't know whether you've got it solved yet or not. You could try to get the latest PCMCIA stuff from: ftp://sunsite.unc.edu/pub/Linux/kernel/pcmcia/ Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/