Kevux Systems
Turtle Kevux - Documentation - Booting & Running
Home
Documentation
Software Listing
Booting & Running
Installing Turtle Kevux
System Configuration
Server Configuration
Additional Notes
Credits

Booting Live System


This tutorial is assuming that you have either a live-usb or a live-cdrom.
In order to boot the Live system you need to have your computer boot the device by rebooting the computer.
While booting your machine, you may have to press a key to select boot options or something of similar meaning.
Note: live-usb's cannot be directly booted to on most machines that only support usb 1.1 or less.
To boot a live-usb on a usb 1.1 system, you will need a live cdrom that contains the appropriate grub.

Available Boot Options:
   Install Kevux System
   Boot Live System - Run From Memory
   Boot Live System - Run From CD-Rom
   Maintenance Mode
   Check Memory


Advanced Kevux-Specific Boot Options


What Should Happen


When all things work correctly, you should end up sitting on an XFCE desktop screen with a backgroup picture of a stream in a forest.
This is the default desktop environment and the default layout.
Enjoy.

If you do not want a graphical display to appear on system startup, then you can append xorg=no as a kernel boot parameter.


Something Went Wrong


Unfortunately, not all things work all of the time.
Whenever something goes wrong with the boot process, you will get stuck with a login prompt.
In order to Login, see Logging In Below.

Okay, so the system started up but you are not sitting in a graphical XFCE desktop with the kevux logo in the background.
In this situation, the most probably cause is that the Xorg (and therefore XFCE) failed to start.
The most common cause of this is a video card problem.
To fix this problem, you will need to manually tell xorg to use your particular video card or use vesa.

WARNING: This may require some moderate to advanced knowledge of the linux command line and understanding of what your video card specifically is.

If the system is not responding then you may need to be able to boot the system without xorg, so add the xorg=no boot parameter in the grub config at boot time.
Once you find a way to login you need to edit the /etc/X11/xorg.conf file to work with your appropriate video card.
To add your video card to the xorg.conf file, scroll to the bottom of that file looking for the part that begins with Section "Device"
Inside of this section, look for the part that begins with #Driver
Uncomment this line by removing the leading #.
On the same line, to the immediate right, you should see something text surrounded in double quotes.
Replace that text with the appropriate video card driver name.
If you do not know the proper driver then you will have to do some researching or asking for assistance as determining this is advanced and may be complex.
You may be able to identify your video card by running the command lspci and looking for a line that has VGA Compatible controller or Display controller.

For the actual login process, see the Logging In below.

If all else fails and you still cannot get into the system, try booting into maintenance mode by passing the grub command line option: maintenance.
However, using maintenance mode almost definitely requires advanced to expert knowledge.


Logging In


The login screen is pretty straight-forward.
Just type in your username and you will be prompted for a password.
The default username is turtle
The default password is kevux\
Do not forget the trailing slash: \



Immediately following a successful login, you will be prompted for the particular type of login.

Login Types:
  Terminal - Drop to a Terminal (Console).
  Webbrowser - Drop to a command-line webbrowser (Console).
  Xorg - Start Xorg (Graphical Display) using the manager defined in ~/.xinitrc (This is the default).



If you selected Terminal, then you will see a login prompt where you can type in any console commands you desire.
This console environment uses the bash shell.


Virtual Machines

Running Kevux on a virtual machine is pretty straight-foward and therefore only known issues will be listed here.

Physical Address Extension, aka PAE, is used by this system.
If the virtual machine does not have PAE, support enabled, then the system will not boot.

Hardware Virtualization features such as VT-z/AMD-V, are know to prevent GRUB from booting properly.
If for any reason your system does not boot, try disabling VT-z/AMD-V, support.