Igor Sverkos
2013-Jul-19 16:00 UTC
[syslinux] Illegal OpCode on PXE exit with syslinux-6.0{1,2}
Hi,> Do you see the same error with 5.11-pre8?Yes, I do :( -- Regards, Igor
Matt Fleming
2013-Jul-19 16:14 UTC
[syslinux] Illegal OpCode on PXE exit with syslinux-6.0{1,2}
On Fri, 19 Jul, at 06:00:38PM, Igor Sverkos wrote:> Hi, > > > Do you see the same error with 5.11-pre8? > > Yes, I do :(OK, so presumably this regression introduced with the following commit in 5.11-pre3, commit 398cee85e1835b77e1b83a01fc20587bee8cc578 Author: Matt Fleming <matt.fleming at intel.com> Date: Wed Jun 26 20:35:32 2013 +0100 PXELINUX: implement our own version of local_boot16 We need to do different things for PXE, such as reset the PXE environment when booting from the local disk from PXELINUX. This fixes a localboot regression. Signed-off-by: Matt Fleming <matt.fleming at intel.com> Could you try 5.11-pre2 just to confirm that works? -- Matt Fleming, Intel Open Source Technology Center
Igor Sverkos
2013-Jul-22 14:21 UTC
[syslinux] Illegal OpCode on PXE exit with syslinux-6.0{1,2}
Hi,> Have you ever successfully used this config file with 4.06 or earlier?Mh, no. And I'll get the illegal opcode on 4.06 exit for local boot as well. Not sure if it has something to do with the fact, that there is no local bootloader, syslinux can start (it is a new system where's currently no OS installed). The config itself was grabbed from various PXE boot tutorials, for example from Ubuntu. -- Regards, Igor
Matt Fleming
2013-Jul-22 15:05 UTC
[syslinux] Illegal OpCode on PXE exit with syslinux-6.0{1,2}
On Mon, 22 Jul, at 04:21:38PM, Igor Sverkos wrote:> Hi, > > > Have you ever successfully used this config file with 4.06 or earlier? > > Mh, no. > > And I'll get the illegal opcode on 4.06 exit for local boot as well. > > Not sure if it has something to do with the fact, that there is no > local bootloader, syslinux can start (it is a new system where's > currently no OS installed).If you were booting a kernel instead of local booting I'd suggest using the "keeppxe" command line option, to leave the PXE stack resident in memory. But that doesn't work for LOCALBOOT. The last time this came up, Peter suggested using chain.c32 as a workaround to chainload the next boot stage, http://www.syslinux.org/archives/2008-June/010397.html -- Matt Fleming, Intel Open Source Technology Center