lkml.org 
[lkml]   [2000]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: INITRD/RAMDISK/SYSLINUX booting fails with new kernel (vs 2.2series)
On Mon, 21 Aug 2000, H. Peter Anvin wrote:

> Mike Galbraith wrote:
> >
> > On Mon, 21 Aug 2000, Michael Peddemors wrote:
> >
> > > On Mon, 21 Aug 2000, Mike Galbraith wrote:
> > >
> > > > Hi Michael,
> > > >
> > > > I booted test7-pre5 via syslinux-1.44 with a minimal initrd.gz today.
> > > > Can't do much with kernel and initrd on a floppy, but she mounted
> > > > /dev/ram0 just fine. I do not have devfs compiled into this kernel..
> > > > nor any idea how to use it properly if I _did_ enable it ;-).
> > >
> > > I haven't got DEVFS enabled.
> > > append= release=VPN-1.1b console=tty0 initrd=initrd.gz ramdisk_size=4096
> > > boot=/dev/fd0u1743,vfat load_ramdisk=1 root=/dev/ram0
> >
> > Now, _I'm puzzled_ ;-) None of these command-line options mean spit.
> > (you should not need load_ramdisk=1, that's implicit in initrd=, and
> > you shouldn't need to say explicitly what the rd size is.. that's a
> > responsibility of the boot-loader. [why this option boot=/dev/fd0u1743,vfat])
> >
> > Please send me (offline) your grep '=[ym]' .config output to stare at.
> > I don't doubt that it doesn't work for you, but it works fine for me.
> >
>
> load_ramdisk=1 means the kernel should try to load a ramdisk from a floppy after boot. This will trash your initrd.

Yes, I tried that (boot/root) functionality too. I didn't think to see
if superfulous information interfered though. (Does it Michael?)

-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:37    [W:0.035 / U:3.732 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site