[syslinux] pxelinux limits on imagefile for tftp transfer?
Martin Egloff
martin1.egloff at hispeed.ch
Sat Jun 19 12:10:14 PDT 2004
>> snip...
>>
>> With a ramdisk image size of about 60 Mb things go well, the file gets
>> transfered completely and Linux boots perfectly.
>>
>> With a ramdisk image size of about 104 Mb the tftp transfer of the
>> kernel succeds but
>> the transfer of the ramdisk image fails. As tftp daemon I use atftpd.
>> Is log says:
>>
>> tftpd: Requested file to big, increase BLKSIZE
>>
>> At the end, the image is going to be 150 Mb. Is there any experiance
>> out there with this size of image to transfer?
>> Is there a way to convice pxelinux to use another (bigger) blocksize?
>>
>> snip...
>
> What version of atftpd? If this happens with 0.7, we should send a bug
> report to the atftpd people (in the meantime you can use tftp-hpa); if
> this is an earlier version, try atftpd 0.7.
It is version 0.6.3.
I switched to tftp-hpa which I got to work finally. Obviously it doesn't
like if the requested filename (pxelinux.0) is a symbolic link. It said
it doesn't find the file. Is this a known issue?
Atftpd worked on the same file.
>
> With unicast TFTP, block numbers should just roll over harmlessly.
> Doesn't work with multicast, however, but PXELINUX doesn't use it.
I had a brief look at the code of version 0.7 of atftpd. I'm not sure
but I think the problem ist still there. I'll check it as soon as it
gets into debian 'testing'
Martin
More information about the Syslinux
mailing list