I am using SuSE 7.1 with kernel 2.4.2. I recompiled it with 4GB memory and SMP. So this creates the modules in /lib/modules/2.4.2-4GB-SMP. The problem is that machine 'wants' to load modules from /lib/modules/2.4.2. How do I correct this? I have rebuilt the kernel about 4 times, same problem.
Shonne Beavers wrote:
I am using SuSE 7.1 with kernel 2.4.2. I recompiled it with 4GB memory and SMP. So this creates the modules in /lib/modules/2.4.2-4GB-SMP. The problem is that machine 'wants' to load modules from /lib/modules/2.4.2. How do I correct this? I have rebuilt the kernel about 4 times, same problem.
Try this command: /sbin/depmod -ae -F /boot/System.map-2.4.2-4GB-SMP 2.4.2-4GB-SMP It assumes the System.map file for your kernel is /boot/System.map-2.4.2-4GB-SMP. I don't know for sure if it is or not. Mark
I tried that already. The System.map is created as /boot/System.map. Should I delete this when I compile another kernel. Typically, what I do is I delete the old kernel modules. Then I run make menuconfig. After that I run make dep clean bzImage. Finally I run make modules modules_install bzlilo. Then I reboot. Did I miss something? Shonne Beavers wrote:
I am using SuSE 7.1 with kernel 2.4.2. I recompiled it with 4GB memory and SMP. So this creates the modules in /lib/modules/2.4.2-4GB-SMP. The
problem
is that machine 'wants' to load modules from /lib/modules/2.4.2. How do I correct this? I have rebuilt the kernel about 4 times, same problem.
Try this command: /sbin/depmod -ae -F /boot/System.map-2.4.2-4GB-SMP 2.4.2-4GB-SMP It assumes the System.map file for your kernel is /boot/System.map-2.4.2-4GB-SMP. I don't know for sure if it is or not. Mark -- 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/faq and the archives at http://lists.suse.com
Shonne Beavers wrote:
I tried that already. The System.map is created as /boot/System.map. Should I delete this when I compile another kernel. Typically, what I do is I delete the old kernel modules. Then I run make menuconfig. After that I run make dep clean bzImage. Finally I run make modules modules_install bzlilo. Then I reboot. Did I miss something?
It almost sounds like you aren't running the kernel you think you are. I would go back and verify that /etc/lilo.conf is pointing to the kernel you want and that the kernel you want is in fact the one being built. It's been a while since I messed with any of SuSE's kernel sources. I always had problems with the way their versions were labeled (ie 4GB and such). Although I'm about to have to do just that. Mark
On Wednesday 09 May 2001 19:57, you wrote:
I tried that already. The System.map is created as /boot/System.map. Should I delete this when I compile another kernel. Typically, what I do is I delete the old kernel modules. Then I run make menuconfig. After that I run make dep clean bzImage. Finally I run make modules modules_install bzlilo. Then I reboot. Did I miss something?
Perhaps.. When I do a compile I do make dep clean bzlilo modules modules_install. Having it do the bzImage, and then later bzlilo seems to be defeating the purpose, and might be causing something to be removed. It's just a thought. I recently did a compile of the 2.4.4 sources using the above line and everything works. Mike -- Powered by SuSE 7.1, Kernel 2.4.4 KDE2.1.1 For a great linux portal try http://www.freezer-burn.org
* Shonne Beavers (shonne_beavers@pvamu.edu) [20010509 19:58]:
I tried that already. The System.map is created as /boot/System.map.
Sigh, I should put this up in pub/people/pthomas ;-) Below is my patch for arch/i386/boot/Makefile. just change to your kernel source directory and then do a 'patch -p0 -i /path/to/diff'. After applying this, you only need to create a new entry in /etc/lilo.conf (or change an existing one) for the new kernel. After that, you can run 'make bzlilo' and it will create a unique kernel and matching System.map *and* call LILO to reflect the change. --- arch/i386/boot/Makefile.old Wed May 9 21:27:43 2001 +++ arch/i386/boot/Makefile Wed May 9 21:39:28 2001 @@ -30,10 +30,14 @@ dd bs=8192 if=$(BOOTIMAGE) of=/dev/fd0 zlilo: $(CONFIGURE) $(BOOTIMAGE) - if [ -f $(INSTALL_PATH)/vmlinuz ]; then mv $(INSTALL_PATH)/vmlinuz $(INSTALL_PATH)/vmlinuz.old; fi - if [ -f $(INSTALL_PATH)/System.map ]; then mv $(INSTALL_PATH)/System.map $(INSTALL_PATH)/System.old; fi - cat $(BOOTIMAGE) > $(INSTALL_PATH)/vmlinuz - cp $(TOPDIR)/System.map $(INSTALL_PATH)/ + if [ -f $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) ]; then \ + mv $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE).old; \ + fi + if [ -f $(INSTALL_PATH)/System.map-$(KERNELRELEASE) ]; then \ + mv $(INSTALL_PATH)/System.map-$(KERNELRELEASE) $(INSTALL_PATH)/System-$(KERNELRELEASE).old; \ + fi + cat $(BOOTIMAGE) > $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) + cp $(TOPDIR)/System.map $(INSTALL_PATH)/System.map-$(KERNELRELEASE) if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi install: $(CONFIGURE) $(BOOTIMAGE) -- Philipp Thomas <pthomas@suse.de> Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany Penguins shall save the dinosaurs -- Handelsblatt about Linux on S/390
Philipp Thomas wrote:
* Shonne Beavers (shonne_beavers@pvamu.edu) [20010509 19:58]:
I tried that already. The System.map is created as /boot/System.map.
Sigh, I should put this up in pub/people/pthomas ;-) Below is my patch for arch/i386/boot/Makefile. just change to your kernel source directory and then do a 'patch -p0 -i /path/to/diff'. After applying this, you only need to create a new entry in /etc/lilo.conf (or change an existing one) for the new kernel. After that, you can run 'make bzlilo' and it will create a unique kernel and matching System.map *and* call LILO to reflect the change.
--- arch/i386/boot/Makefile.old Wed May 9 21:27:43 2001 +++ arch/i386/boot/Makefile Wed May 9 21:39:28 2001 @@ -30,10 +30,14 @@ dd bs=8192 if=$(BOOTIMAGE) of=/dev/fd0
zlilo: $(CONFIGURE) $(BOOTIMAGE) - if [ -f $(INSTALL_PATH)/vmlinuz ]; then mv $(INSTALL_PATH)/vmlinuz $(INSTALL_PATH)/vmlinuz.old; fi - if [ -f $(INSTALL_PATH)/System.map ]; then mv $(INSTALL_PATH)/System.map $(INSTALL_PATH)/System.old; fi - cat $(BOOTIMAGE) > $(INSTALL_PATH)/vmlinuz - cp $(TOPDIR)/System.map $(INSTALL_PATH)/ + if [ -f $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) ]; then \ + mv $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE).old; \ + fi + if [ -f $(INSTALL_PATH)/System.map-$(KERNELRELEASE) ]; then \ + mv $(INSTALL_PATH)/System.map-$(KERNELRELEASE) $(INSTALL_PATH)/System-$(KERNELRELEASE).old; \ + fi + cat $(BOOTIMAGE) > $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) + cp $(TOPDIR)/System.map $(INSTALL_PATH)/System.map-$(KERNELRELEASE) if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi
install: $(CONFIGURE) $(BOOTIMAGE)
-- Philipp Thomas <pthomas@suse.de>
Shoone, DO what Philipp suggests here. It's what I do now even with vanilla kernels. I just do it manually but it will really eliminate alot of headache. Phillip, why don't they use these rules in the vanilla kernels? Mark
Or better yet why doesn't SuSE use these rules?? Mark
* Mark Hounschell (markh@compro.net) [20010509 21:59]:
Phillip, why don't they use these rules in the vanilla kernels?
I guess because this clutters up the directory your kernels reside in. And it isn't perfect. If done correctly, there would have to be a possibility to specify the tool for creating an initrd and that tool would have to be called before calling lilo. But as that tool needs the modules installed, which in turn need the kernel to be installed as otherwise depmod will fail, it's kind of a catch22. And that's also the reason why this isn't in our kernel, as we make heavy use of modules. Philipp -- Philipp Thomas <pthomas@suse.de> Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany Penguins shall save the dinosaurs -- Handelsblatt about Linux on S/390
participants (4)
-
Mark Hounschell -
Mike -
Philipp Thomas -
Shonne Beavers