Home Guides

Guides

Step-by-step how-tos for setup, troubleshooting, and common tasks.
Sean Rhodes
By Sean Rhodes
21 articles

Booting into recovery mode

Booting into Recovery Mode If your system isn’t booting properly, you can use Recovery Mode to diagnose and fix issues. Follow the steps below to access it. 1. Boot into GRUB Turn on your laptop and repeatedly tap the Esc key as it starts up. Stop pressing once the Star Labs logo disappears - this should bring up the GRUB menu: GRUB Menu 2. If You Press Esc Too Many Times If you see the screen below, you’ve gone one step too far. At the GRUB command line, type: normal Press Enter, then tap Esc again until the menu appears. If it still doesn’t show, restart your laptop and repeat step 1. GRUB Prompt 3. Select Recovery Mode Use the arrow keys to highlight Advanced options for Ubuntu, then press Enter. From the next menu, choose the second option — the one ending with (recovery mode). Advanced Options 4. Boot into Recovery Mode Press Enter to start the laptop in recovery mode. After a short moment, you’ll see the Recovery Menu: Recovery Menu 5. Recovery Options Explained Here’s what each option does: - resume – Exit recovery mode and start your laptop normally. - clean – Remove leftover installation files from installed programs. - dpkg – Resume incomplete installations (often useful after an interrupted update). - fsck – Check and repair file system errors (useful after power loss). - grub – Scan for installed operating systems and add them to the GRUB boot menu. - network – Enable internet access (wired only by default). - root – Open a terminal with administrator access — useful for: - Installing or removing software - Editing configuration files - Manually repairing GRUB 6. Connecting to a Wireless Network If you need to connect to Wi-Fi while in recovery mode, use this command - replacing NETWORK and PASSWORD with your own details: iwconfig wlan0 essid NETWORK key s:PASSWORD

Last updated on Feb 24, 2026

Changing desktop environment

All Star Labs machines ship with a choice of Linux distributions, allowing you to pick the one that best fits your needs — whether that’s Ubuntu, Linux Mint, Zorin OS, or others. Each distribution comes with its own default desktop environment (for example, Ubuntu ships with GNOME), but you can easily change or install new environments at any time to customise your experience. This guide will show you how to install, select, and remove different desktop environments using simple terminal commands. The examples below work on Ubuntu, Linux Mint, Elementary OS, and most other Debian-based distributions. Popular Desktop Environments Environment Package Name Command to Install GNOME gnome-session sudo apt install gnome-session Xfce xubuntu-desktop sudo apt install xubuntu-desktop KDE Plasma kubuntu-desktop sudo apt install kubuntu-desktop Cinnamon cinnamon-desktop-environment sudo apt install cinnamon-desktop-environment MATE mate-desktop-environment sudo apt install mate-desktop-environment Selecting Your New Desktop Environment 1. Reboot Once installation is complete, reboot your laptop. 2. Choose the Environment at Login At the login screen, click the gear icon or “Session” option next to your username. Then select your preferred desktop environment from the list. Desktop selection option Desktop session selector 3. Enjoy! Log in and enjoy your new desktop experience. Removing a Desktop Environment If you’d like to remove a desktop environment, open the Terminal and run the appropriate commands below: GNOME sudo apt remove ubuntu-gnome-desktop sudo apt autoremove -y Xfce sudo apt remove xubuntu-desktop -y sudo apt autoremove -y KDE sudo apt remove kubuntu-desktop sudo apt autoremove -y Cinnamon sudo apt purge cinnamon sudo apt autoremove -y MATE sudo apt remove mate-desktop sudo apt autoremove -y

Last updated on Feb 24, 2026

Getting started with the terminal

The terminal can look a little intimidating at first, but don’t worry - it’s simply a way to tell your computer what to do using text commands instead of a mouse. It’s fast, powerful, and once you learn a few basics, it becomes one of the most useful tools on your system. Don’t be afraid to experiment - most commands are completely safe to try. If something doesn’t work, the terminal will usually just return an error message, not break anything. And remember: you can always close the terminal window or type exit to get out of a session. About This Guide This quick guide is designed to help new users get started with the terminal. The terminal uses keyboard input only, and while commands can vary between operating systems, the examples below are for Ubuntu’s GNOME Terminal. Most of these commands will also work on other Linux distributions - if they don’t, you can search for the equivalent ones for your specific distro. Opening the Terminal You can open the terminal in a couple of ways: - Open the GNOME Launcher and search for Terminal. - Or, on most Linux distributions, press Ctrl + Alt + T to open it directly. Using the Tab Key This might sound odd, but it’s one of the most common tips we give at Star Labs: Tab is your friend. Pressing the Tab key auto-completes commands or filenames. For example, if you type: do and press Tab, you’ll see a list of all commands starting with “do”: do done dosfsck domainname do-release-upgrade dosfslabel If there’s only one match, Tab will complete it automatically. For instance, typing do-r and pressing Tab becomes: do-release-upgrade Navigating the File System Learning how to move around your system is one of the first steps. - Show your current directory: pwd Example output: /home/star - Change to another directory: cd Desktop - Go back to the parent directory: cd .. - List files and folders: ls - Include hidden files: ls -a Running Commands as Superuser Some tasks (like installing software or updating the system) require administrator permissions. To run a command with those permissions, use sudo before it. - Run a command as superuser: sudo - Install a program: sudo apt install program-name - Update installed packages: sudo apt update - Upgrade packages automatically: sudo apt upgrade -y - Upgrade packages and dependencies: sudo apt dist-upgrade -y - Remove unused dependencies: sudo apt autoremove - Search for installed programs by keyword: sudo apt list --installed | grep keyword Viewing and Editing Files You can read or edit text files right from the terminal: - View a file’s contents: cat filename - Edit or create a file: nano filename

Last updated on Feb 12, 2026

Installing an alternative kernel

Most Linux distributions automatically provide kernel updates through their package managers. However, these updates may not always include the very latest kernel version. If you want to take advantage of new features or performance improvements, you can manually install a newer kernel. ⚠️ Important: Using a kernel that hasn’t been tested by your Linux distribution can cause stability or compatibility issues. Proceed with caution. 1. Check Your Current Kernel Version To check which kernel version your system is currently running: 1. Open the GNOME Launcher and click on Terminal. 2. Type the following command: uname -r The output will display your current kernel version, for example: 6.5.0-28-generic 2. Download the New Kernel New kernel versions for Ubuntu, Linux Mint, elementary OS, and other Ubuntu-based distributions are available at: 👉 http://kernel.ubuntu.com/~kernel-ppa/mainline/ At the time of writing, the latest stable release is 6.8.7. ⚠️ Note: Versions marked with rc (release candidate) are not stable and should generally be avoided for daily use. After selecting your desired kernel version, scroll down to the section titled “Build for amd64 succeeded” and download the following three files: Headers: linux-headers-6.2.0-060200_6.2.0-060200.202302191831_all.deb Image: linux-image-unsigned-6.2.0-060200-generic_6.2.0-060200.202302191831_amd64.deb Modules: linux-modules-6.2.0-060200-generic_6.2.0-060200.202302191831_amd64.deb 3. Install the Downloaded Files Once the downloads are complete: 1. Open Terminal and navigate to your Downloads directory: cd ~/Downloads/ 2. Install all three downloaded files using the following command: sudo dpkg -i *.deb 3. Update your GRUB configuration: sudo update-grub 4. Reboot Your Laptop Restart your system for the new kernel to take effect. After rebooting, verify that the new kernel is active: uname -r You should now see the version number of the newly installed kernel. 5. Removing Older Kernels If you want to remove an older kernel version, use the following command — replacing the version number with the one you wish to remove: sudo apt remove linux-*6.2.0* Once the removal is complete, reboot your system to apply the changes.

Last updated on Feb 24, 2026

Installing/changing linux distribution

Installing Linux on Your Star Labs Laptop This guide covers installing Ubuntu and Linux Mint — two of the most popular Linux distributions. The steps are almost identical for other distributions as well. 🟠 Installing Ubuntu 1. Create a Bootable USB Drive Follow one of our guides to create a bootable USB stick: - On Linux - On macOS - On Windows 2. Boot from USB 1. Insert your bootable USB drive. 2. Turn on your computer and repeatedly tap the F2 key to open the boot menu. 3. Select your USB drive from the list and press Enter. Ubuntu Boot Menu 1. In the next menu, choose Install Ubuntu to start the installation process. Ubuntu Installer 3. Select Keyboard Layout Choose your preferred keyboard language and layout. Keyboard Layout 4. Updates and Software Options You’ll see two installation types: - Normal installation: Includes popular applications such as a media player and office tools. - Minimal installation: Installs only the essentials. We recommend selecting: - ✅ Download updates while installing Ubuntu - ✅ Install third-party software 💡 Tip: A network connection is required for downloading updates. Software Options 5. Erase Disk and Install Select Erase disk and install Ubuntu to proceed. ⚠️ Warning: This will delete all data on your drive. Erase Disk 6. Select Region Choose your region or time zone. Region Selection 7. Create Your User Account Enter your name, device name, and password. User Setup 8. Wait for Installation to Complete Once installation finishes, remove your USB drive when prompted and press Enter to restart. Installation Progress 9. Installation Complete At the login screen, select your user account and enter your password to start using Ubuntu. Ubuntu Login 🟢 Installing Linux Mint 1. Create a Bootable USB Drive Follow one of our guides to create a bootable USB stick: - On Linux - On macOS - On Windows 2. Boot from USB 1. Insert your USB drive. 2. Turn on your computer and tap the F7 key repeatedly to open the boot menu. 3. Select your USB drive and press Enter. Mint Boot Menu 1. Choose Start Linux Mint, and once the desktop loads, double-click Install Linux Mint to begin. Mint Desktop 3. Select Keyboard Layout Choose your preferred keyboard language and layout. Keyboard Layout 4. Connect to the Internet and Updates You’ll be prompted to connect to a network. While optional, it’s recommended to do so for updates and driver installation. If connected, enable Install third-party software for better hardware compatibility. Network Setup 5. Erase Disk and Install Select Erase disk and install Linux Mint to proceed. ⚠️ Warning: This will delete all data on your drive. Erase Disk 6. Select Region Choose your region or time zone. Region Selection 7. Create Your User Account Enter your name, device name, and password to create your user account. User Setup 8. Complete the Installation Once installation finishes, click Restart Now. When prompted, remove the USB drive and press Enter. Restart 9. Installation Complete You’ll arrive at the login screen. Select your username and enter your password to start using Linux Mint. Linux Mint Login ✅ That’s it! You’ve successfully installed Linux. You can now begin personalising your system, installing updates, and exploring your new OS.

Last updated on Feb 24, 2026

Is your wireless slow?

Improving Slow Wireless Performance on Star Labs Devices If you’re experiencing slow Wi-Fi speeds or unstable wireless transfers, this guide can help you identify and resolve common issues. 🔍 Understanding the Issue Star Labs devices use Intel AX200 or AX201 wireless cards. These cards include advanced power-saving features that help reduce energy consumption, but on some wireless N networks, this can lead to lower performance. 💡 Note: If your wireless adapter appears as “Wireless-AC 9462”, don’t worry — this is simply how some Linux kernels identify the AX201 card. By default, the wireless card operates in power-saving mode, which can limit throughput. The steps below will show you how to temporarily disable power saving, test performance, and (if effective) make the change permanent. 1. Temporarily Disable Power Saving Open a Terminal window and run the command for your device: LabTop Mk IV: sudo iwconfig wlp0s20f3 power off StarLite Mk IV: sudo iwconfig wlp0s12f0 power off Then test your connection speed again to see if performance improves. 2. Installing Useful Network Tools To better monitor your wireless connection, install wireless_tools and wavemon — a simple, live Wi-Fi monitoring tool. 🧰 Install Wireless Tools (for Manjaro / Arch-based) sudo pacman -S wireless_tools 📡 Install Wavemon Debian / Ubuntu-based: sudo apt install wavemon Arch / Manjaro-based: sudo pacman -S wavemon Fedora-based: sudo dnf install wavemon To start live monitoring: wavemon 3. Checking Wireless Signal and Connection Quality Use these commands to view available networks and monitor your connection: List all visible networks: nmcli device wifi list Monitor your current connection status: watch -n1 iwconfig These tools will help you detect weak signals, interference, or unstable links. 4. Make the Fix Permanent If disabling power saving improves performance, you can make the change permanent by adjusting your system configuration. ⚙️ Enable Link Aggregation and Disable Power Saving Run the following commands: sudo touch /etc/modprobe.d/starlabs.conf echo "options iwlwifi 11n_disable=8 power_save=off" | sudo tee -a /etc/modprobe.d/starlabs.conf sudo update-grub Then reboot your laptop to apply the new settings. 5. Advanced Configuration (Use with Caution) ⚠️ Warning: The following settings are for advanced users only. Incorrect changes may cause reduced performance or compatibility issues. You can further adjust /etc/modprobe.d/iwlwifi.conf to experiment with other driver options. For example, to disable only power saving, edit the file to read: options iwlwifi power_save=off Alternatively, you can create a new configuration file: sudo touch /etc/modprobe.d/starlabs.conf echo "options iwlwifi 11n_disable=8 power_save=off" | sudo tee -a /etc/modprobe.d/starlabs.conf sudo update-grub To revert to default settings: sudo rm /etc/modprobe.d/starlabs.conf 6. Optional Driver Parameters You can test additional parameters to fine-tune wireless performance: Parameter Description options iwlwifi bt_coex_active=0 Disables Bluetooth coexistence (may improve Wi-Fi throughput). options iwlwifi bt_coex_active=1 Enables Bluetooth coexistence (recommended if using Bluetooth devices). options iwlwifi 11n_disable=8 Enables antenna aggregation for improved performance. options iwlwifi swcrypto=1 Uses software encryption (can improve stability on some systems). options iwlwifi power_save=off Disables power saving (increases throughput). options iwlwifi d0i3_disable=1 Disables low-power idle state (LAR). options iwlwifi uapsd_disable=1 Disables U-APSD; may fix low throughput on some access points. ✅ Summary 1. Test disabling power saving with iwconfig. 2. Use wavemon and nmcli to monitor your connection. 3. If speeds improve, make the change permanent with /etc/modprobe.d/starlabs.conf. 4. Reboot and verify stability. You should now experience faster and more consistent wireless performance.

Last updated on Feb 12, 2026

Recovery from a bootable USB drive

If your laptop can’t boot into the operating system, you can use a bootable recovery USB drive to repair the boot loader. 🛈 Note: You can follow this guide to create a bootable USB drive. 1. When You Can’t Boot If you can’t access your operating system or its recovery menu, it can often be repaired from a bootable USB drive. 1. Insert the USB drive. 2. Turn on your laptop and repeatedly press F7 to open the boot menu in AMI or F2/Down Arrow for coreboot. Boot Menu 2. Boot from the Recovery USB Use the arrow keys to select your USB drive and press Enter to boot from it. You’ll need to use the live mode of the USB — this is typically labelled Live, Try, or Start. For Ubuntu, select Try Ubuntu. Live USB Menu 3. Check the Disk Path Open the GNOME Launcher and start Terminal. Open Terminal Then enter: sudo fdisk -l | grep 'nvme\|sda' 4. Identify the Correct Partition This command lists your storage devices — usually either sda or nvme. Locate the main system partition (typically ending with a p2). Partitions 5. Mount the Partitions Most systems have two partitions: one for the main system and one for EFI. Mount them by running: sudo mount /dev/nvme0n1p2 /mnt sudo mount /dev/nvme0n1p1 /mnt/boot/efi sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys 6. Enable Networking (Optional) If you need internet access while in recovery, run: sudo cp /etc/resolv.conf /mnt/etc/resolv.conf 7. Connect to the Installation Next, connect to your system installation with: sudo chroot /mnt /bin/bash 8. You’re Now Connected You are now in a root terminal running from your system’s internal drive. Chroot Session 9. Run Diagnostics and Repairs From here, you can perform various repair tasks: - fsck – Check the file system - GRUB Repair – Update the boot loader - dpkg – Fix broken packages If your issue was caused by an interrupted update (often leaving the system stuck at a GRUB prompt), try: sudo dpkg --configure -a sudo apt -f install You can find additional help in our guide on Booting into recovery mode.

Last updated on Feb 24, 2026

Star LabTop Mk IV - Complete Disassembly Guide

Place the Star LabTop Mk IV on a soft protected surface to avoid any possible scratching of the anodized finish. 1. Remove the 10x outer short Phillips screws from the backplate. 2. Remove the 2x inner centre longer Phillips screw from the backplate. 3. Carefully remove the backplate. Please note: The speakers may require carefully prizing away from the backplate. Check whilst lifting the backplate on the bottom left and right corners, to avoid damaging the speaker cables/connectors. 4. Battery removal: Disconnecting the battery connector. 5. Remove the 4 Phillips screws that hold the battery in place. 6. Carefully lift out the battery, carefully unhooking the antenna, speaker and CPU Fan cabling from the top left cable guides. 7. I/O board Removal: Lift the ribbon cable clamp to detach the ribbon cable. Remove the 3x Phillips screws that hold the IO Board in place. You can then lift out the I/O Board. 8. Disconnect the Display connector, Wireless and Bluetooth Antennas. 9. Disconnect the following ribbon cables/connectors from the Mainboard: I/O Board, Keyboard, Touchpad & Speakers connector. 10. Removal of the DC Jack: Remove the 2 silver Philips screws connecting the DC Jack shield to the mainboard. You can then disconnect the cable from the mainboard afterwards. 11. Removal of the Mainboard Remove the 4x Phillips screws around the Mainboard and then the 2x Phillips screws around the CPU Fan. 12. You can then lift out the Mainboard from the chassis. 13. Remove the I/O ribbon cable from the chassis. 14. Removal of the Display Array: 14.1 Remove the 4x Phillips screws from the left hinge.... 14.2 And then the right hinge. 14.3 Carefully lift the hinges to 90 degrees, to allow the chassis to clear the hinges. 14.4 Then lift the chassis to slide away from the display array. 15. Disassembly is now complete. 16. Reassembly is the reverse of these steps.

Last updated on Feb 12, 2026

Why is my machine booting to EFI Shell prompt?

If your laptop starts directly into the EFI Shell, this usually means the boot loader is no longer working properly. Don’t worry — this can often be fixed by manually booting and updating the boot configuration. Step 1: Attempt to Manually Boot via EFI Shell At the EFI Shell prompt, type the following commands one by one, pressing Enter after each: map -r fs0: cd EFI cd ubuntu grubx64.efi If successful, your system should boot into Ubuntu. Step 2: Update the Boot Loader Once you’ve booted into Ubuntu, open the Terminal (Ctrl + Alt + T) and run: sudo update-grub Then reboot your laptop to see if this resolves the issue. Step 3: Boot from a USB Drive (if the above fails) If the EFI Shell method doesn’t work, try booting from a bootable USB drive. If you don’t already have one, you can easily create it using a blank USB stick — see our guide here: 👉 Recovery from a Bootable USB Drive Once you’ve booted into the Ubuntu Live environment, open a Terminal (Ctrl + Alt + T) and check if your SSD is detected: For SATA SSDs: sudo fdisk -l | grep sda If no drive appears, it may not be seated correctly — continue to the next step. For NVMe SSDs: sudo fdisk -l | grep nvme Step 4: Check the SSD Connection If your SSD isn’t detected, you’ll need to physically check it. Please refer to the disassembly guide for your specific model in our Help Centre before proceeding. These guides include detailed steps and images to help you safely access and reseat your SSD. Step 5: Need Help? If you’ve tried all the above steps and are still experiencing issues, please contact our support team — we’re happy to help: 📧 [email protected]

Last updated on Feb 24, 2026

Speaker pop/click sound (Linux)

Overview Sometimes you might hear a pop/click from the speakers, usually when audio starts/stops, or around suspend/shutdown. We have upstreamed a runtime adjustment to improve this, but while that change trickles down to different distributions, you can use the workaround below. What you will do You will: - Create a small configuration file for the audio driver. - Rebuild the initramfs (on some distributions). - Reboot. Step 1: Open a Terminal Open the Terminal app. Common shortcuts: - On many distributions: press Ctrl + Alt + T - Or open your app launcher and search for Terminal Step 2: Create the config file Copy and paste this command into the Terminal, then press Enter: sudo tee /etc/modprobe.d/sls-eapd.conf >/dev/null <<'EOF' options snd_hda_intel power_save=0 EOF Notes: - You may be prompted for your password. When typing your password, you will not see any characters appear. This is normal. - This change can slightly increase idle power usage (battery life). Step 3: Rebuild initramfs (pick your distribution) Some distributions bundle driver options into an initramfs (an early-boot image). Rebuilding it ensures the change is picked up. Run the command that matches your distribution: Ubuntu / Debian (and derivatives) sudo update-initramfs -u Fedora (and derivatives) sudo dracut -f Arch / Manjaro sudo mkinitcpio -P Step 4: Reboot Reboot your system. The change takes effect after reboot. sudo reboot Verify (optional) After reboot, you can check the setting with: cat /sys/module/snd_hda_intel/parameters/power_save It should output 0. Undo (revert the change) 1. Remove the config file: sudo rm -f /etc/modprobe.d/sls-eapd.conf 2. Rebuild initramfs again (same command as in Step 3 for your distribution). 3. Reboot.

Last updated on Feb 12, 2026

Ubuntu: Enable Hibernate (S4) with a Swapfile (plain ext4)

This guide is written for non‑technical users. You will copy/paste a few commands into Terminal. Easy method (recommended) — Use the one‑click “Enable Hibernate” launcher If you were provided a folder called hibernate-launcher, you can enable hibernate by double‑clicking: Enable Hibernate (S4).desktop You will be asked for an administrator password. If it does not run: - Right‑click the file → Allow Launching - If you don’t see that option: right‑click → Properties → Permissions → enable “Allow executing file as program” After it completes, reboot. What this does - Creates a swapfile at /swapfile (used for hibernate). - Configures the system so it can resume from hibernation using that swapfile. - Optionally changes lid close / power button to use Hibernate (S4) instead of Sleep (S3). Before you start (important) - Plug in power if possible. - Save your work and close important apps. - Security note: hibernation writes the contents of RAM to disk. If your disk is not encrypted, sensitive data may be recoverable from the swapfile. Step 1 — Open Terminal Try one of these: - Press Ctrl + Alt + T - Or press the Windows / Super key, type Terminal, press Enter Step 2 — Create the swapfile (recommended for 64GB RAM) The swapfile needs to be large enough to store (roughly) the contents of RAM when hibernating. As a simple rule: - Pick a swapfile size that is at least your RAM size - If you are unsure, use RAM + 25% (rounded up) Examples: - 8GB RAM → 10–12GB swapfile - 16GB RAM → 20GB swapfile - 32GB RAM → 40GB swapfile - 64GB RAM → 72GB swapfile When you see a password prompt, type your password and press Enter (you won’t see the characters as you type — that’s normal). First, check how much RAM you have: free -h Look at the Mem: line (the total column). Copy/paste this whole block into Terminal: set -euo pipefail # Choose a swapfile size (change this if you have more/less RAM) # Examples: 12G (8GB RAM), 20G (16GB RAM), 40G (32GB RAM), 72G (64GB RAM) SWAPSIZE=72G # Turn off any old swapfile (if present) sudo swapoff /swap.img 2>/dev/null || true sudo swapoff /swapfile 2>/dev/null || true # Remove old /swap.img entry from /etc/fstab (if present) sudo sed -i.bak '/^[[:space:]]*\/swap\.img[[:space:]]\+none[[:space:]]\+swap[[:space:]]/d' /etc/fstab # Create /swapfile. This can take a minute or two. sudo rm -f /swapfile sudo fallocate -l "$SWAPSIZE" /swapfile # Lock down permissions (required) sudo chmod 600 /swapfile # Format as swap and enable it sudo mkswap /swapfile sudo swapon /swapfile # Make it permanent across reboots grep -qE '^[[:space:]]*/swapfile[[:space:]]+none[[:space:]]+swap[[:space:]]' /etc/fstab || \ echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab >/dev/null # Show result swapon --show free -h Expected result: - swapon --show lists /swapfile with a size close to what you chose (for example 20G). Step 3 — Configure resume-from-hibernate (the important bit) Copy/paste this whole block into Terminal: set -euo pipefail # Find the root filesystem device (where /swapfile lives) ROOTDEV=$(findmnt -no SOURCE /) ROOTUUID=$(blkid -s UUID -o value "$ROOTDEV") # Find the swapfile's physical offset (this is required for swapfile hibernate) OFFSET=$(sudo filefrag -v /swapfile | awk '$1 ~ /^[0-9]+:$/ {print $4; exit}' | cut -d. -f1) echo "Root device: $ROOTDEV" echo "Resume UUID: $ROOTUUID" echo "Offset: $OFFSET" # Tell initramfs-tools what to resume from printf "RESUME=UUID=%s\nresume_offset=%s\n" "$ROOTUUID" "$OFFSET" | sudo tee /etc/initramfs-tools/conf.d/resume >/dev/null sudo update-initramfs -u # Also add resume arguments to GRUB (more reliable across boots) sudo sed -i.bak -E 's/(^|[[:space:]])resume=[^[:space:]]+//g; s/(^|[[:space:]])resume_offset=[^[:space:]]+//g' /etc/default/grub sudo sed -i -E "s/^(GRUB_CMDLINE_LINUX_DEFAULT=\")([^\"]*)\"/\\1\\2 resume=UUID=${ROOTUUID} resume_offset=${OFFSET}\"/" /etc/default/grub sudo update-grub Note: - You might see a warning during update-initramfs like “no matching swap device is available”. With a swapfile, that warning can be harmless (it tries to validate a swap partition). The real test is the reboot + resume test below. Step 4 — Reboot Reboot the computer normally. Step 5 — Verify it’s configured correctly (after reboot) Open Terminal again and run: cat /proc/cmdline | tr ' ' '\n' | grep -E '^resume(=|_offset=)' swapon --show Expected result: - You see both resume=UUID=... and resume_offset=... - swapon --show includes /swapfile Step 6 — Test hibernate Run: sudo systemctl hibernate If everything is working, the machine should power off, then later boot and restore your session. If it did not resume (troubleshooting) After a failed resume (you got a fresh boot), run: journalctl -b -1 | grep -Ei 'hibernate|resume|swsusp|swap|image' || true dmesg | grep -Ei 'hibernate|resume|swsusp|PM:' || true Common causes: - The swapfile was recreated or moved (its resume_offset changed). Re-run Step 3. - A “defrag” / file-moving tool moved swapfile extents. Avoid defragging /swapfile. Optional — Make “sleep” actions use Hibernate (S4) by default This changes what happens when you close the lid or press the power button. Option A (graphical) — GNOME via “Dconf Editor” On many Ubuntu installs (GNOME), the normal Settings app does not always show “Hibernate” as a choice. If you want a graphical method, use Dconf Editor: 1) Open the app store (Ubuntu Software / App Center) 2) Install Dconf Editor 3) Open Dconf Editor 4) Go to: org → gnome → settings-daemon → plugins → power 5) Set these to hibernate: - lid-close-ac-action - lid-close-battery-action - power-button-action Optional (also set these to hibernate if you want “auto-sleep when inactive” to hibernate): - sleep-inactive-ac-type - sleep-inactive-battery-type Log out and log back in (or reboot) to be safe. Option B (system-wide) — systemd logind.conf This works even without GNOME and applies system-wide. Edit logind settings: sudoedit /etc/systemd/logind.conf Set (or uncomment and set) these lines: HandleLidSwitch=hibernate HandleLidSwitchExternalPower=hibernate HandleLidSwitchDocked=ignore HandlePowerKey=hibernate HandleSuspendKey=hibernate Apply changes: sudo systemctl restart systemd-logind Notes: - Desktop menus may still show “Sleep” and may still request S3 suspend. The above primarily affects lid close / keys. Notes - If /swapfile is ever recreated, re-run Step 3 (offset changes). - Do not run “defrag” tools on /swapfile.

Last updated on Feb 15, 2026

Enable “StarLabs Mic (Processed)” (echo-cancel mic)

Overview This guide helps you turn on echo cancellation by selecting the processed microphone input. First: create the “StarLabs Mic (Processed)” device (one-time) The “StarLabs Mic (Processed)” option will not appear until you create it with a PipeWire config file. Step 1: Open Terminal - Press Ctrl + Alt + T Step 2: Create the config file Copy/paste this whole block into Terminal: mkdir -p ~/.config/pipewire/pipewire.conf.d cat > ~/.config/pipewire/pipewire.conf.d/99-starlabs-mic-processing.conf <<'EOF' context.modules = [ { name = libpipewire-module-echo-cancel flags = [ ifexists nofail ] args = { # Creates a virtual source that applies WebRTC processing. # Note: select this new source in your audio settings. aec.method = webrtc aec.args = { noise_suppression = true gain_control = true high_pass_filter = true } source.props = { node.name = "starlabs_mic_processed" node.description = "StarLabs Mic (Processed)" media.class = "Audio/Source" } capture.props = { node.name = "starlabs_mic_capture" } sink.props = { node.name = "starlabs_mic_sink" node.description = "StarLabs Mic (Processed Sink)" media.class = "Audio/Sink" } playback.props = { node.name = "starlabs_mic_playback" } } } ] EOF Step 3: Restart audio services Copy/paste: systemctl --user restart pipewire pipewire-pulse wireplumber Wait 5–10 seconds. Step 2 (Recommended): Select it in GNOME Settings 1. Open Settings. 2. Click Sound. 3. Scroll to Input. 4. Select StarLabs Mic (Processed). Important: Some apps pick their own microphone Apps like Zoom, Microsoft Teams, and Google Meet may have a mic selector inside the app. - If it still sounds wrong in the app, open the app’s Audio / Microphone settings. - Select StarLabs Mic (Processed) there too. Terminal fallback: set it as default with wpctl Step A: Find the device ID Run: wpctl status Look under Sources for StarLabs Mic (Processed) and note the ID number. Step B: Set it as the default microphone Replace <ID> with the number you found: wpctl set-default <ID> Troubleshooting I don’t see “StarLabs Mic (Processed)” in Settings 1. Restart services again: systemctl --user restart pipewire pipewire-pulse wireplumber 2. Confirm the config file exists: ls -l ~/.config/pipewire/pipewire.conf.d/99-starlabs-mic-processing.conf If that file is missing, the processed mic won’t appear.

Last updated on Feb 16, 2026