Guides

Accessing the BIOS and Boot Menu

Your Star Labs laptop will use one of two types of firmware: AMI or coreboot. The steps to access system settings or the boot menu vary slightly depending on which one your device uses. 🧭 For AMI Firmware - Press F2 to open BIOS Settings This is where you can configure hardware options, boot order, and other system settings. - Press F7 to open the Boot Menu This menu lets you choose a temporary boot device (for example, a USB drive). ⚙️ For coreboot Firmware When using coreboot, the correct key to press will be shown briefly on screen during startup. Unlike AMI, coreboot does not have a full BIOS interface (in older versions)— only a boot menu. 💡 Tip: If you’re looking to change firmware settings such as boot order or performance options, you can do this using the coreboot-configurator utility within your operating system. 🔑 Function Lock Users If Function Lock is enabled on your keyboard, you’ll also need to hold the Fn key when pressing the BIOS or Boot Menu keys. For example: - To open the boot menu, press Fn + F7

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

Booting with a previous kernel

Booting with a Previous Kernel If your system fails to start after a kernel update, you can try booting with an earlier kernel version. Here’s how: 1. Boot into GRUB Turn on your laptop and repeatedly tap the Esc key as it starts up. Stop pressing it once the Star Labs logo disappears — this should bring up the GRUB menu, as shown below: 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 Then press Enter, and tap Esc again until the menu appears. If that doesn’t work, simply restart the laptop and repeat step 1. GRUB Prompt 3. Select a Previous Kernel Use the arrow keys to highlight “Advanced options for Ubuntu”, then press Enter. You’ll see a list of available kernels. When troubleshooting, it’s usually best to choose the oldest version (listed near the bottom) — just make sure to select one without “(recovery mode)” at the end. Kernel List 4. Boot the Selected Kernel Press Enter to start your laptop using the kernel you selected.

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

Connect a Bluetooth device

1. Open Bluetooth Settings Open the GNOME Launcher and select Settings. From the sidebar, navigate to Settings → Bluetooth. 2. Bluetooth Console When the Bluetooth settings window is open, your laptop will automatically begin scanning for nearby Bluetooth devices. Put your device into pairing mode according to its instruction manual. Bluetooth Settings 3. Pairing After approximately 15 seconds, your device should appear in the list of available devices. Click the device name to initiate pairing. 4. Verification Some Bluetooth devices display a verification code to confirm that you’re connecting to the correct device. If prompted, verify that the code matches and confirm the connection. 5. Audio Devices ⚠️ Note: When pairing Bluetooth audio devices, you may encounter sound quality issues. Follow the steps below to adjust the audio profile if needed. 1. Open the GNOME Launcher and select Settings. 2. Navigate to Settings → Sound. 3. Select your Bluetooth audio device under the Output section. Choose the appropriate audio profile depending on your device type: Device Type Recommended Audio Profile Audio output only High Fidelity Playback (A2DP Sink) Audio input and output (headset/microphone) Headset Head Unit (HSP/HFP) Sound Settings

Creating a bootable USB stick on Linux

Warning: This will erase all data on your USB drive. You can use a bootable Linux USB stick to: - Install or upgrade your current operating system - Test or use Linux without affecting your current operating system - Repair your current operating system This guide covers how to create a bootable USB stick whilst using Linux, but it can also be done using Microsoft Windows or Apple macOS. 1) Using Startup Disk Creator If you are using Ubuntu or one of its derivatives, you can easily create a recovery USB using a program called Startup Disk Creator. This can be installed from the Ubuntu Apps Directory or by using the command below in Terminal: sudo apt install usb-creator-gtk -y 2) Open Software Once installed, open Startup Disk Creator undefined It will automatically look for any ISO files in your Downloads folder, as well as any attached USB storage. If you do not see ISO, click Other... to manually locate your downloaded ISO file. 3) Create Disk Click Make Startup Disk to create the bootable USB stick. You will be asked to confirm the correct disk has been selected, as this will erase all data on the USB drive. The process is now complete, and your bootable USB stick is ready to use.

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

How to reset your password

Resetting Your Password If you’ve forgotten your password, don’t worry — you can easily reset it through Recovery Mode. Instructions on how to enter Recovery Mode can be found here. Once you’re in the recovery menu, follow these steps: 1. Select “Root” using the arrow keys, then press Enter. This will open a terminal window with administrator (root) access. 2. Reset your password by typing the following command: passwd {your-username} 1. If you’re not sure what your username is, you can see a list of users by typing: ls /home 1. You’ll be prompted to enter a new password, then re-enter it to confirm. 2. When done, type: reboot and press Enter to restart your machine. You should now be able to log in using your new password.

How to use function keys

Function Keys Overview Your laptop includes 12 function keys (F1–F12) that provide quick access to various system features. These keys can be used by holding down the Fn key while pressing the desired function key. Function Lock You can toggle the Function Lock by pressing the Lock key. When enabled, the F-keys will behave as if the Fn key is always held down—allowing you to use the shortcut functions directly without needing to press Fn each time. 1. Mute Toggles mute on or off for the current audio output device. 2. Volume Down Decreases the system volume. 3. Volume Up Increases the system volume. 4. Display Select Cycles through available display configurations—such as external monitors, mirrored displays, or extended screen setups. 5. Previous Media Track Skips to the previous track in your current media player. 6. Play / Pause Media Track Plays or pauses the current audio or video track. 7. Next Media Track Skips to the next track in the media queue. 8. Display Brightness Down Lowers the brightness of the built-in display. 9. Display Brightness Up Increases the brightness of the built-in display. 10. Trackpad On / Off Enables or disables the built-in trackpad. 11. Keyboard Backlight On / Off Turns the keyboard backlight on or off. You can adjust backlight timing and behavior in the BIOS settings. 12. Screenshot Captures a screenshot of all connected displays.

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.

Installing SATA Drive in a Byte

Follow steps 1-4 of the Byte Mk II - Complete Disassembly Guide to separate the chassis from the PCBA. Once the chassis is open, the internal layout will look like this: byte_6.jpg The SATA connector is the taped connector highlighted below. ByteZoomIn.jpg 1. Carefully remove the black tape holding down the SATA connector. 2. Gently pull upward on the end connected to the PCBA to disconnect it. 3. Slide the connector into the 2.5-inch drive, aligning the longer and shorter ends so it fits only one way. 4. Remove the four black screws securing the SSD mount rails to the chassis. 5. Using the four short screws in the VESA mount package, attach the mount rails to each side of the SSD. 6. Reattach the SSD mount rails to the chassis using the same four screws. 7. Reattach the SSD connector to the PCBA with the white dot facing up.

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 our guide to create a bootable USB stick: - Create a bootable USB stick This guide also covers Windows and macOS. 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 our guide to create a bootable USB stick: - Create a bootable USB stick This guide also covers Windows and macOS. 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.

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 wireless cards such as AX200, AX201, AX210 and AX211. These cards include advanced power-saving features that help reduce energy consumption, but on some networks this can reduce throughput or make the connection feel inconsistent. 💡 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 may operate in power-saving mode. The steps below show how to identify the active wireless interface, temporarily disable power saving, test performance, and make the change permanent if it helps. 1. Find Your Wireless Interface Open a Terminal window and run: WIFI_IFACE="$(iw dev | awk '$1=="Interface"{iface=$2} $1=="type" && $2=="managed"{print iface; exit}')" echo "$WIFI_IFACE" This automatically selects the first active managed Wi-Fi interface. On many models this will be something like wlp0s20f3, but the exact name depends on the model and wireless card. To confirm the current connection and link speed, run: iw dev "$WIFI_IFACE" link Look for the signal, rx bitrate and tx bitrate lines. 2. Temporarily Disable Power Saving Run: sudo iw dev "$WIFI_IFACE" set power_save off iw dev "$WIFI_IFACE" get power_save Then test your connection speed again to see if performance improves. This change is temporary and will usually be lost after a reboot or reconnect. 3. Installing Useful Network Tools To better monitor your wireless connection, install wavemon — a simple, live Wi-Fi monitoring tool. 📡 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 4. 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 iw dev "$WIFI_IFACE" link These tools will help you detect weak signals, interference, or unstable links. 5. Make the Fix Permanent If disabling power saving improves performance, you can make the change permanent with NetworkManager: sudo mkdir -p /etc/NetworkManager/conf.d printf '[connection] wifi.powersave = 2 ' | sudo tee /etc/NetworkManager/conf.d/99-disable-wifi-powersave.conf sudo systemctl restart NetworkManager Then reconnect to Wi-Fi and check the setting: iw dev "$WIFI_IFACE" get power_save To revert this change: sudo rm /etc/NetworkManager/conf.d/99-disable-wifi-powersave.conf sudo systemctl restart NetworkManager 6. Advanced Intel Driver Parameters (Use with Caution) ⚠️ Warning: The following settings are for advanced users only. Incorrect changes may cause reduced performance or compatibility issues. For Intel wireless cards using the iwlwifi driver, you can create /etc/modprobe.d/starlabs.conf with additional driver options. For example: echo "options iwlwifi 11n_disable=8 power_save=off" | sudo tee /etc/modprobe.d/starlabs.conf sudo update-initramfs -u Then reboot your laptop. To revert to default settings: sudo rm /etc/modprobe.d/starlabs.conf sudo update-initramfs -u Then reboot again. 7. 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, but can affect Bluetooth devices. | | 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 Intel wireless driver power saving. | | options iwlwifi d0i3_disable=1 | Disables low-power idle state. | | options iwlwifi uapsd_disable=1 | Disables U-APSD; may fix low throughput on some access points. | ✅ Summary 1. Identify your active wireless interface with iw dev. 2. Test disabling power saving with sudo iw dev "$WIFI_IFACE" set power_save off. 3. Use wavemon, nmcli and iw dev "$WIFI_IFACE" link to monitor signal and link speed. 4. If speeds improve, make the power-saving change permanent with NetworkManager. 5. Only use driver parameters if the basic power-saving change is not enough. You should now experience faster and more consistent wireless performance.

Managing user accounts

You can create, edit, and remove user accounts either through the terminal or graphically using the system settings. This guide walks you through the graphical method, which is simple and beginner-friendly. 1. Open User Settings 1. Open the GNOME Launcher and select Settings. 2. In the left-hand menu, navigate to Details → Users. 3. To make any changes, click Unlock in the top-right corner of the window. 4. Enter your password when prompted. Once unlocked, you’ll be able to add, modify, or remove users. 2. Add a New User 1. Click Add User in the top-right corner. 2. A window will appear allowing you to set details for the new account, such as: Account Type (Standard or Administrator) Full Name Username Password options Add User Window 3. When you’ve entered the necessary information, click Add to create the account. 3. Modify an Existing User You can also edit existing user accounts from the same window. 1. Select the user you’d like to edit from the list at the top of the window. 2. Update details such as the account type, password, or automatic login preferences. Modify User Settings Your changes will be applied immediately.

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.

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.

What do the LEDs mean?

Understanding the LED Indicators on Your Device This guide explains what the power and charging LED lights mean, helping you quickly identify your device’s status or power state. 🔌 Power LED LED State Meaning Off The device is powered off (Soft Off state). Pulsing The device is in Sleep Mode (S3 Suspend) — low-power standby. Flickering The device is transitioning between power states (e.g., waking or sleeping). Solid On The device is fully powered on (S0) and operating normally. 🔋 Charging LEDs LED Colour / Pattern Meaning Red Charging normally. Blue The battery is fully charged — charging has reached the upper limit. Purple Overcharge protection is active. Red / Blue Alternating No battery detected. Red Flickering Low battery — connect to power soon. Red / Purple / Blue Alternating The battery is calibrating. ⚙️ Special LED Combination LED Pattern Meaning Power LED + Red / Blue Flicker The device is entering G3 (Mechanical Off) — all power is disconnected.

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: 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: 📧 support@starlabs.systems

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.

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. 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 1. 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.

Enable processed microphone (Linux)

Overview This guide creates a processed microphone input with WebRTC noise suppression, gain control and high-pass filtering. The created input is named automatically: - Detachable Microphone on StarFighter systems. - Internal Microphone on other Star Labs systems. Before you start Set your audio input to the built-in microphone before running the command below. The command sets the real microphone path to 30%, then creates the processed microphone on top of it. After that, control input level using the new processed microphone. Step 1: Open Terminal - Press Ctrl + Alt + T Step 2: Create the processed microphone Copy/paste this whole block into Terminal: TARGET_SOURCE="$(wpctl inspect @DEFAULT_AUDIO_SOURCE@ | awk -F'= ' '/node.name =/{gsub(/"/,"",$2); print $2; exit}')" RAW_SKU="$(cat /sys/class/dmi/id/product_sku 2>/dev/null || true)" case "$RAW_SKU" in F1|F1-A|F2) MIC_NAME="Detachable Microphone" ;; *) MIC_NAME="Internal Microphone" ;; esac if [ -z "$TARGET_SOURCE" ]; then echo "Could not find the current audio input. Please select the built-in microphone and try again." exit 1 fi # Keep the real microphone input low enough to avoid clipping/noise. wpctl set-volume @DEFAULT_AUDIO_SOURCE@ 30% 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 = { aec.method = webrtc aec.args = { noise_suppression = true gain_control = true high_pass_filter = true } source.props = { node.name = "starlabs_mic_processed" node.description = "$MIC_NAME" media.class = "Audio/Source" } capture.props = { node.name = "starlabs_mic_capture" target.object = "$TARGET_SOURCE" } sink.props = { node.name = "starlabs_mic_sink" node.description = "$MIC_NAME 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. If this command reports that one of the services does not exist, reboot instead: sudo reboot Step 4: Select the processed microphone Open Settings → Sound → Input, then select: - Detachable Microphone on StarFighter systems. - Internal Microphone on other systems. 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 and select the processed microphone there too. Terminal fallback: set it as default with wpctl Step A: Find the device ID Run: wpctl status Look under Sources for Detachable Microphone or Internal Microphone, then 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 the processed microphone 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 microphone won’t appear. My microphone is still too loud or distorted Make sure the original microphone input is set to 30%: wpctl set-volume @DEFAULT_AUDIO_SOURCE@ 30% Then keep using the processed microphone as the selected input.

Enable Internal Speakers EQ (Linux)

Overview This guide creates an Internal Speakers PipeWire output with the Star Labs EQ profile applied. It is for Linux distributions that use PipeWire for audio. What you will do You will: - Set the real built-in speaker path to 100% so the EQ has the full range to work with. - Create a user-level PipeWire configuration file. - Restart the PipeWire audio services. - Select Internal Speakers as your audio output. Before you start Set your audio output to the built-in speakers before running the command below. This is important because the EQ connects to whichever output is currently selected. If Bluetooth, HDMI, USB audio, or another external output is selected, the EQ may target that instead of the internal speakers. 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 Internal Speakers profile Copy and paste this command into the Terminal, then press Enter: TARGET_SINK="$(wpctl inspect @DEFAULT_AUDIO_SINK@ | awk -F'= ' '/node.name =/{gsub(/"/,"",$2); print $2; exit}')" if [ -z "$TARGET_SINK" ]; then echo "Could not find the current audio output. Please select the built-in speakers and try again." exit 1 fi # Give the EQ the full real-speaker range to work with. wpctl set-volume @DEFAULT_AUDIO_SINK@ 100% mkdir -p ~/.config/pipewire/pipewire.conf.d cat > ~/.config/pipewire/pipewire.conf.d/51-star-labs-eq.conf <<EOF context.modules = [ { name = libpipewire-module-filter-chain args = { node.description = "Internal Speakers" media.name = "Internal Speakers" filter.graph = { nodes = [ { type = builtin name = eq_band_1 label = bq_lowshelf control = { "Freq" = 105.0 "Q" = 0.80 "Gain" = 3.0 } } { type = builtin name = eq_band_2 label = bq_lowshelf control = { "Freq" = 190.0 "Q" = 0.75 "Gain" = 7.0 } } { type = builtin name = eq_band_3 label = bq_peaking control = { "Freq" = 280.0 "Q" = 1.00 "Gain" = -0.5 } } { type = builtin name = eq_band_4 label = bq_peaking control = { "Freq" = 2800.0 "Q" = 1.10 "Gain" = 1.5 } } { type = builtin name = eq_band_5 label = bq_highshelf control = { "Freq" = 8500.0 "Q" = 0.70 "Gain" = 0.5 } } ] links = [ { output = "eq_band_1:Out" input = "eq_band_2:In" } { output = "eq_band_2:Out" input = "eq_band_3:In" } { output = "eq_band_3:Out" input = "eq_band_4:In" } { output = "eq_band_4:Out" input = "eq_band_5:In" } ] } audio.channels = 2 audio.position = [ FL FR ] capture.props = { node.name = "effect_input.star-labs-eq" node.description = "Internal Speakers" media.class = "Audio/Sink" priority.session = 1600 } playback.props = { node.name = "effect_output.star-labs-eq" target.object = "$TARGET_SINK" node.passive = true } } } ] EOF Notes: - This only changes your user account, not the whole system. - You should not need to enter your password. - The real speaker path is set to 100%; control listening volume using the new Internal Speakers output. Step 3: Restart PipeWire Restart the audio services: systemctl --user restart pipewire pipewire-pulse wireplumber Audio may briefly stop while the services restart. If this command reports that one of the services does not exist, reboot instead: sudo reboot Step 4: Select Internal Speakers Open your sound settings and select Internal Speakers as the output device. If you prefer to use the command line, run: wpctl status Find effect_input.star-labs-eq under Filters, then set it as default with: wpctl set-default ID Replace ID with the number shown next to effect_input.star-labs-eq. Verify (optional) You can check that the EQ is loaded with: wpctl status You should see effect_input.star-labs-eq under Filters. Undo (revert the change) 1. Remove the config file: rm -f ~/.config/pipewire/pipewire.conf.d/51-star-labs-eq.conf 2. Restart PipeWire again: systemctl --user restart pipewire pipewire-pulse wireplumber 3. Select your normal built-in speaker output again in sound settings.

StarBook Horizon - Backplate Installation Guide

Refitting the Horizon Backplate To fit the backplate correctly, it must be clipped into place in the correct order before the screws are tightened. If the backplate is not fitted properly, the machine may wobble, and the touchpad may not operate as it should. Follow these steps: 1. Start at the front edge, closest to the touchpad. 2. Press firmly along the entire front edge until it clips evenly into the touchpad bar. 3. Check that the touchpad bar is fully clipped in across its entire length. 4. Next, clip in the left and right sides. 5. Finish at the hinge side (the back of the machine). 6. Check that the backplate is sitting flat all the way around with no gaps. 7. Before fitting the screws, check the touchpad by pressing on both the left and right sides. It should click and move freely on both sides. 8. If the touchpad clicks correctly, refit the screws. Important: Do not use the screws to pull the backplate into position. If any edge is sitting proud, the touchpad bar is not fully clipped in, or the touchpad does not click properly on both sides, remove the backplate and repeat the fitting sequence. Forcing the backplate into place with the screws can cause the machine to wobble or prevent the touchpad from operating correctly. 1. Engage Touchpad clips: 2. 3. 4. 5. 6. 7. 8. 9. 10. All done, refit the screws. GUIDE: Green = Long screws, Purple = Short screws

How to encrypt your drive - Privacy Academy Zorin OS

This guide shows how to reinstall Zorin OS with drive encryption enabled on a Privacy Academy system. Watch the video guide Important This process erases the current operating system and data on the drive. Make sure the disk decryption password is written down safely; if it is forgotten, the encrypted data cannot be recovered. Start the installer 1. Connect the Zorin OS recovery USB drive. 2. Turn the computer on and press F2 or Down Arrow to open the coreboot boot menu. 3. Select the USB drive and start the Zorin OS installer. Enable encryption 1. When asked how to install Zorin OS, select Erase disk and install Zorin OS. 2. Before clicking Install Now, select Additional features... or Advanced features.... 3. Select Use LVM with the new Zorin OS installation. 4. Select Encrypt the new Zorin OS installation for security. 5. Click OK, then Install Now. 6. Enter a disk decryption password in Choose a security key, then repeat it in the confirmation field. 7. Continue through the remaining installer steps normally.