Lighthouse logoLighthouse 64 Boot Options

(Most options are case-sensitive and lower case.)

To obtain a boot prompt from the LiveCD/DVD, press <Esc> from the boot menu with the dark blue background.

Type lhp (or puppy) then a space pfix=<option>,<option>...

Or select, then edit the desired menu option as directed at bottom of the boot menu screen.
(When using these in a bootloader, enter the options at the end of the line beginning with linux or append, without lhp or puppy.)

pfix=ram        Clean boot, ignore saved sessions
pfix=fsck       Do filesystem check on save file and ext2/3/4 partitions

pfix=noautosave No automatic save file updates; manual or shutdown (after prompting) only
pfix=vesa       Use the vesa driver during automatic Xorg setup
pfix=xorgwizard Use this if your monitor doesn't support EDID
pfix=nox        Command line only, do not start X
pfix=clean      File cleanup (simulate version upgrade)
pfix=purge      More radical file cleanup (to fix broken system)
pfix=<n>        Number of saved sessions to ignore (multisession-CD)
acpi=off        Default on for PCs >2001, may give boot/shutdown problems
pci=noacpi      May solve boot boot problems on some hardware
pci=nocrs       Discard pci ACPI information. Fixes boot failures (t3500)
pkeys=<xx>      Keyboard layout, choices: azerty be-latin1 br-abnt2 br-abnt
 br-latin1-abnt2 br-latin1-us by cf croat cz de de-latin1 dk dvorak dvorak-l
 dvorak-r es et fi fr gr hu101 hu il it jp106 lt mk nl no pl pt-latin1
 ro ru se sg sk-qwerty sk-qwertz slovene sv-latin1 uk us wangbe
Examples: lhp pfix=ram pkeys=fr No save file, enable French keyboard layout
          lhp pfix=nox,ram      Clean boot without X. No space after comma.
vesa (or) lhp nomodeset pfix=vesa,ram  Try this for blank screen problems.

Simple: (no lhp pfix=)  ram Clean boot    memtest Run Memtest86+ diagnostic
f filesystem check      h or lbn Boot hard disk, n=0-6 or lbf (floppy)

The 'Simple' options are for entering at the LiveCD boot menu only, (not for
the kernel line in a Grub bootloader.)

SFS (squash file system) Boot Options
SFS add-ons can be selected and configured prior to mounting the layered
file system. If any add-ons are found, a brief prompt enables choice of
which ones to use that session, and whether to copy them to RAM.

Type lhp or puppy then a space pfix=<option>,<option>...

copy     copy .sfs files into ram.
nocopy   prefer not to copy .sfs files into ram
sfsauto  Skip prompt and auto-load current SFS list
sfscfg   Configure SFS at boot without prompting first
nosfs    Skip prompt and don't load any .sfs add-ons


lhp pfix=sfsauto          Skip prompt and auto-load .sfs files
lhp pfix=ram,sfsauto,copy Clean boot, skip prompt, auto-load .sfs into RAM
lhp pfix=ram,sfscfg       Clean boot, launch .sfs configuration
lhp pfix=ram,nosfs        Clean boot, don't load any .sfs add-ons

Install Configuration Boot Options
The following are mostly in GRUB/Syslinux setup for installed LH64. Files
are found automatically at bootup but these can help the 'init' script. 


pdev1=sdc1      The boot partition.
psubdir=lhp601  Subfolder into which LH64 is installed, (1 level deep.)
psavemark=2     Partition number (in boot drive) to save session to.
pmedia=usbflash Type of media booting from. Choose one of these:
           usbflash usbhd usbcd ataflash atahd atacd atazip scsihd scsicd cd

Advanced / Debugging Options (LH64-6.01 and later)
Prevent named list of modules (drivers) to be loaded. Use this if the
system cannot start up due to suspected bad modules. The syntax is: 
blacklist=module1,module2,module3 and so on. 
Note: separate module names by comma, and there is no space in between.

Example: lhp blacklist=nouveau (for Nvidia driver installation.)

This parameter is the opposite of blacklist. It tells Lighthouse 64 to
load specific modules that are not automatically loaded, probably because
it is not detected or because it has a conflict with others modules. This
can be used to load any modules, although it is meant for loading modules
required to access save devices (the device where the savefiles are
located) - although if this is the case, coldplug may be a better option
(at a cost of slightly longer boot time). 

If the modules are not required during boot time, don't use this parameter.
Load modules from /etc/rc.d/rc.local instead by adding a line like this:
modprobe <module_name>

Note: loadmodules takes precedence over blacklist.

Do hardware detection & driver/module loading as early as possible at boot.

loglevel=<n>  Bootup verbosity, n=3-7 7 is high verbosity for debugging.
safe          nomodeset debug pfix=ram,fsck,nox,vesa,nocopy (LiveCD boot
                                                             menu only)
pfix=rdsh     Execute 'init' then dropout to prompt in initramfs.
pfix=rdsh0    Dropout early, before loading kernel drivers.
pfix=rdsh6    Dropout just before mount layered filesystem.

More help here:

Back to top