Section "Keyboard layout" is vague. The last step "# keytab-lilo de > de.ktl" doesn't even work, because the kmap file is missing and then an empty file *.ktl file is created. The Note is unclear in explanation on where those prerequisites are described. T.ask (talk) 13:51, 28 October 2015 (UTC)
- Considering that the topic of keyboard layout in the Syslinux boot prompt is a repetitive issue (see https://bbs.archlinux.org/viewtopic.php?id=206752 as one of several examples), I have added some generic info / example in the wiki ( https://wiki.archlinux.org/index.php?title=Syslinux&diff=413588&oldid=410194 ). It might be enough so to push users towards the right direction. Ady (talk) 18:58, 27 December 2015 (UTC)
HOW do you install Syslinux as a bootloader?
The last step of the instillation guide simply state install a boot loader with a link to available boot loaders.
From the list of available boot loaders I chose Syslinux which brought me here.
This guide simply states install from official distributions? Again HOW?
The link for official distributions just takes me to a lengthy page on what official distributions are.
I still have no idea HOW to install Syslinux as my boot loader for my bran new install of Arch-linux. At this point I will have to abandon the whole thing for failed instructions. Neither apt or aptitude are installed with the distro and again, the instructions do not tell me anything about what my options are or how to go about the task given. Not providing instructions is an epic fail for a set of instructions.
I tried registering on the forums to find the answer but the registration system is broken asking a anti-bot question I can't possibly answer. Some code thing, but I'm no programmer and haven't clue. —This unsigned comment is by Krahazik (talk) 20:07, 25 November 2015. Please sign your posts with ~~~~!
- Fixed the installation link with 
- For the rest, see the Beginners' guide. -- Alad (talk) 19:17, 25 November 2015 (UTC)
Location of kernel and initrd files in UEFI systems
The edition  seems to be too-strong in its wording (i.e. "must") with no real indication of what is happening or why such path should be used in syslinux.cfg (which is not completely accurate anyway).
The path in syslinux.cfg for files such as vmlinuz-linux depends on where exactly the files are located, in relation to the working directory of syslinux.efi.
For example, if the kernel and initrd files are located in the root of the $esp, and syslinux.efi is located in
$esp/EFI/syslinux/, then the paths to be used in
$esp/EFI/syslinux/syslinux.cfg would start by
../../ as "mandated" by the aforementioned edition.
But if the kernel and initrd files are located in the
$esp/EFI/ directory (as another example), then the paths to be used in
$esp/EFI/syslinux/syslinux.cfg would start by
../, not by
Considering that the "UEFI systems" section does not mandate any specific directory for the location of the kernel and initrd files – as of syslinux.efi 6.03, they only need to be somewhere in the $esp partition – I would tend to think that the wording of this edition might need some tweaking, and/or more accurate information should be provided regarding the (recommended) location of the kernel and initrd files for UEFI systems.
IMHO, the aforementioned edition lacks context / accuracy when reading the "UEFI systems" section of this article.
Additionally, the reason for this edition points to  but, to a user seeking for instructions / information (i.e. without prior knowledge / understanding), that forum topic does not seem to provide any justification for this "mandatory" change of paths, nor instructions for users to follow, especially considering the lack of context for this edition within the wiki page itself. Ady (talk) 17:20, 20 February 2016 (UTC)
- I see, my editing realy does more harm than good.
- When you install this stuff the first time you just follow the description and apply the examples to your installation without paying much attention. So paths in example don't always match your installation (which shouldn't be surprising). But I wanted to warn the reader.
- I will remove my edit and add a note to examples section. Thompson 19 March 2016
"If you do not want to see the Syslinux menu at all, use the #Boot prompt, and set PROMPT to 0 and comment out any UI menu entries. Setting the TIMEOUT variable to 0 might also be a good idea. Make sure there is a DEFAULT set in your syslinux.cfg."
Is there a key sequence to interrupt boot in order to edit kernel parameters when using a zero prompt/timeout? If so, it would be nice for this to be included in this section. --TheChickenMan (talk) 21:03, 12 May 2016 (UTC)
- See the upstream Syslinux wiki, http://www.syslinux.org/wiki/index.php/Directives/special_keys . Ady (talk) 12:03, 13 May 2016 (UTC)