Installing Linux: Live USB to First Boot

• Before You Install
  • Hardware and Installer Prep Checklist
• Create a Bootable USB
• BIOS and UEFI Settings
• Partitioning Choices
  • Safe Default Layout
  • Full Disk vs Dual-Boot
  • How Much Space Should You Allocate
  • Encryption Decision
• During Installation
  • Timezone, Locale, and Keyboard Notes
• First Boot Checklist
  • First Boot Validation Commands
• Common Install Problems
  • Installer Does Not Boot
  • No Wi-Fi After Install
  • Boots Straight into Old OS
  • Black Screen After First Reboot
  • System Boots but Feels Unstable
• Post-Install Hardening Basics
• First Week Stabilization Plan

Installing Linux is much easier when you treat it like a checklist instead of a one-shot gamble. This chapter focuses on a beginner-safe workflow you can reuse on laptops, desktops, and dual-boot systems.

Before You Install

Do these checks before you boot the installer:

• Back up important files from your current system.
• Confirm whether your system boots in UEFI mode (modern default).
• Decide if this is full-disk Linux or dual-boot with Windows.
• Download the ISO only from the official distribution website.
• Verify the ISO checksum when available.

Why this matters: Most install failures come from skipped prep, not from Linux itself.

Hardware and Installer Prep Checklist

Before committing to install, verify these practical details:

• You have at least 25 to 30 GB free for the OS and updates.
• You have enough RAM for your chosen desktop environment.
• You know whether your disk is NVMe (/dev/nvme0n1) or SATA (/dev/sdX).
• You can boot the live USB and confirm keyboard, trackpad, audio, and Wi-Fi work.

If any core device fails in live mode, stop and solve that first.

Create a Bootable USB

Use one of these tools:

• Balena Etcher (simple GUI workflow)
• Rufus (common on Windows)
• Ventoy (multi-ISO USB)
• dd (advanced terminal method)

Typical Linux command-line method:

lsblk
sudo dd if=linux.iso of=/dev/sdX bs=4M status=progress oflag=sync

Replace /dev/sdX with the USB device, not a partition like /dev/sdX1.

Warning: Writing to the wrong disk with dd can destroy data immediately.

BIOS and UEFI Settings

Before booting from USB, enter firmware settings and check:

• USB boot is enabled.
• Boot mode is UEFI for modern installs.
• Fast Boot is disabled if USB boot is ignored.
• Secure Boot is left on unless your distro or driver setup requires disabling it.

If the USB does not appear in boot options, recreate it and try a different USB port.

Partitioning Choices

For most beginners, use installer defaults unless you have a clear reason not to.

Safe Default Layout

• EFI System Partition (FAT32, usually 300 MiB to 1 GiB)
• Root partition (/, ext4)
• Optional home partition (/home, ext4)
• Optional swap partition or swap file

Full Disk vs Dual-Boot

• Full disk Linux: simplest and most reliable install path.
• Dual-boot: useful during transition, but requires extra care with disk space and boot entries.

How Much Space Should You Allocate

Common desktop sizing guidance:

• Root (/): 100 to 200 GB for general desktop usage
• Home (/home): as much as possible for personal files
• Swap: often 2 to 8 GB, or larger if you rely on hibernation Note: swap isn’t needed unless you have very low RAM or use hibernation.

If you are unsure, keep layout simple: one root partition plus swap.

Encryption Decision

Many installers offer full-disk or home encryption.

• Use encryption on laptops and portable systems.
• Skip encryption only if you have specific performance or recovery requirements.

If you enable encryption, store recovery details safely and do not forget the passphrase.

If dual-booting:

• Shrink Windows from Windows Disk Management first.
• Disable Windows Fast Startup.
• Keep a recovery USB for both OSes.

During Installation

Recommended beginner choices:

• Create a normal user account and strong password.
• Enable automatic time zone and network if available.
• Install third-party codecs and drivers when offered by trusted installers.
• Use default bootloader settings unless you understand custom changes.

Timezone, Locale, and Keyboard Notes

These settings cause daily friction when incorrect:

• Confirm timezone and clock source.
• Confirm keyboard layout and compose behavior.
• Confirm locale so package manager and logs use expected language and formatting.

First Boot Checklist

After first login:

1. Connect to wired or wireless network.
2. Update system packages.
3. Reboot once after updates.
4. Verify audio, graphics, and Bluetooth.
5. Install one browser and one editor you trust.
6. Create a basic backup of your home folder.

First Boot Validation Commands

Use these checks to confirm the system is healthy:

uname -r
lsblk -f
ip address
systemctl --failed

• uname -r: confirms active kernel.
• lsblk -f: confirms partition and mount layout.
• ip address: confirms interface detection.
• systemctl --failed: checks for failed services.

Cross-distribution update commands:

# Debian and Ubuntu
sudo apt update && sudo apt upgrade -y

# Fedora and RHEL-based
sudo dnf upgrade --refresh -y

# Arch-based
sudo pacman -Syu

Common Install Problems

Installer Does Not Boot

• Recreate USB media.
• Try another USB port.
• Disable Fast Boot.
• Verify ISO checksum.

No Wi-Fi After Install

• Check if hardware is detected with lspci or lsusb.
• Open networking chapter and verify NetworkManager status.
• Install required firmware package for your chipset.

Boots Straight into Old OS

• Enter firmware boot menu and choose Linux boot entry.
• Confirm EFI entry exists.
• Reinstall bootloader from live media if needed.

Black Screen After First Reboot

• Try booting an older kernel from advanced boot options.
• Switch display session type (Wayland or Xorg) at login.
• For NVIDIA hardware, verify matching driver and kernel module versions. nomodeset kernel option may be needed for older hardware.

System Boots but Feels Unstable

• Re-run updates and reboot again.
• Check failed services with systemctl --failed.
• Check disk usage with df -h.
• Remove experimental tweaks until baseline stability returns.

Post-Install Hardening Basics

Once the system is stable, do these security basics:

1. Keep the system updated weekly.
2. Use strong user and disk encryption passwords.
3. Enable firewall defaults.
4. Avoid random install scripts and unknown repositories.
5. Keep backups current before major updates.

First Week Stabilization Plan

During your first week, prioritize consistency over customization.

Day 1 to Day 2:

• Confirm updates complete without errors.
• Confirm suspend, reboot, and shutdown behavior.
• Confirm browser, audio, and input devices are stable.

Day 3 to Day 5:

• Add your core applications only.
• Avoid adding multiple third-party repositories at once.
• Start documenting any change you make to system configs.

Day 6 to Day 7:

• Run a full backup.
• Export a package list or notes for reproducibility.
• Capture a baseline health snapshot (systemctl --failed, df -h, free -h).

This approach gives you a known-good baseline before deeper customization.