MX-14: Cheatcodes

Note: RC=right click
QuickStart | Customization | Files | Localization | MX Apps | Network | Persistence | Remaster | Samba | smxi | Sound | Synaptic | Advanced | About



This document explains many of the boot parameters (AKA cheatcodes) that are used by antiX and MX-14 Live systems. Most users will get by just fine by making selections in the bootloader menus, which provide a convenient GUI for setting some of the options documented here. You can use the F12 key in the bootloader to see what boot options are selected by your current menu choices.

Boot codes not listed in the menus must be added manually. When the boot screen shows, type e (without the quotes) to enable editing the line with the boot parameters.

Boot LiveCD/USB

These options control how the Live media boots. In particular the control where we look for the linuxfs file. The location of this file will be used for other Live features such as persistence and remastering.

The Boot Device

The primary job of Live initrd is to find the compressed file system called a squashfs file. For antiX and MX this file is normally named linuxfs. We need to find the device this file is on and find the file on that device.

Normally we scan all cdrom (and dvd) and usb devices for that file. This default behavior can be modified with the following options. The easiest way to specify the boot device is the from option which specifies what type of device to boot from.


The type of boot device. Valid values cd hd usb. More than one is allowed. The default is usb,cd so by default we will only look at cdrom/dvd devices and usb devices to for the boot directory.

You can also specify a device more specifically but giving a device name (like sda1), a partition label, or a partition UUID.


The name of the boot device. For example bdev=sda1.


The partition label of the boot device.


The UUID of the boot device.

The Boot Directory

By default, we look for the linuxfs file and and persistence files in the /antiX directory on the boot device. If you want to boot more than one Live system on the same device or if you want to do a frugal install, you should change that directory and use the bdir parameter to point to the new directory.


The boot directory. This is the directory where we look for the linuxfs (squashfs) file, persistence files and live-remaster files. The default is /antiX.


Debugging the boot process is described in the antiX FAQs. Sometimes booting problems can be tracked down to a missing driver or a driver that is not getting loaded. These two boot parameters can be helpful in tracking down such problems.


Set one or more breakpoints in the live-init script separated by commas. Use bp=? to get a list of breakpoints to choose from.

  1)   before loading modules
  2)   before looking for linuxfs file
  3)   after mounting boot device
  4)   after preparing persistence
  5)   after mounting persistence device    
  6)   after mounting linuxfs file
  7)   after mounting aufs
  8)   before prepare switch_root
  9)   right before starting init
 ce)   After toram copy file error
 ch)   after init= chroot
  e)   On possibly fatal error
  u)   final umount
  v)   before check VID

Control how much gets printed out during the early boot process. The default level is verb=5. Lower numbers print less, higher numbers print more. Usually 6 or 7 will show you more info without being too obnoxious. The full output is available in the /var/log/live/bootloader.log file. A partial version of the log file is available at /init.log from within most breakpoints.

Loading Modules

One of the primary tasks of the live-initrd is to mount the device that holds the linuxfs file which contains the final file system. Modules (also called drivers) sometimes need to be loaded to allow the kernel to talk to certain types of hardware. Most of the time this is taken care of automatically but if you have very old or unusual hardware, there might be a glitch.


Load one or more specific modules, separated by commas. You need to know the name of the module or modules you need for this to be useful.


Load all modules in the initrd that are not hardware specific. This is a shotgun approach just in case there is a module that is available in the initrd that needs to be manually loaded for your system to boot.


Don't automatically load the standard list of modules.

Other Booting option

These options affect the boot process but the don't fit into any of the categories above.


Use this to boot from a iso file. This feature is deprecated because it defaults some of the more advanced features of the Live system but is supported due to popular (or otherwise) demand.


The maximum number of seconds to try finding the boot directory. The default is 15 seconds. This replaces rootdelay which is no longer used.


These options enable and control Live persistence which allows you to make changes that will persist across reboots. These options are normally used on LiveUSBs but if you specify a persistence device (or use the default LiveCD persistence device) then you can make use persistence on a LiveCD. In this case, the changes will have to be saved on some other device that allows for read-write access.


This is the main option for controlling Live persistence. It can be given one or more of the following parameters, separated by commas


Automatically create rootfs and/or homefs files if they don't already exist and they are required. Normally, we will prompt the user for size and file system type.


Only look on internal hard drives for the persistence device. This is analogous to from=hd for finding the boot device.


Enable and require home persistence. The exclamation point means this form of persistence is required. A non-fatal error will be thrown if it cannot be enabled.


Request home persistence but don't require it. We will try to enable home persistence but if we can't then this fact is briefly noted and the boot continues normally.


Enable and require root persistence. The exclamation point means this form of persistence is required. A non-fatal error will be thrown if it cannot be enabled.


Request root persistence but don't require it. We will try to enable root persistence but if we can't then this fact is briefly noted and the boot continues normally.


If root persistence is enabled then use the static version of root persistence. Normally, dynamic root persistence is used. FIXME explain more?


Only look on usb partitions for the persistence device. This is analogous to from=usb for finding the boot device.

The Persistence Device

Just like the boot device can be specified generally with the from=* option and more specifically with options like bdev=*, the same choices are available for specifying the persistence device.

On a LiveUSB or a frugal install, the default persistence device is the boot device which is what you would expect. Normally the persistence files will sit alongside the linuxfs file that we are booting from.

On a LiveCD the default persistence device is whatever device has the disk label antiX-Persist. If you specify a persistence device with one of the three options below then the defaults are ignored.


The name of the persistence device. For example pdev=sdb2.


The partition label of the persistence device.


The UUID of the persistence device.

Other Persistence Options

These options don't fit into any of the previous categories.


How many seconds to wait for the persistence device to appear. This is only relevant if the peristence device is different from the boot device. The default is 10 seconds.


These two options affect remastering. Normally, remastering is done automatically whenever there is a file in the same directory as the linuxfs file.

noremaster (LiveUSB Only)

Disable remastering even when a file is found.

rollback (LiveUSB Only)

Roll back to the previous version of linuxfs. If you remaster and for some reason things go horribly wrong, then use this feature to get back to the state right before you did the remaster.


These options affect X-windows. They will all be carried over when you do an install. The various keyboards options are carried over in the file /etc/defaults/keyboard. The other options are carried over in the file /etc/X11/xorg.conf.

Keyboard Options

A rather complete list of keyboard options and variants is usually available at /usr/share/X11/xkb/rules/xorg.lst


Set the keyboard layout. This is usually one or more 2-letter country codes separated by commas. For example: kbd=gr,us. This will allow users to quick switch between the US and the Greek keyboard layouts.


Keyboard options. These give special meaning to certain keys or key combinations. For example kbopt=ctrl:nocaps turns the Caps Lock key into an extra Control key.


Keyboard variant. These are variants to the keyboard layout. For example kbvar=dvorak will give you a Dvorak keyboard layout when you use the us layout.

Video Options

These options affect the X-windows video.


DPI stands for "dots per inch". It controls the size of most fonts. A larger DPI value will give you larger fonts and as smaller value will give you smaller fonts. The default is 96. This setting is stored in the Display Manager configuration file. On antiX this is /etc/slim.conf.


Force a particular video driver to be used. By default, the X-Windows server will choose a driver that is tailored to work with your specific video hardware. Sometimes that driver will fail on unusual or very old hardware. You may need to add the nomodeset boot option to prevent a video driver from taking control of the video hardware before X-Windows starts. You can use inxi to check which driver is actually being used:

 inxi -G

Create an xorg.conf file. If xdrvr or xres are given then xorg.conf will be created automatically so there is usually no point in using this options.


Set the default screen resolution in xorg.conf. This is usually not needed because Xorg will automatically set the resolution. All resolutions that are found by probing your hardware will also be added as alternatives to the default.


These options let you customize or personalize your system. They will all be carried over to the hard drive when you install.


Set the hostname of the system. The default hostname is antiX1.


In antiX, this option sets more than just the language. It also sets the keyboard layout, the Debian mirror, and the timezone. If you set any of these others explicitly then that setting will over-ride the value set via lang.


Set the country of the Debian mirror. Usually this option is set to a 2-letter country code such as mirror=gr.


Set the timezone. Example: tz=America/Denver. Some languages, such as en_US (United States English) cover more than one timezone so setting the lang may not set the correct timezone.

Other Live System Features

These options control features that are specific to the Live system but don't fit into any of the previous categories. Some of these are available in the bootloader menus.


Disables certain startup services for a faster boot and a smaller, faster system. Valid values are a combination of the following letters:

 L = lean        Turn off some services
 M = mean        Turn off some networking services
 X = Xtralean    Turn off even more services
 D = nodbus      Dont' launch dbus
checkfs (LiveUSB Only)

Perform file system check on the LiveUSB. This won't check the file system of a LiveCD. Will also check the filesystem of the persistence device (if different from the boot device) and the file systems on the persistence files rootfs and homefs if they exist and are enabled. It will only check the following types of file systems: ext2, ext3, and ext4.

gfxsave=* (LiveUSB Only)

Set the bootloader current bootloader settings as the defaults. Valid values: custom, menus, both, and reset.


Check the md5sum of the three primary files needed to boot a live system: linuxfs, vmlinuz, and initrd.gz. If this test passes then your boot media should be good although this won't necessarily catch intermittent problems.


The LiveUSB acts like an installed system and will automatically check its own filesystem based the time since the last check and/or the number of mounts since the last check. Use this option to turn this feature off.


Copy the entire linuxfs file into RAM. This takes up RAM. The amount of RAM used will be about the same as the size of the .iso file used to create the LiveCD or LiveUSB. It will also take some time when you first boot to copy the file into RAM. But after this, the system will run very fast. You can also eject the LiveCD (or remove the LiveUSB while the system is running.