Try Linux Without Installing: Live USB Guide

A live USB lets you run a full Linux desktop straight from a flash drive—no changes to your hard drive, no commitment. It's the smartest way to check hardware compatibility, try different distros, or rescue a broken system. With persistence enabled, your settings and files survive reboots, making the drive genuinely useful day-to-day before you ever install anything.

What You Need

• A USB drive of at least 8 GB (16 GB or more if you want persistence). USB 3.0 speeds make a real difference—avoid old USB 2.0 drives if you can.
• A downloaded ISO image of your chosen distro. Good beginner picks: Ubuntu 24.04 LTS, Fedora 40 Workstation, or Linux Mint 21.
• A tool to write the ISO. We'll use Ventoy (recommended) and cover balenaEtcher as an alternative.

Verify the ISO Download

Before writing anything, verify the checksum. Distro download pages always list SHA256 hashes. A mismatch means a corrupted or tampered download.

# Replace the filename and hash with the ones from the distro's download page
sha256sum ubuntu-24.04-desktop-amd64.iso

Compare the output against the official hash. Even one character difference means you should re-download.

Method 1: Ventoy (Recommended)

Ventoy formats the USB once, then you just copy ISO files onto it like a normal drive. You can store multiple distros on one stick and pick at boot—no re-flashing needed when you want to try something new.

Install Ventoy on the USB Drive

Download the latest Ventoy release from ventoy.net. It ships as a compressed archive.

# Extract and run the installer; replace X.X.XX with the actual version
tar -xzf ventoy-X.X.XX-linux.tar.gz
cd ventoy-X.X.XX

# Find your USB device name first — do NOT guess
lsblk -d -o NAME,SIZE,MODEL

Identify your USB drive carefully (e.g., sdb or sdc). Picking the wrong device will wipe it. Then install Ventoy:

# Replace sdX with your actual USB device — NOT a partition (sdb, not sdb1)
sudo bash Ventoy2Disk.sh -i /dev/sdX

Ventoy creates two partitions: a small EFI/boot partition and a large exFAT data partition. The script will warn you that all data on the drive will be erased—confirm to proceed.

Copy ISO Files to the Drive

Mount the Ventoy data partition (it will appear as a normal removable drive in your file manager) and copy your ISO directly onto it.

# If it doesn't auto-mount, mount it manually
sudo mkdir -p /mnt/ventoy
sudo mount /dev/sdX2 /mnt/ventoy
cp ~/Downloads/ubuntu-24.04-desktop-amd64.iso /mnt/ventoy/
sudo umount /mnt/ventoy

Method 2: balenaEtcher (Simpler, No Multi-Boot)

Etcher writes a single ISO directly to the USB. It's the fastest option if you only need one distro. Download it from etcher.balena.io. It ships as an AppImage on Linux—no installation required.

# Make the AppImage executable and run it
chmod +x balenaEtcher-*.AppImage
./balenaEtcher-*.AppImage

In the GUI: select your ISO, select your USB drive, click Flash. Done. The drive is not reusable for general storage after this without reformatting.

Enable Persistence (Optional but Useful)

Persistence saves your changes—installed packages, browser bookmarks, Wi-Fi passwords—back to the USB between reboots. Support and setup varies by distro.

Ventoy Persistence

Ventoy supports persistence via a separate image file. Create a persistence image for your distro:

# Create a 4 GB persistence file (adjust size as needed; max depends on filesystem)
# For Ubuntu/Mint — uses casper-rw
dd if=/dev/zero of=/mnt/ventoy/ubuntu-persistence.dat bs=1M count=4096
mkfs.ext4 -L casper-rw /mnt/ventoy/ubuntu-persistence.dat

Then create a Ventoy JSON config that links the persistence file to the ISO. Create the file at /mnt/ventoy/ventoy/ventoy.json:

mkdir -p /mnt/ventoy/ventoy
cat > /mnt/ventoy/ventoy/ventoy.json << 'EOF'
{
    "persistence": [
        {
            "image": "/ubuntu-24.04-desktop-amd64.iso",
            "backend": "/ubuntu-persistence.dat"
        }
    ]
}
EOF

At boot, Ventoy will show a persistence menu automatically. Select the persistence option to use your saved data.

Note: Fedora uses a different persistence mechanism (overlayfs) and does not support Ventoy persistence in the same way. For Fedora live persistence, use the official livecd-iso-to-disk tool on a Fedora host instead.

Boot from the USB

Plug the USB into the target machine and power it on. You need to enter the boot device menu—the key varies by manufacturer but is commonly F12, F11, Esc, or F9. A quick search for your machine model and "boot menu key" will confirm it.

If the USB doesn't appear in the boot menu:

• Enter the UEFI/BIOS setup (usually Del, F2, or F10 at POST) and confirm Secure Boot is not blocking the drive. Ventoy supports Secure Boot enrollment on first launch; follow the on-screen prompts.
• Make sure Fast Boot or Fast Startup is disabled in both the UEFI and Windows (if dual-booting) — Windows fast startup keeps the disk locked.
• Check that USB boot is enabled and prioritized in the UEFI boot order.

Test Your Hardware

Once booted into the live environment, check the components most likely to cause trouble before committing to an install:

• Wi-Fi: Open the network manager applet and attempt to connect. If the adapter isn't detected, check lspci or lsusb output and look up the chipset.
• Graphics: Look for visual glitches, screen tearing, or failed compositing. On Wayland sessions, confirm the compositor is running with echo $XDG_SESSION_TYPE.
• Audio: Play a sound. Check pactl info to confirm PipeWire or PulseAudio sees your hardware.
• Touchpad/trackpad: Multi-finger gestures, palm rejection.
• Suspend/resume: Close the lid and reopen it. Broken resume is one of the most common laptop Linux complaints.

# Quick hardware overview from the live session
inxi -Fz

If inxi isn't installed in the live environment, use lspci -k to see detected devices and their kernel drivers.

Verify the Live Session Is Working Correctly

# Confirm you are running from the live medium, not an installed system
df -h /
# Output should show a tmpfs or overlay filesystem, not a normal ext4/btrfs disk

# Check kernel and distro version
uname -r
cat /etc/os-release

Troubleshooting

Black screen or hangs at boot

Add nomodeset to the kernel boot parameters. In the GRUB menu, press e to edit the boot entry, find the line starting with linux, and append nomodeset before pressing Ctrl+X to boot. This disables kernel mode-setting and forces a basic display driver—useful for diagnosing GPU issues. If it boots successfully with nomodeset, the problem is a graphics driver conflict.

Ventoy shows "Secure Boot Violation"

On first boot with Secure Boot enabled, Ventoy launches an enrollment screen. Select Enroll Key, confirm, and reboot. The key is stored in the UEFI MOK database and persists across reboots on that machine.

Persistence changes not saving

Confirm the persistence label matches what the distro expects (casper-rw for Ubuntu/Mint). Check that the ventoy.json path and ISO filename match exactly—Ventoy is case-sensitive.

Very slow performance in the live session

Live sessions run largely in RAM. On machines with less than 4 GB RAM, expect sluggishness—this does not reflect installed performance. A USB 2.0 drive will also bottleneck disk-heavy operations significantly. Try a USB 3.0 drive before writing off a distro.