Thanks, that worked very well. I still have no idea why mkinitrd freezes my
computer, but it doesn't matter since I don't need an initrd image anyway :)

On Tue, 5 Feb 2002 15:18:18 +1100 (EST), Steve Kieu <[EMAIL PROTECTED]> wrote:
> 
> > 5. Run 'make modules_install && make install'.
> 
> I nerver did that, I just 'make modules_install' and
> manually copy the bzImage file from arch/i386/boot to
> /boot and manually modify lilo.conf. always work :-)
> 
> 
> > 
> > This process used to work perfectly, but now the
> > process freezes my whole
> > computer whenever I get to the /sbin/installkernel
> > phase (part of 'make
> > install'), and specifically when it gets to running
> > mkinitrd. On a quick glance
> > of the 'make install' process, I noticed a reference
> > to zImage. This is strange
> > because I used 'make bzImage', not 'make zImage'.
> > After a hard reboot, the
> > kernel looked as if it was mostly installed: there
> > were modules in /lib/modules/
> > and various files in /boot. The only file missing in
> > /boot was an initrd image.
> > As an experiment, I configured the new kernel in
> > /etc/lilo.conf, but I got a
> > "Kernel [name] is too big!" error whenever I tried
> > to run LILO (as if I had used
> > 'make zImage' instead of 'make bzImage').


-- 
Sridhar Dhanapalan

        "Maybe somebody should tell gcc maintainers about programmers
                that know more than the compiler again."
                          -- Linus Torvalds

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to