From Fedora Project Wiki
(Add virt tip) |
|||
Line 2: | Line 2: | ||
|description= | |description= | ||
This test is intended to ensure that the console= parameter is 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''. | This test is intended to ensure that the console= parameter is 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/ | {{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 serial'' 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) | ||
Line 9: | Line 9: | ||
# Complete installation and boot into installed system | # Complete installation and boot into installed system | ||
|results= | |results= | ||
# The installation displays properly works over the serial line | |||
# Confirm that a login console is presented over the serial device | |||
# When using ''upstart'' (Fedora9), you may confirm that the serial device is configured for login by examining the output of ''initctl''. For example, | |||
<pre>serial (instance) | #: <pre>serial (instance) | ||
(start) running, process 1116</pre> | #: (start) running, process 1116</pre> | ||
# When using ''sysvinit'' (prior to Fedora9), you may confirm that the file ''/etc/inittab'' has a login entry for the requested serial port. For example: <pre>co:2345:respawn:/sbin/agetty ttyS1 115200 vt100-nav</pre> | |||
# The file ''/etc/securetty'' contains a line matching the requested console | # The file ''/etc/securetty'' contains a line matching the requested console | ||
}} | }} | ||
[[Category:User Interface]] | [[Category:User Interface]] |
Revision as of 19:25, 26 January 2010
Description
This test is intended to ensure that the console= parameter is 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 parameter
- Complete installation and boot into installed system
Expected Results
- The installation displays properly works over the serial line
- Confirm that a login console is presented over the serial device
- When using upstart (Fedora9), you may confirm that the serial device is configured for login by examining the output of initctl. For example,
serial (instance)
- (start) running, process 1116
- When using sysvinit (prior to Fedora9), you may confirm that the file /etc/inittab has a login entry for the requested serial port. For example:
co:2345:respawn:/sbin/agetty ttyS1 115200 vt100-nav
- The file /etc/securetty contains a line matching the requested console