I've been using the Chipsailing CS9711 USB fingerprint reader on Arch-based Linux with KDE Plasma, and it works with a community-maintained libfprint driver.

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

Hardware:

• Model: Chipsailing CS9711
• USB ID: 2541:0236
• Small USB fingerprint reader compatible with Windows Hello
• Requires a custom libfprint build on Linux

Linux drivers and installation:

• Original community driver: https://github.com/archeYR/libfprint-CS9711
• My patched fork: https://github.com/thankarezos/libfprint-CS9711/tree/cs9711-rebase
• Arch-based distributions AUR package: https://aur.archlinux.org/packages/libfprint-chipsailing-cs9711-git

For users of Arch Linux and Arch-based distributions (such as EndeavourOS, CachyOS, and Manjaro), the AUR package offers a more convenient installation method than manually compiling the driver. Compatibility may depend on the distribution and its package versions.

Fingerprint management GUI (experimental):

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

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

Disclaimer: This application was vibe-coded (developed with significant AI assistance). Treat it as experimental and use it at your own risk. It hasn't necessarily undergone the same level of code review or security auditing as established Linux authentication tools.

Limitations and upstream development:

The driver uses SIGFM fingerprint matching. Because of the sensor's small capture area, finger positioning matters during authentication.

SIGFM is currently being proposed for inclusion in upstream libfprint:

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

This is an important step toward broader support for fingerprint sensors that rely on SIGFM, although merging SIGFM alone won't automatically add support for the CS9711 hardware.

The CS9711 is not yet officially supported by upstream libfprint.

Where to buy:

The reader is listed on both Alibaba and AliExpress:

• Alibaba: https://www.alibaba.com/product-detail/Boland-USB-Fingerprint-Reader-Windows-Hello_1601939777133.html?spm=a2756.order-detail-ta-ta-b.0.0.404ef19cdZwdJz
• AliExpress: https://www.aliexpress.com/item/1005009201507961.html?spm=a2g0o.order_list.order_list_main.47.ee3c1802OFxniE

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 also suggested including information about the community driver in their listing.

Make sure to confirm the CS9711 chipset and USB ID 2541:0236 before purchasing, since visually similar readers may use different hardware.

I'm not affiliated with the seller, and this isn't sponsored.

I'm sharing this because finding affordable USB fingerprint readers that actually work on Linux can be surprisingly difficult.

Hopefully, more users testing the device and contributing to development will help bring official upstream support eventually.

The pump display on my ASRock Challenger 360 Digital didn’t work on Linux, because ASRock only ships a Windows app. I worked out the USB protocol by statically analysing ASRock’s Windows driver (I never ran it) and wrote a small Linux daemon to replace it.

Shows CPU temperature and clock, switching every 8 s (same as the Windows app)

Plain Python 3, no dependencies; installs as a systemd service that runs without root

Reconnects on its own after USB resets, suspend and reboots

Includes the full protocol write-up (protocol.md) if you want to build your own tool

Tested on Ubuntu 24.04 with a Ryzen 7 9700X and a Gigabyte B850 AI TOP, under load too.

Not done yet: pump/fan RPM (needs the out-of-tree it87 driver), GPU stats and power. Reports from other Challenger models or Intel boards are welcome.

Repo: https://github.com/infopointer/asrock-challenger-display

Processing img zf55dno9ruwh1...

Hi, I haven’t used Linux since around 2018, and I’m looking to buy a Linux-ready laptop for programming. Even though I have prior experience with Linux, I’d prefer a machine where all the hardware works "out of the box" with minimal setup.

I’ve been looking at the ThinkPad E14 Gen 8 (the version with an Intel Core Ultra 5 325), but I’ve seen mixed reviews regarding hardware compatibility (speakers, fingerprint reader, etc.). It’s currently on sale (brand new) for about $1,500—is it worth it?

I’ll be using it for programming, but I’d rather avoid the cheaper, entry-level laptops (in the $600 range). My budget is a maximum of $1,700. What would you recommend within that price range?

PD: Battery life would also be a fairly important factor that I would consider.

So I have a Lenovo ThinkPad E16 with Intel Ultra 7 (155H). I tried installing linux for 3 DAMN DAYS!!. Wanted to double boot. Tried Ubuntu first but got a pink screen and an error with a penguin, then I tried fedora, similar error but with black screen and the penguin. I was using Claude, chat gpt and gemini while doing the installation at all times, they said that ultra 7 with integrated graphics is very new stuff in the market so the distros haven't been updated yet. So for the final thing I tried pop!OS as the AI said that it usually handles these new graphics stuff the best and guess what it did work!!! First time I saw some graphics 🥹 I landed on some lock screen and it was asking for some username and password, I tried lots of things but nothing worked..... Someone please HELP!!!!! WHAT DO I DO???? I WANT TO SWITCH TO LINUX BADLY!!!!!. I would love to use Fedora😋

PS: I'm a beginner to linux so please forgive😶‍🌫️

I've been running Arch on my 2013 gaming desktop for 11 years, very happy with it, but my beloved Vega 64 died in a heat wave and it's time to get a new rig. Considering SteamOS, possibly another distro. I found an ad by a local PC builder and it seems like a decent deal, looking for opinions about the hardware and would like to know what I can expect on Linux, if there any parts I should swap out, etc.

Here are the specs, asking $3000 CAD ($2130 USD), possibly negotiable, I'll probably ask for a 2TB NVMe:

AMD Radeon RX 7900 XTX Sapphire Pulse 24GB VRAM

AMD Ryzen 7 9800X3D - 8 Cores, 16 Threads, up to 5.20 GHz

Thermalright Peerless Assassin 140 Dual Tower High Performance Cooler

MSI MAG X870E TOMAHAWK WiFi & Bluetooth DDR5

32GB (2x16GB) DDR5 Crucial Pro

1TB NVMe M.2 SSD Samsung 990 Evo

Corsair RM1000x- 1000 Watt Gold Fully Modular

Corsair 5000D Airflow - ATX Mid-Tower Tempered Glass

10 x High Performance Fans

Includes Official Windows 11 Pro License

Same system can be sold with 64GB DDR5 RAM, 2TB/4TB NVMe SSD and 9900X/9950X3D CPU

Comes with full warranty and receipts

Can be tested before buying

I'm planning to purchase a Pcie Wifi Bluetooth card for my PC. Wondering if fedora detects this card out of the box.

(FIXED)

TL;DR

Lenovo LOQ 15AHP10 + RTX 5060 + Arch Linux → GPU power limit is stuck at 45W.

Hey everyone, I’m trying to figure out why my RTX 5060 Laptop GPU is stuck at 45W on Linux even though this laptop is supposed to support a much higher GPU TGP.

nvidia-smi reports:

Current Power Limit   : 45.00 W
Requested Power Limit : 45.00 W
Default Power Limit   : 45.00 W
Max Power Limit       : 115.00 W

Trying to change it with:

sudo nvidia-smi -pl 100

doesn't work because NVIDIA says changing the power limit is unsupported.

I also tried Linux's max-power platform profile, but the GPU remains at 45W.

More importantly, my kernel log contains:

ACPI BIOS Error: Could not resolve symbol
[_SB.PCI0.GPP0.PEGP.GPS.NVD1], AE_NOT_FOUND

NVRM: GPU0 _acpiDsmCallbackInit: SBIOS suggested GPS_2X supports
function 517, but the call failed!

NVRM: PlatformRequestHandler failed to get platform power mode from SBIOS

So I'm wondering if this is a Lenovo BIOS/ACPI ↔ NVIDIA Linux driver issue.

Has anyone with this laptop/GPU managed to get the full TGP working on Linux?

I'm looking for a safe fix involving BIOS/kernel/NVIDIA driver/ACPI configuration if possible — not a random VBIOS flash.

Hardware

• Laptop: Lenovo LOQ 15AHP10
• Machine type: 83JG
• GPU: NVIDIA GeForce RTX 5060 Laptop GPU
• BIOS: R8CN26WW
• OS: Arch Linux
• WM/Environment: Hyprland / Omarchy
• NVIDIA driver: 610.57.04
• NVIDIA kernel module: Open

The problem

nvidia-smi initially shows approximately:

Power: ~10W / 45W

And:

nvidia-smi -q -d POWER

reports:

Current Power Limit   : 45.00 W
Requested Power Limit : 45.00 W
Default Power Limit   : 45.00 W
Min Power Limit       : 5.00 W
Max Power Limit       : 115.00 W

So the weird part is that the driver knows about a 115W maximum, but the current/requested/default limit is only 45W.

I tried:

sudo nvidia-smi -pl 100

but received:

Changing power management limit is not supported for GPU: 00000000:01:00.0.
Treating as warning and moving on.
All done.

The limit remains 45W.

Things I've already tried

Linux platform profiles available:

low-power
balanced
performance
max-power
custom

I switched to:

max-power

and also had:

powerprofilesctl get

showing:

performance

But NVIDIA still reports a 45W limit.

ACPI/NVIDIA errors

The part that makes me think this might be firmware/driver related is the kernel log:

ACPI BIOS Error (bug): Could not resolve symbol
[_SB.PCI0.GPP0.PEGP.GPS.NVD1], AE_NOT_FOUND

ACPI Error: Aborting method
_SB.PCI0.GPP0.PEGP.GPS due to previous error (AE_NOT_FOUND)

ACPI Error: Aborting method
_SB.PCI0.GPP0.PEGP._DSM due to previous error (AE_NOT_FOUND)

NVRM: GPU0 _acpiDsmCallbackInit: SBIOS suggested GPS_2X supports
function 517, but the call failed!

NVRM: PlatformRequestHandler failed to get target temp from SBIOS

NVRM: PlatformRequestHandler failed to get platform power mode from SBIOS

I also see:

SW Power Cap              : Not Active
HW Slowdown               : Not Active
HW Power Brake Slowdown   : Not Active

So it doesn't appear to simply be thermal throttling.

What could be causing this?

I'm trying to determine whether this is:

• Lenovo BIOS/ACPI
• NVIDIA Linux driver
• NVIDIA open kernel module
• Linux Lenovo platform/EC support
• BIOS version
• Or something else

And most importantly:

How can I get the RTX 5060 to use its intended higher TGP on Linux?

If anyone has the same LOQ/RTX 5060 combination working properly, I'd really appreciate knowing what kernel, NVIDIA driver, BIOS version, or configuration you're using.

Thanks!

For complete context, I am on Garuda Linux (Arch-based distro), and am also a digital artist (well, more like aspiring digital artist) who uses Krita.

I previously had a budget Gaomon digital display (PD1561) that still works fine, but even with OpenTabletDriver tweaks that I had applied, still had issues with bounding regions and correctly mapping the pen to the display, which led me to just draw on my stanadlone tablet (a Wacom Movinkpad Pro 14, which I use for more than just drawing). That device technically has computer connection software but it's Windows only and can't work through Wine/Bottles/Proton.

I am also aware that the only drawing tablets that really natively support Linux are Wacom, but their standalone displays are a little bit above my current price range. Ergo, I am looking at XP Pen drawing displays, which I know are generally cheaper in quality, but do have the features I actually care about.

I have read a few posts regarding this, but the most relevant one seems to be from a couple of years ago.

Does anyone know if XP-Pen devices (and more specifically pen displays) work well enough on Linux? I am not averse to tweaking as necessary, but I do want something that ideally works better than what I had, given the issues with region bounding and pen mapping.

Otherwise, I'm open to suggestions for other display brands that may work a bit better, or recommendations on how to make my Gaomon PD1561 work better (or if there's a way to force my standalone tablet to be able to connect and act as another display, that would work too).

Thank you in advance.

Hi all — chasing a stubborn failure on a used Tesla V100 SXM2 16GB (SXM2-to-PCIe adapter board, dual 8-pin) and hoping someone recognizes the pattern.

It throws Xid 62 (internal micro-controller halt) roughly once an hour now — 19 times over 10 days, with the interval shrinking from ~60 hours originally. 17 of the 19 happened fully idle (~21 W, 135 MHz), the other 2 under sustained compute load. Volta has no GSP, so I read this as a PMU-side halt.

The interesting part: the payload is deterministic per driver build and identical across every config I've thrown at it —

580.173.02 → first field 0x00018f8d 580.178.04 → 0x00019001 570.211.01 → 0x00018e87

Fields 2–6 are drawn from a small recurring set (0x0fbf, 0x101e, 0x159b, 0x17xxx–0x19xxx), field 7 is always 0x11, field 8 always 0.

Ruled out so far, each one actually tested:

• Three driver versions across kernels 7.0 and 6.17 — crashes on all of them
• PCIe link: the Gen3 AER storm from my riser was fixed by locking Gen2 (zero AER now) — Xid 62 kept coming, so link errors are out
• Power: limit set to 250 W, 300 W (no cap) and 100 W (minimum); also pinned a sustained inference load at exactly ~100 W — crashed after ~5 min
• Clock lock (-lgc 1350,1350, idle power raised to 40 W) — crashed after 4m49s
• GPU topology: crashes with a Quadro display card co-installed AND as the only NVIDIA GPU in the box (desktop moved to an AMD card — after that, crashes stopped taking the whole system down, which was nice)
• ECC: zero correctable/uncorrectable errors, no retired pages across all 19 events; host MCE count zero
• Fresh dual independent 8-pin cables, ASPM off, persistence on

Zero ECC plus a deterministic signature plus an accelerating failure interval smells like a degrading part to me, but I can't decode the payload and the fields aren't documented anywhere I can find.

The card is going back to the seller regardless — I'm mainly posting in case the signature rings a bell for someone, and to leave a data point for the next person who buys a used V100.

Environment: Huananzhi X99-AD3, Xeon E5-2696 v3, Ubuntu, kernels 6.17/7.0. Happy to paste the full 19-event log with timestamps and payloads in the comments if that's useful.

Looking for a tiny, cheap travel PC to run the actual OpenAI Codex desktop GUI, not the web version.
Budget around $75-$100. Must fit a 30 × 25 × 3 cm bag, with good battery life.
Open to Windows, Linux, used tablets, Chromebooks with Linux installed, or weird DIY hardware.
Considering older Surface tablets. Any better suggestions?

I made a driver that works with the GPU completely. both Zink (for opengl 3.3) and Vulcan 1.2 work, both in x11 and in Wayland, please test it and give feedback on bugs or problems, I will be happy to answer them. https://github.com/TumRedSun/apercel

Experiencing issues with the touchpad on an Asus ROG G752VM laptop. Everything else works, but I use the laptop outside of gaming and want to use the touchpad.

* Manufacturer: ELAN Microelectronics Corp.

* Device ID: ELAN1203:00 (Vendor 04f3, Product 0401)

* Physical Size: 106 mm $\\times$ 56 mm

* Max Resolution: 3423 $\\times$ 1793 units

* Connection Type: I²C HID (Intel Serial I/O Controller)

* Touch Support: Up to 5 concurrent fingers (multi-touch)

* Gestures Supported: Taps and swipes (1 to 5 fingers)

* Linux Drivers: i2c_hid_acpi, i2c_hid, hid_elan

I'm working on Kinect2-Linux, an open-source MIT-licensed project for Microsoft Kinect v2.

We already have native RGB, infrared and depth capture working on real Linux hardware, plus an experimental C++ broker that can deliver frames to four independent Python viewers (2 RGB + 2 IR) through a single USB connection.

Our goal is a simple-to-install Linux SDK with one broker service, V4L2 webcam support for Firefox/OBS, and independent RGB/IR/Depth clients.

It's not version 1.0 yet. We're looking for Linux hardware testers, C++/Python contributors, documentation help, and people interested in computer vision and robotics.

You don't need a Kinect to contribute — offline tests and documentation are welcome too!

GitHub: https://github.com/KacperPiotrowski/Kinect2Linux

Feedback and contributions are very welcome!Bringing Kinect v2 back to life on Linux — looking for testers and contributors!

I'm working on Kinect2-Linux, an open-source MIT-licensed project for Microsoft Kinect v2.

We already have native RGB, infrared and depth capture working on real Linux hardware, plus an experimental C++ broker that can deliver frames to four independent Python viewers (2 RGB + 2 IR) through a single USB connection.

Our goal is a simple-to-install Linux SDK with one broker service, V4L2 webcam support for Firefox/OBS, and independent RGB/IR/Depth clients.

It's not version 1.0 yet. We're looking for Linux hardware testers, C++/Python contributors, documentation help, and people interested in computer vision and robotics.

You don't need a Kinect to contribute — offline tests and documentation are welcome too!

GitHub: https://github.com/KacperPiotrowski/Kinect2Linux

Feedback and contributions are very welcome!

Hi everyone!

If you've ever tried running Linux on an Acer Predator (Helios, Triton, Neo) or Nitro laptop, you probably know the pain: PredatorSense only exists for Windows, leaving you unable to control fan speeds, engage Turbo mode, or customize keyboard RGB lighting natively. A lot of users were literally forced to boot into Windows just to turn fans to max, and then reboot into Linux!

To fix this once and for all, we created **PredatorSense for Linux (v1.1.0)**!

🌟 What it offers:

- 🖥️ **Modern Native GUI:** Cyberpunk-inspired aesthetic built with Avalonia UI, with real-time hardware telemetry and Wayland/X11 support.

- 🌪️ **Complete Fan Control:** Auto, Maximum (Turbo), and Custom Manual Fan sliders for both CPU and GPU fans.

- 🌈 **RGB Lighting Engine:** 4-Zone keyboard colors, brightness sliders, Predator logo lighting, and dynamic lighting effects.

- ⚡ **Performance & Battery:** Thermal performance profiles (Quiet, Balanced, Performance, Turbo) and 80% battery charging threshold limiter.

- 🔄 **Zero-Effort Automated Installer:** Single `./install.sh` command that auto-resolves dependencies across Arch, Ubuntu/Debian, Fedora, and openSUSE.

- 🛡️ **DKMS Driver Persistence:** Automatically registers the underlying kernel driver so it automatically recompiles whenever your kernel updates.

- 📦 **Pre-built Standalone Binary:** Self-contained executable without needing .NET runtime installed.

Check out the project and installation instructions here:

👉 GitHub: https://github.com/0PeterAdel/PredatorSense

👉 Latest Release (v1.1.0): https://github.com/0PeterAdel/PredatorSense/releases/tag/v1.1.0

We'd love your feedback, bug reports, and contributions! Feel free to star the repository if it helps you! ⭐

The Ajazz AKP02 (the 9.2" 1920×462 USB side panel sold as a case or desk stats screen) only ships with Windows software, so I wrote a Linux driver and a daemon to drive it.

- **[akp02](https://github.com/deonspengler/akp02)\*\* is the driver library: it talks to the panel over USB HID. MPL-2.0, so you can build your own app on it.

- **[akp02d](https://github.com/deonspengler/akp02d)\*\* is the app: a systemd user service that draws themes you design yourself. GPL-3.0-or-later.

**What it can show**

- Clock, CPU, memory, disk, network, temperatures, uptime, IP address

- An audio visualiser (bars, mirrored, segmented or radial, via cava)

- What's playing, with cover art, from any MPRIS player (Spotify, mpv, browsers...)

- The system volume, following your volume keys as you press them

**The theme editor**

`akp02d-edit` shows a live preview of the panel, and works without the panel plugged in. Drag widgets in, move and resize them, and pick colours, gradients, fonts and data sources. Labels, bars, gauges (arc, car-style dial or analog meter), graphs, the visualiser and images are all there. Hit **Apply to panel** and it's live.

**Running it**

It runs as a user service and can be controlled while running: `akp02d ctl theme <name>`, `akp02d ctl brightness 60`. Save a theme and the panel updates within a second; a theme with a mistake is refused rather than blanking the screen. At 30 fps it uses about 3 ms per frame here.

**Install**

- Arch: `yay -S akp02d` (the driver package includes the udev rule, so no root needed)

- Other distros: `pipx install 'akp02d[editor]'`, then the udev rule and service from the README

Then:

systemctl --user enable --now akp02d

It's my first release, so bug reports, feature ideas and themes are all welcome.