Conversation
|
The iPXE script is currently generated via go here: https://github.com/metal-stack/pixie/pull/43/files#diff-dd39ef3e62b74a7957c600b373597f4a396a29b39e2520904ad879cfe3b4ff34R199 Further improvement to make the code more understandable: Create a second ipxe script, e.g. |
|
Output from a Supermicro machine with |
|
For Gigabyte, we have: |
Nice, can you add this to the script ? |
|
iPXE does not offer a
|
|
Currently, the default console is set to |
|
Adding the |
| if err != nil { | ||
| return nil, fmt.Errorf("expanding cmdline %q: %w", spec.Cmdline, err) | ||
| } | ||
| b.WriteString("console=${console},115200n8 ") |
There was a problem hiding this comment.
We should only add this console line if ${console} is not empty string.
But i don't now how this is possible with ipxe scripting
There was a problem hiding this comment.
Eventually with:
b.WriteString("isset ${console} && console=${console},115200n8 ||")
There was a problem hiding this comment.
We set the console parameter in the boot.ipxe script by default to ttyS1. The variable should be passed down, where we construct the ipxe script. So I assume it should not be an empty string.
However, we could add something like this upfront:
...
b.WriteString("isset ${console} || set console ttyS1")
b.WriteString("console=${console},115200n8 ")
...
Description
Some nice examples: https://www.redpill-linpro.com/techblog/2017/12/13/ipxe-provisioning.html
Information regarding manufacturer comparison with space: https://forum.ipxe.org/showthread.php?tid=7960
TODO:
AI also suggested the following (unverified) to detect if running on console, maybe we can grab some ideas from here: