Do we have specific commands to trace or log syslinux? or do we have any configuration settings via which we can get informative logs while syslinux is booting up? Any method to know at which step syslinux is seeking an issue?
log tracing/debugging/trouble shooting in syslinux
Started by
shareknw
, Aug 15 2011 07:49 AM
1 reply to this topic
#1
Posted 15 August 2011 - 07:49 AM
#2
Posted 15 August 2011 - 01:21 PM
Being open source, one is able to compile Syslinux and enable extra debugging output.Do we have specific commands to trace or log syslinux?
If it gets as far as loading its configuration file, you can enable serial output in the config-file and capture everything via a serial port. This is useful if messages scroll off the screen too quickly, which is typically only the case if one has enabled extra debugging output during compilation.or do we have any configuration settings via which we can get informative logs while syslinux is booting up? Any method to know at which step syslinux is seeking an issue?
The simplest way to trouble-shoot, the same as for GRUB4DOS, is to remove any menu system and enter the label-names from the boot: prompt and observe the results without any menu system clearing the screen.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users