[syslinux] Isohybrid wiki page and UEFI

[Bruno Cornec]

Bruno Cornec via Syslinux said on Thu, Oct 29, 2015 at 04:21:30PM +0100:
>Bruno Cornec via Syslinux said on Sun, Oct 25, 2015 at 12:39:53PM +0100:
>>I'm indeed trying to have everything I need on the boot part of the
>>ISO9660 image (kernel and an initrd which is normally built by
>>MondoRescue which then mounts the ISO9660 FS to have access to
>>additional content once booted). For now I do not seem to get to boot the
>>kernel.
>>
>>My machines are HP BL 460 Gen9 servers with FW I36 07/21/2015, which is
>>the latest one available, even if I could try to get a beta one if
>>needed.
>
>So as a summary of what I've tried up to now:
>
>The ISO image I make with the script previously shown has now 4
>different efi binaries to boot from in the same VFAT32 image embedded on
>the ISO with either mksiofs (from RHEL7) or upstream xorriso.
>
>With syslinux 6.03, syslinux from Gene git or syslinux with debug
>symbols I get the red screens previously shared, and that I've seen
>mentioned in some other messages here, even from people trying with PXE.
>
>With grub.efi (0.99 version from RHEL6) I can have access to the grub
>prompt.
>
>All these are launched from the UEFI menu navigating to the virtual
>media image (my built ISO) the efi binary in each case.
>
>Knowing that again on the same system, launching syslinux.efi (classic
>6.03) through PXE or from the local HDD *is* working.

OK, I was trying to document this PXE setup for some colleagues here,
and had in fact additional iissues:
while I can indeed launch syslinux.efi through PXE, and get a nice
menu,once I choose an entry, I get the kernel loaded fine, but never
have the initrd :-( Seems ther are also here issue with tftp.

I made tests with 6.04 from Gene, version 5.2 of hpa-tftp and tried
various options with no success (-r blksize, -r tsize)

tcpdump shows the following for no options more than -4 -s /prj/tftpboot:

19:49:29.140678 IP (tos 0x0, ttl 64, id 29915, offset 0, flags [none], proto UDP (17), length 32)
    10.3.222.85.1472 > 10.3.222.22.49963: [udp sum ok] UDP, length 4
19:49:29.140768 IP (tos 0x0, ttl 64, id 63524, offset 0, flags [none], proto UDP (17), length 1440)
    10.3.222.22.49963 > 10.3.222.85.1472: [bad udp cksum 5e14!] UDP, length 1412
19:49:29.144224 IP (tos 0x0, ttl 64, id 29916, offset 0, flags [none], proto UDP (17), length 32)
    10.3.222.85.1472 > 10.3.222.22.49963: [udp sum ok] UDP, length 4
19:49:29.144313 IP (tos 0x0, ttl 64, id 63525, offset 0, flags [none], proto UDP (17), length 1440)
    10.3.222.22.49963 > 10.3.222.85.1472: [bad udp cksum e403!] UDP, length 1412

So even here, I'm not able to achieve a deployment fully.
Any option I could give for the client part of the tftp dialog to
syslinux ?

Attached an image of the boot screen at the point it fails.
Lots of progress, but I still miss the last mile ;-)

Bruno.
-- 
Open Source Profession, Linux Community Lead WW  http://opensource.hp.com
HP EMEA EG Open Source Technology Strategist         http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org
-------------- section suivante --------------
Une pi?ce jointe autre que texte a ?t? nettoy?e...
Nom: syslinux.efi-4.png
Type: image/png
Taille: 15795 octets
Desc: non disponible
URL: <http://www.zytor.com/pipermail/syslinux/attachments/20151029/a7b43f54/attachment.png>