similar to: Booting ISO images over PXE

Hello list, I had to boot a Dell Diagnostic Disk today, and tried doing this via memdisk - which was when I noticed memdisk isn't working for me at all, neither from pxelinux nor syslinux. After trying around with 'raw', 'bigraw' and the like I noticed it doesn't even do anything when just using: LABEL diag KERNEL memdisk .. when I try that: boot: diag nothing

Hallo, I'm just trying to boot a Clonezilla *.iso (live-20100521-lucid) via PXE; Label clonezilla kernel memdisk append iso raw initrd iso/clonezilla.iso The first step is ok - I see the boot menu of the *.iso. When I choose "Clonezilla live" the system fails with Isolinux: Disk error 02, AX = 4224, drive E0 when I choose "freedos" it fails with

Hello all, I understand that during PXE boot, it goes into the pxelinux.cfg and it states: 1. "it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam "gethostip" to compute the hexadecimal IP address for any host.) If that file is not found, it will remove one hex digit and try

Hi there everybody! I have the following problem: when i launch isobuster (a tool with which you can extract nearly every existable cd-image) I get an error in the console which says that a file called isobuster.enu couldnt be loaded. It should be in the isobuster directory but on my whole box there is no such file so i think it is implemented in the exe file which is the only one in the

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

I have gotten a couple of probes about NTFS support for Syslinux, and I would like to gauge how serious it is. I'm considering using it as a pilot project for writing Syslinux filesystem modules in C. However, an installer, or more realistically two (one for Win32, one for Linux) have to be written, so it's still a real time commitment. -hpa

Hello, I know this might be slightly off-topic, but I know at least hpa has an intimate knowledge of the linux boot process - and I would want to use it with syslinux/pxelinux, so I figure it might not hurt too much to ask: Is it possible to embedd the initrd with the linux kernel in a way similiar to how it works on some embedded systems? There, you provide an object file with the filesystem,

Is it possible to specify the root device in extlinux.conf by an ext2 label or uuid? How difficult is it to add this support if it is not there? I am in a situation where this is needed and my fstab is configured appropriately, but extlinux.conf still needs to be manually updated when the root drive changes to a different scsi device (due to the number of drives on the bus and the order of the

Hello, Has anyone thought about how one could use the "keeppxe" option with a vmlinuz/initrd? It would allow one to boot this combination, and if possible the linux kernel/initrd (assuming we have busybox in there) would not have to run udhcp and instead leverage what pxe stack information is loaded. The problem is I don't know of any PXE/UNDI linux utilities to look at the pxe

Hello, I was browsing the code for memdisk (I want to adjust it to my hardware) and noticed a couple of things that I am struggling to understand. I would appreciate if someone could clarify the following mysteries to me: 1) _binary_memdisk_bin_start[], _binary_memdisk_bin_end[] and _binary_memdisk_bin_size[]; These variables are declared (as extern const chat in 'setup.c')

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A

> Hi, > > Ady wrote: > > cdrtools.sourceforge.net/private/man/cdrtools-3.01axx/mkisofs.8.html > > Mac Boot entries for the Apple Mac platform. > > Interesting feature. But the El Torito specs of Phoenix and > IBM of 1994 state that "Mac" would be Platform Id 2. > http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf > Page

Axel and everyone Your questions are valid. I had similar question when I bought these cards. These cards in particular have no rom chip on the pci card. If you plug these into a computer they do nothing until you load them with there firmware. When vt6410 are used on motherboards not as stand alone cards the bios has this firmware and loads it into the chip set on boot making them show up

Hi, > I don't understand why you say "*But* the El Torito...". I don't see > a difference with what the mkisofs manual says. The manual announces "Mac" for Apple Mac. The program obviously writes Platform Id 1 in this case. The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". In the sum this does not match. A bug in mkisofs would be the

Extract ElTorio No Emulation image and boot from PXE ? Is this possible, can PXELINUX + MEMDISC intercept the BIOS calls and pretend to the 3rd party No Emulation image to be loading the data from a CD (but instead copy from memory). The driver would be a Real Mode driver and use some part of memory above 1Mb to store the data. I would expect this to be risky, especially if the No Emulation

> Hi, > > > Unfortunately I get the error message: > > isohybrid: slint64-14.1.iso: unable to find mac efi image > > This is probably due to El Torito Platform id "Mac" in > > -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ > -eltorito-boot isolinux/macboot.img \ > > This caused in the image >

Hi, Ady wrote: > cdrtools.sourceforge.net/private/man/cdrtools-3.01axx/mkisofs.8.html > Mac Boot entries for the Apple Mac platform. Interesting feature. But the El Torito specs of Phoenix and IBM of 1994 state that "Mac" would be Platform Id 2. http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf Page 9, Figure 2, Offset 1 of Validation Entry. The

Hi, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The