Re: Unable to compile a bootable kernel, or, how do I make a romfs?
Hi,
It sound like the same or very similar problem I had with every single 2.4.x
kernel I've tied.
In my case LILO started loading and after putting some dots on the screen
the PC just rebooted.
My guess is that it couldn't mount the root filesystem, allthough I'm not
sure as I'm fairly new to this.
(I've compiled several versions of 2.4.10 2.4.12-ac6 with or without initrd
enabled to no avail.
My 2.2.19pre17 kernel works fine with the samer lilo config, though.)
I've posted several messages to this list on that, but nobody replied,
expect for someone guessing that
it might be initrd. Which I'm not sure as I compiled versions without even
ramdisk or loadable module support
and it still didn't work.
I've still no solution to it.
So if you manage to solve it, PLEASE, PLEASE tell me what was it!
Many thanks in advance!
brgds,
Balazs
----- Original Message -----
From: "Timothy J. Miller" <cerebus@sackheads.org>
To: "Debian-User" <debian-user@lists.debian.org>
Sent: Thursday, November 08, 2001 20:22
Subject: Re: Unable to compile a bootable kernel, or, how do I make a romfs?
> On Thu, 2001-11-08 at 11:52, Jeremy T. Bouse wrote:
> > Not sure I follow what you're trying to do with cramfs but I've
> > not had to use the cramfs packaging at all... I just use mkinitrd in the
> > initrd-tools package and haven't had a problem...
>
> Done that, to no effect. All I'm trying to do is get a freaking kernel
> compiled and booted. I snarfed 2.4.13 from kernel.org, applied the
> patches I need successfully, and compiled with make-kpkg.
>
> I installed the resulting kernel-image, checked all the linking, built
> an initrd with mkinitrd, dropped it in /boot, linked to it from where
> lilo expects it, and ran lilo successfully.
>
> At boot, the new kernel cannot find the ramdisk and fails to mount it,
> then panics.
>
> I never had these problems prior to moving to initrd stuff. 8(
>
> -- Cerebus
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
Reply to: