search for: c0a

....405,CNMMH640.405,CNMMT640.405,CNMSH640.405,CNMST640.405,CNMPH640.405,CNMPT640.405,CNMUR640.407,CNMSR640.407,CNMMH640.407,CNMMT640.407,CNMSH640.407,CNMST640.407,CNMPH640.407,CNMPT640.407,CNMUR640.406,CNMSR640.406,CNMMH640.406,CNMMT640.406,CNMSH640.406,CNMST640.406,CNMPH640.406,CNMPT640.406,CNMUR640.c0a,CNMSR640.c0a,CNMMH640.c0a,CNMMT640.c0a,CNMSH640.c0a,CNMST640.c0a,CNMPH640.c0a,CNMPT640.c0a,CNMUR640.40b,CNMSR640.40b,CNMMH640.40b,CNMMT640.40b,CNMSH640.40b,CNMST640.40b,CNMPH640.40b,CNMPT640.40b,CNMUR640.40c,CNMSR640.40c,CNMMH640.40c,CNMMT640.40c,CNMSH640.40c,CNMST640.40c,CNMPH640.40c,CNMPT640.40c,...

...een using pxeboot to pull up a menu, to build or rebuild machines for years. We have this new server, and it fails. Times out. What's happening is that it tries in this order .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d .../pxelinux.cfg/01-88-99-aa-bb-cc-dd .../pxelinux.cfg/C0A8025B .../pxelinux.cfg/C0A8025 .../pxelinux.cfg/C0A802 .../pxelinux.cfg/C0A80 .../pxelinux.cfg/C0A8 .../pxelinux.cfg/C0A .../pxelinux.cfg/C0 .../pxelinux.cfg/C .../pxelinux.cfg/default The first are MAC addresses, etc. I want it to pull default. It takes *minutes* to time out each o...

...om the network. and i just do some experiment of reboot on the clients. but i am surprise of the clients booting failure after several cycles. and i got the info of the clients can not download the config file, such as: Trying to load: pxelinux.cfg/01-00-14-22-a1-53-85 Trying to load: pxelinux.cfg/C0A80146 Trying to load: pxelinux.cfg/C0A8014 Trying to load: pxelinux.cfg/C0A801 Trying to load: pxelinux.cfg/C0A80 Trying to load: pxelinux.cfg/C0A8 Trying to load: pxelinux.cfg/C0A Trying to load: pxelinux.cfg/C0 Trying to load: pxelinux.cfg/C Trying to load: pxelinux.cfg/default I am sure the file...

...9>. Mode octet [05/06 18:24:46.299] File <pxelinux.cfg\01-00-1e-68-a6-9e-a9> : error 2 in system call CreateFile Impossibile trovare il file specificato. [05/06 18:24:46.299] Connection received from 192.168.1.20 on port 57091 [05/06 18:24: 46.299] Read request for file <pxelinux.cfg/C0A80114>. Mode octet [05/06 18:24:46.299] File <pxelinux.cfg\C0A80114> : error 2 in system call CreateFile Impossibile trovare il file specificato. [05/06 18:24: 46.299] Connection received from 192.168.1.20 on port 57092 [05/06 18: 24:46.299] Read request for file <pxelinux.cfg/C0A8011&...

...or rebuild >> machines for years. We have this new server, and it fails. Times out. >> What's happening is that it tries in this order >> .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d >> .../pxelinux.cfg/01-88-99-aa-bb-cc-dd >> .../pxelinux.cfg/C0A8025B >> .../pxelinux.cfg/C0A8025 >> .../pxelinux.cfg/C0A802 >> .../pxelinux.cfg/C0A80 >> .../pxelinux.cfg/C0A8 >> .../pxelinux.cfg/C0A >> .../pxelinux.cfg/C0 >> .../pxelinux.cfg/C >> .../pxelinux.cfg/default >> >> The first...

...:03:37 atftpd[312]: Server thread exiting 13:03:37 atftpd[313]: Serving pxelinux.cfg/01-xx-xx-xx-xx-xx-xx to 192.168.1.67:49153 13:03:37 atftpd[313]: File /opt/tftpboot/pxelinux.cfg/01-xx-xx-xx-xx-xx-xx not found 13:03:37 atftpd[313]: Server thread exiting 13:03:37 atftpd[314]: Serving pxelinux.cfg/C0A80143 to 192.168.1.67:49154 13:03:37 atftpd[314]: File /opt/tftpboot/pxelinux.cfg/C0A80143 not found 13:03:37 atftpd[314]: Server thread exiting 13:03:37 atftpd[315]: Serving pxelinux.cfg/C0A8014 to 192.168.1.67:49155 13:03:37 atftpd[315]: File /opt/tftpboot/pxelinux.cfg/C0A8014 not found 13:03:37 a...

...0 DHCP IP:192.168.0.2 GATEWAY IP: 192.168.0.1 PXELINUX 3.11 2005-09-02 Copyright (c) 1994-2005 H. Peter Anvin UNDI data segment at 00094EA0 UNDI data segment size:3AE0 UNDI data segment at 00098980 UNDI data segment size: 60F8 PXE entry point found (we hope) at 9898:00DA My IP address seems to be C0A800FE 192.168.0.254 ip=192.168.0.254;0.0.0.0:192.168.0.1:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-0018-8b-f9-da-55 Trying to load: pxelinux.cfg/C0A800FE Trying to load: pxelinux.cfg/C0A800F Trying to load: pxelinux.cfg/C0A80 Trying to load: pxelinux.cfg/C0A8 Trying to load: pxelinu...

...me /pxelinux.0 Aug 5 13:10:26 server17 in.tftpd[5222]: RRQ from 192.168.1.240 filename /pxelinux.cfg/01-00-30-48-d3-d8-59 Aug 5 13:10:26 server17 in.tftpd[5222]: sending NAK (1, File not found) to 192.168.1.240 Aug 5 13:10:26 server17 in.tftpd[5223]: RRQ from 192.168.1.240 filename /pxelinux.cfg/C0A801F0 Aug 5 13:10:26 server17 in.tftpd[5223]: sending NAK (1, File not found) to 192.168.1.240 Aug 5 13:10:26 server17 in.tftpd[5224]: RRQ from 192.168.1.240 filename /pxelinux.cfg/C0A801F Aug 5 13:10:26 server17 in.tftpd[5225]: RRQ from 192.168.1.240 filename /pxelinux.cfg/C0A801 Aug 5 13:10:26...

...nux.0 it doesn't seem to be quite as verbose as pxelinux.0 once was about the search enumerations it makes in it's sibling pxelinux.cfg directory, which I miss: /mybootdir/pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C0A8025B /mybootdir/pxelinux.cfg/C0A8025 /mybootdir/pxelinux.cfg/C0A802 /mybootdir/pxelinux.cfg/C0A80 /mybootdir/pxelinux.cfg/C0A8 /mybootdir/pxelinux.cfg/C0A /mybootdir/pxelinux.cfg/C0 /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default Any thoughts and/or detailed clarification of how all the...

...up a menu, to build or rebuild > machines for years. We have this new server, and it fails. Times out. > What's happening is that it tries in this order > .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d > .../pxelinux.cfg/01-88-99-aa-bb-cc-dd > .../pxelinux.cfg/C0A8025B > .../pxelinux.cfg/C0A8025 > .../pxelinux.cfg/C0A802 > .../pxelinux.cfg/C0A80 > .../pxelinux.cfg/C0A8 > .../pxelinux.cfg/C0A > .../pxelinux.cfg/C0 > .../pxelinux.cfg/C > .../pxelinux.cfg/default > > The first are MAC addresses, etc. To be pedanti...

...ull up a menu, to build or rebuild > machines for years. We have this new server, and it fails. Times out. > What's happening is that it tries in this order > .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d > .../pxelinux.cfg/01-88-99-aa-bb-cc-dd > .../pxelinux.cfg/C0A8025B > .../pxelinux.cfg/C0A8025 > .../pxelinux.cfg/C0A802 > .../pxelinux.cfg/C0A80 > .../pxelinux.cfg/C0A8 > .../pxelinux.cfg/C0A > .../pxelinux.cfg/C0 > .../pxelinux.cfg/C > .../pxelinux.cfg/default > > The first are MAC addresses, etc. I want it to pull defau...

PXELINUX 3.85 pre13-1-gee43a6e* Copyright (C) 1994-2010 H. Peter Anvin et al !PXE entry point found (we hope) at 9F00:0680 via plan A UNDI code segment at 9F00 len 0AB0 UNDI data segment at 9E00 len 1000 Getting cached packet 01 02 03 My IP address seems to be C0A80168 192.168.1.104 ip=192.168.1.104:192.168.1.99:192.168.1.1:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-b0-c4-20-00-00-01 Trying to load: pxelinux.cfg/C0A80168 Trying to load: pxelinux.cfg/C0A8016 Trying to load: pxelinux.cfg/C0A801 Trying to load: pxelinux.cfg/C0A80 Trying to load:...

...ript.my 192.168.30.51" ocs_live_run="bash /tmp/custom-ocs-1" ocs_live_keymap="NONE" ocs_live_batch="no" ocs_lang="es_ES.UTF-8" nolocales* The client stay in the boot part: * Trying to load: pxelinux.cfg/01-00-14-22-a1-53-85 Trying to load: pxelinux.cfg/C0A80146 Trying to load: pxelinux.cfg/C0A8014 Trying to load: pxelinux.cfg/C0A801 Trying to load: pxelinux.cfg/C0A80 Trying to load: pxelinux.cfg/C0A8 Trying to load: pxelinux.cfg/C0A Trying to load: pxelinux.cfg/C0 Trying to load: pxelinux.cfg/C Trying to load: pxelinux.cfg/default * and never go on....

...; machines for years. We have this new server, and it fails. Times out. >>> What's happening is that it tries in this order >>> .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d >>> .../pxelinux.cfg/01-88-99-aa-bb-cc-dd >>> .../pxelinux.cfg/C0A8025B >>> .../pxelinux.cfg/C0A8025 >>> .../pxelinux.cfg/C0A802 >>> .../pxelinux.cfg/C0A80 >>> .../pxelinux.cfg/C0A8 >>> .../pxelinux.cfg/C0A >>> .../pxelinux.cfg/C0 >>> .../pxelinux.cfg/C >>> .../pxelinux...

...669]: RRQ from 192.168.2.21 filename pxelinux.0 Aug 16 23:27:17 pxeserver in.tftpd[1669]: tftp: client does not accept options Aug 16 23:27:17 pxeserver in.tftpd[1670]: RRQ from 192.168.2.21 filename pxelinux.0 Aug 16 23:27:17 pxeserver in.tftpd[1671]: RRQ from 192.168.2.21 filename pxelinux.cfg/C0A80215 Aug 16 23:27:17 pxeserver in.tftpd[1671]: sending NAK (1, File not found) to 192.168.2.21 Aug 16 23:27:17 pxeserver in.tftpd[1672]: RRQ from 192.168.2.21 filename pxelinux.cfg/C0A8021 Aug 16 23:27:17 pxeserver in.tftpd[1672]: sending NAK (1, File not found) to 192.168.2.21 Aug 16 23:27:17 px...

On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mar 8, 2014 9:27 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > > > > > > On 03/08/2014 10:06 PM, Gene Cumm wrote: > > >> Hi Gene, > > >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got > >

...d) to 192.168.0.102 Mar 25 14:46:28 smbsrv in.tftpd[18852]: RRQ from 192.168.0.102 filename pxelinux.cfg/01-00-01-6c-61-95-16 Mar 25 14:46:28 smbsrv in.tftpd[18852]: sending NAK (1, File not found) to 192.168.0.102 Mar 25 14:46:28 smbsrv in.tftpd[18853]: RRQ from 192.168.0.102 filename pxelinux.cfg/C0A80066 Mar 25 14:46:28 smbsrv in.tftpd[18853]: sending NAK (1, File not found) to 192.168.0.102 Mar 25 14:46:28 smbsrv in.tftpd[18854]: RRQ from 192.168.0.102 filename pxelinux.cfg/C0A8006 Mar 25 14:46:28 smbsrv in.tftpd[18854]: sending NAK (1, File not found) to 192.168.0.102 Mar 25 14:46:28 smbsrv...

...2002-01-01 Copyright (C) 1994-2002 H. PXELINUX 1.66 2002-01-01 Copyright (C) 1994-2002 H. Peter Anvin UNDI data segment at: 00090D40 UNDI data segment size: B450 UNDI code segment at: 0009C190 UNDI code segment size: 30E0 PXE entry point found (we hope) at 9C19:0106 My IP address seems to be C0A86697 192.168.102.151 ip=192.168.102.151:192.168.102.150:192.168.102.1:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/C0A86697 Trying to load: pxelinux.cfg/C0A8669 Trying to load: pxelinux.cfg/C0A866 Trying to load: pxelinux.cfg/C0A86 Trying to load: pxelinux.cfg/C0A8 Trying to load: pxelin...

...389]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/37313930-3631-5347-4834-353058385048 Oct 8 20:49:22 foreman in.tftpd[5390]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/01-38-63-bb-43-b7-d4 Oct 8 20:49:22 foreman in.tftpd[5392]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A86729 Oct 8 20:49:22 foreman in.tftpd[5393]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A8672 Oct 8 20:49:22 foreman in.tftpd[5394]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A867 Oct 8 20:49:22 foreman in.tftpd[5395]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A...

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Wednesday, October 07, 2015 4:43 PM >> To: For discussion of Syslinux and tftp-hpa; Geert Stappers >> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 >> >> On Wed, Oct