Hello Ben, Try the following:
gPXE> initrd http://ip-address/gpxe/initrd gPXE> kernel "ramdisk_blocksize=4096 initrd=/gpxe/initrd root=/dev/ram0 ramdisk_size=144000000 console=ttyS3 splash=silent vga=791" gPXE> boot Kernel "appends" go after the kernel filename, and your initrd can be downloaded before or after the kernel, but both have to be downloaded before gPXE will pass control to your downloaded kernel, via the "boot" command. Also, the "chain" command can be used in lieu of "kernel," as a method of downloading a kernel and executing it ("booting" it) immediately. Cheers, Andrew Bobulsky ramdisk_blocksize=4096 initrd=/gpxe/initrd root=/dev/ram0 ramdisk_size=144000000 console=ttyS3 splash=silent vga=791 On Fri, Aug 19, 2011 at 11:30 AM, Ben Francis <wireless...@gmail.com> wrote: > I have a netboot system that works over TFTP. It consists of vmlinuz and > initrd. > > I want to convert it to gPXE so it will boot across subnets. > > So I put the files on a web server and tried to test from the gPXE command > line: > > gPXE> kernel http://ip-address/gpxe/vmlinuz > > That command works. However, > > gPXE> initrd http://ip-address/gpxe/initrd > > just slowly fills up the screen with periods. I tried using the append > command from the working pxelinux setup: > > append ramdisk_blocksize=4096 initrd=/gpxe/initrd root=/dev/ram0 > ramdisk_size=144000000 console=ttyS3 splash=silent vga=791 > > but gpxe doesn't have append. > > The initrd is about 143MB. > > What to do? > > Ben > > > > _______________________________________________ > gPXE mailing list > gPXE@etherboot.org > http://etherboot.org/mailman/listinfo/gpxe > > _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
