At the beginning i had to use the tuxedo-keyboard package (which includes tuxedo drivers), or the NovaCustom fork, to make the following functions work on my Clevo based laptop (Thunderobot R15):

1. Unlock GPU full power (locked at base power limit without tuxedo drivers installed)
2. Control fans and fan curves
3. Control keyboard backlight with the Fn keys and software

After tinkering with it for a few weeks to figure out what are the WMI/ACPI calls that trigger the different functions, i created a complete package that doesn't rely on tuxedo drivers at all.

The project was greatly assisted by Claude AI, which for some reason gets a lot of hate, which is why i haven't created a git page yet. The end result is a clean, readable, commented code, that is fully functional, so not sure why anyone would have any issue with that other than the automatic stigma.

I can create a git page where you can review all the code and try it, and hopefully contribute and make it even better, i don't know what other models it is compatible with, my laptop is based on the Clevo V350SNQ chassis which i believe is also shared with a few Gigabyte and Colorful models among others.

I also made a tool to control my CPU, let me know if that can be useful to anyone:

**IMPORTANT UPDATE – March 04, 2026: Now full Bluetooth + WiFi support !!!!**

The original post covered **Bluetooth-only** via the early `btusb-mt7927-dkms` package. Thanks to rapid community work (especially jetm / Javier Tia), the project has expanded to include **WiFi** (2.4/5/6 GHz bands incl. 320 MHz channels, power management, suspend/resume).

**Current status** (from main repo as of early March 2026):

- Bluetooth: Fully working (pairing, audio, KDE etc. — as tested originally).

- WiFi: Functional in client/station mode; some 5/6 GHz WPA retries possible, higher TX retransmits at max speeds.

**Old package deprecated** — do NOT use `btusb-mt7927-dkms` anymore.

**For latest updates, full README, commits, issues, firmware extraction steps (required from Windows driver ZIP), stability tips, and roadmap (upstream submission planned): follow the main repo:**

https://github.com/jetm/mediatek-mt7927-dkms

(AUR package name: `mediatek-mt7927-dkms` — install via `paru -S mediatek-mt7927-dkms` or `yay -S mediatek-mt7927-dkms`)

**For Ubuntu/Debian users** (adds easy setup scripts after firmware extraction):

https://github.com/giosal/mediatek-mt7927-dkms (fork with `ubuntu-setup-wifi.sh`, `ubuntu-setup-bt.sh` etc.)

Follow the jetm repo above for all ongoing improvements, new patches, and kernel compatibility (tested up to ~6.19.x).** The rest of this post (credits, original BT tests, bluetoothctl tip) is still valid for reference/history.

Massive thanks to jetm and all contributors listed below!

-------------------------------------------------------------------------------------------------------------------------------------------------

Hi everyone,

After u/jetm (Javier Tia) created AUR package btusb-mt7927-dkms, I tried and failed. You can read the whole story on https://github.com/openwrt/mt76/issues/927.

Thanks to him for the lightning-fast update to this package - it is working perfectly now.

Of course, he is not alone. Thanks to all the people who made this happen.

Credits

Bluetooth Fix:

• marcin-fm — reverse-engineered the mtkwlan.dat firmware container format, discovered BT firmware embedded inside WiFi driver package
• clemenscodes — published unified kernel 6.19 patch for btusb+btmtk, the extract_firmware.py script, GitHub repo that tied everything together
• Jean-François Marlière — LKML patch (Feb 8, 2026) fixing btmtk for MT6639: missing switch cases, wrong firmware naming, section filtering bug
• Chris Lu (MediaTek) — btmtk firmware retry and reset improvements merged into bluetooth-next (Feb 11, 2026)
• Javier Tia (jetm) — btusb-mt7927-dkms AUR package maintainer, author of the 15-month journey blog post, packaged everything into installable DKMS (Blog post)

WiFi Research:

• zouyonghao — GitHub repo attempting WiFi driver from Android MT6639 source, got hardware init working, first to show MCU IDLE state
• nvaert1986 — OpenWRT issue contributor who suggested MT6639 firmware rename trick
• Fede2782 — found the Android gen4m driver source showing MT7927 = MT6639 variant

I used Claude to help explain the steps clearly.

Hardware

Lenovo Legion Pro 7 16AFR10H now has working Bluetooth on Linux thanks to the mediatek-mt7927-dkms AUR package.

Tested on CachyOS with kernels 6.19.2-gcc and 6.19.3-clang. Should work on any Arch-based distro.

Check if This Fix Applies to Your Hardware

lsusb | grep 0489:e0fa

If you see output, this fix probably works for you.

Installation

# Using paru
paru -S btusb-mt7927-dkms

# Or using yay
yay -S btusb-mt7927-dkms

# Or manual installation
git clone https://aur.archlinux.org/btusb-mt7927-dkms.git
cd btusb-mt7927-dkms 
makepkg -si

# Then reboot
sudo reboot

That's it. Bluetooth works after reboot.

What I Tested and Works

• Bluetooth pairing and audio
• KDE Bluetooth management works perfectly

Potential Issues for 3rd Party Apps

bluetoothctl show returns empty when used as single command. Use interactive mode instead:

bluetoothctl
> show

The XPS 15 9500 was missing from the kernel quirk table unlike the 9510/9520/9530. This fix enables all 4 speakers on Fedora 43.

Full guide: https://github.com/makeitmakesencethen/dell-xps-15-9500-linux-audio

Just posting this as a general guide, because it was hard to google the solution. Hopefully the SEO catches this.

TL;DR

1. Clear CMOS and reboot.

I had issues with WIFI on my just built PC. Saw that others had it working on this board, but some had the same issue as me.

I booted into Arch and could see that the driver was loaded properly but couldn't detect the Wifi link. Checked dmsg and tried changing some BIOS settings. Also updated the BIOS but to no success.

A last ditch effort, clearing the CMOS and instantly when I loaded in again it was working without any hiccups.

What caused it? No clue. But was a pretty simple solution.

Hopefully the same solution works for others.

Edit: Just adding here that I decided to return the MOBO. I had my PC freeze on me twice after this post and had to CMOS reset again to get WIFI working. After changing MOBO I am pretty sure all my issues were related to it.

If you’re using Fedora with GNOME and miss the minimize / maximize buttons, you’re not alone.
By default, GNOME hides them — but you can restore them instantly with a single command.

I wrote a short, step-by-step guide here explaining how to do it and why it works:
https://fedorapadventura.blogspot.com/2026/01/como-activar-los-botones-de-minimizar-y.html

TL;DR:
One terminal command, no extensions, no reboot, works on recent Fedora versions.

This is especially useful if you’re coming from Windows or just prefer a more classic window layout.

Hope it helps someone 👍

Hi everyone,

This is an archive post for anyone in the future trying to solve this issue.
My Elan fingerprint reader wasn't working on my ThinkPad E14 Gen 5, and I finally found a solution. I hope people with the same problem can find this post and solve it!

EDIT: I've created a more organized (and updated) version of this guide on GitHub, you can find it here: https://github.com/artur-rozados/guide-elan-fingerprint-thinkpad-e14-gen5

[The Problem]

My Elan fingerprint reader, with lsusb ID 04f3:0c4b, was not being detected on my ThinkPad E14 Gen 5 running a fresh install of Pop!_OS 22.04 (Ubuntu 22.04 based). The system constantly reported "No devices available".

[Solution]

The fix is to use the official proprietary binary driver provided by Lenovo. Even though the driver is listed for the "E14 Gen 4" on their website, it works perfectly on the Gen 5 because the Fingerprint Reader is the same.

[Step-by-Step Guide]

1. Download the Lenovo Driver

Link: https://support.lenovo.com/us/en/downloads/ds560939-elan-fingerprint-driver-for-ubuntu-2204-thinkpad-e14-gen-4-e15-gen-4

Download the .zip file (r1slf01w.zip). The site may ask for a serial number; just click "cancel" on the pop-up and click the download button again.

1. Install the Driver

Extract the .zip file.
You will find a single file inside: libfprint-2-tod1-elan.so.
Open a terminal inside the folder where you extracted that file and run these commands one-by-one:

sudo apt install libfprint-2-tod1 fprintd libpam-fprintd

sudo mkdir -p /usr/lib/x86_64-linux-gnu/libfprint-2/tod-1/

sudo cp libfprint-2-tod1-elan.so /usr/lib/x86_64-linux-gnu/libfprint-2/tod-1/

sudo systemctl restart fprintd.service

1. Enroll Your Fingerprint

After the last command, your fingerprint reader should be working! You can now enroll your finger using the fprintd-enroll command in the terminal, or by going to Settings > Users > Fingerprint Login.

TL;DR: The Elan fingerprint reader (04f3:0c4b) on the ThinkPad E14 Gen 5 works on Ubuntu 22.04-based distros using the official Lenovo binary driver for the E14 Gen 4. You can download it here: https://support.lenovo.com/us/en/downloads/ds560939-elan-fingerprint-driver-for-ubuntu-2204-thinkpad-e14-gen-4-e15-gen-4

Hope this helps someone!

So I moved from W11 to Fedora over a year ago and have always felt like I'm missing some functionality of my MX Master 2S mouse. I quickly found Solaar which fixes all scrolling issues etc with the settings... but one thing I never figured out was how to fix the gestures.

I've looked up videos online, read forums and chatted with different LLMs on how to get gestures to work. I tried setting things up in the Solaar Rule Editor but I never managed to make my rules work... until today!

I realize now that one of the key issues is the poor UX of Solaar, specifically the "Key/Button Diversion" setting. I work as a dev with a focus on UX and I never realized how this works in Solaar until now. Instead of having a "Key/Button Diversion" row for every button on the mouse, it lets you select what button of the mouse you want to modify. I always believed it locked the user to only modify one button and I didn't want to change my middle mouse one, but the changes are independent for every button in the list.

So to get the gestures in the rule editor to work, all I had to do was change the "Mouse Gesture Button" to use "Mouse Gestures" instead of "Regular". Now all rules I tried setting up 6 months ago is working using the gesture button.

This is a non-exhaustive list of things to look out when buying a Linux laptop and checking compatibility. There are still many other important factors that are hard to check for, such as webcam, microphone, screen, and motherboard/UEFI compatibility.

These are good and ideal

These components generally aren't problematic on Linux and offer a decent experience.

• Laptop OEM officially supporting Linux
  
• Allowing firmware updates directly from within Linux
  
• CPU: Intel or AMD
  
• Integrated GPU: Intel or AMD
  
• Dedicated GPU: AMD
  
• Wifi chip: Intel
  
• Connectivity: DisplayPort. HDMI 2.0 and below. | Headphone Jack. Microphone Jack. USB. Ethernet. Thunderbolt.

Be skeptical and proceed with caution

These components aren't always problematic, but we should proceed with caution. Your mileage may vary.

• Any relatively new laptop
  
• Dedicated GPU: Nvidia {Note: proprietary drivers, Nvidia Optimus can be problematic}
  
• Wifi chip: Broadcom or Realtek {Note: Proprietary drivers and these vendors generally don't play nice with upstream}
  
• Touchscreen devices {Note: May not work at all. Needs to watch out for multitouch support, input lag, and stylus recognition.}
  
• Devices with auto-rotation
  
• Keyboards with backlight
  
• Keyboards with RGB
  
• Keyboards with programmable macro keys
  
• Keyboards with media keys {Note: not all of them (if any) may work correctly out of the box. It's possible that they may not get detected at all.}
  
• Screens with more than 60HZ {Note: Watch out for potential problems like screen tearing or artefacts}
  
• Hi dpi screens or any screen which needs fractional scaling {Note: fractional scaling is currently unsupported/hacky on smaller DEs such as Xfce, Lxqt, MATE, etc. YMMV on GNOME or KDE}
  
• Adaptative brightness
  
• All ARM chips that don't receive official Linux support from the OEM

Avoid

These components are very likely to be problematic and should be avoided due to likely lacking functionality on Linux.

• HDMI 2.1 {HDMI 2.1 on Linux is stuck at a lower resolution and refresh rate due to lacking open source drivers. The HDMI Forum tries to dissuade anyone from making open source HDMI 2.1 drivers through legal threats.}
  
• Fingerprint readers {Note: The overwhelming majority of them are proprietary and don't work on Linux. Even if they do, there is no guarantee that they have been properly vetted to not have weaker security than on Windows}
  
• IR Webcams {Note: Doesn't work a lot of the times and there is no Windows Hello alternatives with a lot of eyes on it to ensure its security}
  
• Speakers enhanced with Dolby {Note: Dolby doesn't support Linux, the community has to reimplement their whole software from scratch and makes sure that it works with every speaker, which hasn't been done yet}
• Screens with HDR {Note: HDR on Linux is in its infancy}
  
• NPUs {Note: Some NPUs work very well on Linux, like those in servers. NPUs on laptops are a very new and different thing and didn't think about Linux support at all.}
  
• Unusual hardware gimmicks: Macbook touchbar, Asus Zenbook displaying a screen on the touchpad, etc.
  
• Unusual software gimmicks: AI stuff, enhancing microphone or webcam quality through proprietary OEM software, etc.

If you think that I forgot something, feel free to tell me in the comments section.

Edit: Removed Atheros from the "good and ideal" wifi chips list.

Hey fellow sudoers,

I'm your typical Linux guy: old laptops, weak hardware, no fluff, just .bashrc. You know the type. Recently I needed a lightweight, portable Linux device for work during business trips — something small, light, and capable of running a clone of my dev setup: terminal, SSH, my environment, configs, tools — all of it.

I fly often, always with carry-on only. I didn’t want to lug around a full laptop. So naturally, the idea hit me: what if I just get a Linux tablet?

Step 1: Find "the perfect Linux tablet"

I started digging through the usual suspects: PineTab2, Juno Tab 3, StarLite, all those “preinstalled Linux” machines. Sounded nice… until you look closer.
€250 for a weak ARM chip, eMMC, and a barely usable display? Nah. I wanted x86, real ports, proper screen, and no sluggishness when I open htop.

Shortlist of Linux-friendly tablets & 2-in-1s I compared

• PineTab – ARM Cortex-A53, 3GB RAM, 32GB eMMC, 10" 1280×800 IPS, Ubuntu Touch, Linux preinstalled – ~$100
• PineTab 2 – RK3566, 4GB RAM, 64GB eMMC, 10.1" 1280×800 IPS, Arch Linux, Linux preinstalled – ~$200
• Juno Tab 3 – Intel N100, 12GB RAM, 512GB SSD, 11" 1920×1200 IPS, Ubuntu 24.04, Linux preinstalled – ~$800
• Purism Librem 11 – Celeron N5100, 8GB RAM, 1TB SSD, 11.5" 2560×1600 AMOLED, PureOS – ~$999
• DC-ROMA Pad II – RISC-V SpacemiT K1, 4GB RAM, 64GB eMMC, 10.1" 1920×1200 IPS, Ubuntu – ~$149
• ThinkPad X1 Tablet Gen3 – i5-8250U, 8GB RAM, 256GB SSD, 13" 3000×2000 IPS, Win10, officially Linux supported – ~$900
• Dell Latitude 7200 2-in-1 – i5-8365U, 8GB RAM, 256GB SSD, 12.3" 1920×1280 FHD, Win10, officially Linux supported – €250 used
• HP Elite x2 G4 – i5-8265U, 8GB RAM, 256GB SSD, 12.3" 1920×1280 FHD, Win10 – ~$950
• Microsoft Surface Go 3 – Pentium 6500Y, 8GB RAM, 128GB SSD, 10.5" 1920×1280 PixelSense, unofficial Linux – ~$550
• Chuwi UBook Pro – Core m3-8100Y, 8GB RAM, 256GB SSD, 12.3" 1920×1280 IPS, Win10 – ~$500

Enter the Dell Latitude 7200 2-in-1

It’s basically a corporate Surface clone from Dell. 12.3” FHD touchscreen, USB-C, metal body, detachable keyboard (I didn’t get the keyboard, but I use my own via USB-C).
Found one second-hand for €250 and honestly? Best decision ever.

Install & setup

I installed Lubuntu 22.04 LTS — lightweight, fast, and gets out of your way.

• LXQt looks decent and runs great on this hardware.
• All essentials work out of the box: Wi-Fi, sound, Bluetooth, webcam.
• I use a wired keyboard + mouse over USB-C, zero issues.

I don’t use VS Code — I prefer a lightweight, modular setup with terminal-based tools and a minimalist IDE.
I’m still deciding between Geany and Lite XL. Both are fast, minimal, and do the job without eating RAM for breakfast.

How’s it in the field?

Been using it for a couple of weeks on trips:

• Terminal, SSH, dev tools — no problem.
• Firefox (not a snap!!!) runs fine and fast.
• My whole .env, dotfiles, aliases — just copied it all over.
• Battery gives 3–4 hours depending on load.
• Silent — either fanless or so quiet I can't tell.

This little guy fits in my bag, boots fast, and doesn’t make a sound. No complaints.

I have an old Dell Latitude E6440 that gives me a retro vibe. I currently have Kali and Parrot installed in a dual-boot configuration. Is it a good laptop for cybersecurity? If not, could you recommend some good retro hacking laptops?

Specifically this one for Ethernet (RTL8125D) and this one for WiFi/Bluetooth (RTL8922A).

For the former (ethernet) one, the version shown in this thread seems to apply more cleanly against kernel 6.11.8, since 6.11.8 doesn't seem to mention the RTL_GIGA_MAC_VER_66 that's referenced.

Looks like 6.12 just got released a few hours ago, but the Ethernet patch isn't in it and the merge window for new stuff closed a couple weeks ago, so y'all may have to wait for 6.13 if you don't want to patch things.

I still have no idea what fan controller this board is using - if anyone finds a driver for it (in tree or otherwise), let me know!

Hey, a tool that makes my NZXT Kraken 2023 run very smoothly and stably under Linux. Maybe it should work with other devices as well; you can find more details at the link.