On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten via Syslinux wrote:> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > You should be able to see the effects of the DISPLAY directive when > > > > testing the floppy image I sent you, because it starts with the boot > > > > prompt, not with a menu. > > > > > > I see the effects, both good and bad. I'm having trouble knowing how > > > bad the bad is. > > > > How about comparing it with the current behaviour in BIOS mode? > > Everything in current BIOS mode works perfectly as far as I can tell. > We know things are different with efi, but that alone isn't a blocker.Have you tried to updating to a newer gnu-efi ? The one included in syslinux is very old. I have one here: https://github.com/joakim-tjernlund/syslinux While I am here, I want to ask: Is there a way to create a combined PXE boot img for both BIOS and EFI ? Currently one have to use 2 different images. Also, can one have GRUB bootable PXE img? Jocke
On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote:> > On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten via Syslinux wrote: > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > > > You should be able to see the effects of the DISPLAY directive when > > > > > testing the floppy image I sent you, because it starts with the boot > > > > > prompt, not with a menu. > > > > > > > > I see the effects, both good and bad. I'm having trouble knowing how > > > > bad the bad is. > > > > > > How about comparing it with the current behaviour in BIOS mode? > > > > Everything in current BIOS mode works perfectly as far as I can tell. > > We know things are different with efi, but that alone isn't a blocker. > > Have you tried to updating to a newer gnu-efi ? The one included in syslinux is very old.I am using the binaries from https://sources.debian.org/src/syslinux/3:6.04%7Egit20171011.af7e95c3+dfsg1-6/debian/changelog/> I have one here: https://github.com/joakim-tjernlund/syslinuxquick look makes me wonder why it would have newer code: Syslinux GIT repo; master is identical to upstream master http://www.syslinux.org/wiki/index.ph? -- Carl K
On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote:> While I am here, I want to ask: > Is there a way to create a combined PXE boot img for both BIOS and EFI ? > Currently one have to use 2 different images.I'm a little fuzzy what you mean here. do you want the tftp server to send boot img? I think you should explain the steps of what boots what.> > Also, can one have GRUB bootable PXE img?I would ask on a grub list ;)> > Jocke-- Carl K
On Wed, 2018-12-12 at 17:05 -0600, Carl Karsten wrote:> On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten via Syslinux wrote: > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > > > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > You should be able to see the effects of the DISPLAY directive when > > > > > > testing the floppy image I sent you, because it starts with the boot > > > > > > prompt, not with a menu. > > > > > > > > > > I see the effects, both good and bad. I'm having trouble knowing how > > > > > bad the bad is. > > > > > > > > How about comparing it with the current behaviour in BIOS mode? > > > > > > Everything in current BIOS mode works perfectly as far as I can tell. > > > We know things are different with efi, but that alone isn't a blocker. > > > > Have you tried to updating to a newer gnu-efi ? The one included in syslinux is very old. > > I am using the binaries from > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsources.debian.org%2Fsrc%2Fsyslinux%2F3%3A6.04%257Egit20171011.af7e95c3%2Bdfsg1-6%2Fdebian%2Fchangelog%2F&data=02%7C01%7CJoakim.Tjernlund%40infinera.com%7C1d50b660417a4c6e2c3f08d66086688e%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636802527742019220&sdata=UYyZaxiiKgLpp%2BrdXmZ3UMVRkvTCagf2SZk%2FVtZnGdM%3D&reserved=0 >I cannot tell but I guess you are using newer gnu-efi. You should check how your repo does this: https://github.com/joakim-tjernlund/syslinux/commit/22d32c15ea96c01c8c05b8c1551095716d42f3a4
On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten wrote:> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > > While I am here, I want to ask: > > Is there a way to create a combined PXE boot img for both BIOS and EFI ? > > Currently one have to use 2 different images. > > I'm a little fuzzy what you mean here.Can you have one pxelinux.0 which will work for both UEFI resp. BIOS PXE ?> > do you want the tftp server to send boot img? > > I think you should explain the steps of what boots what. > > > > Also, can one have GRUB bootable PXE img? > > I would ask on a grub list ;) >No, this is a syslinux thing. Basically have grub load(over tftp) and run pxelinux.0 using some other syslinux module. Jocke