/ Hardware Engineer · Linux Specialist · Embedded Systems
Aineas
Giannakoulias
I fix what others give up on — then build something better.
aineas@cv:~$ ./boot.sh [ OK ] Hardware interface: detected [ OK ] Linux kernel: CachyOS / 6.x.x-cachyos [ OK ] Repair database: 65+ devices loaded [ WARN ] Windows tolerance module: active (ntlite-patched) [ OK ] Local LLM: Ollama · running [ OK ] EEPROM programmer: CH341A · standby [ NOTE ] Help-desk module: NOT LOADED (by design) [ INFO ] Career objective: keep systems alive until death [ READY] Accepting opportunities... _
Scroll to explore ↓
// Section 01
Hardware
Mastery
Started at 12. Paid clients by 16. Component-level repairs on laptops, phones, and desktops — if it has a PCB, I've probably fixed it.
HP, Dell, ASUS — from screen swaps and hinge repairs to DC jack replacement and thermal paste renewal. 65+ units total, 97%+ success rate.
Hover to see stats
| Brand | Units | Rate | Common Fix |
|---|---|---|---|
| HP | 40+ | 100% | Screen, DC jack, hinge |
| Dell | 25+ | 100% | RAM, SSD, thermal |
| ASUS | 10+ | 100% | Custom builds & tune |
| Compaq | 1 | Retired | Kept alive for years — died of old age |
The Compaq earned its retirement after years of faithful service. Some things you keep alive as long as possible, then let go with respect.
KSGER T12 station. Replaced screen driver transistors on a 16-year-old personal laptop to bring it back from the dead. It still runs.
Hover for tools
- KSGER T12 temp-controlled iron (leaded solder)
- SMD transistor replacement on laptop PCBs
- Connector and port re-soldering
- EEPROM read/write via CH341A programmer
- Multimeter diagnostics
- ESD mat + wrist strap (always)
- iFixit precision screwdriver kit
- Pentalobe, tri-wing, Torx sets
Multiple custom AMD/Intel PC builds — every single one still running. No post-build failures. Cable management, BIOS config, and stress-testing included as standard.
Hover for build process
- Part selection: AMD/Intel + Gigabyte/ASUS boards
- Assembly with ESD precautions
- BIOS/UEFI tuning (XMP, fan curves, boot order)
- Stability testing: MemTest86+, Prime95, FurMark
- OS install: CachyOS (preferred) or modded Windows
- Driver audit and clean install
- Cable management: zip-tie military-grade
- Zero. Post-build. Failures. Ever.
iPhone and Android screen replacements. LCD and digitizer work. One Lenovo tablet that taught me the limits of component-level repair (it didn't survive, but I learned).
Hover for details
- iPhone screen replacements (multiple models)
- Android screens — Samsung, Xiaomi, generic
- Battery swaps and charging port replacement
- Software flashing and recovery
CH341A EEPROM programmer for BIOS flash and recovery. Reverse-engineered EC registers on my Tongfang laptop to take full control of what the manufacturer won't let you touch.
Hover for detail
- CH341A programmer: read, write, verify BIOS chips
- BIOS recovery on bricked / corrupted boards
- BIOS modification and custom option unlocking
- Embedded Controller protocol reverse-engineering
- EC register mapping via ACPI table analysis
- Direct I/O port communication (0x62/0x66)
- Fan curve and power limit manipulation via EC
No tool? Build one. No documentation? Reverse-engineer it. No precedent? Figure it out anyway. This is how I've operated since age 12 — pragmatism over theory, every time.
Hover for approach
- Diagnose at component level, not just symptom level
- Use AI as a force multiplier, not a replacement for thinking
- If the docs are wrong, the hardware tells the truth
- Open-source the solution so no one else fights it again
- Document nothing in meetings — everything in commit history
- If I've fixed it once, it won't break the same way twice
// Section 02
Linux &
Infrastructure
8 years of Linux use. Not as a tool — as a lifestyle. Distro-hopped my way to CachyOS, running Docker, QEMU, local LLMs, game servers, and VPS infrastructure along the way.
- Game servers: Minecraft (Raspberry Pi 4B), Rust, SCUM (SteamCMD)
- VPS management: deployment, hardening, maintenance
- Home media: TrueNAS / OpenMediaVault (past) → Stremio + Real-Debrid
- Containerisation: Docker (experienced the pain, understand the internals)
- Virtualisation: WSL, Wumu, QEMU/KVM — including nested VM setups
- Local AI: Ollama + OpenCode — LLMs running privately, no API costs
- NordVPN kill-switch — managed complex routing for QEMU networking through VPN
Ran an AI container (OpenClaw) inside QEMU while hosting a local LLM on the host — all traffic through NordVPN kill-switch. NordVPN's TUN adapter fights QEMU's virtual bridge by design. Required manual iptables rules, custom network namespaces, and 6 hours of debugging across 4 docs and 5 AI instances. Qwen gave up. I didn't.
// Section 03 · Open Source
Tongfang RGB
Controller
When manufacturer software is locked-down and poorly built, the correct response is to reverse-engineer the firmware and write something better. So I did.
Tongfang and Aistone laptops are enthusiast-grade machines — performance-focused, price-competitive, and deeply niche. The official control software is terrible. I reverse-engineered the Embedded Controller firmware protocol by analysing ACPI tables and diffing EC register states, then built an open-source replacement that gives the user actual control over their own hardware.
The control centre was built through hands-on reverse engineering — analysing hardware behaviour, cross-referencing documentation, and a lot of trial and error. The internals are documented in the repo for anyone working with the same hardware. Implementation details are kept within the project itself rather than broadcast publicly.
Currently 0 stars — Tongfang laptops are a niche enthusiast product and the repo hasn't been advertised. The code exists and works. Discovery is the next step.
// Section 04
Technical Skills
Self-taught across hardware, Linux, and systems. Depth over breadth — I specialise in what I can do at a component or kernel level, not what I can Google.
// Section 05
I Don't Just
Use AI — I Build It.
Most people use ChatGPT as a search engine. I've built a self-improving agent that adapts based on feedback loops — and I use it as a daily productivity multiplier.
// Autonomous Learning Agent — Architecture User submits prompt / task ↓ Agent processes with current reasoning chain ↓ Output generated ↓ User evaluates: [+ positive] or [- negative] ↓ Feedback loop triggers analysis: ├─ What worked in this interaction? ├─ Where did reasoning break down? └─ What should be weighted differently? ↓ Agent behaviour adjusts for next task ↓ Compounds over time — gets measurably better // Implementation details: proprietary — not yet open-sourced
- Runs entirely locally — no cloud dependency, no API cost
- Integrated with existing local LLM infrastructure (Ollama)
- Feedback mechanism: manual rating per session outcome
- Persistent memory across sessions
- Full privacy: nothing leaves the machine
- Implementation details proprietary — open-source release TBD
- Understands AI beyond "prompt and hope"
- Engineers tools — doesn't just consume them
- Grasps feedback loops and reinforcement learning concepts
- Optimises for efficiency without relying on paid APIs
- Already working in the way IT roles will require in 2026+
// Section 06 · Work Style
Systems Over Support.
Depth Over Noise.
I specialise in infrastructure and hardware — not end-user hand-holding. Here's the honest picture of where I add the most value.
Give me root access, clear objectives, and space to work — and I'll keep your infrastructure running while documenting everything so the next person understands it. I don't explain where the Windows key is. I harden the endpoint so the password reset ticket never gets raised.
Small teams, async communication, clear scope. Remote-first globally. On-call capable. Give me the problem and stand back.
Hover for detail
- Team size: Solo or 2–8 people (clear ownership)
- Communication: Async preferred, Slack/chat over meetings
- Supervision: Objectives in, results out — no micromanagement
- Remote: Worldwide, any timezone, immediate availability
- On-call: Yes — including nights and weekends, if compensated
- Reporting: Detailed logs and dashboards, not standup theatre
Hardware repair, Linux administration, IT infrastructure, embedded systems, field technician work. Anything with real machines, real stakes, and real problems.
Hover for role list
- Hardware Repair Technician (Bench or Field)
- Linux Systems Administrator
- IT Infrastructure Engineer
- Embedded Systems / Firmware Technician
- DevOps Engineer (hands-on, not pure-cloud)
- Security Operations (offensive/defensive hybrid)
Based in Greece. Remote worldwide in English or Greek. Will relocate for the right opportunity and package.
Hover for details
- Remote (worldwide): Immediate — any timezone
- On-site Greece: Immediate
- Relocate EU: 2 weeks notice
- Relocate Global: 1 month + relocation package
- Languages: Greek (native), English (fluent)
- Work auth: EU (Greek citizen)
// Section 07
Let's Work
Together
If you have a role where keeping machines alive matters more than keeping users happy — reach out.
- 18 years old — started repairing devices at 12, Linux at 10
- Self-taught across hardware, firmware, Linux, and AI tooling
- 65+ devices repaired, zero custom PC build failures
- Open-source BIOS/EC reverse-engineering project on GitHub
- Local AI infrastructure running 24/7 (Ollama, OpenCode)
- Available remote worldwide — English or Greek
- SAEK-enrolled (military service deferment, Greece)
- Adapt or die. Always have.