Re: loop.o

[Joshua Schmidlkofer <menion mindless com>]

Do you need a RamDisk?  I personally prefer to link all my core drivers
into the kernel, then anything that I use once in a while, set it as a
module.  And for building a new kernel, i HIGHLY recommend 'make
menuconfig' as the first step (if you have not already done that)  It is
pretty friendly.

thanks
js

lem wrote:
> 
> why is that when i build a custom kernel after following all the steps
> in
> the users guide
> 
> make dep
> make clean
> make modules
> rm -rf /lib/modules/2.0.27-old
> mv /lib/modules/2.0.27 /lib/modules/2.0.27-old
> make modules_install
> 
> when i get to the part when i must build a ramdisk ( initrd )
> 
> the manual says:
> 
> /sbin/mkinitrd /boot/newinitrd-image 2.0.12
> 
> (2.0.12 doesn't mean the kernel but it has an error when i try it like
> this
> no directory or something, so i try to put in the kernel's numbers
> 2.0.27)
> 
> then it says (error):
> 
> "could not find any loop device, and, according to /proc/devices, this
> kernel does not know about the loop device. (if so, the recompile or
> `insmod loop.o') "
> 
> so naturally i look for loop.o..... i cant find the blasted file.....
> sometimes i find it under /lib/modules/2.0.27-old/block/loop.o  i
> tried to
> insmod it my booting fails.  vfs panic...
> 
> is there a way to add the loop device to /proc/devices manually.......
> 
> ---lem
> 
> p.s i boot my machine with loadlin vmlinuz root=/dev/sda3
> initrd=initrd
> lilo doesn't work on my machine, maybe scsi problem.... large hd.
> 
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST
> ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips
> /mailing-lists
>          To unsubscribe: mail redhat-install-list-request redhat com
>                      with "unsubscribe" as the Subject.