[syslinux] garbage on serial console after pxelinux.0 is loaded

Scheie, Peter M Petre.Scheie at gd-ms.com
Mon Mar 5 12:17:15 PST 2018


A little more info:
I was mistaken in saying that the garbage on the screen doesn't interfere with typed commands/stanzas; it does.  If I can type the name of a stanza and hit enter quickly enough before the garbage is spat to the screen, it seems to start loading a kernel, but then it aborts.

And the garbage appears to be varying quantities of '[0n', as in sometimes there will be one instance of that in the string spit out, and sometimes there will be a dozen, or any quantity in between.  Sometimes it's all just blank spaces; and sometimes, as mentioned, there are fragments of text that was previously displayed.

Any ideas as to what [0n is?  Some sort of screen formatting?

Peter

-----Original Message-----
From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Scheie, Peter M via Syslinux
Sent: Monday, March 05, 2018 11:57 AM
To: syslinux at zytor.com
Subject: [syslinux] garbage on serial console after pxelinux.0 is loaded

We have some x86_64 systems that have DisplayPort and USB ports for a monitor & keyboard and when I use these to PXE boot, everything works fine.  However, these systems will eventually become headless and in the production process access to the console will be via serial port.  Using the serial port mostly works in that once we get to the PXE boot: prompt we can type in the name of the desired stanza from default and the kernel and initramfs specified will be loaded & executed.  But when the system initially reaches that boot: prompt, something starts spitting small strings of garbage, say 20-40 characters, in random places on the screen, about once per second or every other second.  The strings contain bits of text that were previously displayed, e.g., I can make out part of Peter Anvin's name sometimes in the garbage, suggesting it has something to do with the screen refresh.  Entering the name of the desired stanza works at this point, although it looks like what is bein!
 g typed is getting messed up (even if that is just an illusion).  But the production folks won't put up with this, and they shouldn't have to, so I have to fix it.

I don't think it's a baud rate mismatch between the terminal software (minicom) and the system board because all the text about choosing network boot, broadcasting for a DHCP server, etc. looks just fine (and we see the same behavior using putty on Windows for the terminal program).  The problem doesn't appear until the pxelinux.0 module is loaded.  I vaguely recall seeing a similar problem with pxelinux five or six years ago, but I could be imagining that.  Any ideas as to what is going on?

BTW, has syslinux gotten so stable that the latest release is really from Oct. 2014?  That's amazing!

Peter
_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux



More information about the Syslinux mailing list