Displaying 8 results from an estimated 8 matches for "drblclient".
Did you mean:
dbclient
2014 Mar 09
2
Syslinux EFI + TFTPBOOT Support
On Sun, Mar 9, 2014 at 8:09 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
>> On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote:
>>>
>>> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware
>>> VMXNet3? Feel free to
2014 Mar 08
4
Syslinux EFI + TFTPBOOT Support
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
> >
2014 Mar 10
0
Syslinux EFI + TFTPBOOT Support
...tpd[4821]: Serving drblwp.png to
192.168.120.3:1552
Mar 10 08:13:14 drbldbn atftpd[4821]: Serving vmlinuz-pxe to
192.168.120.3:1553
Mar 10 08:13:17 drbldbn atftpd[4821]: Serving initrd-pxe.img to
192.168.120.3:1554
Mar 10 08:14:25 drbldbn dhcpd: Client 0:c:29:68:f3:23 requests
1:3:6:c:f:1c:2a - DRBLClient - no dhcp-client-id
=================
As you can see, with one core this time it took longer to download
initrd-pxe.img.
For the Lenovo client, any test I could do?
Thanks in advance.
Steven.
--
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center fo...
2014 Mar 07
2
Syslinux EFI + TFTPBOOT Support
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
>>
2014 Mar 07
2
Syslinux EFI + TFTPBOOT Support
...the debug/verbose messages in system log. The messages like the following will be shown:
# Client 0:c:29:3b:34:fb requests 1:2:3:5:6:b:c:d:f:10:11:12:2b:36:3c:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
# Client 0:c:29:3b:34:fb requests 1:3:6:c:f:1c:28:29:2a - DRBLClient - no dhcp-client-id
# Begin of log command
log(info, concat("Client ",
binary-to-ascii(16, 8, ":", substring(hardware, 1, 6)),
" requests ",
binary-to-ascii(16, 8, ":", option dhcp-parameter-request-list),
" - ",...
2014 Nov 28
0
pxelinux efi64 boot woes on hyper-v gen 2
On Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote:
> Gene,
>
> As it happened I started working on this again just as you mailed me.
I saw it in IRC.
> It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no
2014 Nov 28
2
pxelinux efi64 boot woes on hyper-v gen 2
...the debug/verbose messages in system log. The messages like the following will be shown:
# Client 0:c:29:3b:34:fb requests 1:2:3:5:6:b:c:d:f:10:11:12:2b:36:3c:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
# Client 0:c:29:3b:34:fb requests 1:3:6:c:f:1c:28:29:2a - DRBLClient - no dhcp-client-id
# Begin of log command
log-facility local7 ;
log(info, concat("Client ",
binary-to-ascii(16, 8, ":", substring(hardware, 1, 6)),
" requests ",
binary-to-ascii(16, 8, ":", option dhcp-parameter-request-list),...
2014 Nov 27
2
pxelinux efi64 boot woes on hyper-v gen 2
Gene,
As it happened I started working on this again just as you mailed me.
It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy.
The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to