I have updated syslinux in Parted Magic's test version to the 5.10 release. With 4.06 I booted plop like this: LINUX /boot/plpbt/plpbt.bin Now it says /boot/plpbt/plpbt.bin... ok Booting kernel failed: Invalid argument Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... all work with 5.10. Revert to 4.06 and plop works again. Is this a problem with syslinux or plop? Patrick Verner partedmagic.com
> I have updated syslinux in Parted Magic's test version to the 5.10 release. > With 4.06 I booted plop like this: > > LINUX /boot/plpbt/plpbt.bin > > Now it says /boot/plpbt/plpbt.bin... ok > Booting kernel failed: Invalid argument > > Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... > all work with 5.10. Revert to 4.06 and plop works again. > > Is this a problem with syslinux or plop? >Testing under VBox 4.2.14, Syslinux 6.01-pre5, BIOS, ISOLINUX, menu.c32: LABEL plop_test MENU LABEL PLoP Boot Manager V5.0.15-TEST COM32 linux.c32 APPEND plpbt_test.bin fails with: syslinux_boot_linux() failed: Error 22 linux.c32 failed: Boot aborted! and LABEL plop MENU LABEL PLoP Boot Manager V5.0.14 COM32 linux.c32 APPEND memdisk initrd=plpbt.img.gz successfully boots PLoP. Note the different PLoP versions (stable / test), and that one Syslinux entry uses the PLoP kernel and the other uses the image with memdisk. I have not tried without using linux.c32. I have not actually tried to go on with additional booting steps to boot something else, from inside PLoP itself. It might be worth testing Syslinux 5.11-preN too (instead of 5.10) with different versions of PLoP, and with and without MEMDISK. Regards, Ady.
Thanks for the tips Ady. I have tried about everything I could think of + your ideas and nothing works. I'm just going to downgrade to 4.06 and check back in 6 months. Patrick On Sat, Jun 29, 2013 at 3:11 AM, Ady <ady-sf at hotmail.com> wrote:> > > I have updated syslinux in Parted Magic's test version to the 5.10 > release. > > With 4.06 I booted plop like this: > > > > LINUX /boot/plpbt/plpbt.bin > > > > Now it says /boot/plpbt/plpbt.bin... ok > > Booting kernel failed: Invalid argument > > > > Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, > etc... > > all work with 5.10. Revert to 4.06 and plop works again. > > > > Is this a problem with syslinux or plop? > > > > Testing under VBox 4.2.14, Syslinux 6.01-pre5, BIOS, ISOLINUX, > menu.c32: > > LABEL plop_test > MENU LABEL PLoP Boot Manager V5.0.15-TEST > COM32 linux.c32 > APPEND plpbt_test.bin > > fails with: > syslinux_boot_linux() failed: Error 22 > linux.c32 failed: Boot aborted! > > and > > LABEL plop > MENU LABEL PLoP Boot Manager V5.0.14 > COM32 linux.c32 > APPEND memdisk initrd=plpbt.img.gz > > successfully boots PLoP. > > Note the different PLoP versions (stable / test), and that one > Syslinux entry uses the PLoP kernel and the other uses the image with > memdisk. > > I have not tried without using linux.c32. > > I have not actually tried to go on with additional booting steps to > boot something else, from inside PLoP itself. > > It might be worth testing Syslinux 5.11-preN too (instead of 5.10) > with different versions of PLoP, and with and without MEMDISK. > > Regards, > Ady. > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >
On 06/28/2013 05:32 PM, Patrick Verner wrote:> I have updated syslinux in Parted Magic's test version to the 5.10 release. > With 4.06 I booted plop like this: > > LINUX /boot/plpbt/plpbt.bin > > Now it says /boot/plpbt/plpbt.bin... ok > Booting kernel failed: Invalid argument > > Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... > all work with 5.10. Revert to 4.06 and plop works again. > > Is this a problem with syslinux or plop? >I suspect this is the "ancient kernel" problem again. Do you have a point to the specific plpbt.bin you are using? -hpa
> On 06/28/2013 05:32 PM, Patrick Verner wrote: > > I have updated syslinux in Parted Magic's test version to the 5.10 release. > > With 4.06 I booted plop like this: > > > > LINUX /boot/plpbt/plpbt.bin > > > > Now it says /boot/plpbt/plpbt.bin... ok > > Booting kernel failed: Invalid argument > > > > Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... > > all work with 5.10. Revert to 4.06 and plop works again. > > > > Is this a problem with syslinux or plop? > > > > I suspect this is the "ancient kernel" problem again. Do you have a > point to the specific plpbt.bin you are using? > > -hpa >If with "ancient kernel" you are referring to the memtest(86|86+) issue, I don't see the same *exact* problem / behavior. FWIW, let me give you some examples, with Syslinux 6.01-pre5 BIOS, and/or with 5.11-pre3, testing with the same VBox 4.2.14 VM. I have also deleted the ".bin" filename extension from the kernels. Note: In this context, when I mention "plop" here, I am referring to "PLoP boot manager" only, and not to other products which include the word "PLoP" in it from the same developer. _ I am able to boot ISOLINUX -> memtest, but not ISOLINUX -> plop. _ memtest seems to fail mostly from PXELINUX, or when using linux.c32. _ Some versions of memtest seem to start booting (from ISOLINUX, for example) but then hang within memtest itself (possible memtest bug?). OTOH, when trying to boot plop, is Syslinux the one refusing to boot the plop kernel at all, giving some error message. BTW, to be sure you can see the exact error message, you might need to use CLI; using menu.c32 might immediately erase the error message from the screen, going back to display the Syslinux menu. Note that the error message is not the same, depending on whether linux.c32 was used or not. _ Using MEMDISK -> plpbt.img (FAT12 bootable floppy image with plop as boot loader in it), plop can be booted. This is a particular case, since plop itself is a boot loader; this is not applicable to memtest. So the problem with plop seems to be trying to boot the kernel directly, from whichever variant of Syslinux 5+, while memtest can still be booted directly with at least some variants of Syslinux 5+. Using MEMDISK, plop can be booted. Of course, please keep in mind that these tests were performed in one VM only, and different real hardware might behave differently. Regards, Ady.
On Fri, 28 Jun, at 07:32:30PM, Patrick Verner wrote:> I have updated syslinux in Parted Magic's test version to the 5.10 release. > With 4.06 I booted plop like this: > > LINUX /boot/plpbt/plpbt.bin > > Now it says /boot/plpbt/plpbt.bin... ok > Booting kernel failed: Invalid argument > > Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... > all work with 5.10. Revert to 4.06 and plop works again.Could you try Syslinux 5.11-pre5?> Is this a problem with syslinux or plop?For some reason, the plpbt.bin file didn't have a valid initrd_addr_max field in its header, for some reason. Which caused the kernel loader to barf. Do you know why this field was zero? How did you build your kernel image? -- Matt Fleming, Intel Open Source Technology Center
On Mon, 01 Jul, at 11:49:45AM, Patrick Verner wrote:> You're right, I tried pre4 last. My brain hasn't fully recovered from the > weekend yet... plop works with pre5 just like it did with 4.06. I guess > this is fixed in pre5 then. Thanks!Excellent, thanks for testing. -- Matt Fleming, Intel Open Source Technology Center
> On Fri, 28 Jun, at 07:32:30PM, Patrick Verner wrote: > > I have updated syslinux in Parted Magic's test version to the 5.10 release. > > With 4.06 I booted plop like this: > > > > LINUX /boot/plpbt/plpbt.bin > > > > Now it says /boot/plpbt/plpbt.bin... ok > > Booting kernel failed: Invalid argument > > > > Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... > > all work with 5.10. Revert to 4.06 and plop works again. > > Could you try Syslinux 5.11-pre5? > > > Is this a problem with syslinux or plop? > > For some reason, the plpbt.bin file didn't have a valid initrd_addr_max > field in its header, for some reason. Which caused the kernel loader to > barf. Do you know why this field was zero? How did you build your > kernel image? > > -- > Matt Fleming, Intel Open Source Technology Center > _______________________________________________Hi Matt, I don't know if 4.06 (where PLoP works OK) uses the same method as 5.11pre5, but anyway... Vbox 4.2.14; isolinux-debug.bin 5.11-pre5; menu.c32; then A_ MEMDISK; plop.img (from official plop manager package) ; OK. B_ 'LINUX plop' ; OK C_ 'linux.c32 plop' ; OK D_ 'ifplop.c32 -- plop' ; FAILS as before. Which probably means ifplop.c32 also needs some patch in v.5+ (?). To be clear, I only tested booting plop 5.0.15-test (and under VBox 4.2.14 only), and I have NOT tested the next step, which would be using PLoP itself to boot something else. Additional tests might be helpful, under different circumstances and real hardware, and using PLoP itself (initially booted from each Syslinux variant) to actually boot something from it. Regards, Ady.