similar to: A UEFI

Ady, There are at least 3 ways to set up your DHCP server to differentiate between std DHCP, BIOS PXE and UEFI PXE. Option 93 (arch) is one way. In ISC syntax, here's 3 ways: 1. Match on VCI class "pxe-clients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; set vendor-string = substring ( option vendor-class-identifier, 0, 9);

This is a post I sent by mistake directly to Ady without a reply to all (i.e., to the thread "Fail to set up UEFI syslinux on ArchLinux USB Flash Drive") It should go between Ady's post of Sun Mar 15 13:23:26 PDT 2015 and Ady's post of Mon Mar 16 06:03:58 PDT 2015 ---------- Forwarded message ---------- From: alex lupu <alupu01 at gmail.com> Date: Sun, Mar 15, 2015 at 7:07

On 03/21/16 19:53, jsl6uy js16uy wrote: > Apologies if this has been gone over, but I believe I have checked the > intertubes more than a bit..... > > I am using libvirt and have vms booting under an OVMF.fd to use an efi > firmware. I can create vms, linux ubuntu, and they will boot up. > However, everytime I reboot am I dropped into the default efi shell > provide by the

Hi Ady, I'm the developer of manjaroiso, the tool we use to build our install medias for Manjaro Linux. During our testings we found out, that syslinux6 won't work on older hardware. I've a new Lenovo i7 notebook which booted up our images just fine. Even with syslinux6. On my other PCs I got similar error messages as Carl got. Here is the code I'm using for either syslinux6

Hi there, since I didn't had the time to test, this might be the solution for the issue Arch-based distros faced: https://projects.archlinux.org/svntogit/packages.git/plain/trunk/syslinux-6.02-fix-chainloading.patch?h=packages/syslinux This is included in the latest syslinux package you find in testing/unstable at Manjaro. kind regards Phil On 11/23/2013 03:44 PM, Philip M?ller wrote:

> Ady wrote: > > The reason genisoimage is highly modified is because... It is > > unmaintained! > > Sad but true. The cdrkit website is gone. Most "original" is > the debian source package. > > > > The "real" genisoimage (and any reincarnation of > > it) might never work with Syslinux; who knows? > > It works fine for BIOS

Ady Ady via Syslinux wrote: > > As usual, builds/versions should not be mixed, at least within the same > platform (bios/ia32/x64). > > Currently, the Syslinux-related binary packages in Debian are: > > _ extlinux > _ isolinux > _ pxelinux > _ syslinux > _ syslinux-common > _ syslinux-efi > _ syslinux-utils > > The list of packages and their

This is slightly off-topic for the Syslinux mailing list, but I think it is still pertinent and it might be helpful anyway. I am confused about some conflicting information regarding DHCP option 93, Architecture Type. The UEFI specification v.2.4 Errata B, Table 179, "PXE Tag Definitions for EFI", makes reference to a table in:

On 11/6/14, Ady <ady-sf at hotmail.com> wrote: > >> I have done another install to the usb stick. >> >> # syslinux --directory EFI/BOOT --install /dev/sdc1 >> >> ...this creates files ldlinux.c32 and ldlinux.sys in /EFI/BOOT >> >> I then mounted the 1st partition of the usb stick and copied >> syslinux.efi and ldlinux.e64 from

Hi Ady, Ady Ady via Syslinux wrote: > > To me, it is not so clear what exactly is your goal. sorry for not being detailed enough. > Do you want to build an image for an internal HDD that could be capable > of booting in both, BIOS mode and UEFI mode? Yes. This would make us independent from the BIOS boot mode. > Or, is this for a portable (USB) device? Maybe - would be nice

> It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or > DVD on older - non-UEFI - systems. Any attempt to do so will result in the > following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = > 4279, drive FE Is this happening on "every" system? Or are we talking about specific models or with specific characteristics? Is this behavior

> Hello > > > > > > I'm currently working on a project to rolling out a new TFTP boot > server, for a fairly large infrastructure (>200 servers, >1500 > clients, with heterogeneous configurations/setups). We are using > Syslinux version 6.03 for all the function within our TFTP server. > > > > > > We

Hi, Bruno Cornec wrote: > With grub.efi (0.99 version from RHEL6) I can have access to the grub > prompt. Most of the various EFI bootable ISOs use FAT images with GRUB2 equipment. E.g. this 250 MB image: http://cdimage.debian.org/debian-cd/8.2.0/amd64/iso-cd/debian-8.2.0-amd64-netinst.iso > Any other idea wrt debugging that is again welcome. I dimly remember to have read a sparse

> Im a long time PXE boot fan. I use it for wimbooting windows PE, linux > images via http, and memtest mainly. > > Ive got it nicely customised with my own graphics etc. > > Then UEFI booting came along. Till now ive been content simply setting > bios's to CSM mode and doing my thing.... > > Ive had another go at EFI PXE booting and can now get the menus and

> > On 7/1/2015 2:58 AM, Gene Cumm wrote: > >> I'm setting up UEFI booting and got to the point of having the system talk > >> >to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and > >> >then continuously request the secondary image file (ldlinux.e64). > > So it appears to go deaf. > > > >> >I'm wondering

> We're having the following issue: when in UEFI mode, > any output/errors from a lua script is invisible! > > This occurs even just running 'lua -v'. It runs and returns to > a (visible) 'boot:' prompt, but there is simply no output visible > from lua! (It does do a linefeed, but no visible text appears.) Yes, the report can be confirmed. FWIW, the

Thanks VERY MUCH for all the info and help! Apologies for the extreme delay. I got distracted by other threads that forced out this work to later date. Also some frustration as well. ;) I completely missed this update. Apologies and thanks Will be diving back into this shortly! On Thu, Mar 24, 2016 at 3:57 PM, Laszlo Ersek <lersek@redhat.com> wrote: > On 03/21/16 19:53, jsl6uy js16uy

Hello, Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > Not at this time, no. It took me quite some time to find that :-( Google didn't really help. I'd like to get a bit more details on this issue: 1/ Using syslinux.efi for PXE booting of a UEFI server is working for me. 2/ Using

> Let me know what kind of info would be useful for debugging the > mboot issue, and I will collect it all. Also, EFI is still somewhat > new to me, so I don't know how to find the UEFI firmware revision > or UEFI extension agents. I'll see if it's in the server manual, > but if you have an idea how one typically finds those, I'd appreciate > any pointers. >

> Dear gentlemen, > > here goes the documentation fix I was talking about :-) > > The Wiki page on PXElinux, specifically the chapter on UEFI at the end > of that page: > https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#UEFI > ...contains a few examples of ISC DHCPd configuration. > > The stumbling block for me was the syntax of these "if"