10

Yes, this is possible provided your target network is configured to relay DHCP and TFTP traffic. You'll likely need IP "helper addresses" on the client's network that point back to the actual DHCP server's IP address. See: Broadcast between VLANs


2

Instead of making sure that the boot-loader is configured to pass the necessary parameter to the kernel, just get rid of the feature altogether: aptitude purge biosdevname && update-initramfs -u


2

You are using the wrong install media. The Server Edition ISO does not use a graphical installer program. The server edition uses a text based menu based process for the install. From: https://help.ubuntu.com/13.10/serverguide/installing-from-cd.html Unlike the Desktop Edition, the Server Edition does not include a graphical installation program. The ...


2

The syslinux.efi is the correct loader; unfortunately 6.03 has several issues affecting both UEFI and PXE. i.e. http://www.syslinux.org/archives/2016-October/025395.html this is just an example, there are many more issues, like faulty TFTP transfers, bad next-server detection, etc. The patches for all these issues have been submitted and some of them are ...


2

Note that the configfile is relative to the pathprefix: if option arch = 00:00 { option pxelinux.configfile "common.cfg"; option pxelinux.pathprefix "/pxelinux/configs/"; filename "/pxelinux/images/BIOS/pxelinux.0"; this will look for a config file called /pxelinux/configs/common.cfg ...


2

Let's consider that you are trying to boot BIOS clients if your NBP is pxelinux.0 then you won't be able to use the HTTP capabilities. For HTTP and FTP transfers you must use lpxelinux.0 instead. The prepending "l" stands for the use of the lwIP (lightweight IP) library.


2

If your SAN LUN is the next device in the system's boot order after the install CD, then this should do it: LOCALBOOT -1 This causes ISOLINUX to report that it's failed to boot, causing the next device in the boot order to be used instead.


1

pxelinux.0 offers you a PXE menu for booting legacy targets BOOTX64.EFI will help you to boot a particular Linux distro but you won't have a menu of different PXE booting assets pxelinux.efi syslinux.efi offers you a PXE menu for booting UEFI targets


1

1) Definitely the 20 min for a 40 Meg TFTP transfer is the result of Syslinux 6.03 UEFI TFTP bug/s. The only way you have to overcome this is either upgrade Syslinux (even when today 6.04 final does not exist) or transfer by HTTP instead. 2) Arch:00007 implies you have an UEFI 64 client, you might have several issues loading UEFI 32 and/or 32 Bit OSs on ...


1

You can't mix com32 modules from one version of syslinux/pxelinux with another version of syslinux/pxelinux. If you want to build a working pxelinux and acpioff.c32, build the code from the tip of this branch: https://github.com/awalls-cx18/syslinux/tree/acpi_off?files=1


1

this is not correct if option architecture-type = 00:07 { filename "pxe/shim.efi"; } else { filename "pxe/pxelinux.0"; please consider DHCP Option 93 Client's pre-OS runtime 0 BIOS 6 EFI32 7 EFI64 9 EFI64 In your case an UEFI 64 client using DHCP option 93 = 9 would get ...


1

Using memdisk of course you cannot pass parameters to your winpe.iso if you decide to boot your Win PE "WDS style" (pxeboot.n12/bootmgr.exe/BCD etc) you also cannot pass unattended parameters to your winpe.wim therefore you have only one choice: a custom application taking control right after winpe.wim is booted providing the freedom of retrieving (menu) ...


1

have you compared the USB disk identifier on both to see WHICH FAT32 or NTFS each version is using? this is often a drive format error - there are a about 20 different FAT32 formats , and quite a few NTFS - GRUB has problems with some of them


1

The problem was solved enabling Legacy Only mode in the Boot Configuration of the BIOS. It must follow this order: Legacy Only Hard Disk 0 If we put only "Legacy Only", the machine fails to boot anyway.


Only top voted, non community-wiki answers of a minimum length are eligible