[SOLVED[ PXE default menu.c32 locks up boot

[gmc]

curaga, tinypoodle - Thanks!

[gmc]

I have a special request.  Would someone be willing to try creating a PXE boot menu using a clean boot of TCL?  I know it is a lot to ask but I am stumped and don't know what I might be missing here...

Thanks in advance.

[genec]

By the way, using UI should override PROMPT.

Did you try to launch menu from the boot prompt?

[gmc]

Hi genec,

I did try, but can't remember the details.  Will try again and let you know.

[genec]

Also try something like this at the end of the file (the sequence is read entire config file, parse, then execute DEFAULT/UI or proceed to CLI; SAY is executed during the parse):

Code: [Select]

SAY End of config file

[gmc]

genec - I love it!!  I put the SAY directive at the end of the 'default' file and set PROMPT to 1.  The entire file was parsed with no errors and the SAY directive printed out the message "end of config file".  At the "boot:" prompt I typed: menu.c32 and pressed Enter.  Immediate freeze. 

However, when I put the UI directive in the 'default' file I get an unknown keyword message at PXE client boot, just before the menu.c32 freeze (or before the 'boot:' prompt, depending on the PROMPT mode.  So it appears that UI is not recognized?  Is UI valid in version 4.02?

[genec]

UI was introduced in 3.74.  As far as the bad keyword, I'm not sure what it would be (assuming you put your entire config in the first message).  What's the exact text?

menu.c32 appears to be your issue (or at least triggers it).  Any chance you could try pxelinux.0 and menu.c32 from the precompiled archive of  4.05 or 4.06?

I can probably try out TC as a boot system to see if I can see it in my VMs (on a VMware hosted platform).

[gmc]

gene - you are closer to the truth than you know!  I did try the precompiled archives of 4.02 and 4.05.  But before I tried 4.0 I thought it would be wise to try the "grep PXELINUX /usr/share/syslinux/pxelinux.0" method (thanks tinypoodle) to get the actual syslinux version.  I found that syslinux in TC 4.7.5 is at version 3.61! 

Once I knew that little detail it was not too hard to figure out what to do next!  I downloaded the 3.61 binaries from syslinux (thanks for your tip), extracted and copied menu.c32 and pxelinux.0 to /netboot (after running tc-terminal-server) and tried a PXE client boot with a modified 'default' menu.  Need I say that it worked?  Well, just in case there is any doubt, IT WORKS!  I have a functional menu!  This has been a battle but it feels good, very good, to have it working.

Thanks to each and every one of you for the help you have given.

[tinypoodle]

But before I tried 4.0 I thought it would be wise to try the "grep PXELINUX /usr/share/syslinux/pxelinux.0" method (thanks tinypoodle) to get the actual syslinux version.  I found that syslinux in TC 4.7.5 is at version 3.61! 

If my fading memory serves me right - several years have passed - it may actually have been genec giving me the pointer to check such.

[genec]

I found that syslinux in TC 4.7.5 is at version 3.61!

Typical behavior of a COM32R in a COM32 environment.  Must be a few extensions with Syslinux component.

[genec]

What TC version are you using?

EDIT: I see it in 4.7.5 core.gz

[gmc]

Greetings!

Imagine my surprise and pleasure as I was browsing the Web and found a reference to the latest TC release (4.7.6) and noted that one of the items changed was the PXE boot file name fix!  How cool is that!  Made my day.

I immediately downloaded the latest, greatest ISO, created a CD and booted.  Imagine my surprise and disappointment when I found that the same old problem exists! tc-terminal-server script still has 'option bootfile /pxelinux.0...'  Nothing has changed.  Sigh...

Well, it was nice to know that it was supposed to have been fixed.  Maybe next time...

[curaga]

The new line was added, but removing the old line didn't seem to be necessary. boot_file is there in 4.7.6.

Does the presence of both lines cause issues on your client?

[gmc]

Hi, I did not see the added line, just noted that the old one was as before. 

Clients still won't boot until old line is changed.

Thanks for letting meknow what's going on.  I'll go look at tc-terminal-server script again...

[curaga]

Oh, here having them both didn't cause issues. Will remove the old line then.