From Fedora Project Wiki
(no reason to mention upstart anymore?) |
("serial" boot option was removed) |
||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description= | |description= | ||
This test is intended to ensure that the ''console=X | This test is intended to ensure that the '''console=X''' parameters are honored and the post-installed systems is configured properly for a non tty0 console. While the examples mention the use of ''console=ttyS0'', it it acceptable to use any device other than the default ''tty0''. | ||
{{Admon/note|Serial Cable?| This test case may require using a DB-9 serial cable to connect to the system under test. Additionally, you may be required to update the BIOS to enable the serial port.}} | {{Admon/note|Serial Cable?| This test case may require using a DB-9 serial cable to connect to the system under test. Additionally, you may be required to update the BIOS to enable the serial port.}} | ||
{{Admon/tip|Go Virtual|Since the focus of this test is not to validate the physical DB-9 serial cable connection, or to ensure the cables are seated properly, it is entirely acceptable (and ''encouraged'') to use [[Virtualization]]. For example, creating any KVM/QEMU virtual guest with the correct ''console{{=}}ttyS0 | {{Admon/tip|Go Virtual|Since the focus of this test is not to validate the physical DB-9 serial cable connection, or to ensure the cables are seated properly, it is entirely acceptable (and ''encouraged'') to use [[Virtualization]]. For example, creating any KVM/QEMU virtual guest with the correct ''console{{=}}ttyS0'' will setup a serial console for use with this test.}} | ||
|actions= | |actions= | ||
# Using a DB-9 serial cable, connect to your test system on the first port (typically S0) and start a serial port monitoring application (ttywatch, cermit, or minicom) | # Using a DB-9 serial cable, connect to your test system on the first port (typically S0) and start a serial port monitoring application (ttywatch, cermit, or minicom) | ||
# Boot installation program passing the ''console=ttyS0 | # Boot installation program passing the '''console=ttyS0''' command line parameters | ||
# Complete installation and boot into installed system | # Complete installation and boot into installed system | ||
|results= | |results= |
Revision as of 13:20, 16 May 2012
Description
This test is intended to ensure that the console=X parameters are honored and the post-installed systems is configured properly for a non tty0 console. While the examples mention the use of console=ttyS0, it it acceptable to use any device other than the default tty0.
How to test
- Using a DB-9 serial cable, connect to your test system on the first port (typically S0) and start a serial port monitoring application (ttywatch, cermit, or minicom)
- Boot installation program passing the console=ttyS0 command line parameters
- Complete installation and boot into installed system
Expected Results
- The installation displays properly and responds to user input over the serial line
- Confirm that a login console is presented over the serial device. When using
systemd
(Fedora 15 and newer), you may confirm that the serial device is configured for login by examining the output ofsystemctl status serial-getty@ttyS0.service
. For example:Loaded: loaded (/lib/systemd/system/serial-getty@.service) Active: active (running) since Tue, 01 Mar 2011 12:46:54 -0500; 4min 29s ago Main PID: 736 (login) CGroup: name=systemd:/system/serial-getty@.service/ttyS0
- The file
/etc/securetty
contains a line matching the requested console and the user is able to login to the system using the serial login prompt