search for: nbi_img

...or "tftp://<my-server>/shared/vmlinuz" in your > configs instead of "../shared/vmlinuz" (which is prone to issues). Because pxelinux.0, bootia32.efi and bootx64.efi are different names, so I can put them in the same path, no problem for this, i.e. $ ls -alFh /tftpboot/nbi_img/{*.0,*.efi} -rw-r--r-- 1 root root 157K Apr 22 15:30 /tftpboot/nbi_img/bootia32.efi -rw-r--r-- 1 root root 160K Apr 22 15:30 /tftpboot/nbi_img/bootx64.efi -rw-r--r-- 1 root root 105K Apr 22 15:30 /tftpboot/nbi_img/gpxelinux.0 -rw-r--r-- 1 root root 74K Apr 22 15:30 /tftpboot/nbi_img/lpxelinux.0 -r...

...://www.syslinux.org/archives/2013-June/020242.html My screen only shows: ==================== Getting cached packets My IP is 192.168.1.3 ==================== (See attached file "uefi-netboot.png") I am sure I use the precompiled binaries from 6.03-pre7 from kernel.org: strings /tftpboot/nbi_img/bootx64.efi | grep -i "^syslinux 6.03" Syslinux 6.03 (EFI; 6.03-pre7) I also compared its sha1sum (attached file "sha1sum.txt") and confirmed that. >From the system log file (attached file "daemon-log.txt"), apparently the uEFI x86_64 did try to fetch bootx64.efi a...

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

...;my-server>/shared/vmlinuz" in your > > configs instead of "../shared/vmlinuz" (which is prone to issues). > Because pxelinux.0, bootia32.efi and bootx64.efi are different names, so > I can put them in the same path, no problem for this, i.e. > $ ls -alFh /tftpboot/nbi_img/{*.0,*.efi} > -rw-r--r-- 1 root root 157K Apr 22 15:30 /tftpboot/nbi_img/bootia32.efi > -rw-r--r-- 1 root root 160K Apr 22 15:30 /tftpboot/nbi_img/bootx64.efi > -rw-r--r-- 1 root root 105K Apr 22 15:30 /tftpboot/nbi_img/gpxelinux.0 > -rw-r--r-- 1 root root 74K Apr 22 15:30 /tftpboot/nb...

.... Mar 8 14:48:29 atftpd[11886]: timeout: retrying... ==================== My /etc/default/atftpd is: ==================== USE_INETD=false OPTIONS="--tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.255.0.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 --port 69 /tftpboot/nbi_img/" ==================== Files are in the correct path: ls -alFh /tftpboot/nbi_img/{*.efi,*e64} -rw-r--r-- 1 root root 179K Mar 7 21:41 /tftpboot/nbi_img/bootx64.efi -rw-r--r-- 1 root root 137K Mar 7 21:41 /tftpboot/nbi_img/ldlinux.e64 and they were extracted from prebuilt binary 6.03-pre7 ta...

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

On 2014?03?07? 23:05, Ady wrote: > I understand that these remarks might seem not the main issue, but I > tend to think that once you are successful while using only "default" > > values and in a minimalistic case, you could add complexity > (different paths, multiple firmwares, additional kernels, multiple > cfg files...). Ady, Thanks. I will follow your advice to

....html > My screen only shows: > ==================== > Getting cached packets > My IP is 192.168.1.3 > ==================== > (See attached file "uefi-netboot.png") > > I am sure I use the precompiled binaries from 6.03-pre7 from kernel.org: > strings /tftpboot/nbi_img/bootx64.efi | grep -i "^syslinux 6.03" > Syslinux 6.03 (EFI; 6.03-pre7) > > I also compared its sha1sum (attached file "sha1sum.txt") and confirmed > that. > From the system log file (attached file "daemon-log.txt"), apparently > the uEFI x86_64 did...

....html > My screen only shows: > ==================== > Getting cached packets > My IP is 192.168.1.3 > ==================== > (See attached file "uefi-netboot.png") > > I am sure I use the precompiled binaries from 6.03-pre7 from kernel.org: > strings /tftpboot/nbi_img/bootx64.efi | grep -i "^syslinux 6.03" > Syslinux 6.03 (EFI; 6.03-pre7) > > I also compared its sha1sum (attached file "sha1sum.txt") and confirmed > that. > From the system log file (attached file "daemon-log.txt"), apparently > the uEFI x86_64 did...

...out: retrying... > Mar 8 14:48:19 atftpd[11886]: timeout: retrying... > Mar 8 14:48:24 atftpd[11886]: timeout: retrying... > Mar 8 14:48:29 atftpd[11886]: timeout: retrying... > and they were extracted from prebuilt binary 6.03-pre7 tarball on > kernel.org: > sha1sum /tftpboot/nbi_img/{*.efi,*e64} > d0ca7d52228231b08c36967262cb796be9e71499 /tftpboot/nbi_img/bootx64.efi > 55f17d57e1790071af0cb84e0ac6109a210f06ca /tftpboot/nbi_img/ldlinux.e64 Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > Another thing you I'd like to mentioned is, aft...

Hi all, I'm looking for a cloning solution for our Windows/Linux/*nix computer park and ran into Clonezilla. Apparantely the DRBL and other documentation mentions CentOS as a suitable base for it. Does anybody on this list use this solution and can say something about it in the running-Clonezilla-with-CentOS-context, be it recommendations, gotchas', warnings or whatever? Thanks. -- BW,