[syslinux] ifcpu[64].c32 functions drop to command line

[Gene Cumm]

On Tue, Apr 30, 2013 at 9:09 AM, John McDonnell <mcdonnjd at pcam.org> wrote:
>> And now for the results of testing 5.10-pre2... I'm now getting an error
>> message stating: Initial menu has no LABEL entries!
>
> Well, it seems that if I comment out including my vesamenu.config file (it sets my resolution to 1024x768, adds a background image, moves some lines around, changes some colors, and works perfectly in 4.06 and 5.01 but gives the Initial menu has no LABEL entries error message in 5.10) the text based menu will load but not the graphical menu. (Can tell due to the color scheme, doesn't have the graphic menu default colors. I also tried setting the resolution directly in my default config but it had no effect.)

1) Since the included file is just for the menu, why not use MENU
INCLUDE instead?

2) TIMEOUT and TOTALTIMEOUT are global options.  I find it easier to
put these outside LABELs for clarity.

>> But when manually entering my label for System Rescue (rescuecd) it does
>> seem to detect that I'm on a 64-bit machine and attempts to load
>> http://****/rescue64 but fails to load it with a No such file or directory error.
>> However if I enter http://****/rescue64 into my browser, it does download
>> the file, so I know it is actually there.
>
> I just tested a 32-bit machine with 5.10-pre2 and it reboots after connecting to the TFTP server, presumably when loading gpxelinux.0. (Log file only shows "in.tftpd[1953]: tftp: client does not accept options" which is all the log is filled with. Not sure how to get more verbose logging for tftp-hpa on FreeBSD, I'll have to dig it seems. Never had an issue before, so never checked the TFTP logs before.) The 32-bit machine does boot properly into 5.01 but also has the issue with ifcpu.c32 not working.

3) I find logging in atftpd better although a packet capture can also
work (and is sometimes necessary).

>> I'll take a look to see if I can figure out why my menu doesn't load in 5.10-
>> pre2 and if something different needs to be done for HTTP booting my
>> kernel/initrd/etc. Been up for about 20 hours now after 3 hours of sleep, so
>> not sure I'll be able to find it. If I can't and I don't get any pointers before I
>> head to bed, I'll take another look when I get back into work.
>
> I'm not seeing anything out of place. It's a copy of my working config from 5.01 (and 4.06) so I don't think there's anything wrong with it unless 5.10-pre2 requires a different config file format.
>
> Attached are my default and vesamenu.config config files. These work perfectly on both 64-bit and 32-bit systems on 5.01 with gpxelinux.0. All of the labels load properly except for the ones using ifcpu.c32 which drop to the command line. Manually entering the label for *32 or *64 will load the appropriate label properly though I obviously want ifcpu.c32 to work so I can keep the menu system neater looking.
>
> With 5.10-pre2, if I comment out the line to include vesamenu.config, it will load into the text menu system on a 64-bit PC but the 32-bit PC reboots when loading gpxelinux.0. But ifcpu.c32 does seem to work on the 64-bit PC, however, it will not load the kernel from HTTP.

4) What about if you use pxelinux.0 (but requires only TFTP) or lpxelinux.0?

5) Reading over the entire config, I don't see anything wrong.  Could
you try pwd.c32 (which should show "::") and Ctrl-N (which should show
the IP address and path prefix)?  I vaguely recall reading someone hit
that message when the menu got confused somehow.

--
-Gene