The Linux console is a system console internal to the Linux kernel. A system console is the device which receives all kernel messages and warnings and which allows logins in single user mode.[1] The Linux console provides a way for the kernel and other processes to send text output to the user, and to receive text input from the user. The user typically enters text with a computer keyboard and reads the output text on a computer monitor. The Linux kernel supports virtual consoles – consoles that are logically separate, but which access the same physical keyboard and display.[2] The Linux console (and Linux virtual consoles) are implemented by the VT (virtual terminal) subsystem of the Linux kernel, and do not rely on any user space software. This is in contrast to a terminal emulator, which is a user space process that emulates a terminal, and is typically used in a graphical display environment.
The Linux console was one of the first features of the kernel and was originally written by Linus Torvalds in 1991[3] (see history of Linux). There are two main implementations: framebuffer and text mode. The framebuffer implementation is the default in modern Linux distributions, and together with kernel mode setting, provides kernel-level support for display hardware and features such as showing graphics while the system is booting.[4] The legacy text mode implementation was used in PC-compatible systems with CGA, EGA, MDA and VGA graphics cards. Non-x86 architectures used framebuffer mode because their graphics cards did not implement text mode.[4] The Linux console uses fixed-size bitmap, monospace fonts, usually defaulting to 8x16 pixels per character.[4]
The Linux console is an optional kernel feature, and most embedded Linux systems do not enable it. These systems typically provide an alternative user interface (e.g. web based), or boot immediately into a graphical user interface and use this as the primary means of interacting with the user. Other implementations of the Linux console include the Braille console to support refreshable Braille displays[5] and the serial port console.[6]
See also: Linux startup process.
The Linux console provides a way for the kernel and other processes to output text-based messages to the user, and to receive text-based input from the user. In Linux, several devices can be used as system console: a virtual terminal,[7] serial port,[8] USB serial port,[9] VGA in text-mode,[10] framebuffer.[11] Some modern Linux-based systems have deprecated kernel based text-mode input and output, and instead show a graphical logo or progress bar while the system is booting, followed by the immediate start of a graphical user interface (e.g. the X.Org Server on desktop distributions, or SurfaceFlinger on Android).
During kernel boot, the console is commonly used to display the boot log of the kernel. The boot log includes information about detected hardware, and updates on the status of the boot procedure. At this point in time, the kernel is the only software running, and hence logging via user-space (e.g. syslog) is not possible, so the console provides a convenient place to output this information. Once the kernel has finished booting, it runs the init process (also sending output to the console), which handles booting of the rest of the system including starting any background daemons.
After the init boot process is complete, the console will be used to multiplex multiple virtual terminals (accessible by pressing Ctrl-Alt-F1, Ctrl-Alt-F2 etc., Ctrl-Alt-LeftArrow, Ctrl-Alt-RightArrow, or using chvt[12]). On each virtual terminal, a getty process is run, which in turn runs /bin/login to authenticate a user. After authentication, a command shell will be run. Virtual terminals, like the console, are supported at the Linux kernel level.[13]
The Linux console implements a terminal type of "linux" and the escape sequences it uses are in the console_codes man page.[14]
See main article: article and Virtual console.
Virtual consoles allow the storage of multiple text buffers, enabling different console programs to run simultaneously but interact with the user in different contexts. From the user's point of view, this creates the illusion of several independent consoles.
Each virtual console can have its own character set and keyboard layout.Linux 2.6 introduced the ability to load a different font for each virtual console (kernel versions predating 2.6 change the font only on demand).
See also: VGA-compatible text mode and Text mode.
The text mode implementation is used on PC-based systems with a legacy CGA/EGA/MDA/VGA video card that implements text-based video modes. In text mode, the kernel sends a 2D array of characters to the video card, and the video card converts the characters to pixels for display.
The text buffer is a part of VGA memory which describes the content of a text screen in terms of code points and character attributes. Code points in the text buffer and font are generally not the same as encoding used in text terminal semantics to put characters on the screen. The set of glyphs on the screen is determined by the current font. The text screen is handled by and drivers. There is a utility for altering fonts and terminal encodings called .
The Linux kernel (driver) has almost complete support for keyboard input (keyboard layouts), but it remains a bit inconsistent because it interacts badly with different character sets. Layouts are loaded by the utility.
These two utilities and corresponding data files are packed in Linux Console Tools http://lct.sourceforge.net/ shipped with many Linux distributions.
Efforts on the internationalization of Linux at the kernel level started as early as in 1994 by Markus Kuhn and Andries Brouwer.
The Linux console is capable of supporting any VGA-style text mode, but the kernel itself has very limited means to set these modes up. SVGATextMode helps to enable more complex text modes than the standard EGA and VGA modes. It is fully compatible with Console Tools, but has some conflicts with dosemu, SVGAlib and display servers.
Currently, there is no support for different modes on different virtual consoles.
Microsoft Windows (of any version) does not have a fully functional support of the console. The comparable feature there, but for application software only, is the Win32 console.
| Feature | Linux | Windows | DOS | |
|---|---|---|---|---|
| VGA text attributes | ||||
| Custom fonts | ||||
| Character set | 512 glyphs max. (on VGA text), any code page or UTF-8 | 223 or 256 characters (depends on access method), any code page, or Unicode | ||
| Run-time character set switching | ||||
| Terminal emulation | , ANSI-compatible (TERM=linux) | , since Windows 10 "Threshold 2"[15] | , ANSI (with ANSI.SYS) | |
| Run-time switching between text mode and GUI | ||||
| Run-time changing numbers of rows and columns | ||||
| Switching between applications | (some terminate-and-stay-resident programs may be activated) | |||
| Non-standard modes | ||||
| Mouse support | (with gpm or similar) | |||
| only AltKey pressed -> programm noticed | ||||
See main article: article and Linux framebuffer.
The Linux framebuffer (fbdev) is a graphic hardware-independent abstraction layer, which was originally implemented to allow the Linux kernel to emulate a text console on systems such as the Apple Macintosh that do not have a text-mode display. Now it offers a kernel space text mode emulation on any platform. Its advantage over (currently unmaintained) SVGATextMode is a reliance and better hardware compatibility. It also permits to overcome all technical restrictions of VGA text modes.
A Linux framebuffer console differs from a VGA one only in ways of drawing characters. The processing of keyboard events and virtual consoles’ support are exactly the same.
Linux serial console is a console implementation via serial port, enabled by option CONFIG_SERIAL_CONSOLE in the kernel configuration. It may be used in some embedded systems, and on servers, where a direct interaction with operator is not expected. The serial console allows the same mode of access for the system, but usually at a slower speed due to the small bandwidth of RS-232. A serial console is often used during development of software for embedded systems, and is sometimes left accessible via a debug port.
The console responds to a number of control characters:[16]
| Control character | ASCII name | Description | |
|---|---|---|---|
| BEL | Bell sound | ||
| BS | Backspace | ||
| HT | Horizontal tab | ||
| LF | Line feed | ||
| VT | Vertical tab | ||
| FF | Form feed | ||
| CR | Carriage return | ||
| SO | Shift out | ||
| SI | Shift in | ||
| CAN | Cancel escape sequence | ||
| SUB | Cancel escape sequence | ||
| ESC | Escape / begin escape sequence | ||
| DEL | Nothing | ||
| Start command sequence |
| Control sequence | Description |
|---|---|
| Reverse line feed | |
| Line feed | |
| Carriage return and line feed | |
| Set tab stop | |
| Store cursor | |
| Restore cursor | |
| Switch keypad to numeric mode | |
| Switch keypad to application mode | |
| Reset terminal settings | |
| Print terminal ID | |
For ^[press the Escape key. The console also supports extended escape sequences, [[ANSI escape code#CSI codes|ANSI CSI Mode]] sequences, and DEC Private Mode sequences. These extended sequences can control colors, visual effects like blinking, underline, intensity and inverse video, bell tone frequency and duration, VESA screen blanking interval. Aside from the textual blanking, there is no known way to place the VGA adapter into standby.
The Kmscon projects aims to create a modern user-space replacement for the Linux console.[17] [18] Development priorities include support for multi-monitor setups, Unicode font rendering with Pango, XKB keyboard handling, and GPU OpenGL acceleration.[19] Complaints about the current kernel implementation include "that it's a user-interface in kernel-space, the code is poorly maintained, handles keyboards badly, produces bad font rendering, misses out on mode-setting and multi-head support, contains no multi-seat awareness, and only has limited hot-plugging handling, limited to VT102 compliance."[20]
| Name | Major | Minor | Description | |||
|---|---|---|---|---|---|---|
| /dev/tty0 | align=right | c 4 | align=right | 0 | "current console" | |
| /dev/tty1 ... /dev/tty63 | align=right | c 4 | align=right | 1 ... 63 | virtual consoles (keyboard controlled) | |
| /dev/ttyS0 ... | align=right | c 4 | align=right | 64 ... | Serial ports, suitable for system console | |
| /dev/vcs | align=right | c 7 | align=right | 0 | Virtual Console Screen /dev/vcs is the contents of the current virtual screen. | |
| /dev/vcs1 ... /dev/vcs63 | align=right | c 7 | align=right | 1 ... 63 | The text (the character pointer table) of a virtual screen. | |
| /dev/vcsa1 ... /dev/vcsa63 | align=right | c 7 | align=right | 129 ... 191 | Virtual Console Screen with Attributes Full image of a virtual text buffer; first 4 bytes contain numbers of rows, columns and cursor position |