IMD SolutionComputing LibraryShop main store

How-to

Add a Linux desktop and browser to a Debian edge PC

Operating systems on the plant floor Published 7 min read

Short answer

Install GNOME on the running system: run sudo apt update, then sudo apt upgrade, reboot, then sudo apt install gnome. The download is about 1-2 GB and the procedure needs 10 GB of free disk; GNOME Web comes with it. Reinstall Debian with the graphical installer only when you are rebuilding the box anyway.

On this page
  1. Which path should I take: GNOME install or Debian reinstall?
  2. How much disk space and memory does GNOME need?
  3. What has to work on the network before the install?
  4. How do I install GNOME on the running Debian system?
  5. What does the reboot stop on the box?
  6. When is a graphical Debian reinstall the right call?
  7. How do I verify the desktop, browser, and package path?
  8. Questions asked

Install GNOME on the Debian system that is already running: sudo apt update, then sudo apt upgrade, then sudo reboot, and finally sudo apt install gnome. The documented procedure downloads about 1-2 GB of packages, needs the free disk sized in the section below, and brings GNOME Web as its browser. A graphical Debian reinstall produces a desktop too, but it replaces the operating system, so reserve it for a box you are rebuilding anyway. The sections below give both paths, the numbers to check first, and how to verify the result.

Which path should I take: GNOME install or Debian reinstall? #

Install GNOME on the existing system whenever that system is healthy and worth keeping: it takes about 1-2 GB of downloads and one block of free disk, sized in the next section, and it preserves your installed packages, configuration, and collected data. Take the reinstall only when a clean start is already the plan.

GNOME on the existing system Graphical Debian reinstall
What you run sudo apt install gnome Bootable USB, then the "Graphical Debian Installer"
Browser included GNOME Web Firefox
Free disk See the disk-space section below The same figure
Internet during setup Required; 1-2 GB of packages download Optional; answer yes at "use a network mirror"
Effect on the box Updates packages and adds the desktop Replaces the operating system installation

If the box boots, its package path works, and its data matters, install GNOME: it is the shorter path and it touches nothing you have already built on the system. Reinstalling is the right call for wrong partitioning, a contaminated image, or a fresh deployment where the desktop belongs in the build from day one.

How much disk space and memory does GNOME need? #

Plan for 10 GB of free disk and an internet path that can carry 1-2 GB of packages; Debian's installer baseline is 780 MB of RAM and 1160 MB of disk for a normal installation, and the GNOME desktop's comfortable-use recommendation is 2 GB RAM and 20 GB disk.

The proportions matter more than any single figure. Debian's installation manual puts a standard amd64 installation, with the standard package set and the default kernel, at 843 MB of disk, so the base system is small and the desktop task is what the free-space figure above protects. The installer minimums are for getting Debian onto the disk at all, not for running a desktop beside an edge workload.

Worked example, with example inputs. Box A has a 60 GB SSD with 24 GB already used: 60 GB - 24 GB = 36 GB free, comfortably past the requirement, so install GNOME on Box A. Box B has a 16 GB eMMC module with 9 GB used: 16 GB - 9 GB = 7 GB free, which is 3 GB short, so leave Box B headless and browse from a management PC, or move it to larger storage first.

For memory, commit to these bands: 4 GB runs the desktop and the edge workload together; 2 GB is the comfortable-use line, so keep one browser window open and nothing else; below 2 GB, stay headless. Whatever space remains after the desktop lands still has to carry logs and collected data, and sizing that side is its own calculation, covered in choosing edge storage for high-rate vibration data.

What has to work on the network before the install? #

The download rides one chain: an active physical link, working addressing and a route to the internet, name resolution, and a reachable Debian mirror, and you should check them in that order before running any GNOME command. A fault at any layer stops the job with the same visible symptom: no packages arrive.

Path layer How it fails What to fix
Physical link No traffic leaves the interface Cable, switch port, interface link state
Addressing and route Local communication works, repositories unreachable Interface addressing and the default route
Name resolution Repository hostnames do not resolve The configured name-resolution path
Package source sudo apt update cannot retrieve index data The configured Debian sources

Do not troubleshoot GNOME while sudo apt update still fails. Fix the chain first, then install.

How do I install GNOME on the running Debian system? #

Four commands do it, in this order: sudo apt update, then sudo apt upgrade, then sudo apt reboot, no — sudo reboot, then sudo apt install gnome, and the documented run reached the graphical login without any systemctl set-default step.

  1. sudo apt update refreshes the package index. If nothing is pending you see "All packages are up to date." Errors here belong to the network layers above; fix them before moving on.
  2. sudo apt upgrade applies the pending updates. Review the transaction and let it finish completely, because an interrupted upgrade is not a sound base for the desktop task.
  3. sudo reboot restarts the box after the upgrade and before GNOME goes on. Schedule it as covered below.
  4. sudo apt install gnome resolves the GNOME 3 and GNOME Classic desktop environments and their dependencies. Keep power and network connected until package configuration finishes.
  5. Log in at the graphical session and open GNOME Web.

If APT completed without errors but no login screen appears, the packages are in and the fault is in the display or login session; check first that a display is actually attached, because a box that has always run headless has never needed one. One security note: a browser adds an outbound path from a plant box, so keep that desktop on the management network, not on the process VLAN.

What does the reboot stop on the box? #

The sudo reboot between the upgrade and the GNOME install stops everything on the box, including Node-RED flows, Python scripts, brokers, and logging to the historian, so schedule it like any other controlled plant restart. Nothing collects or forwards while the box is down.

Container restart policies and service units should bring the pieces back on their own, so confirm each workload resumed rather than assuming it. If the box runs Python and Node-RED beside PLC code on an edge PC, verify both came back before you call the restart done.

When is a graphical Debian reinstall the right call? #

Choose the graphical Debian reinstall when the box is being rebuilt anyway, such as wrong partitioning, a contaminated image, or a fresh deployment, because it replaces the operating system, needs the same free-disk headroom, and ships Firefox instead of GNOME Web.

  1. Back up everything that must survive: configuration, collected data, licenses.
  2. Write the Debian installer to a bootable USB and boot the box from it.
  3. Pick the "Graphical Debian Installer" option when the installer starts.
  4. At "Configure the package manager", answer yes to "use a network mirror" if the box will ever reach the internet, because a no here leaves the installed system unable to run sudo apt update and sudo apt upgrade properly later.
  5. Finish the installation, boot, and log into the desktop; Firefox is the included browser.

Internet connectivity is optional during the install, but the mirror answer is not optional in its effect: it decides whether the installed system is prepared to pull packages online at all. Re-imaging several boxes goes faster with a PXE server than with a USB stick at each one, and deploying FOG Project on Debian for PXE imaging walks through that route. The release choice itself is covered in choosing an operating system image for an industrial PC; if you switch distributions, take its LTS release.

How do I verify the desktop, browser, and package path? #

Verify three things once the box comes back: a normal boot with no half-finished package state, a graphical login where keyboard, pointer, and display respond, and a clean sudo apt update that proves the repository path still works end to end.

Open the browser, GNOME Web on the package path or Firefox on the reinstall path, and load a page through the same network the download used. If MQTT sensor data does not reappear in Node-RED after the restart, treat that as its own fault and work it separately; fixing MQTT sensor data missing in Node-RED covers that diagnosis.

Questions asked

Do I need a systemctl set-default command to get the graphical login?

No. In the documented run, sudo apt install gnome after the reboot brought up the graphical session without a separate systemctl set-default step. If APT finished cleanly but no login screen appears, separate the two faults: the packages are in, so inspect the display and login session state instead of repeating the download.

Can I install GNOME on a 16 GB eMMC edge PC?

Not with a used system on it. A 16 GB disk with 9 GB already used leaves 7 GB free, which is 3 GB short of the free-disk requirement. Keep that box headless and browse from a management PC, or move the installation to larger storage first and then add the desktop.

What happens if I answer no to the network mirror during a reinstall?

The installed system comes up without an online package source, and later sudo apt update and sudo apt upgrade commands fail to fetch anything. Answer yes at the Configure the package manager screen whenever the box will ever reach the internet; the fix afterwards is correcting the configured package sources.

Which browser do I end up with, and can I change it?

The GNOME package path includes GNOME Web; the graphical Debian reinstall includes Firefox. Either way the browser is just a package: add another one through the same APT path afterwards and count its download inside your free-space budget, which is one reason to treat the requirement as headroom rather than a target to fill.

Keep reading

  • How-to

    Configure IP networking on an edge PC with no SSH access

    A new edge PC that leaves the factory with DHCP and static addressing disabled has no IP address, so SSH cannot connect to it. Do the first configuration at a keyboard and monitor: set X1 to DHCP and the plant-side port to the planned static address, restart networking, then confirm both addresses with nmcli device status and ip a before opening SSH or browser management on port 9090.

    Operating systems on the plant floor

  • How-to

    Read CPU temperature on a Linux edge PC with lm-sensors

    Install lm-sensors, run sensors-detect accepting the Intel thermal sensor, then read the value with sensors or watch sensors. With nothing installed, cat /sys/class/thermal/thermal_zone*/temp and divide each millidegree value by 1000 for degrees Celsius. Zone numbers identify board temperature inputs, not proven CPU cores, so confirm which zone tracks processor load before you label it CPU temperature.

    Operating systems on the plant floor

  • How-to

    Install Node-RED Natively on a Linux Edge Computer

    Install Node-RED directly on the Debian-based edge computer rather than in Docker: give the login account sudo, install build-essential, git and curl, then run Node-RED's official Debian install script and start the runtime without the -v flag. The script installs Node.js, npm and Node-RED and registers a systemd service, so the runtime also starts at boot.

    Edge computing and IIoT