I wrote an unofficial Linux replacement for the RM-Hardware 2.7 service used by the COUGAR POSEIDON VISTEK display.

It currently works with the HWCX USB Display identified as 2c65:1000. I’m looking for owners of the same display/cooler who can test it on different CPUs, motherboards and distributions—especially Intel systems and AMD systems without my sensor configuration.

It does not flash firmware or require a kernel module. It reads standard Linux hwmon, thermal, CPUFreq and powercap interfaces and sends telemetry through hidraw.

Please start with:

./poseidon-display.py --diagnose

Then, if your display has USB ID 2c65:1000:

sudo ./poseidon-display.py --once --debug

When reporting results, please include your distro, kernel, CPU, motherboard, displayed/missing metrics and sanitized debug output.

Repository: https://github.com/VillainRU/poseidon-linux-display

Title, i’ve been looking all over and read that the regular Thrustmaster 16 000M should have linux drivers in their website but it doesn’t seem to have it.

Anyone have any experience with HOTAS and is currently running one with linux?

I recently got a 2010 hp touchsmart from my father, and I've been attempting to daily drive it for fun. It's surprisingly holding up quite well for web browsing, vs code, and my favorite game stardew valley.

Hello! I'm getting to the point where long story short I'm biting the bullet and deciding to attempt a Linux pc build over a Windows one. This is following a number of issues that have finally sent windows over the edge into "more annoying to use" rather than Linux.

I already have suggestions and am studying what Distro I want to use, but that's not my question here!

As someone VERY VERY new to Linux I am blissfully unaware of a LOT of things, but I know in general that not every bit of hardware is created equally! As such, are there any important things I should keep in mind when choosing pc parts for a Linux build that I might not have to keep in mind for something like Windows?

Hey everyone, I made an open source configurator for the AULA F75. AULA only makes driver software for Windows, so if you're on Linux there was basically nothing for changing RGB effects, remapping keys or setting per key colors. This runs in Chrome using WebHID, so no install, just one udev rule.

What works right now:

- all 19 lighting effects with speed/brightness/color

- per key colors (works wired and over the 2.4G dongle)

- remapping both layers

- debounce settings, profiles, backup/restore of your lighting config

Macros can be recorded but can't be saved to the board yet, still working on that. Wireless config also not done, use the cable except for animations.

If you have an F75 (or F87/F99, same chip family) give it a try and let me know if anything breaks

link in comments ;D

Hi,

I'm looking to buy a new personal laptop, and I'm considering the Lenovo ThinkPad T14 G7 AMD with Ubuntu preinstalled. However, I'd like to install Debian instead of Ubuntu and encrypt the drive. Do you foresee any issues with this setup (Firmware/UEFI, WiFi, LUKS)? Is Debian Testing stable enough for a personal laptop, or should I stick with Debian Stable?

Any suggestions would be appreciated.

Thanks in advance.

I’ve been using my laptop with Arch Linux for a year now. Previously, I had no issues adjusting the keyboard backlight, but it stopped working after the release of kernel version 6.18.6. Are there any solutions to this problem? All the fixes I’ve found only work for kernel versions prior to 6.18.5.

I have a strange and reproducible issue with a Kingston KC3000 NVMe SSD on Arch Linux, using LUKS.

After every reboot, KDiskMark shows normal sequential read performance, but sequential write performance is much lower:

SEQ1M Q8T1

Read: ~6260 MB/s

Write: ~3500 MB/s

This is with a 1 GiB test size. I have also tried a 32 GiB test size in KDiskMark, but the write speed is still around 3–3.5 GB/s.

Then I run this fio test:

fio --name=w \

--directory="$HOME/fio-tmp" \

--rw=write \

--bs=1M \

--direct=1 \

--iodepth=32 \

--ioengine=libaio \

--size=8G \

--runtime=8 \

--time_based \

--group_reporting

The fio test itself gets around:

WRITE: bw=6342MiB/s (6650MB/s)

Immediately after running it, KDiskMark now reports:

SEQ1M Q8T1

Read: ~6280 MB/s

Write: ~6500 MB/s

The weird part is that the faster write speed persists. KDiskMark continues to show ~6.5 GB/s writes until I reboot, after which it drops back to ~3–3.5 GB/s again.

Any ideas on what could be causing fio to apparently put the drive/controller into a higher write-performance state?

Pre fio:

Post fio:

EDIT:
It is not until reboot, but rather just a few minutes, i tried disabling the linux nvme power saving mode, but that did not help

Background story: I live in Hong Kong, we can buy and return from taobao fairly easily (think of it as Aliexpress, but target domestic china. In fact many aliexpress products are just marking up one from taobao and ship globally).

I keep seeing many interesting devices on taobao, e.g. i3-1215U 13 inch tablet + stand + keyboard in 3749 rmb ~= 600 usd, or some niche 10 inch laptop, but I solely run linux on my daily drivers, and I never know how they work under linux.

So when I buy my next laptop, I proably will:

• ask the seller about return policy. usually they prohibit windows activision so I should be fine as long as I don't boot windows with wifi connected
• buy it, within the return window (usually 7 days)
  • run linux (haven't figure out this part yet, plan is to run on a bootable usb ssd)
  • test as much as I can (probabaly make a check list)
• if it checks, stay, otherwise return

but if there's enough interest, maybe I don't just have to do this for my next laptop, maybe I can do that on a regular basis, or do by request, and run a review site / youtube channel. How does it sound to you? Any thoughts / questions would help, thanks.

I am struggling to find a mouse that works on Linux.

I have used the MX Master 4 with Solaar but that doesn't seem to work poperly and the functions are limited. Neither does a Logitech G903 work poperly with Piper.

I am on Fedora 44.

Are there mice that work natively or does something web based work well?

EDIT: I may have worded this incorrectly. The mice do work but I can't seem to change their macros.

Picked up an EWEADN H2 wireless mouse and quickly found out — like most sub-$30 gaming mice — it has zero Linux support. The only way to change DPI or adjust polling rate was their official web-based configurator (WebHID), and even that doesn't show battery percentage anywhere in the UI — despite the device actually reporting it over HID the whole time. It's also just not that reliable — in my experience it sometimes fails to load the mouse's actual state properly and shows garbage/stale values instead. So I reverse-engineered the protocol straight out of the web driver's JS and built a native Qt app that exposes the battery reading it was already quietly capable of, plus DPI/rate control, with a bit more consistency about it.

What it does:

• Live battery % + firmware version — not shown anywhere in the official web driver, even though the device reports it
• Polling rate switching (125/250/500/1000Hz)
• Full DPI editor — all 6 slots, sliders + number entry, pick the active slot and how many are in rotation
• Dark mode, fullscreen support
• Ships as a single AppImage, no faffing with dependencies

There's also a headless CLI version (h2_battery.py) if you just want battery % piped into Waybar/Polybar/whatever, without the GUI.

Repo + build instructions: https://github.com/MuhtasimJawad/EWEADN-H2-Control

If anyone here actually owns this mouse, I'd genuinely love to know if it works for you too — I've only been able to test against my own unit, so any feedback (or bug reports) are very welcome. And if you find it useful, a star on the repo helps other H2 owners actually stumble across it.

Edit : As some people in this sub and other places suggested, I am working towards libratbag intregration but before that, I think I should handle the custom keybind feature that both the web driver and libratbag supports. Left this out in the first place cz personally had no need for it. Thanks for your feedback!

Hi everyone,

I built an open-source Linux monitor for the XYZ HYDROTEMP AIO 360 because the manufacturer only provides software for Windows.

The project includes:

- A native Rust/egui graphical interface

- CPU, AMD GPU, RAM and cooling monitoring

- USB HID communication with the AIO

- LCD monitoring support

- A documented protocol reconstructed through testing and USB analysis

- MIT license

I am not a professional software developer. This is a personal learning project created to make the AIO work on my own Linux PC. It was developed with research, hardware testing and assistance from AI tools.

It currently works on my setup:

- Garuda Linux

- AMD Ryzen 7 9800X3D

- AMD Radeon RX 9070 XT

- XYZ HYDROTEMP AIO 360

I am sharing it in case it helps other Linux users with the same hardware. It is provided as-is, without a commitment to ongoing maintenance or support. Forks, adjustments and community improvements are welcome.

Repository:

https://github.com/Abrahan-M/xyz-monitor

Feedback about compatibility with other hardware would be appreciated.

Hello so I'll be studying comp science and i want to buy a new laptop.

I've done a bit of research and I found 2 laptops that I think could work the best for me, those being: the zephyrus g14 or the thinkpad x1 carbon gen 13 aura edition.

G14 would have 2tb SSD and 32GB ram with Ryzen AI 9 HX 370 RTX 5080.
X1 would have 2tb SSD and 64GB ram with  Intel Core™ Ultra 7 265U.

I don't know which one would be better. I kind of wanna go for the X1 more but the gpu is a downside.

I'll be coding on it, rendering 3d, AI/LLM, VMs, etc. I would also like to game but not triple A games and more like: Minecraft/Silksong/Rain World/Roblox Studio/Etc.

I'm also worried bout the G14 battery life (at least 6-8 hours) + fan noise. I would like it to be silent or moderate enough that it won't bother people.

The weight doesn't matter. Also I would like to dual boot windows + linux on it.

With that said I'm not sure if the X1 can handle all the gpu heavier stuff so I don't know what to buy. If you have any better laptop suggestions I would love to hear them.

Hi all, I just got the 2025 Lenovo Yoga Book 9i (the dual 14" OLED one, Intel Core Ultra 7 255H) and I want to move to Linux on it. I know this machine's fancy dual-screen features are Windows-only, and I'm okay losing the gesture/mode-switching stuff. My realistic goal is a clean, usable Linux setup where at minimum the two touchscreens work.

My questions:

1. Which distro would you recommend for this hardware in 2025? I'm leaning toward something with a recent kernel and good hardware support (thinking Fedora or something Arch-based), but open to suggestions. Wayland vs X11 preference for dual touch + pen also welcome.

2. Touchscreen is my must-have. How do I get both digitizers working? I've read the two built-in tablets show up as identical devices and get confused, and that libwacom support had to be added upstream. Is basic touch working out of the box now on newer kernels, or is there still manual config involved?

3. Bonus if you've solved any of these: auto-rotation / sensor-based orientation, pen input + palm rejection, and sleep/wake on the Core Ultra chip.

Has anyone actually daily-driven Linux on this exact 2025 model? Would love a rough guide or even just "install X, expect Y to be broken." Dual-booting with Windows is fine if that's the sane path. Thanks!

I've been working on BoostLock, a small root-only Linux CLI/daemon for keeping CPU boost available during idle periods.

The 0.2.0 release discovers /sys/devices/system/cpu/cpufreq/policy* instead of guessing from CPU model names. Each policy keeps its own frequency limits and effective target, so mixed-capacity systems don't inherit one policy's range. --target auto uses each policy's active upper limit, and numeric MHz requests are clamped per policy.

Before startup changes anything, BoostLock builds the full policy plan and opens every planned write path. If a later write fails, completed writes are rolled back. Controls are capability-driven: a writable boost, EPP, EPB, PM QoS, or cpuidle path is added to the same plan, and an unavailable control is reported as skipped.

I have Intel, AMD, and ARM policy fixtures in the test suite, but I haven't done physical hardware smoke testing across all those drivers yet. If you try it, I'd like to know the CPU, driver, kernel, and what sudo boostlock status --json reports. It needs root and can increase idle power and temperature.

Repo: https://github.com/vindeckyy/boostlock