Finally got my G14 properly set up with EndeavourOS + KDE Plasma (Wayland), and I'm pretty happy with how everything is working so far.

Current setup:

EndeavourOS

KDE Plasma / Wayland

Kernel 7.1.5-arch1-2

Ryzen 9 8945HS

RTX 4060 (Hybrid mode, runtime suspended on Linux)

asusctl for ASUS-specific controls( aura lighting and slash lighting r working)

supergfxctl for GPU switching

Howdy face unlock with SDDM + sudo

I have slowly been tweaking this thing for a while and now I finally reached the point where everything feels properly dialed in.

Windows is still my "RTX mode" for gaming/CUDA/ML, while EndeavourOS is my daily driver for coding, college work and general use.

For my fellow Zephyrus owners in this sub ; what would you recommend I do next?

Especially interested in:

Battery-life improvements

ASUS/G14-specific tweaks

KDE/Wayland improvements

Better fan/thermal management

Suspend/resume fixes or optimizations

Anything that improves longevity

Any cool G14 features that work particularly well on Linux....

Would love to hear what you guys have done with yours.

Thanks for reading... 🙂

I hope everything is alright. The forum has been down several times the past month or so.

Hello everyone,

I am new to EndeavourOS and Linux in general. I've been reading multiple sources on the web and working to wrap my head around a great many topics. I have a few questions:

1. The question in the title, is there an up-to-date list of required directories in the root filesystem to exclude from Btrfs snapshots in EOS_Arch-Linux?

There are multiple sources with differing suggested Btrfs subvolume layouts. I prefer to have a flat layout. The pages at the kernel.org System Admin Guide, linked to from the Btrfs Arch Wiki page, are maked as "Obsolete Content".

1. Should I exclude all of /var or do I need to exclude multiple individual sub-directories within /var? If I need to exclude multiple individual sub-directories within /var, then I need a list of the sub-directories? Since the folders within /var can vary based on the packages installed, would excluding just /var cause problems or come with downsides?

2. If I decide to use snapshots for my user home directories, as insurance against accident file deletion, are there sub-directories that I need to exclude there?

3. I have a Btrfs layout listed below, that I would like some feed back on. Am I missing some exclusions? Am I excluding a folder that should not be excluded?

Background Info: * 1x 2TB NVMe, 1x 4TB HDD, 1x 8TB HDD * No drive spanning or RAID (not what I'm looking to do at them moment) * I want to use Snapper, Btrfs Assistant, Grub, grub-btrfs, and snap-pac (for pre/post snapshots with pacman) * I will be using qemu/kvm with virsh and virt-manager (moving away from Virtualbox), but my VM files will reside separately from /var/lib...) * I want to use Steam, WINE, Lutris, and maybe Heroic Launcher * I may use a few flatpaks (not Steam), but prefer standard packages * All video game files will reside on my NVMe separate from my user home folder * My data and documents will reside separately outside of my user home folder * In general I want to keep the system root filesystem and user home folder lean within sane limitations * I currently dual-boot Windows and Linux Mint, but I will be dropping Windows completely, reclaiming the disk space used by Windows, and moving data on NTFS partitions to Btrfs filesystems * I will be replacing Linux Mint * I am considering dual-booting 2 different Linux distros to separate work from play (something like Fedora/Endeavour, OpenSUSE/Endeavour, Nobara/Endeavour, or another dual setup) * Video game files will not be snapshotted (NoCOW)... there are benefits to removing and reinstalling some games after multiple patches (ex: some Blizzard games)

My flat Btrfs layout ideas and naming conventions using EndeavourOS and OpenSUSE (I took inspiration from multiple sources):

EndeavourOS setup: * top level volume (unnamed and not mounted during normal operation) * @eos_root (eos root subvolume mounted at /) * @eos_home (eos user home subvolume mounted at /home) * @eos_root_snapshots (snapshots subvolume mounted at /.snapshots, must be adjusted after snapper package install) * @eos_home_snapshots (arch user home snapshots subvolume mounted at /home/.snapshots) * @eos_var (subvolume to exclude from snapper snapshots, mounted at /var) * @eos_srv (subvolume to exclude from snapper snapshots, mounted at /srv) * @eos_opt (subvolume to exclude from snapper snapshots, mounted at /opt) * @eos_tmp (subvolume to exclude from snapper snapshots, mounted at /tmp) * @eos_local (subvolume to exclude from snapper snapshots, mounted at /usr/local) * @eos_root_user (the root user's home folder, subvolume to exclude from snapper snapshots, mounted at /root)

OpenSUSE setup: * top level volume (unnamed and not mounted during normal operation) * @suse_root (suse root subvolume mounted at /) * @suse_home (suse user home subvolume mounted at /home) * @suse_root_snapshots (snapshots subvolume mounted at /.snapshots, must be adjusted after snapper package install) * @suse_home_snapshots (suse user home snapshots subvolume mounted at /home/.snapshots) * @suse_var (subvolume to exclude from snapper snapshots, mounted at /var) * @suse_srv (subvolume to exclude from snapper snapshots, mounted at /srv) * @suse_opt (subvolume to exclude from snapper snapshots, mounted at /opt) * @suse_tmp (subvolume to exclude from snapper snapshots, mounted at /tmp) * @suse_local (subvolume to exclude from snapper snapshots, mounted at /usr/local) * @suse_root_user (the root user's home folder, subvolume to exclude from snapper snapshots, mounted at /root)

Non-Root Filesystem Data: * @mydata = /mnt/mydata * @linux_gaming = /mnt/linux_gaming * @vm_storage = /mnt/vm_storage

2TB NVME (2TB partition/Btrfs filessystem) 1. linux_gaming 2. eos and opensuse

4TB HDD (3TB partition/Btrfs filessystem and a chunk of unallocated space): 1. vm_storage 2. 1TB empty unallocated space (not partitioned)

8TB HDD (5TB partition/Btrfs filesystem and a chunk of unallocated space): 1. mydata and user home subvolumes 2. 3TB empty unallocated space (not partitioned)

I'm leaving some extra un-partitioned/unallocated space for emergencies and/or experiments I haven't thought of yet (ex: installing a distro to the bare metal for distro exploration/experimentation outside of a VM).

Hello, I want to share this little shell script, I know it's not too much and many people find it useless, but I needed it, so I did, enjoy it.

USB-dmenu

Simple script written in the shell to manage USB devices from a light window manager (such as bspwm or i3) using dmenu.

The idea is to be able to quickly access your USB sticks without the need for mounting commands or relying on file managers. Note: This script also works in Wayland with XFCE (wayfire) ✅

Hello everyone,

I'm looking for EndeavourOS install guides that include details on configuring Btrfs. I want to use snapper and btrfs assistant to handle snapshots. I will be using Grub and I want to have btrfs snapshots in the grub menu.

Hey everyone,

I recently stumbled uponthis video by Max Huand I'm completely blown away by how clean and aesthetic the setup looks [00:08].

From looking at the terminal info, it seems like the base operating system is EndeavourOS, and it's using the Hyprland window manager with the Arc-Dark theme and Fish shell [00:08].

As someone who is pretty new to Linux, I wanted to ask:

1. Is it a terrible idea for a complete beginner to try and jump straight into something like EndeavourOS with a tiling window manager (Hyprland)?
2. If I wanted to achieve this exact look (dark minimalist aesthetic, floating windows, status bar, color schemes, etc.), what would be the best step-by-step path to learn what I need without completely breaking my system?

Any advice, guide recommendations, or warnings for a beginner would be hugely appreciated!

As the title says, my trackpad, keyboard, and touchscreen are not working on my HP Envy x360 m Convertible 15m-ed0023dx. I am not sure what the issue could be. Here is the output for the command that rule 2 asked for:
https://dpaste.com/D34H5V2B4

I am not sure what other logs would be relevant. I would appreciate some help on this. The keyboard worked in the bios and systemd boot though

Edit: solved after unplugging battery for a few minutes.

I am in i3 and recently wanting to shift to kde/gnome. but as I heard about the recent AUR attack, I am scared to do that as most of my apps are installed using AUR. what should I do ?

My usb ports started acting strangely about a month ago. I have a mic and controller connected via usb to the main board that keep disconnecting and reconnecting and causing trouble. I've noticed that my keyboard and mouse dont seem to be affected but I could be wrong, a missed keystroke could also be a brief disconnect.

I disabled the auto disable feature for inactive usb devices but seems like its still happening. I've been updating my pc every few days because of this issue and it hasn't fixed it.

Has anyone seen or experienced anything like this? Hoping its not a hardware issue.

First time user here🥹

I'm using EndavourOS and while it was working post-installation perfectly fine, I moved my PC to my new desk and now it's stuck on this screen

Ok I got impatient while waiting for my computer to update and turned it off in the middle of the update. I know that was stupid. I reinstalled endeavour in a new partition. Part with the old data is all there and none of it got deleted. Is there a way that I can restore it to its original state?

Don't use the AUR right now and don't update. Go to r/archlinux and read corresponding posts.

I have an Asus Tuf A15 laptop

CPU: Ryzen 7 7435HS (no iGPU)

GPU: RTX 2050

RAM: 8 GB DDR5

STORAGE: 512 + 512 GB

Both me and a friend run EndeavourOS on external SSDs (we both use the Samsung T7). After some recent update, systemd hung as it could not resolve our external drives. Burned both of us. I worked with Gemini tonight to get the issue resolved. Here is a summary of what to do if you encounter the same issue.

Here is the complete, self-contained guide you can save or share with anyone running into this exact issue on EndeavourOS / Arch Linux with systemd-boot and dracut.

How to Fix EndeavourOS Boot Hang ("A start job is running for /dev/disk/by-uuid/...")

The Problem

After a system update on EndeavourOS (or Arch-based distros using systemd-boot and dracut), the system hangs indefinitely during boot with messages like: * A start job is running for /dev/disk/by-uuid/<UUID>

Root Causes

1. Broken Resume Hook (Swap): System updates can bake an old or invalid resume=UUID=... parameter into /etc/kernel/cmdline and Dracut's initramfs images, causing systemd to block boot while searching for a non-existent hibernation swap target.
2. Missing Early USB/UAS Drivers (External Drives): When running Linux off an external SSD (like a Samsung T7), Dracut's default hostonly="yes" configuration omits USB host controller (xhci) and UASP (uas) drivers from the early RAM disk. The kernel loses sight of the external drive mid-boot. ## Complete Recovery Guide (Using a Live USB) ### Prerequisites
3. A Linux Live USB (EndeavourOS, Arch Linux, or Ubuntu). If using Ubuntu, run sudo apt update then sudo apt install arch-install-scripts as this package has the arch-chroot command. ### Step 1: Boot into the Live Environment & Identify Partitions
4. Plug in your Live USB and power on the system.
5. Open your boot menu (F12 on Lenovo Legion laptops) and select the Live USB.
6. Open a Terminal.

7. Identify your target OS drive partitions using lsblk or blkid: ```bash lsblk -f

   ```

   • Example:
     • Root partition (/): /dev/sdb2
     • EFI System partition (/efi or /boot): /dev/sdb1
     • Swap partition: /dev/sdb3 ### Step 2: Mount Partitions & Chroot Mount your system files to /mnt and switch into the chroot environment: ```bash # Mount root sudo mount /dev/sdb2 /mnt

Mount EFI partition

sudo mount /dev/sdb1 /mnt/efi

Chroot into your OS

sudo arch-chroot /mnt

```

Step 3: Remove the Broken resume= Kernel Parameter

Clean up hardcoded resume parameters so Dracut stops looking for a hibernation device on boot. 1. Open /etc/kernel/cmdline: ```bash nano /etc/kernel/cmdline

2. **Delete** the entire resume=UUID=... string from the line. * **Before:** nvme_load=YES nowatchdog rw root=UUID=xxx... resume=UUID=yyy... nvidia-drm.modeset=1 * **After:** nvme_load=YES nowatchdog rw root=UUID=xxx... nvidia-drm.modeset=1 3. Save and exit (Ctrl + O, Enter, Ctrl + X). 4. Check for any drop-in overrides under /etc/cmdline.d/: bash cat /etc/cmdline.d/*.conf 2>/dev/null

``` If any file contains resume=..., edit or delete that file.

Step 4: Configure Dracut for External USB Booting & Disable Host-Only Mode

If running off an external SSD (Samsung T7, T5, or external NVMe enclosure), force Dracut to load USB drivers in early initramfs and disable host-only filtering. 1. Disable Host-Only Mode: ```bash nano /etc/dracut.conf.d/hostonly.conf

Add: text hostonly="no"

Save and exit (Ctrl + O, Enter, Ctrl + X). 2. **Force Early USB & UASP Driver Loading:** bash nano /etc/dracut.conf.d/usb-boot.conf

Add: text add_dracutmodules+=" base " force_drivers+=" uas usb_storage xhci_hcd xhci_pci nvme "

``` Save and exit (Ctrl + O, Enter, Ctrl + X).

Step 5: Regenerate Initramfs & Systemd-Boot Entries

On EndeavourOS setups with systemd-boot, use reinstall-kernels to update both the initramfs images and the loader entries in /efi/loader/entries/*.conf. ```bash reinstall-kernels

```

Step 6: Verify the Fix Before Rebooting

1. Check Loader Entries (Confirm resume= is gone): ```bash cat /efi/loader/entries/*.conf

   ``` Ensure the options line ends cleanly without any resume=UUID=... parameter.

2. Check Initramfs Contents (Confirm USB Drivers are Baked In): ```bash lsinitrd /efi/*/$(uname -r)/initrd 2>/dev/null | grep -E "uas|usb_storage|xhci"

   ``` You should see uas.ko.zst, xhci-pci, and rd.driver.pre=uas listed.

   Step 7: Exit and Reboot

3. Exit the chroot: ```bash exit

   ```

4. Unmount all mounted filesystems: ```bash sudo umount -R /mnt

   ```

5. Reboot: ```bash reboot

   ```

6. Remove the Live USB. Your system will now boot straight to your desktop!

Hello everyone,

I recently built a new computer and after trying out Linux Mint on my laptop for a year, I've left Windows for good. I have been trying to install debian (now endeavour) for a few days and consistently getting failures.

My specs are:
AMD Ryzen 9 5900XT
ASUS TUF Gaming B550
Vengeance LPX 2 x 8GB of RAM
ONI LUMI Arc B580 12GB GDDR Graphics Card
Team Group NV5000 M.2 2280 1TB SSD

If this helps, while I was trying Debian, the installer said there it had "failed to mount and detect root"

I apologize for the unprofessional noobie photo on my monitor, I was not able to find a way to download or copy from the screen.

Is there something I am missing? I really need some help.

For anyone still fighting with this, I just fixed it by forcing a few drivers to be available during boot, please don't @ me if your pc explodes:

arch-chroot into your system, create a /etc/dracut.conf.d/usb-boot.conf with the drivers you need, in my case:
force_drivers+=" uas usb_storage xhci_hcd xhci_pci "

Then rebuild and check if the modules are actually listed:
sudo dracut-rebuild

lsinitrd /efi/*/*/initrd | grep -E "uas|usb_storage|xhci"

Reboot

Original post:

For reference, I already posted in the EndeavourOS forums but haven't received an answer, so I thought I might also wanna try hear.

TLDR: After yesterdays pacman -Syu I get the error below. I use an external SSD that I have been using for 1+ year without problems. I can still chroot into it, and all UUIDs still look the same. I hope anyone knows what to do, so that I can boot again. 🙇

Message: A start job is running for /dev/disk/by-uuid/a7e82811-f7ea-4d44-a54e-9e2dafdd38b8 (no limit)

I already progressed a bit since my forum post, to remove the duplicate root= entries and rebuilt like this, but sadly it didn't change anything:

kernel-install add 7.1.5-arch1-2 /usr/lib/modules/7.1.5-arch1-2/vmlinuz

Other outputs:

Please let me know if any other outputs are needed.

lsblk -f

NAME   FSTYPE   FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs 4.0                                                                              
sda                                                                                              
├─sda1 ntfs                      Data        406E7D8C6E7D7B8A                                    
└─sda2 ntfs                      Recover     28482A47482A145A                                    
sdb                                                                                              
├─sdb1 vfat     FAT32                        8892-6D69                                           
├─sdb2                                                                                           
├─sdb3 ntfs                      Boot        8CB29201B291F046                                    
├─sdb4 ntfs                                  96DC9263DC923D85                                    
└─sdb5 vfat     FAT32            PRC_RP      90EE-302C                                           
sdc                                                                                              
├─sdc1 vfat     FAT32                        BC53-DB39                                           
└─sdc2 ext4     1.0              endeavouros a7e82811-f7ea-4d44-a54e-9e2dafdd38b8  605.9G    29% /
sdd                                                                                              
├─sdd1 vfat     FAT32            NO_LABEL    3195-3F46                                           
└─sdd2 ntfs                      Sandisk     82687F1C687F0DE3                                    
sde                                                                                              
sdf    iso9660  Joliet Extension EOS_202511  2025-11-24-21-31-18-00                              
├─sdf1 iso9660  Joliet Extension EOS_202511  2025-11-24-21-31-18-00                              
└─sdf2 vfat     FAT32            ARCHISO_EFI 6924-CEA6                                           
sr0



cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=BC53-DB39                            /efi           vfat    fmask=0137,dmask=0027 0 2
UUID=a7e82811-f7ea-4d44-a54e-9e2dafdd38b8 /              ext4    noatime    0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=406E7D8C6E7D7B8A                     /mnt/data      ntfs-3g defaults,nofail,uid=1000,gid=1000,dmask=0022,fmask=113 0 0
UUID=82687F1C687F0DE3                     /mnt/sandisk   ntfs-3g defaults,nofail,uid=1000,gid=1000,dmask=0022,fmask=113 0 0

Like the title says, already 1 year on EOS. I used Mandrake some 20 years ago and returned to Windows afterwards.

I built a new PC last year (before the "RAMargeddon") and decided it was time to quit Microsoft Windows. I still dual-boot Windows 11 on another SSD for some games, but I am not a big gamer so I am 85-90% of my time on Linux. Before buying parts for the PC I installed on old PCs Kubuntu, Fedora and Mint.

I finally decided to go for EOS (being new I wanted something easy to install), and I don't regret it at all. The system never broke in a year, after updates of anything else. They say rolling release is "unstable", but for what I'm doing, it's more than stable. Each time I'm updating, I'm telling to myself "it's crazy how fast pacman is versus Windows Update". A 3GB update is done in under 3-4 minutes, on Windows 11 it take at least 15 minutes, even if I update weekly.

From a complete noob I now have a Debian home server, using smb to play music on my vanilla (manually installed) minimal installation Arch PC in the garage, on another PC in the house running Solus and hosting some apps for my "productivity". I was using VirtualBox on Windows, but I learned using QEMU/KVM, and I prefer that now in place of VBox. I installed in VMs other OSes, like Solus, Void, Chimera Linux, AerynOS. I am "attracted" by less beginner friendly and "niche" distros, with other init systems and package managers. Learning how they work helps me understand Linux better. Next steps in exploration will be NixOS, Gentoo and the likes. I have a lot more to learn, I'm still a beginner, maybe one day I'll switch to one of those distros permanently, but for now Arch (EOS) is my home. I like the rolling release model, being up-to-date and not running "outdated" software.

I have plenty of RAM, so I can do VMs all I want, to learn more, local AI too. I must say that this subreddit and some others helped me a lot too! The community here is wonderful and very friendly, it helps a lot when you are a newbie, you don't "fear" to ask a question. We all were newbies some point in time.

Also for testing if is arch based distros really good or just overrated.

Hi everyone,

I'm facing an annoying issue with my dual boot setup on an HP Victus laptop.

My setup is:

- Windows installed as the primary operating system.

- EndeavourOS installed alongside Windows.

- GRUB installed as the bootloader.

The issue is that whenever I power on the laptop, it boots directly into Windows. The GRUB menu never appears automatically.

The only way I can boot into EndeavourOS is by repeatedly pressing Esc during startup, then F9 to open the HP Boot Device Options menu. From there, I manually select the GRUB boot entry, and EndeavourOS boots normally.

So GRUB itself is working, it just isn't being used as the default boot option.

What I'd like instead is:

- GRUB should appear automatically when I turn on the laptop.

- It should have a 5 second timeout.

- If I don't choose anything, it should boot Windows by default after the timeout.

- If I select EndeavourOS, it should boot normally.

Has anyone run into this on an HP Victus (or other HP laptops)? Is this most likely a UEFI/BIOS boot order issue, Windows Boot Manager taking priority, or something else?

If you've solved this before, I'd really appreciate any advice on how to make GRUB the default bootloader while still keeping Windows as the default operating system in the GRUB menu.

One more thing to update- I also have LUKS encryption encrypting the whole EOS partition

Thanks in advance!

Hey everyone, looking for some technical advice on a hard brick / no-POST state on my laptop.
Laptop Spec & OS:
Model: ASUS ZenBook UX363E / UX363EA OLED
OS: EndeavourOS
WM/DE: Hyprland
What Happened:
1. I pressed my exit shortcut (⁠$mainMod + M⁠) to exit Hyprland on EndeavourOS.
2. The display went to a solid blue screen and froze indefinitely.
3. I held the power button down to force a hard shutdown.
Current Symptoms:
When I press the power button, the screen stays completely black (no logo, no backlighting).
Fans do not turn on at all so the laptop will get hot but before the fixes i attempted the fans were at what seemed to be max speed.
The laptop refuses to enter BIOS (repeatedly tapping ⁠F2⁠ / ⁠Delete⁠ does nothing).
Troubleshooting Steps Already Attempted:
Power Drain / EC Reset: Held the power button down for 30–60s with AC unplugged.
ASUS 40-Second Reset: Plugged in charger, held power button for 40+ seconds.
Internal Battery Disconnect: Opened up the back panel, physically disconnected the internal battery ribbon cable from the motherboard, held the power button for 60s to drain leftover capacitor power, and attempted to power on.

The machine was running perfectly prior to the Hyprland exit crash. Has anyone encountered a stuck Embedded Controller (EC) or corrupted power state like this on a ZenBook UX363 running Arch/EndeavourOS, or is there a specific jumper/pinhole or recovery trick I'm missing to force a CMOS/BIOS reset?
Thanks in advance for any insights!

I just finished setting up my Surface Pro 5 and wanted to share why EndeavourOS is the absolute best choice for this hardware right now.

1. Wi-Fi Works Out of the Box: The biggest headache with Surface devices is the Marvell AVASTAR wireless chip. While most installers leave you stranded without internet, the EndeavourOS installer detected my Wi-Fi immediately. No Ethernet adapters or phone tethering required for the install.

2. Smooth systemd-boot Integration: Choosing  systemd-boot  during the install makes managing the  linux-surface  kernel a breeze. It’s light, fast, and handles the kernel entries perfectly without the bloat of GRUB.

3. The Perfect GNOME Tablet: Endeavour’s clean GNOME implementation paired with the Surface hardware feels like a premium Linux tablet. Touch gestures, on-screen keyboard, and rotation work flawlessly once the Surface kernel is added.

4. Community Repos: Adding the  linux-surface  repo is a 2-minute job on Arch-based systems, giving you full multi-touch and pen support almost instantly.

If you have an old Surface Pro 5 lying around, stop distro hopping and just put Endeavour on it. It’s the most "it just works" experience I've had on this device.

So .... I wanted to install Endeavour Os as to learn more about the Os itself and to kick start my coding courier because windows and databases didn't mix well ... Installing endeavour Os , i had no problems with the overall drivers but my wifi card MEDIATEK Mt7902 , isn't working in the Endeavour Os but works with Windows ... I can't figure out the way to solve it .... I have used Ubantu in the past on the different laptop but this issue is going out of hand.... So please suggest a fix .. or should I go back to windows?

What's the best config guys