On 29 March 2017 at 13:53, Ковалёв Сергей SKovalev@ptsecurity.com wrote:
Hello Neil,
If imgargs is a command available on your device-type
I could do this without 'imgargs' and it succeed:
set console console=ttyS0,115200n8 lava_mac={LAVA_MAC} set extraargs initrd=/initramfs.cpio root=/dev/ram0 ip=dhcp kernel http://192.168.0.1:8000/linaro/debian/vmlinuz ${extraargs} ${console} initrd http://192.168.0.1:8000/linaro/debian/initramfs.cpio ===
This is not the same as how the lava log shows:
iPXE> [?25hkernel tftp://192.168.0.1/72/tftp-deploy-WDRuCl/kernel/vmlinuz ${extraargs} ${console}"
You've changed the protocol from tftp to http.
Your version of iPXE claims to support TFTP: Features: DNS HTTP iSCSI TFTP SRP AoE EFI Menu However, maybe that isn't working fully.
You're also testing with the initramfs.cpio not the compressed initramfs.cpio.gz
Try putting the files into the tftp location manually and use that path. Also try with the compressed initramfs.
Then, leave the device running and see if it has actually booted but just not sent any output to the console.
Please always provide the full log.
That was answer to previous letter (with logs) so I didn't include logs again. This time I attach job definition and logs.
So the question is previous: what do you do to make it work or what I have missed?
This looks like a difference in how your device behaves compared to the x86 machines we use. Using iPXE means that you are bypassing the UEFI, maybe that could be part of the problem and you'll need to change the boot method from ipxe to uefi-menu with a UEFI menu item which loads Grub etc.
If TFTP doesn't work and http does, you could change the jinja2 template commands to use http but you will have to retain the same directory structure as TFTP for the files to be found by your device.
You need to work out which commands can work and how to adapt the jinja2 template to use those commands.