Hello ALL, I've got a diskless server working (under Gentoo), booting on it works. (a linux session start with no problem.) My Big problem, is to get Memdisk to boot with PXE. In fact memdisk is loaded, but it cannot find the img file. I've tried a lot of thing, but nothing works... tftp use : /diskless the config file for PXE in then in : /diskless/pxelinux.cfg/ the root for the slaves linux is : /diskless/all/ default in /diskless/pxelinux.cfg/ : ***** PROMPT 1 DEFAULT 0 label 0 kernel /bzImage APPEND ip=dhcp root=/dev/nfs nfsroot=192.168.1.1:/diskless/all label 1 kernel /memdisk append initrd=fdos1440.img label 2 kernel /memdisk append initrd=/fdos1440.img label 3 kernel /memdisk append initrd=fd label 4 kernel /memdisk append initrd=/fd ***** The first label it a good one, it boots linux OK. The others are test labels, none works. I copies the fdos1440.img to fd, to see if it was maybe an extension error... any one has an Idea ?? thanks
put the disk image in /diskless. That should work. Mine is called fdboot.img, as on the FreeDOS cdrom. Best scenario for testing PXE is to get MEMTEST86+ working (www.memtest.org), and then try MEMDISK + (Win98)bootdisk image. my example below shows a Bochs harddisk image being loaded (cdrv.img) Bernd Blaauw F:. | memdisk | memtest | pxelinux.0 | fdboot.img | \---pxelinux.cfg default prompt 0 default 3 ontimeout 3 timeout 150 # standard FreeDOS bootdisk, 360KB, GZIP compressed (www.gzip.org) label 0 kernel memtest label 1 kernel memdisk append initrd=win98.img label 2 kernel memdisk append initrd=fdboot.img label 3 kernel memdisk append initrd=cdrv.img ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing: http://www.fontys.nl/disclaimer The above disclaimer applies to this e-mail message. ----------------------------------------------------------------
Hi william,> kernel /memdisk > append initrd=fdos1440.imgDoes this image is available in the root directory of your tftp server ? (in your case the same place as your memdisk) Initrd path is relative to the root directory of your tftp server. -- Erwan Velu Linux Cluster Distribution Project Manager Mandrakesoft 43 rue d'aboukir 75002 Paris Phone Number : +33 (0) 1 40 41 17 94 Fax Number : +33 (0) 1 40 41 92 00 OpenPGP key : http://www.mandrakesecure.net/cks/
Thank all, But I found the problem.. :) For some reason, the image was chmod in read only for root...... yep a typical but i didn't see it coming. So now, well I've got it working, even did a 15Mo hard drive image in a gzip format , all works great... The sad part is some utilities (from ubcd) like docmem or windiag, just hang the computer, and the western digital tools reboot the computer.... Well I've was Happy with this server, it would help me for the 150 computers we build every day. But like in all computer stories..... I've done got to update the bios of the Asrock k7s8x that we use, for the Sempron... And now the Netboot option is broken, it doesn't even tries to load the little pxe agent on the mainboard.... So... after All this, I'm stuck with some other problem... :( haaaaaaaa Thank again... -----Message d'origine----- De : Erwan Velu [mailto:erwan at mandrakesoft.com] Envoy? : jeudi 26 ao?t 2004 15:11 ? : William Sellier Cc : syslinux at zytor.com Objet : Re: [syslinux] pxe + memdisk ..?? Hi william,> kernel /memdisk > append initrd=fdos1440.imgDoes this image is available in the root directory of your tftp server ? (in your case the same place as your memdisk) Initrd path is relative to the root directory of your tftp server. -- Erwan Velu Linux Cluster Distribution Project Manager Mandrakesoft 43 rue d'aboukir 75002 Paris Phone Number : +33 (0) 1 40 41 17 94 Fax Number : +33 (0) 1 40 41 92 00 OpenPGP key : http://www.mandrakesecure.net/cks/