JetKVM Admin Terminal On Raspberry Pi 3

This page owns the Raspberry Pi side of the JetKVM story.

It does not explain the JetKVM hardware itself, and it does not cover Wake-on-LAN on the Proxmox host. Those already have better homes.

• For the base JetKVM device and its recovery role, start with JetKVM.
• For the host-side remote power-on path, use Wake-on-LAN For Proxmox.

What this page covers is the client-side path: imaging the Pi cleanly, choosing the right Raspberry Pi OS variant, and turning a Raspberry Pi 3 into a small dependable browser terminal for JetKVM.

Why A Pi 3 Still Works

A Raspberry Pi 3 is not a luxury admin workstation. That is exactly why it works here.

JetKVM mostly needs one stable browser session, reliable networking, and a device you can leave near the rack without turning it into another full desktop project. A Pi 3 has enough CPU and RAM for that job as long as the scope stays narrow.

Hardware And Image Choice

Hardware Required

✅ Raspberry Pi 3 Model B or B+
✅ 32 GB or larger microSD card
✅ Wired Ethernet connection
✅ Micro USB power supply for the Pi
✅ HDMI cable, keyboard, and mouse for first setup
✅ Another computer to prepare the microSD card

Raspberry Pi's official setup guidance puts desktop images on at least 32 GB of storage, and the Pi 3 family wants a real power supply rather than a random spare phone charger.¹²

Use Raspberry Pi OS Desktop, Not Lite

For Pi-hole or a headless utility node, Lite is often the right answer. For JetKVM, the browser is the workload.

Raspberry Pi's own setup guidance separates desktop and headless roles for that reason: desktop use expects a graphical environment, while headless use is better suited to SSH-only jobs.¹ When the point of the box is "open JetKVM and work from the console," Desktop is the simpler and more honest choice.

Prepare The Image

Use Raspberry Pi Imager

Download Raspberry Pi Imager from the official software page and use it to select the device, the operating system, and the boot media.¹³

In Imager:

1. Choose device: Raspberry Pi 3.
2. Choose OS: Raspberry Pi OS Desktop.
3. Choose storage: the microSD card you actually want to keep in the Pi.

Then open the customisation flow before writing. Imager can preconfigure hostname, user credentials, Wi-Fi, and SSH at install time, which is much cleaner than improvising on first boot.¹

Recommended Imager Settings

• Hostname: jetkvm-pi
• Username: choose the admin user you will actually keep
• Remote access: enable SSH so the Pi stays manageable without a spare monitor later
• Authentication: prefer SSH keys if you already use them
• Wi-Fi: configure it only if Ethernet is impossible
• Browser choice: pick one default browser and keep the box focused

Ethernet is the better admin path. The Pi 3 supports both wired networking and Wi-Fi, but a JetKVM terminal is easier to trust when the client is not competing with wireless noise.¹²

First Boot

Boot the Pi, complete the desktop setup, and let it settle into one boring job.

The first useful pass is simple:

1. Confirm the Pi has a stable IP on the LAN.
2. Apply system updates once.
3. Make sure SSH works from your main workstation.
4. Open JetKVM in the browser and prove the local workflow before you add anything else.

If you skipped Imager customisation, Raspberry Pi OS will walk you through hostname, browser choice, user creation, and software updates on first boot.¹

Update the box once before you trust it as an admin terminal:

sudo apt update
sudo apt full-upgrade -y
sudo reboot

Daily-Use Best Practices

• Keep JetKVM as the primary browser job on this Pi.
• Use wired Ethernet whenever the Pi can live near the switch.
• Leave SSH enabled so you can repair the Pi without borrowing a keyboard and monitor again.
• Avoid turning the device into a general browsing or download machine.
• If it starts feeling slow, close background tabs before you blame JetKVM.

The Pi 3 is fine as a focused terminal. It only becomes frustrating when you ask it to be five machines at once.

When To Outgrow It

Move up to a newer Pi or a thin client when the job changes from "dedicated JetKVM terminal" to "general admin workstation." The moment you want several heavy dashboards, multiple browsers, video calls, and the JetKVM console all at once, the Pi 3 stops being the right tool.

Related Topics

• JetKVM - the base device workflow, cabling, first access, and recovery role.
• Wake-on-LAN For Proxmox - the host-side power-on path when JetKVM should wake the machine instead of only watching it stay off.
• Raspberry Pi - the rest of the Pi-specific infrastructure guides.