Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
console [2012/03/27 12:41] mcb30 |
console [2015/10/16 16:10] mcb30 |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| #define KEYBOARD_MAP de | #define KEYBOARD_MAP de | ||
| + | |||
| + | ==== Graphical framebuffer console ==== | ||
| + | |||
| + | {{ :screenshots:background.png?200x150|Graphical framebuffer console}} | ||
| + | |||
| + | The graphical framebuffer console uses the same locally-attached keyboard and monitor as the BIOS console, but allows for higher resolutions, arbitrary colours, and background pictures. You can enable or disable the graphical framebuffer console using the build option ''[[:buildcfg:CONSOLE_FRAMEBUFFER]]''. | ||
| + | |||
| + | To activate the graphical framebuffer console, you must use the ''[[:cmd:console]]'' command to configure the console. | ||
| + | |||
| + | To use background pictures, you must enable support for a suitable image format, such as ''[[:buildcfg:IMAGE_PNG]]''. | ||
| ==== Serial port console ==== | ==== Serial port console ==== | ||
| Line 48: | Line 58: | ||
| You will need to ensure that your syslog server is configured to accept messages received via the network. | You will need to ensure that your syslog server is configured to accept messages received via the network. | ||
| + | |||
| + | ==== Encrypted syslog console ==== | ||
| + | |||
| + | The encrypted syslog console sends output to a remote syslog server via a TLS-encrypted connection. You can enable or disable the encrypted syslog console using the build option ''[[:buildcfg:CONSOLE_SYSLOGS]]''. | ||
| + | |||
| + | The encrypted syslog server address is configured using the ''[[:cfg:syslogs]]'' setting. For example, to send log messages to syslog.example.com: | ||
| + | |||
| + | iPXE> set syslogs syslog.example.com | ||
| ==== VMware console ==== | ==== VMware console ==== | ||
