hardware-appeal
A request for one working machine, kept public so it can be checked rather than taken on trust. Repo ↗
My only machine, a Dell Latitude E5440 from 2014, died. This repo is the whole ask: a request for a working computer, kept in public so it can be checked rather than taken on trust.
Page: https://pdev-labs.github.io/hardware-appeal/ Profile: https://github.com/pdev-labs Contact: pdev.labs@gmail.com
What broke
| Machine | Dell Latitude E5440 |
| Built | 2014 |
| Status | Dead — board failure |
| Detail | 4th-gen Core i5, DDR3, spinning disk. Motherboard is gone. Nothing recoverable. |
What I do with a machine
I am 16. Solo maintainer: I write Linux-on-Android tooling, Rust clients, ESP32 firmware and Python packaging. Everything is public, and every release is built by CI I wrote. There are 30 public repositories of my own on the profile. These are the ones a working machine unblocks:
- Linux-For-Android — Runs a real Linux desktop (Ubuntu, Debian, Kali, Arch, Fedora, openSUSE, Void, Alpine) on Android through Termux, with no root. Verified across Android 5.1 to 16. (Shell · 5 stars)
- pocketdesk — Streams a Linux desktop to a phone and drives it remotely. Rust host, native Android client, built end to end in GitHub Actions. (Rust)
- linux-on-esp32 — A NOMMU Linux environment for the ESP32-S3 microcontroller, with Wi-Fi and I2C support. (C)
- NanoNAS-S3 — ESP32-S3 network storage with a Material UI, chunked background copies and fast SDMMC I/O. (C++)
- FluxMedia — Published Python module and PyPI package: a LAN QR share portal plus a media player. Shipped with AUR, deb and rpm packages. (Python · 1 star)
- pdev — A small programming language written in Python with Hinglish keywords: a CLI, worked examples, tests and a VS Code extension, under the GPL. (Python)
What would fix it
Minimum
- x86-64, 4 cores or better
- 16 GB RAM (8 GB is workable, 16 GB removes the ceiling)
- NVMe SSD, 256 GB or larger
- Runs Linux with no out-of-tree driver fights
Helpful
- 32 GB RAM (local Android emulator + Rust release builds at the same time)
- USB-C with DisplayPort alt mode
- User-replaceable battery and SSD
Not asking for the newest or the fastest. Refurbished, previous-generation, or review-unit hardware all do the job.
How this is being built right now
Nothing above was built on a laptop. The desktop comes from Linux-For-Android, a full Linux environment running on Android with no root. When something needs a real GUI session, it runs inside a GitHub Actions runner provisioned by Free-Github-Actions-RDP. Both are my own projects, so the workaround is part of the portfolio rather than an excuse.
What I give back
- Named credit in the repositories. Whoever provides the machine is credited by name in the README of every repository it unblocks, and at the top of the build log. Not a temporary banner that quietly disappears — it stays there.
- A public build log. What shipped each week, what broke, and how long each build took — on the actual hardware.
- A written Linux compatibility report. What worked out of the box, what needed a quirk, and what I would tell the next person who buys it. Published in full, with attribution, and nobody gets to edit it first.
- Upstream fixes. Every driver quirk, packaging bug and kernel problem I hit turns into a patch or a bug report rather than a tweet.
- It stays in circulation. If the machine is replaced later, it goes to another maintainer, not into a drawer.
Scope
This is not a mailing list and there is no form. One message per organisation, sent once, to the address that organisation publishes for this kind of enquiry. No follow-ups unless someone replies.
<sub>Page figures are pulled from the public GitHub API on 2026-11-15. Generated by build.py — edit appeal.toml, not this file.</sub>