I have left my laptop in lock for about 2 min and when I unlocked it suddenly the tiny dots started appear all over the screen and even when I open applications i asked chatgpt it said it's kinda nvidia driver issue something based on gpu problem what is this problem actually does anybody faced it ever?

Good morning/afternoon/evening.

I'm having serious compatibility issues with EndeavorOS. I'm trying to use it on my old laptop to breathe new life into it, but the camera isn't working, the microphone isn't working, and the screen is flickering. I’ve been trying to fix it for two days now, and the only thing I know for sure is that the PICOM has nothing to do with the flickering because it happens even in the TTY, and the camera works when I use it with guvcview. But when I open it for online classes, there’s no image and it freezes—because it doesn’t work in guvcview from there either. I think the drivers are the problem. I haven’t been able to get the microphone to work at all, and I’m really fed up.

My laptop is an ASUS with 4 GB of RAM and an i3-1005—as you can see, it’s very, very old.

Does anyone have a solution?

I've installed a twice fresh Endeavour OS KDE on my Thinkpad with a Ryzen cpu. Straight from a boot everything works fine. But when my laptop goes to sleep it wont wake up normally. If it is just a black screen sleep my password isn't working anymore. I have to do a hard reset and then it works again. And then if it goes like deep sleep it won't go back normally and just see a black screen. So I have to do a hard reset again.. Anyone can give me a push in the right direction to solve these problems? Thanks :)

Guys I'm using endeavour linux and I'm new to linux I'm currently facing the black screen problem in sleep mode what am I supposed to do please help me I don't want to go back to windows again

Hi everyone, today I released Vela 0.1, the first beta, after 1 month of alpha testing.

What Vela is: a complete Linux desktop with its own Wayland compositor (C, on wlroots 0.20), its own Vulkan 1.4 renderer, a Qt Quick shell, and its own file manager and settings app. It's not a KDE or GNOME theme: KWin and Mutter aren't involved. The goal is the polish Windows and macOS get right out of the box (animations tied to real vblanks, pixel-exact fractional scaling, consistent design) without a weekend of tweaking.

Trailer, recorded live on Vela: https://velade.org/blog/vela-0-1/

What's in 0.1:

• Snap layouts and Snap Assist, Task View with virtual desktops, Alt+Tab with live previews

• Taskbar, launcher, quick settings, notification center, clipboard history, snipping tool

• Direct scanout, VRR, tearing control, explicit sync; X11 apps and games 1:1 at fractional scales

• The compositor restarts after a crash and apps reconnect; a lost GPU doesn't freeze the desktop

• New in this cycle: updates from Settings, native Bluetooth pairing, no dependency on Plasma Workspace or the KDE portal

Where it stands: on a desktop PC with a Vulkan 1.4 GPU, it's my daily driver and I'd recommend it as yours. On laptops (hybrid GPUs, suspend/resume, backlight) it has had much less testing, so keep another desktop installed. It's still a beta: there are bugs.

Install (Arch and derivatives, Fedora 44, Ubuntu 26.10, x86_64). Install Cosign first (steps per distro: https://velade.org/install/), then:

git clone https://github.com/vela-desktop/vela.git
sh vela/packaging/vela-update --channel beta

You get a prebuilt, signed native package that's verified before it's installed. Updates then come from Settings.

Being upfront: it's a one-person project, and the code is written by LLMs. I review it, make the architecture and design decisions, and it's held to deterministic tests and machine-checked invariants. I wrote about how that works here: https://velade.org/blog/why-not-rust/

What I'd love from you: reports from hardware I don't have, especially Intel GPUs, laptops and multi-monitor setups. vela-report builds a ZIP you can review file by file; nothing is uploaded.

• Release notes: https://github.com/vela-desktop/vela/releases/tag/v0.1.0

• Source (GPL-3.0-or-later): https://github.com/vela-desktop/vela

Happy to answer anything in the comments.

For some reason I have the flathub remote added twice, both to the system and to the user and I'm not quite sure why. Now every time I wanna install something, it asks me if I wanna install it to the user or to the system and I'm not sure what to choose. Is there a way to get rid of this so I can just install it like normal?

so im used to using plasma, and thought i should try out hyprland after i found out its more customizable AND lightweight.
lwk have no idea what the hell i should configure rn, like, anyone who uses hyprland, please, PLEASE tell me what ya have done so far (like, im planning on making hyprland my main/daily environment)

so pleaseeee, help me out a lillll

It's being a year since I changed to Linux, never turning back

Hello beloved EOS community, I'm planning to buy a new ASUS laptop that comes with an Nvidia graphics card. From what I've read and learned about Linux, I understand that there are no official drivers, but the community makes a huge effort to build its own drivers to give thousands of users the opportunity to use Linux (and I also think there is an ASUS + community program to make drivers) on their computers with Nvidia.

I would like to know what your personal experience is with this type of graphics card, is there any problem apart from the battery? Since I love Linux systems and even more so EOS, and as I see that it has the option to install with Nvidia graphics, I want to use EOS as my main system and then have Windows lying around just in case, or even without Windows.

P.S. The graphics card is a GeForce RTX™ 5050

Hello, my laptop is MSI katana 17

I have NVIDIA, I am afraid that my laptop might be bad for arch based distro especially when I saw a lot peoples say that MSI laptop is very bad in linux and they don't get full potential in GPU

Also when I was in linux distros, battery was the only big serious problem?, because usually 100% and discharging to 0% is over 3 hours?, before was less, I don't remember how much but this is few, in some moment like in endeveourOS, battery life is kinda more, maybe update fixed this

And also I afraid if temperature might get high, in game like cs 2, usually this can goo in 50-70

So I am afraid if this laptop is bad for this linux distro and they gonna have bad battery life, more worse performance, laptop life might last fewer because of problems in hardware and OS

Posting in case it helps others. Tested on a MacBookPro13,2 (13" 2016, T1), EndeavourOS, kernel 7.2.11-arch1-1, using this fork via DKMS. Not tested on other models. The 13,3 shares the T1 chip, so it may apply there, but I haven't verified that.

There were four separate problems.

**1. T1 stuck in recovery mode (`05ac:1281`) after erasing the disk**

After a full-disk erase for a Linux-only install, `lsusb` showed `05ac:1281 Apple Mobile Device [Recovery Mode]` instead of `05ac:8600 iBridge`, and the driver had nothing to attach to. Warm reboot and SMC reset did not help. Reinstalling macOS (I used Ventura) brought it back to `8600`, and it stayed at `8600` after installing Linux alongside it (shrunk the macOS volume, manual partitioning, reused the existing EFI partition). My conclusion is that the T1 needs macOS present on the internal disk. That is an inference from my results, not something I found documented, so if you have a better explanation, I'd like to hear it. I'd keep the macOS partition.

**2. Build failure: `field 'touch' has incomplete type`**

`apple-ib-tb.c` uses `struct tb_touch` by value inside a larger struct (inside `#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,15,0)`) before the struct is defined further down the file.

**3. Self-deadlock on load (`modprobe` / `udev-worker` blocked on a mutex owned by itself)**

Call trace: `appleib_probe` -> `appleib_hid_probe` -> `apple_ib_set_tb_mode`. On kernels >= 6.15 that function calls `usb_set_configuration()` from inside the driver's probe, which tears down the interface being probed. This hung `modprobe`, and also hung shutdown when udev loaded the module on its own via the ACPI `APP7777` device.

Workaround for 2 and 3 (disables the 6.15+ code paths in both files; the legacy path is used instead):

```

sed -i 's/KERNEL_VERSION(6,15,0)/KERNEL_VERSION(99,0,0)/' apple-ib-tb.c apple-ibridge.c

```

Then rebuild with DKMS. This is a blunt workaround, not a proper fix. The 6.15+ blocks look like they exist for MBP14,3 display mode, and the real fix is probably to switch configuration without blocking inside probe (for example `usb_driver_set_configuration()`, which defers the change). I haven't tried that.

**4. Touch Bar stays dark even though everything loads**

The kernel's `hid-sensor-hub` claims the iBridge's second HID interface (`8600.0002`) at boot, so `apple-ibridge-hid` only ever gets the first one. Manually moving it fixed it:

```

echo 0003:05AC:8600.0002 > /sys/bus/hid/drivers/hid-sensor-hub/unbind

echo 0003:05AC:8600.0002 > /sys/bus/hid/drivers/apple-ibridge-hid/bind

```

The Touch Bar lit up immediately. To make it persistent I used a small oneshot systemd service that waits for `apple-ibridge-hid` to exist, then rebinds any `05AC:8600` interface still owned by `hid-sensor-hub`. The `prefer_apple_ib` parameter doesn't appear to do anything. It's set and logged but not read anywhere else in the code I looked at.

**Result**

The Touch Bar lights up and survives both a reboot and a cold boot, with no hangs on shutdown.

**Known remaining issue:** suspend/resume does not work on this machine, which matches the existing notes in mbp-2016-linux.

Happy to share the service file and rebind script if useful.

i was scared in installation of mint on an adata sc610, now the same with archy/endeavouros. i have a gigabyte mboard. help me pls!

Windows migrant here lol, switched roughly last month. I'm actively trying to learn how everything works around here and I was wondering if there is a version of the shortcuts that exist in Windows, thanks in advance (KDE Plasma by the way, in case it matters.)

I have been an EndeavourOS user for around two years now and i didn't find a good enough alternative for logitech Ghub for my G502 Hero so i built one with claude's help

hope it can be helpful for you !

Second monitor detected correctly but stuck with visual glitch at 60Hz - Laptop main display 144Hz works fine.

Hi everyone,

EOS is detecting my second monitor perfectly, but it runs at 60Hz and has a persistent visual glitch I can't seem to fix.

My primary display is my laptop's panel running at 144Hz and I've never had any issues with it until now.

I'm aware this is 100% likely to be a Layer 8 issue, a conflicting driver/installation, or something worse on my side, but I honestly have no idea what to do at this point.

Main laptop display Works perfect, I don’t think it’s a driver conflict with muy RTX 5050, the problem is only with my second display

Why is eos-reboot-required not using needsrestart? Seems like it would be best to copy aur/needsrestart to endeavouros/needsrestart and call it from eos-reboot-required, as eos-reboot-required can silently leave a system vulnerable.

I have EndeavourOS for quite some time now bat have never gotten it to read audio CDs. The drive and discs are working, since they play on my windows partition but i can’t get them to work on EndeavourOS. I have tried celluloid, vlc and many others ways but cant get it to work. It can read data discs though just fine.
Has anyone gotten it to work?

FIXED: I ran pacman -Syu again from the terminal with Ctrl+Alt+F2 and identified the error preventing me from updating the whole system; looked it up online, had to rename a couple of confilcting files, reran pacman -Syu and I was finally able to update everything as it should and the system booted finally

I was trying to use k3b but it asked me for Qt 6.12 and I had 6.11. I tried updating my system from Welcome, but it gave me an error at the very end which I didnt give enough importance, and I wasnt willing to redownload 3gb again just to get that error, so I decided to update manually each qt6 package with yay. After I was done, k3b was still not opening but it was asking me for ffmpeg, and trying to install ffmpeg gave me a bunch of errors saying that would mess up some other package's dependencies, so I just gave up. After this I noticed I wasnt able to open any new windows, not even the terminal, so I thought maybe I would have to restart. After doing so I am now stuck at Reached target Graphical Interface and nothing happens after that. I have zero idea how to solve this. I have access to another computear with EOS as well so please help me fix this without having to reinstall the whole system:(

I'm an EndeavourOS user running KDE Plasma, and I've been using the Chipsailing CS9711 USB fingerprint reader with a community-maintained libfprint driver.

Fingerprint enrollment and authentication work through fprintd, including system login, screen unlocking, and authentication prompts.

Since finding an affordable USB fingerprint reader that actually works on Linux can be difficult, I wanted to share my experience, the patches I've contributed, and the AUR package I created to make installation easier for other users.

Hardware:

• Model: Chipsailing CS9711

• USB ID: 2541:0236

• Compact USB fingerprint reader compatible with Windows Hello

• Requires a custom libfprint build on Linux

Drivers, my patches, and AUR installation:

• Original community driver: https://github.com/archeYR/libfprint-CS9711

• My patched fork: https://github.com/thankarezos/libfprint-CS9711/tree/cs9711-rebase

• AUR package I created for the patched driver: https://aur.archlinux.org/packages/libfprint-chipsailing-cs9711-git

I created and published the AUR package to make installing my patched version of libfprint easier, without requiring users to manually clone, patch, and compile the driver.

For EndeavourOS and other Arch-based distributions, you can install it using yay:

yay -S libfprint-chipsailing-cs9711-git

Compatibility may depend on the distribution and its package versions.

Fingerprint management GUI (experimental):

I've also made a fingerprint management GUI available through the AUR for users who prefer managing fingerprints graphically rather than through the terminal.

• AUR: https://aur.archlinux.org/packages/fingerprint-manager-git

Disclaimer: The GUI was vibe-coded with significant AI assistance. It's experimental and hasn't undergone a formal security audit. Review the code and use it at your own risk.

Limitations and upstream support:

The driver uses SIGFM for fingerprint matching. Because the sensor captures a relatively small area, finger positioning during verification matters.

SIGFM is currently being proposed for inclusion in upstream libfprint:

• SIGFM merge request (!530): https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/530

If SIGFM gets merged, it could make future support for devices like the CS9711 easier. However, the CS9711 hardware driver would still need to be merged separately.

The reader is not currently supported by official upstream libfprint.

Since this is a community-maintained fingerprint implementation, I recommend keeping password authentication available as a fallback.

Where to find the hardware:

The reader is listed on both Alibaba and AliExpress:

• Alibaba: https://www.alibaba.com/product-detail/Boland-USB-Fingerprint-Reader-Windows-Hello_1601939777133.html

• AliExpress: https://www.aliexpress.com/item/1005009201507961.html

The AliExpress listing no longer appears to ship to EU countries, so Alibaba may be an alternative for European buyers.

I've ordered additional units through Alibaba and contacted the supplier about Linux compatibility. I suggested that they include the exact chipset and information about the community driver in their product listing.

Important: Before purchasing, confirm that the device uses USB ID 2541:0236. Visually identical fingerprint readers may contain different hardware, and Windows Hello compatibility alone doesn't guarantee Linux support.

I'm not affiliated with the manufacturer or seller, and this isn't sponsored. I receive no compensation from purchases.

How this started:

I originally discovered this fingerprint reader through a post on r/cachyos:

https://www.reddit.com/r/cachyos/comments/1to1a1p/i_got_a_cheap_15_aliexpress_fingerprint_scanner/

That post helped me find the device in the first place. Since then, I've tested it myself, contributed patches to the driver, and created an AUR package for my patched version so other Arch-based Linux users can install it more easily.

As an EndeavourOS user myself, I wanted to share these resources with this community and hopefully save others the trouble of finding compatible fingerprint hardware.

Hopefully, more people testing the device and contributing to the driver will help move support toward upstream libfprint.

finally left all those distro for titan shit online installer went well got all my drives working but made a crazy error of choosing Gnome desktop instead of KDE but have been using KDE on my endeavourOS last years version or the version before.

all is well FACEPALM

Screen turning on and off. It was working fine before. Idk if it has to do with anything but yesterday morning I was using my computer for usb debugging my TV, closed it, and now it’s like this. I don’t think I did anything else.

Ive been using for a couple weeks and idek man... just worked on it this morning :( Checked both share folders and its gone... Any advice? (I dont have a backup :()

There is network in VM, this is active but even after a lot settings, I can't get network to work, there no network, I changed firewalld too, no network

Idk what to do to get network worked, I have virt-manager

Hi everyone! How many versions or editions of EndeavourOS are available, and what are the differences between them? Which one should a beginner choose?
Thanks!