| blob | 1e6ade061b05916c1bfb8abca9b56c32050d9032 |
4 <head>
9 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
11 /* Default font. */
12 body {
14 }
16 /* Title font. */
24 }
26 body {
28 }
30 a {
33 }
36 }
38 em {
41 }
43 strong {
46 }
53 }
57 }
58 h2 {
60 }
61 h3 {
63 }
64 h3 + * {
66 }
67 h5 {
69 }
73 }
75 hr {
77 }
79 p {
82 }
86 }
96 }
103 }
105 }
107 }
114 }
118 }
122 }
127 }
133 }
139 }
143 }
145 /* Block element titles. */
152 }
155 }
159 }
162 }
165 }
172 }
179 }
187 }
192 }
197 }
201 }
202 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
205 }
214 }
218 }
223 }
229 dl {
232 }
233 dt {
238 }
241 }
245 }
248 }
251 }
254 }
257 }
260 }
267 }
269 tfoot {
271 }
274 }
279 }
282 }
285 }
291 }
294 }
298 }
302 }
306 }
310 }
315 }
319 }
329 }
335 }
338 }
342 }
346 }
354 }
359 }
363 }
367 }
371 }
417 /*
418 * xhtml11 specific
419 *
420 * */
425 }
428 }
432 }
435 }
436 /* Because the table frame attribute is overriden by CSS in most browsers. */
439 }
443 }
447 }
450 /*
451 * html5 specific
452 *
453 * */
458 }
462 }
465 }
472 }
478 }
483 }
487 }
490 }
494 }
497 }
500 }
504 }
507 }
510 }
513 /*
514 * manpage specific
515 *
516 * */
523 }
526 }
529 }
533 }
536 </style>
538 /*<![CDATA[*/
541 /////////////////////////////////////////////////////////////////////
542 // Table Of Contents generator
543 /////////////////////////////////////////////////////////////////////
545 /* Author: Mihai Bazon, September 2002
546 * http://students.infoiasi.ro/~mishoo
547 *
548 * Table Of Content generator
549 * Version: 0.4
550 *
551 * Feel free to use this script under the terms of the GNU General Public
552 * License, as long as you do not remove or alter this notice.
553 */
555 /* modified by Troy D. Hanson, September 2006. License: GPL */
556 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
558 // toclevels = 1..4.
568 }
570 }
576 }
581 // Function that scans the DOM tree for header elements (the DOM2
582 // nodeIterator API would be a better technique but not supported by all
583 // browsers).
590 }
592 }
593 }
594 }
597 }
602 }
604 // Delete existing TOC entries in case we're reloading the TOC.
613 }
616 }
618 // Rebuild TOC entries.
631 }
634 },
637 /////////////////////////////////////////////////////////////////////
638 // Footnotes generator
639 /////////////////////////////////////////////////////////////////////
641 /* Based on footnote generation code from:
642 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
643 */
646 // Delete existing footnote entries in case we're reloading the footnodes.
651 }
657 }
660 }
662 // Rebuild footnote entries.
669 n++;
672 // Use [\s\S] in place of . so multi-line matches work.
673 // Because JavaScript has no s (dotall) regex flag.
679 }
686 }
687 }
691 // Process footnoterefs.
700 }
701 }
702 }
703 },
712 }
713 }
718 }
723 else
725 }
727 }
729 /*]]>*/
730 </script>
731 </head>
734 <h1>
735 syslinux.cfg(5) Manual Page
736 </h1>
739 <p>syslinux.cfg -
740 *Syslinux* configuration file
741 </p>
742 </div>
743 </div>
748 <div class="paragraph"><p>Configuration for the boot behavior and user experience of <strong>Syslinux</strong>
749 boot loaders, the format of display files and the boot prompt behavior.</p></div>
752 different from the one described above may still work correctly in this
754 </div>
755 </div>
759 <div class="paragraph"><p><strong>SYSLINUX</strong> (before 4.00) used the configuration filename of
760 syslinux.cfg. <strong>EXTLINUX</strong> (merged into <strong>SYSLINUX</strong> as of 4.00) used the
761 filename extlinux.conf. Both default to searching for the config file
762 in the installed directory (containing ldlinux.sys/extlinux.sys). As of
764 directory before falling back to the next directory.</p></div>
765 <div class="paragraph"><p>As of 3.35, <strong>SYSLINUX</strong> also searches /boot/syslinux, /syslinux and /.</p></div>
766 <div class="paragraph"><p><strong>ISOLINUX</strong> (before 4.02) used the configuration filename of
767 isolinux.cfg, searching /boot/isolinux (starting 2.00), then /isolinux
769 syslinux.cfg in /boot/isolinux before searching for the same files in
770 /isolinux, /boot/syslinux, /syslinux, and /.</p></div>
771 </div>
772 </div>
779 </dt>
780 <dd>
781 <p>
783 comment is no longer required.
784 </p>
785 </dd>
788 </dt>
789 <dd>
790 <p>
791 (3.00+) A directive for the simple menu system, treated as a comment
792 outside the menu. See menu.txt.
793 </p>
794 </dd>
797 </dt>
798 <dd>
799 <p>
800 Inserts the contents of another file at this point in the configuration
801 file. Files can currently be nested up to 16 levels deep, but it is not
802 guaranteed that more than 8 levels will be supported in the future.
803 </p>
804 </dd>
807 </dt>
808 <dd>
809 <p>
810 Sets the default command line (which often references a LABEL). If
813 result in an override.
814 </p>
815 <div class="paragraph"><p>If no configuration file is present, or no <strong>DEFAULT</strong> or <strong>UI</strong> entry is
816 present in the config file, an error message is displayed and the
818 </dd>
821 </dt>
822 <dd>
823 <p>
825 vesamenu.c32). The command-line interface treats this as a directive
828 to not prompt (but these directives may have effects on other
829 configuration parsers). Multiple uses will result in an override.
830 </p>
831 </dd>
834 </dt>
835 <dd>
836 <p>
840 DIRECTIVES</strong> being used instead of the global instance.
841 </p>
842 <div class="paragraph"><p><em>mylabel</em> must be unique. Currently the first instance is used but may
844 character that is not a non-white-space printable character and should
845 be restricted to non-white-space typeable characters. Prior to version
850 <div class="paragraph"><p>Within a <strong>LABEL</strong>, using multiple <strong>KERNEL-LIKE DIRECTIVES</strong> or reuse of
851 <strong>LABEL-ONLY DIRECTIVES</strong> or <strong>DUAL-PURPOSE DIRECTIVES</strong> will result in an
852 override. Otherwise, multiple instances of the same directive will
853 result in the last being effective.</p></div>
854 </dd>
855 </dl></div>
856 </div>
857 </div>
861 <div class="paragraph"><p>Use of any of the <strong>DUAL-PURPOSE DIRECTIVES</strong> as <strong>GLOBAL DIRECTIVES</strong> is
867 </dt>
868 <dd>
869 <p>
870 Add one or more options to the kernel command line. These are added
871 both for automatic and manual boots. The options are added at the very
872 beginning of the kernel command line, usually permitting explicitly
873 entered kernel options to override them. This is the equivalent of the
874 LILO "append" option.
875 </p>
876 <div class="paragraph"><p>Use of the parameter <em>initrd=</em> supports multiple filenames separated by
878 This is mostly useful for initramfs, which can be composed of multiple
879 separate cpio or cpio.gz archives.</p></div>
880 <div class="paragraph"><p>Note: all initrd files except the last one are zero-padded to a 4K page
881 boundary. This should not affect initramfs.</p></div>
882 <div class="paragraph"><p>Note: Only the last effective <em>initrd=</em> parameter is used for loading
883 initrd files.</p></div>
884 </dd>
887 </dt>
888 <dd>
889 <p>
890 Append nothing. <strong>APPEND</strong> with a single hyphen as argument in a <strong>LABEL</strong>
892 </p>
893 </dd>
894 </dl></div>
898 </dt>
901 </dt>
902 <dd>
903 <p>
905 The <strong>SYSAPPEND</strong> option was introduced in <strong>Syslinux</strong> 5.10; it is an
909 OR (sum) of the following integer options:
910 </p>
914 </dt>
915 <dd>
916 <p>
917 An option of the following format should be generated, based on
918 the input from the DHCP/BOOTP or PXE boot server and added to the kernel
919 command line(see note below; empty for non-PXELINUX variants):
920 </p>
923 <pre><code>ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask></code></pre>
924 </div></div>
926 <table><tr>
929 </td>
931 the booted system and should instead only be used to seed the client for
932 a request. Without regular renewals, the lease acquired by the PXE BIOS
933 will expire, making the IP address available for reuse by the DHCP
934 server.</td>
935 </tr></table>
936 </div>
937 </dd>
940 </dt>
941 <dd>
942 <p>
943 An option of the following format should be generated, in
944 dash-separated hexadecimal with leading hardware type (same as for the
945 configuration file; see pxelinux.txt.) and added to the kernel command
946 line, allowing an initrd program to determine from which interface the
947 system booted(empty for non-PXELINUX variants):
948 </p>
952 </div></div>
953 </dd>
956 </dt>
957 <dd>
958 <p>
959 An option of the following format should be generated, in lower
960 case hexadecimal in the format normally used for UUIDs (same as for the
961 configuration file; see pxelinux.txt.) and added to the kernel command
962 line:
963 </p>
967 </div></div>
968 </dd>
971 </dt>
972 <dd>
973 <p>
974 (5.10+) indicate the CPU family and certain particularly
975 significant CPU feature bits:
976 </p>
980 </div></div>
981 <div class="paragraph"><p>The <family> is a single digit from 3 (i386) to 6 (i686 or higher.) The
982 following CPU features are currently reported; additional flags may be
983 added in the future:</p></div>
986 <pre><code>P Physical Address Extension (PAE)
987 V Intel Virtualization Technology (VT/VMX)
988 T Intel Trusted Exection Technology (TXT/SMX)
989 X Execution Disable (XD/NX)
990 L Long Mode (x86-64)
991 S AMD SMX virtualization</code></pre>
992 </div></div>
993 </dd>
996 </dt>
997 <dd>
998 <p>
999 (5.10+) The following strings are derived from DMI/SMBIOS
1000 information if available:
1001 </p>
1004 <pre><code>Bit String Significance
1005 -------------------------------------------------------------
1006 0x00010 SYSVENDOR= System vendor name
1007 0x00020 SYSPRODUCT= System product name
1008 0x00040 SYSVERSION= System version
1009 0x00080 SYSSERIAL= System serial number
1010 0x00100 SYSSKU= System SKU
1011 0x00200 SYSFAMILY= System family
1012 0x00400 MBVENDOR= Motherboard vendor name
1013 0x00800 MBVERSION= Motherboard version
1014 0x01000 MBSERIAL= Motherboard serial number
1015 0x02000 MBASSET= Motherboard asset tag
1016 0x04000 BIOSVENDOR= BIOS vendor name
1017 0x08000 BIOSVERSION= BIOS version
1019 </div></div>
1020 <div class="paragraph"><p>If these strings contain white-space characters, they are replaced with
1021 underscores (_).</p></div>
1023 specification, available at <a href="http://www.dmtf.org/">http://www.dmtf.org/</a>. As of version 2.7.1
1024 of the specification, the following values are defined:</p></div>
1028 2 Unknown
1029 3 Desktop
1030 4 Low profile desktop
1031 5 Pizza box
1032 6 Mini tower
1033 7 Tower
1034 8 Portble
1035 9 Laptop
1036 10 Notebook
1037 11 Handheld
1038 12 Docking station
1039 13 All-in-one
1040 14 Subnotebook
1041 15 Space-saving
1042 16 Lunch box
1043 17 Main server chassis
1044 18 Expansion chassis
1045 19 Subchassis
1046 20 Bus expansion chassis
1047 21 Peripheral chassis
1048 22 RAID chassis
1049 23 Rack mount chasss
1050 24 Sealed-case PC
1051 25 Multi-system chassis
1052 26 Compact PCI
1053 27 Advanced TCI
1054 28 Blade
1056 </div></div>
1057 </dd>
1058 </dl></div>
1059 </dd>
1060 </dl></div>
1061 </div>
1062 </div>
1069 </dt>
1070 <dd>
1071 <p>
1073 on file extension, listed under the non-auto-detecting directives,
1075 </p>
1076 </dd>
1077 </dl></div>
1081 non-Linux kernel loaded in a Linux-like fashion.</p></div>
1085 </dt>
1086 <dd>
1087 <p>
1088 (<strong>ISOLINUX</strong> only: .bin; <strong>SYSLINUX</strong> only: .bs) Load a boot sector. .bin
1089 is a "CD boot sector" and .bs is a regular disk boot sector.
1090 </p>
1091 </dd>
1094 </dt>
1095 <dd>
1096 <p>
1098 superblock patched in.
1099 </p>
1100 </dd>
1103 </dt>
1104 <dd>
1105 <p>
1107 images may also be runnable from DOS while .cbt images are not. See
1109 </p>
1110 </dd>
1113 </dt>
1114 <dd>
1115 <p>
1116 (.c32) Load a <strong>Syslinux</strong> COM32 (32-bit <strong>COMBOOT</strong>) image. See also
1118 </p>
1119 </dd>
1122 </dt>
1123 <dd>
1124 <p>
1125 Load a new configuration file. The configuration file is read, the
1127 configuration file is parsed.
1128 </p>
1129 </dd>
1132 </dt>
1133 <dd>
1134 <p>
1136 image.
1137 </p>
1138 </dd>
1141 </dt>
1142 <dd>
1143 <p>
1144 (<strong>PXELINUX</strong> 1.53+; <strong>ISOLINUX</strong> ??3.10+; <strong>SYSLINUX</strong> 3.70+)Attempt a
1145 different local boot method. The special value -1 causes the boot
1146 loader to report failure to the BIOS, which, on recent BIOSes, should
1147 mean that the next boot device in the boot sequence should be activated.
1148 Values other than those documented may produce undesired results.
1149 </p>
1150 <div class="paragraph"><p>On <strong>PXELINUX</strong>, <em>type</em> 0 means perform a normal boot. <em>type</em> 4 will
1151 perform a local boot with the Universal Network Driver Interface (UNDI)
1153 boot with the entire PXE stack, including the UNDI driver, still
1154 resident in memory. All other values are undefined. If you don’t know
1155 what the UNDI or PXE stacks are, don’t worry — you don’t want them,
1157 <div class="paragraph"><p>On <strong>ISOLINUX</strong>/<strong>SYSLINUX</strong>, the <em>type</em> specifies the local drive number to
1159 drive.</p></div>
1160 </dd>
1163 </dt>
1164 <dd>
1165 <p>
1167 PXE protocol does not provide any means for specifiying or using a
1168 command line or initrd.
1169 </p>
1170 </dd>
1171 </dl></div>
1172 </div>
1173 </div>
1180 </dt>
1181 <dd>
1182 <p>
1183 (3.71+) An initrd can be specified in a separate statement (INITRD)
1187 </p>
1188 </dd>
1189 </dl></div>
1190 </div>
1191 </div>
1196 affecting the user experience and not the boot process.</p></div>
1200 </dt>
1201 <dd>
1202 <p>
1204 the kernel command line. The only options recognized are those
1206 </p>
1207 </dd>
1210 </dt>
1211 <dd>
1212 <p>
1215 </p>
1216 </dd>
1219 </dt>
1220 <dd>
1221 <p>
1224 the user types anything on the keyboard, the assumption being that the
1225 user will complete the command line already begun. The timer is reset
1226 to 0 upon return from an unsuccessful attempt to boot or from a module.
1227 A timeout of zero (the default) will disable the timeout completely.
1228 </p>
1229 </dd>
1232 </dt>
1233 <dd>
1234 <p>
1235 Indicates how long to wait until booting automatically, in units of
1237 used to deal with serial port glitches or "the user walked away" type
1238 situations. A timeout of zero (the default) will disable the timeout
1239 completely.
1240 </p>
1241 <div class="paragraph"><p>Both <strong>TIMEOUT</strong> and <strong>TOTALTIMEOUT</strong> can be used together, for example:</p></div>
1245 # always boot after 15 minutes.
1246 TIMEOUT 50
1248 </div></div>
1249 </dd>
1250 </dl></div>
1254 </dt>
1255 <dd>
1256 <p>
1257 Sets the command line invoked on a timeout (which often references a
1259 </p>
1260 </dd>
1263 </dt>
1264 <dd>
1265 <p>
1266 If a kernel image is not found (either due to it not existing, or
1269 directive reads as:
1270 </p>
1274 </div></div>
1279 </div></div>
1280 <div class="paragraph"><p><strong>Syslinux</strong> will execute the following as if entered by the user:</p></div>
1284 </div></div>
1285 </dd>
1288 </dt>
1289 <dd>
1290 <p>
1292 /dev/ttyS0 = COM1, etc.) or an I/O port address (e.g. 0x3F8); if
1295 </p>
1296 <div class="paragraph"><p><em>flowcontrol</em> is a combination of the following bits:</p></div>
1300 0x002 - Assert RTS
1301 0x008 - Enable interrupts
1302 0x010 - Wait for CTS assertion
1303 0x020 - Wait for DSR assertion
1304 0x040 - Wait for RI assertion
1305 0x080 - Wait for DCD assertion
1306 0x100 - Ignore input unless CTS asserted
1307 0x200 - Ignore input unless DSR asserted
1308 0x400 - Ignore input unless RI asserted
1310 </div></div>
1316 0x303 - Null modem cable detect
1317 0x013 - RTS/CTS flow control
1318 0x813 - RTS/CTS flow control, modem input
1319 0x023 - DTR/DSR flow control
1321 </div></div>
1322 <div class="paragraph"><p>For the <strong>SERIAL</strong> directive to be guaranteed to work properly, it should
1323 be the first directive in the configuration file.</p></div>
1325 <table><tr>
1328 </td>
1330 detected by the BIOS. They may or may not correspond to the legacy port
1332 </tr></table>
1333 </div>
1336 potentially cause problems with buggy BIOSes.</p></div>
1337 <div class="paragraph"><p>This option is "sticky" and is not automatically reset when loading a
1338 new configuration file with the CONFIG command.</p></div>
1339 </dd>
1342 </dt>
1343 <dd>
1344 <p>
1346 processor while idle significantly reduces the power consumption, but
1347 can cause poor responsiveness to the serial console, especially when
1348 using scripts to drive the serial console, as opposed to human
1349 interaction.
1350 </p>
1351 </dd>
1354 </dt>
1355 <dd>
1356 <p>
1359 default.)
1360 </p>
1361 <div class="paragraph"><p>Some BIOSes try to forward this to the serial console and sometimes make
1362 a total mess thereof, so this option lets you disable the video console
1363 on these systems.</p></div>
1364 </dd>
1367 </dt>
1368 <dd>
1369 <p>
1370 Load a font in .psf format before displaying any output (except the
1371 copyright line, which is output as ldlinux.sys itself is loaded.)
1373 contains a Unicode table it is ignored. This only works on EGA and VGA
1374 cards; hopefully it should do nothing on others.
1375 </p>
1376 </dd>
1379 </dt>
1380 <dd>
1381 <p>
1383 simplistic (it simply remaps the keycodes received from the BIOS, which
1384 means that only the key combinations relevant in the default layout — usually U.S. English — can be mapped) but should at least help people
1385 with AZERTY keyboard layout and the locations of = and , (two special
1386 characters used heavily on the Linux kernel command line.)
1387 </p>
1388 <div class="paragraph"><p>The included program keytab-lilo.pl from the LILO distribution can be
1389 used to create such keymaps. The file keytab-lilo.txt contains the
1390 documentation for this program.</p></div>
1391 </dd>
1394 </dt>
1395 <dd>
1396 <p>
1397 Displays the indicated file on the screen at boot time (before the boot:
1399 </p>
1401 <table><tr>
1404 </td>
1406 </tr></table>
1407 </div>
1408 </dd>
1411 </dt>
1412 <dd>
1413 <p>
1414 Prints the message on the screen.
1415 </p>
1416 </dd>
1419 </dt>
1420 <dd>
1421 <p>
1423 key is pressed, or Caps Lock or Scroll lock is set (this is the
1425 </p>
1426 </dd>
1429 </dt>
1430 <dd>
1431 <p>
1433 escapes. Use this (together with PROMPT 0) to force the default boot
1434 alternative.
1435 </p>
1436 </dd>
1439 </dt>
1440 <dd>
1441 <p>
1443 boot: prompt.
1444 </p>
1445 </dd>
1446 </dl></div>
1450 </dt>
1453 </dt>
1456 </dt>
1459 </dt>
1462 </dt>
1465 </dt>
1468 </dt>
1471 </dt>
1474 </dt>
1477 </dt>
1480 </dt>
1483 </dt>
1484 <dd>
1485 <p>
1486 Displays the indicated file on the screen when a function key is pressed
1487 at the boot: prompt. This can be used to implement pre-boot online help
1488 (presumably for the kernel command line options.) Please see the
1489 section below on DISPLAY files.
1490 </p>
1491 <div class="paragraph"><p>When using the serial console, press <Ctrl-F><digit> to get to the help
1495 </dd>
1498 </dt>
1499 <dd>
1500 <p>
1502 of directories to search when attempting to load modules. This directive
1503 is useful for specifying the directories containing the lib*.c32 library
1504 files as other modules may be dependent on these files, but may not
1505 reside in the same directory. Multiple instances will append additional
1506 paths.
1507 </p>
1508 </dd>
1511 </dt>
1512 <dd>
1513 <p>
1517 underscores.
1518 </p>
1519 <div class="paragraph"><p>This command limits the cookies send; 0 means no cookies. The default
1521 <div class="paragraph"><p>This option is "sticky" and is not automatically reset when loading a
1522 new configuration file with the CONFIG command.</p></div>
1523 </dd>
1524 </dl></div>
1525 </div>
1526 </div>
1530 <div class="paragraph"><p>DISPLAY and function-key help files are text files in either DOS or UNIX
1532 are interpreted:</p></div>
1537 </dt>
1538 <dd>
1539 <p>
1540                                  = <Ctrl-L> = ASCII 12<br />
1541 Clear the screen, home the cursor. Note that the screen is filled with
1542 the current display color.
1543 </p>
1544 </dd>
1547 </dt>
1548 <dd>
1549 <p>
1551 screen is filled with the current display color.
1552 </p>
1553 </dd>
1556 </dt>
1557 <dd>
1558 <p>
1560 </p>
1561 <div class="paragraph"><p>Clear the screen, home the cursor. Note that the screen is filled with
1562 the current display color.</p></div>
1563 </dd>
1566 </dt>
1567 <dd>
1568 <p>
1570 Clear the screen, home the cursor. Note that the screen is filled with
1571 the current display color.
1572 </p>
1573 </dd>
1576 </dt>
1577 <dd>
1578 <p>
1580 </p>
1583 corresponding to the standard PC display attributes:</p></div>
1588 2 = dark green a = bright green
1589 3 = dark cyan b = bright cyan
1590 4 = dark red c = bright red
1591 5 = dark purple d = bright purple
1592 6 = brown e = yellow
1594 </div></div>
1598 </dd>
1601 </dt>
1602 <dd>
1603 <p>
1605 </p>
1606 <div class="paragraph"><p>If a VGA display is present, enter graphics mode and display the graphic
1607 included in the specified file. The file format is an ad hoc format
1608 called LSS16; the included Perl program "ppmtolss16" can be used to
1609 produce these images. This Perl program also includes the file format
1610 specification.</p></div>
1611 <div class="paragraph"><p>The image is displayed in 640x480 16-color mode. Once in graphics mode,
1613 differently: the background color is ignored, and the foreground colors
1614 are the 16 colors specified in the image file. For that reason,
1615 ppmtolss16 allows you to specify that certain colors should be assigned
1616 to specific color indicies.</p></div>
1617 <div class="paragraph"><p>Color indicies 0 and 7, in particular, should be chosen with care: 0 is
1618 the background color, and 7 is the color used for the text printed by
1620 </dd>
1623 </dt>
1624 <dd>
1625 <p>
1627 If we are currently in graphics mode, return to text mode.
1628 </p>
1629 </dd>
1632 </dt>
1633 <dd>
1634 <p>
1636 </p>
1637 <div class="paragraph"><p>These codes can be used to select which modes to print a certain part of
1638 the message file in. Each of these control characters select a specific
1639 set of modes (text screen, graphics screen, serial port) for which the
1640 output is actually displayed:</p></div>
1643 <pre><code>Character Text Graph Serial
1644 ------------------------------------------------------
1653 </div></div>
1655 console is in:</p></div>
1658 <pre><code><DC1>Text mode<DC2>Graphics mode<DC4>Serial port<ETB></code></pre>
1659 </div></div>
1660 </dd>
1663 </dt>
1664 <dd>
1665 <p>
1667 </p>
1669 </dd>
1672 </dt>
1673 <dd>
1674 <p>
1676 Beep the speaker.
1677 </p>
1678 </dd>
1679 </dl></div>
1680 </div>
1681 </div>
1685 <div class="paragraph"><p>The Linux boot protocol supports a "boot loader ID", a single byte where
1694 </div></div>
1696 /proc/sys/kernel/bootloader_type.</p></div>
1697 </div>
1698 </div>
1702 <div class="paragraph"><p><strong>Syslinux</strong> will attempt to detect booting on a machine with too little
1703 memory, which means the Linux boot sequence cannot complete. If so, a
1704 message is displayed and the boot sequence aborted. Holding down the
1705 Ctrl key while booting disables this feature.</p></div>
1706 <div class="paragraph"><p>Any file that <strong>Syslinux</strong> uses can be marked hidden, system or readonly
1709 attributes on LDLINUX.SYS.</p></div>
1710 </div>
1711 </div>
1719 DEFAULT linux
1720 PROMPT 1
1721 TIMEOUT 600
1723 LABEL linux
1724 LINUX vmlinuz
1725 APPEND initrd=initrd1.gz,initrd2.gz
1727 LABEL m
1728 COM32 menu.c32</code></pre>
1729 </div></div>
1733 executed as a Linux kernel, initrd files initrd1.gz and initrd2.gz are
1734 loaded as initial ramdisk files (like cpio.gz files for initramfs). If
1736 executed to launch a menu system.</p></div>
1737 </div>
1738 </div>
1743 <a href="http://www.syslinux.org/wiki/index.php/Common_Problems">http://www.syslinux.org/wiki/index.php/Common_Problems</a> and known
1744 hardware compatibility issues are listed at
1745 <a href="http://www.syslinux.org/wiki/index.php/Hardware_Compatibility">http://www.syslinux.org/wiki/index.php/Hardware_Compatibility</a> with
1746 filename translation difficulty and early PXE stacks being some of the
1747 most common. Reporting of other encountered issues is welcome and
1748 appreciated.</p></div>
1749 </div>
1750 </div>
1755 would also like to hear from you if you have successfully used Syslinux,
1757 <div class="paragraph"><p>If you are reporting problems, please include all possible information
1758 about your system and your BIOS; the vast majority of all problems
1759 reported turn out to be BIOS or hardware bugs, and I need as much
1760 information as possible in order to diagnose the problems.</p></div>
1762 announcements of new and test versions. To join, or to browse the
1763 archive, go to:</p></div>
1764 <div class="paragraph"><p><a href="http://www.zytor.com/mailman/listinfo/syslinux">http://www.zytor.com/mailman/listinfo/syslinux</a></p></div>
1766 (including multipart/alternative or similar.) All such messages will be
1767 bounced.</p></div>
1768 </div>
1769 </div>
1774 <strong>SYSLINUX</strong> documentation by H. Peter Anvin <<a href="mailto:hpa@zytor.com">hpa@zytor.com</a>>. The conversion
1775 to an AsciiDoc was made by Gene Cumm <<a href="mailto:gene.cumm@gmail.com">gene.cumm@gmail.com</a>></p></div>
1776 </div>
1777 </div>
1778 </div>
1783 </div>
1784 </div>
1785 </body>
1786 </html>