Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp server and the client is served with the image, but it's getting no menu. I got first: menu.c32 not a COM32R image. I learned to press the TAB key and I see the entries, I gave for this box. Then I selected the "reboot" entry and got a similar error: reboot.c32: not a COM32R image. I found no exact configuration example and I am now really very confused, because I even connot differentiate between bootps, PXE, gPXE, iPXe, etherboot, SYSLINUX, PXELINUX, GPXELINUX, ISOLINUX, UDIONLY .... No flame intended ... The files on the syslinux-6.02 are just too much and lost control completely. Additionally - this was my first step - I followed the debian instructions: https://wiki.debian.org/PXEBootInstall so, this part works. But looks very different. If I look into the files of these two ways, I see: syslinux vesamneu ~27 k debian vesamenu ~152k Finally, I'll achive to offer complete ISO images to boot via iSCSI. Hopefully. So, the one or other tip could help to to escapre the hell ;-) Thanks anyway and best regards, ++mabra
On Thu, Jun 19, 2014 at 9:24 PM, <webman at manfbraun.de> wrote:> I got first: > > menu.c32 not a COM32R image.Which says either your client messed up the download, you grabbed the wrong file or you're mixing versions. Be sure to copy bios/com32/menu/menu.c32 to your TFTP. http://www.syslinux.org/wiki/index.php/Common_Problems#Modules> I learned to press the TAB key and I see the entries, I gave for this > box. Then I selected the "reboot" entry and got a similar error: > > reboot.c32: not a COM32R image. > > I found no exact configuration example and I am now really > very confused, because I even connot differentiate between > bootps, PXE, gPXE, iPXe, etherboot, SYSLINUX, PXELINUX, > GPXELINUX, ISOLINUX, UDIONLY ....bootp server/services Preboot eXecution Environment, a defacto standard of extending DHCP booting. etherboot, a community and its original project, targetted to be a PXE stack to replace existing ones or add when there is none present. gPXE, a reimplementation of most of etherboot (effectively unmaintained) iPXE, an active fork of gPXE. SYSLINUX, a Syslinux variant for disk-based file systems, formerly only for FAT* but now covers all disk-based file systems PXELINUX, a Syslinux variant for PXE GPXELINUX, PXELINUX wrapped in gPXE to extend the existing PXE stack for TFTP/HTTP/iSCSI ISOLINUX, a Syslinux variant for ISO9660 file systems via the El Torito standard UNDIONLY, just meaning iPXE/gPXE only talks with the UNDI directly rather than attempting to load its own hardware-specific driver.> No flame intended ... > > The files on the syslinux-6.02 are just too much and lost control > completely. Additionally - this was my first step - I followed the > debian instructions:There's the source then three binary directories, each for a different target architecture.> https://wiki.debian.org/PXEBootInstall > > so, this part works. But looks very different. If I look into the files > of these two ways, I see: > > syslinux vesamneu ~27 k > debian vesamenu ~152kWhich will happen across versions from non-ELF to ELF. Think static versus dynamic binary.> Finally, I'll achive to offer complete ISO images to boot via iSCSI. > Hopefully.-- -Gene
> Hello ! > > I am completely new to syslinux. > > I followed this instruction manually: > > http://www.wonkity.com/~wblock/docs/html/pxe.html > > I am on debian and do not have syslinux installed, but using > this debian box as a tftp server. I had to modify the instructions > given by the installation above. I downloaded the 6.02 version > and copied the files to the tftp root. > > I am using dnsmasq as a tftp server and the client is served > with the image, but it's getting no menu. > > I got first: > > menu.c32 not a COM32R image. > > I learned to press the TAB key and I see the entries, I gave for this > box. Then I selected the "reboot" entry and got a similar error: > > reboot.c32: not a COM32R image. > > I found no exact configuration example and I am now really > very confused, because I even connot differentiate between > bootps, PXE, gPXE, iPXe, etherboot, SYSLINUX, PXELINUX, > GPXELINUX, ISOLINUX, UDIONLY .... > > No flame intended ... > > The files on the syslinux-6.02 are just too much and lost control > completely. Additionally - this was my first step - I followed the > debian instructions: > > https://wiki.debian.org/PXEBootInstall > > so, this part works. But looks very different. If I look into the files > of these two ways, I see: > > syslinux vesamneu ~27 k > debian vesamenu ~152k > > Finally, I'll achive to offer complete ISO images to boot via iSCSI. > Hopefully. > > So, the one or other tip could help to to escapre the hell ;-) > > Thanks anyway and best regards, > > ++mabraMost instructions /tutorials / articles... for using Syslinux are not updated to use version 6.xx. Since you are new to Syslinux and using Debian, I would suggest using the Syslinux _package_ from the Debian stable repo, which is still version 4.05. I believe it would help you understand those tutorials and achieve the expected results. Please note that the version of all the Syslinux c32 modules shall match the version of the Syslinux bootloader, so you should probably get rid of all the files that came from the different versions you have now and just use one (the Syslinux package from Debian stable would be my suggestion for your case). Regards, Ady.