**Works with normal fprintd: enroll, verify, sudo and the lock screen.**

Got the fingerprint reader on my Yoga 9 14IAP7 working on Debian 13. Packaged it up so others can use it too.

It never touches the sensor firmware, and your password still works if the finger fails.
you need the Windows install that came with the laptop, since the sensor's key gets pulled from it once. Steps are in the repo.

https://github.com/fdjfnd222dd/goodix-550c-linux-debian

Thanks to the-great-king-bart for the original reverse engineering. If you have a Yoga 9 14IRP8 feel free to try it out

(screenshots are from demo mode)

Last spring I bought an HP OmniBook 5 (Snapdragon X Plus, 32 GB) for $650 and tried to get native Linux running on it. I was living in my 2013 Civic at the time, coding in parking lots.

I logged more than 1000 reboots. Some things came up, but every step meant fighting closed firmware and missing drivers. Eventually money ran out, and I had to sell the laptop.

What stuck with me: I wasn't fighting Linux, I was fighting hardware I couldn't see inside. So I flipped it. Now I'm building a 16" laptop around a NanoPi M6 (RK3588), where the parts are documented.

So far:

• designed my own DSI→eDP bridge board, and it drives a real 16" laptop panel
• the display and the SBC run straight off a 4S6P 21700 pack (no 12V converter anymore)
• keyboard + touchpad board is designed, next to order

Everything is open source. Question for people here: if you wanted a Linux laptop you could actually repair and understand, would you go ARM SBC like this, or stick with x86 (Framework, ThinkPad)?

Full story and board files, if anyone's curious: tagoslabs.com/story

Hi everyone,

I'm experiencing a frustrating suspend/resume issue with my ASUS Zenbook S 14 running Arch Linux.

System:

• Laptop: ASUS Zenbook S 14 UX5406SA
• CPU: Intel Core Ultra 7 258V (Lunar Lake)
• GPU: Intel Arc (Xe driver)
• OS: Arch Linux, KDE Plasma (Wayland)
• Suspend: s2idle
• Power management: TLP

The problem:

After suspending my laptop for several hours, waking it up causes the entire system to become extremely sluggish. The mouse lags, applications respond slowly, and everything feels almost frozen.

This lasts around 3–4 minutes, after which performance returns to normal.

What I've tried:

Adding intel_idle.max_cstate=2 to my kernel parameters completely fixes the issue.

However, this significantly increases battery drain during s2idle, so it's not a practical long-term solution.

Without this parameter, battery consumption during suspend is much better, but the sluggishness returns.

I found a potentially related issue involving CPU throttling after resume:

https://github.com/dantmnf/zenbook-s14-ux5406sa-linux/issues/11

Has anyone experienced this on Lunar Lake laptops? Is there a fix that preserves low suspend power consumption without restricting CPU C-states?

Any suggestions would be appreciated!

I'm running Linux on Assus ZenBook S14 (Lunar Lake, Intel Ultra 7 258V CPU, integrated graphics, 3k OLED panel).

I'm curious if there are any known issues with Asus specifically and my chipset in particular - I have not noticed any issues, running 4 days only. So far - longer battery, much cooler and much more responsive system. What am I missing besides obvious OLED care? BIOS updated to the latest version.

Any info would be appreciated.

Thank you in advance for your time!

Title. I've been using an RTX 2070 for years now but I'm starting to run into VRAM degradation & crashing so I've been looking into upgrading some parts of my system. I've been using the proprietary drivers pretty much since they came out and I've never really had any issues so I was just going to buy whatever is cheapest when I have the scratch. I wanted to reach out and ask if comparability is still an issue?

Basically, is limiting myself to AMD cards worth the (potential) extra cost?

^{Edit: Fixed a giant run-on sentence I somehow didn't notice}

Been driving the ASUS ProArt 14 with the NVIDIA RTX Spark N1X on Arch Linux ARM and honestly… it's great. Everything works and it's snappy.

- Touchpad, trouchscreen, wifi, sound, Wayland/GNOME all good, ran vllm with 2b, 4b models and nvfp4 also.
- Steam works through FEX (x86 emulation, the same tech Valve uses on the Steam Frame). Took an evening of tinkering, but the client runs fine and x86 games get the real NVIDIA GPU.-Tested BG3 realy quickly wirh DLSS.

Thanks NVIDIA and ASUS now I have a dreamy laptop for both work and gaming. Now I have to get the 16" one 😅 to run my work stuff.

Here is repo with all stuff (use on your own :

https://github.com/mikivolek/archlinuxarm-proart-p14/tree/main (cudos to pfeifferj).

One catch: the laptop needs patched ACPI tables to run Linux properly. Those tables are ASUS/NVIDIA firmware and can't legally be redistributed, so nobody can hand you a ready-made fix. You have to dump the tables from your own laptop and patch them locally (the project has scripts and a guide for it). It takes about 15 minutes, once.

--- small updsate Oct 26 6:05PM

After comming home from work I fixed a build bug in FEX's Vulkan thunks, so games now talk straight to the native ARM NVIDIA driver instead of an emulated x86 one. Only the game code is emulated now, the GPU side runs native, and it shows. HDR works too, desktop and BG3. GNOME didn't detect the OLED as HDR because the panel only reports it in a newer EDID format, so I patched the library that reads it. Games then needed GE-Proton10 with Wine's Wayland driver, plus a few fixes to FEX's Wayland thunk so it could run natively. BG3 now outputs real HDR10 on the OLED.

I’ve been working on LogiOptions, an independent Linux app inspired by Logitech Options+.

It started because I wanted to use my MX Master 4 and MX Keys for Business on Linux without giving up their settings. It now has mouse DPI, scrolling and SmartShift controls, adjustable haptic feedback, keyboard function-key and backlight settings, and an experimental Actions Ring with per-app shortcuts.

The tray and background service start at login, so the Actions Ring works with the settings window closed. The project grew from studying the official macOS app and testing direct HID++ communication with my devices over Bolt.

This is an experimental release. Support currently targets these two devices on Ubuntu 26.04 (amd64), with GNOME 50. Broader device support, Flow, macros and full Options+ parity are still unfinished. New global button shortcut assignments still need an end-to-end physical mouse test.

GitHub: https://github.com/enriquemorenotent/logioptions-linux

Install with automatic updates:

curl -fsSL https://enriquemorenotent.github.io/logioptions-linux/install.sh | sudo bash

You can review the installer in the repository first. After first-time installation, log out of Ubuntu and back in to load the Actions Ring extension.

The screenshot shows example button assignments. The application code is GPLv3; the device artwork and fonts are Logitech assets with separate terms. This is an independent project, not affiliated with or endorsed by Logitech.

I’d love feedback from other MX Master 4 and MX Keys users on Linux!

Hello all,

Thanks for taking the time to check this post out. I have tried to do some digging on this, but have not been able to find a conclusive answer to get me pointed in the right direction, and wanted to get some opinions on a good laptop for my scenario.

Due to life circumstances, I will be unable to have a desktop PC for the next couple of years, and thus will be restricted to a laptop. I currently have a Lenovo ThinkPad E595, and to be entirely honest, it is not doing it for me. The trackpad and keyboard are both not great, and overall performance has not been where I am wanting it to be.

So, here is the description of the unicorn I am looking for:

- Reasonable used price (~750 but less is of course fine, and might be willing to adjust up *slightly* for a large improvement.

- Good enough performance to run a decent amount of games. Hypothetically, if it could run up to something like Starfield, that would be great.

- Small form factor and good build quality. Think something close to a MacBook (Based on my reading, I know there is not really any company with as good build quality, just wanting decent build quality, metal if possible.)

- An important thing, especially given my current laptop, is a good trackpad and keyboard. I actually really like the ones on the Dell Pro 14 (which is what we have been purchasing at my job).

- Docking capabilites if possible. Not a necessity, but would be nice if it ends up working out really well, and I want to continue using it into the future.

To sum it up, essentially looking for a high performance "linux macbook". I will say, battery life is not super important to me, given that I don't travel a whole lot, and thus don't need to run off of the battery much.

used linux for a while and didn't see a good alternative so i built my own with claude's help

Hope you guys find it useful

Hey everyone. I have an Attack Shark X6 and there's no official software for Linux, so I ended up building my own. I captured the traffic from the Windows software in a VM, worked out the protocol, and built the app bit by bit. It's written in Go with Wails and React, ships as an AppImage, and updates itself from inside the app.

Right now you can set DPI per stage, polling rate, lighting, button remapping, and macros with keyboard input, delays and loops. Profiles are already in the main branch, but I haven't cut a release yet because there's one bug I want to fix first.

What I really want is for this to stop being just my project and become one for everyone who uses Attack Shark on Linux. The brand is getting more popular and we don't have anything decent on the desktop, so it makes sense to build it together.

So I'm asking for three things. Try it out, especially if you have another model (X3, R1, X11...) or a different distro than mine, because I can only vouch for what I've tested on my own X6. Tell me what features you miss or what annoys you about other mouse software. And if you feel like getting your hands dirty, open issues or PRs. Someone once found a real bug of mine in the lighting checksum and we fixed it together, and that was honestly the best part of the whole project.

Repo: [attack-shark-linux](https://github.com/blak0p/attack-shark-linux)

All feedback is welcome, including the harsh kind. I'd rather hear that something is badly designed than keep building on top of it.

I’m the maintainer of an experimental Linux project for the Logitech G Pro 2 Lightspeed (not the Superlight): https://github.com/opigod/pro2-linux

The goal is to provide Linux-side configuration for a mouse that currently has very limited Linux software support. The kernel side has improved, but the userland configuration tooling is still missing.

Important caveat: the project is entirely AI-written under my direction. It may work partially, but it likely contains bugs and unverified assumptions. I’m posting because I need help turning it into something more reliable.

I’m specifically looking for:

• Hardware testers with the exact G Pro 2 Lightspeed
• People who can confirm device IDs, receiver behavior, and battery reporting
• Bug reports with dmesg, lsusb, and project logs
• Code review and PRs
• Packaging help for Arch/AUR and other distros

Repo: https://github.com/opigod/pro2-linux

Not affiliated with Logitech. Experimental software—use at your own risk.

Hey guys,

Trying to install Linux on my old T430 and I'm completely stuck. Any USB I boot just gives me a black screen. No GRUB, no cursor, no Ventoy menu, nothing. Screen stays black forever.

What I've tried:

• Rufus, Balena Etcher, and Ventoy. Same result with all three.
• F12 boot menu → select "USB HDD: Generic Storage Device" → instant black screen.
• BIOS (F1): UEFI/Legacy Boot = UEFI Only, CSM Support disabled, Secure Boot off, SATA = AHCI, OS Optimized Defaults disabled.
• Tried a USB 2.0 port instead of the blue USB 3.0 one.
• Full shutdown with Shift before booting.
• Windows 11 is still on the internal SSD, if that matters.
• T430 has Intel HD 4000 graphics only, no Nvidia.

Since even the Ventoy menu doesn't show up, I'm guessing it's failing before Linux/GRUB even loads. So kernel params like nomodeset are useless here because I never see a boot menu.

Has anyone actually fixed this exact "black screen, no GRUB, no Ventoy" thing on a T430? Did I miss a BIOS setting? Is there a way to force USB boot or inject kernel params without seeing GRUB? Any help would be appreciated. This laptop is too nice to give up on lol.

its old and i mean REALLY REALLY old it runs solitare at a smooth 30fps i want to use a distro with a built in browser and isnt shitty and ancient like antix or puppy

.

A few months ago, I shared Acer Control Center, a project I started to bring better control over Acer gaming laptops to Linux. Since then, I've been working on improving the project, cleaning up the architecture, and making it easier to maintain and extend.

I'm now releasing v2.0.0.

The main focus this time has been on improving the overall structure and bringing the different parts of the application together. Acer Control Center has a desktop interface, a background daemon for hardware communication, and supporting components for things like keyboard lighting and fan monitoring/control on supported hardware.

Some of the things the project currently includes:

• A dashboard for system and hardware status
• Keyboard RGB controls with a live preview
• Fan monitoring and available fan modes on supported hardware
• A D-Bus-based daemon for communicating with hardware components
• A DKMS driver and installation support
• Release checking and other system integration features

I'm developing and testing this primarily on my Acer ALG AL15G-53 running Fedora. Hardware support is still something that needs careful testing, so I don't want to imply that every feature works on every Acer model or Linux distribution.

There's still plenty to do, but this release is a good step forward from the first version. I'm also interested in hearing from people with other Acer laptop models who are willing to help test things or share hardware-specific details.

GitHub: Acer Control Center

Discord community: Join acerctl

One note on development: I do use AI tools to assist with parts of the development process, including brainstorming, debugging, and reviewing ideas. I still make the implementation decisions, test the project on actual hardware, and work through the issues that come up. I wanted to be transparent about that rather than leave it unmentioned.

If you're using an Acer ALG laptop on Linux, I'd appreciate feedback, bug reports, and contributions.

Hi all! I switched my Nitro 14 (AN14-41) to Fedora KDE and missed NitroSense, so I wrote Linux Sense:

- Eco / Quiet / Balanced / Performance / Turbo profiles, synced with the physical profile key, with automatic switching on AC/battery

- Fans: auto, max or manual, live RPM

- 4-zone RGB keyboard with effects and live preview

- Battery: 80% charge limit, calibration, USB charging while off

- N key opens the app; Fn+F11/F12 keyboard brightness in 5% steps with Plasma's popup

- 10 languages

Driver based on Linuwu-Sense (patched for kernel 7.x), installed through DKMS.

I could only test it on the AN14-41. Other Nitro/Predator models probably just need a DMI entry: if you try it, please open an issue with your model and what works

Hope it helps :)

GitHub: https://github.com/PoPoGne/linux-sense

Hi, Linux Mint XFCE x64 is installed on my system by using a pendrive to avoid dual boot error. Now my question is if I run it every day, will it create any error for pendrive ( SANDISK ULTRA USB 3.0 32 GB ). I've heard that AntiX is the lightest and LUBUNTU also. So which distro is lightweight on my system for booting from the USB pendrive? Or is an external SSD good? But as of now Mint is running.

Please suggest. Thanks in advance.

Hi everyone,
I’m trying to troubleshoot a suspend issue on my Acer Nitro V 16S AI (ANV16S-41), and I’d appreciate any suggestions.
Hardware:
Laptop: Acer Nitro V 16S AI, model ANV16S-41
BIOS: V1.05
CPU: AMD Ryzen 7 260
iGPU: AMD Radeon 780M
dGPU: NVIDIA RTX 5060 Laptop GPU
RAM: 32 GB DDR5
Software:
Current OS: EndeavourOS
Kernel: 7.2.11-arch1-1
Desktop: KDE Plasma (Wayland)
Previously tested: Fedora 44 with kernel 7.2.11-200.fc44
The problem:
When I try to suspend the laptop on Linux, it freezes during the process. The display goes black, the system becomes unresponsive, and I have to force a shutdown using the power button.
Windows 11 suspend works correctly on the same laptop, so the issue appears to be Linux-specific.
What I’ve checked so far:
/sys/power/mem_sleep shows only [s2idle]; deep is not available.
ACPI reports S0, S4 and S5 states.
On Fedora, pm_test=freezer and pm_test=devices completed successfully.
On Fedora, pm_test=platform caused a similar hard freeze.
I investigated the NVIDIA driver and SELinux on Fedora, but neither appeared to explain the issue.
The AMD PMC S0ix statistics showed 0/0/0, and the last S0i3 status was reported as Unknown/Fail.
I have reproduced the suspend failure on both Fedora and EndeavourOS.
Some kernel messages I’ve encountered include:
ucsi_acpi: UCSI_GET_PDOS failed (-70)
i2c_hid_acpi: device did not ack reset
GPP7.WWAN AE_NOT_FOUND
BAT1._BIX AE_AML_PACKAGE_LIMIT
I don’t know whether these messages are related to the suspend failure.
Latest test:
After another failed suspend attempt on EndeavourOS, I tried retrieving the previous boot’s kernel journal using:
sudo journalctl -k -b -1 --no-pager | grep -Ei 'suspend|resume|sleep|PM:|ACPI|amd_pmc|s0ix|ucsi|nvidia|amdgpu|failed|error|timeout'
The command produced no output. I still need to determine whether the relevant logs were saved and whether the journal contains anything useful from the failed suspend attempt.
My questions:
Has anyone encountered this issue on a recent AMD-based Acer laptop?
Could this be related to the laptop’s ACPI implementation, AMD s2idle/S0ix support, BIOS firmware, or a kernel regression?
Is there a reliable way to capture useful kernel logs when the system hard-freezes during suspend?
Is there anything else I should check before considering a BIOS update or reporting this as a kernel/platform issue?
I’m happy to run diagnostic commands and share the results. I’d prefer to identify the cause before trying random kernel parameters or configuration changes.
Thanks!