While playing with the current master of Syslinux, I figured out two bugs I'd like to share with you. 1- Missing menu entires If you consider a file with the following entries, only the first item appears label mga32 kernel anything label mga64 kernel anything Looks like the number at the end of the label is giving some headaches to gfxboot. If I do rename this two entries by "firstlabel" and "secondlabel" it works perfectly. Does any of you have an idea on the reason ? 2- Loading complementary com32 modules Some of my label entries are calling other com32 modules. Syslinux reports that it can't find any of my modules. Looks like the path went away or something got broken. I tried to load any combinations of the existing paths I have without success. Of course, If I disable the "UI gfxboot.c32 <theme>" directive, my setup is working fine. Any ideas of what's behind this bug ? Thanks for your help, Erwan
Erwan Velu wrote:> While playing with the current master of Syslinux, I figured out two > bugs I'd like to share with you. > > 1- Missing menu entires > > If you consider a file with the following entries, only the first item > appears > label mga32 > kernel anything > > label mga64 > kernel anything > > Looks like the number at the end of the label is giving some headaches > to gfxboot. > If I do rename this two entries by "firstlabel" and "secondlabel" it > works perfectly. > > Does any of you have an idea on the reason ?I just tested the following config and it works as expected (both menu entries shown): UI com32r/gfxboot.c32 bootlogo438 label mga32 kernel vmlinuz-2.6.22.5-31-default label mga64 kernel vmlinuz-2.6.22.5-31-default> 2- Loading complementary com32 modules > > Some of my label entries are calling other com32 modules. > Syslinux reports that it can't find any of my modules. Looks like the > path went away or something got broken. I tried to load any combinations > of the existing paths I have without success. > Of course, If I disable the "UI gfxboot.c32 <theme>" directive, my setup > is working fine. > > Any ideas of what's behind this bug ?Loading the following label works for me: label g2 com32 com32r/gfxboot.c32 append bootlogo438 Which version of gfxboot core are you using? Is PXELINUX involved?> Thanks for your help, > ErwanSebastian
Erwan Velu wrote:> >> I was able to reproduce this problem with pxelinux. >> If i replace your "message" file with a different [1] gfxboot displays >> all three labels (mga32, trentedeux, 64). >> >> [1] >> http://download.opensuse.org/factory/repo/oss/boot/i386/loader/bootlogo > Which release of the gfxboot tools are you using ?I have no idea with which version that file was built. I just tested the openSUSE themes built by 4.3.8 and 4.4.3 and both work fine. Sebastian
On Thu, 3 Nov 2011, Sebastian Herbszt wrote:> Erwan Velu wrote: >> >>> I was able to reproduce this problem with pxelinux. >>> If i replace your "message" file with a different [1] gfxboot displays >>> all three labels (mga32, trentedeux, 64). >>> >>> [1] >>> http://download.opensuse.org/factory/repo/oss/boot/i386/loader/bootlogo >> Which release of the gfxboot tools are you using ? > > I have no idea with which version that file was built.Everything is from http://download.opensuse.org/factory/repo/oss.> I just tested the openSUSE themes built by 4.3.8 and 4.4.3 and both work > fine.Steffen -- Give orange me give eat orange me eat orange give me eat orange give me you. (chimp Nim, using sign language)