Re: trouble with RAMDISK after replacing kernel
Dave_Hein <[email protected]>
| Newsgroups | gmane.linux.tomsrtbt |
|---|---|
| Message-ID | <[email protected]> |
Yes, I took a bzImage and renamed it bz2bzImage -- so that I wouldn't have to edit buildit.s. Sounds dumb (now), but I was just following the suggestion in the wiki page "ReplaceTheKernel". That page says that you can rename the image or modify the script; it seemed safer to rename the image. Of course it talks about "zImage" versus "bzImage" and doesn't mention "bz2" ... I guess that should have been a clue. Keeping the image name as bzImage and modifying 2/usr/bin/buildit.s (and 1/settings.s, for good measure) did the trick. Thanks for the quick response. On Sat, Jun 15, 2002 at 09:58:59AM -0400, Tom Oehser wrote: > > Did you call it bzImage or bz2bzImage? Two things: > > First, The build script is supposed to detect the difference and use > gzip instead of bzip2 for the ramdisk if you use a bzImage kernel > instead of a bz2bzImage kernel. Your bzImage kernel does not support > the bzip2 ramdisk format used by the bz2bzImage kernel, so if you > call the kernel bz2bzImage, but it isn't really, it will fail. > > Second, I've never tested the bzImage/bz2bzImage=>bzip2/gzip logic > in buildit.s, so, assuming you called it bzImage, there may be bugs. > > -Tom > > On Fri, 14 Jun 2002, Dave_Hein wrote: > > > Date: Fri, 14 Jun 2002 23:38:42 -0500 > > From: Dave_Hein <[email protected]> > > To: [email protected] > > Subject: [tomsrtbt] trouble with RAMDISK after replacing kernel > > > > I created a new tomsrtbt with a different kernel and am getting this error message: > > > > RAMDISK: couldn't find valid RAM disk image starting at 867. > > > > I built 2.4.18 kernel with support for RAMDISK and MINIX, plus as few other devices as I could get away with. I then unpacked the distribution (tomsrtbt-2.0.103), replaced the kernel, built the new distribution, and installed it on a floppy. Booting from that floppy fails with the error message above. > > > > I don't think I did anything wrong, but perhaps I missed a step somewhere? > > > > If anyone has seen and solved this problem, please pass on the solution. Thanks. > > > > -- > > Dave Hein <[email protected]> > > -- Dave Hein <[email protected]> Breathing in, I know I am breathing in. Breathing out, I know I am breathing out.