Laszlo, I had similar problems and I fixed it by making a new initrd image (even though there already was one). I renamed the original and then deleted it once I was certain my new image worked. To build the new initrd image, run /sbin/mkinitrd with parameters such as this: /sbin/mkinitrd /boot/initrd-2.4.18-14custom 2.4.18-14 where boot/initrd-2.14.18-14custom is the file to use for your new image, and 2.4.18-14 is the kernel whose modules (from /lib/modules) should be used in the initrd image (not necessarily the same as the version number of the currently running kernel). Reboot and it should now load your new modules. Hope this fixes things for you. -- David E. Williams dewillia@xxxxxxxx "I have never let my schooling interfere with my education." -Mark Twain On Mon, 2003-04-07 at 06:32, Kohl Laszlo wrote: > Hi! > > Could you help my please? > > I have a Red Hat 8.0 with my custom kernel compiled successfully. > > Kernel source installed from the RedHat install CD then: > make config /* The "Set version information on all module symbols" is > not checked because the kernel can not be compiled with it */ > make dep && make bzImage && make modules && make modules_install && make > install (as the documentation mentioned, Red Hat Linux 8.0 customization > guide, page 257-261) > > I am using GURB, the config file: > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this > file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,1) > # kernel /vmlinuz-version ro root=/dev/hda4 > # initrd /initrd-version.img > #boot=/dev/hda > default=0 > timeout=10 > splashimage=(hd0,1)/grub/splash.xpm.gz > > title Red Hat Linux (2.4.18-14custom) > root (hd0,1) > kernel /vmlinuz-2.4.18-14custom ro root=LABEL=/ > initrd /initrd-2.4.18-14custom.img > > title Red Hat Linux (2.4.18-14) > root (hd0,1) > kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ > initrd /initrd-2.4.18-14.img > > title Windows 2000 > rootnoverify (hd0,0) > chainloader +1 > > title Floppy > rootnoverify (fd0,0) > chainloader +1 > > > If I choose my custom kernel it is starting to load. > BUT the kernel loads the modules form the "/lib/modules/2.4.18-14" > directory instead of"/lib/modules/2.4.18-14custom" dir. > > The "uname -a" command shows the info: > Linux custom 2.4.18-14 #10 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 > GNU/Linux > > It seems the loaded kernel is the 2.4.18-14 (factory default), > BUT "#10" shows it is the 10th compilation (I compiled the custom kernel > 10 times). So which kernel was loaded? > I can not load my custom modules (ntfs.o), the error message: > modprobe: Can't locate module ntfs > But the module exist in the > "/lib/modules/2.4.18-14custom/kernel/fs/ntfs" directory. > > What is wrong? > Is it something problem (bug) with the make install? > > I heard this is still problem in 9.0 but it was good in 7.2. > > TIA, > Laszlo. > > PS.: I need to compile the kernel, because I want to read ntfs from > Linux, and the driver is not compiled by Red Hat default... > > > > -- > Psyche-list mailing list > Psyche-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/psyche-list > -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/psyche-list
