On Wednesday February 5 2003 09:20 pm, Charles A Edwards wrote:
> That did not work for me.
> Modprobe loop gives GPL and undefined errors in the pre4-2 kernel.
>
> I was able to successfully install the pre4-3 kernel by booting to
> an old kernel and then installing the pre4-3.
>
>
> Charles
I complied from kernel-source (for Athlon, ie, the -_k7's below)
tom# /sbin/mkinitrd /boot/initrd-2.4.21pre4-2k7.img
initrd-2.4.21pre4-2k7
/boot/initrd-2.4.21pre4-2k7.img already exists.
I'm runnin -2k7 (EXTRAVERSION edit), there were no problems either
compiling or booting. I always uncomment 'export INSTALL_PATH=/boot'
in Makefile so that a last step of 'make install' puts the needed
files and links in /boot for me.
tom# /sbin/mkinitrd /boot/initrd-2.4.21pre4-3k7.img
initrd-2.4.21pre4-3k7
/lib/modules/initrd-2.4.21pre4-3k7 is not a directory.
modules$ l
2.4.21-0.pre3.1k7/ 2.4.21pre3-2k7/ 2.4.21pre4-1k7/
2.4.21pre4-2k7/
2.4.21-0.pre3.1mdk/ 2.4.21pre3-3k7/ 2.4.21pre4-1mdk/
2.4.21pre4-3k7/
^^^^^^^^^^^^^^^
2.4.21pre4-3k7$ l
build@ modules.generic_string modules.parportmap
modules.usbmap
kernel/ modules.ieee1394map modules.pcimap pcmcia/
modules.dep modules.isapnpmap modules.pnpbiosmap
2.4.21pre4-3k7/ is a directory..... with all the same stuff in it
as 2.4.21pre4-2k7/ which had/has no problems.
'make install' failed to make an initrd.img, and I'm unable to make
an initrd for -3k7 by hand. vmlinuz and system.map were correctly
created and placed in /boot for -3k7, and lilo.conf was correctly
edited (ie, -3k7 stanza added), but with the exception of no initrd=
statement.
--
Tom Brinkman Corpus Christi, Texas
