Free up a lot of memory on the Raspberry Pi Zero by disabling the desktop

Did you install the full version of Raspian on your Raspberry Pi only to realize that you are going to run it as a headless appliance with no HDMI attached to it?  It turns out you can disable that desktop which will free up enough memory to leave almost 5x available to programs.   

Disable the Desktop using raspi-config

1. Verify the free memory available after a restart with `free -m`
2. Launch the shell-based configuration tool to disable  the desktop with `sudo raspi-config`
3. Move through the screens shown below.
3. Reboot
4. Verify the free memory after a restart with `free -m`

Raspi-config

Enabling and disabling the desktop involves changing the System Options

We're going to change the boot/Auto Login 

Select one of the console options.  You can always restore desktop access later by picking one of the Desktop options

The desktop should be disabled upon the end of the next restart.

Before and After disabling the Desktop

Disabling the desktop frees up almost 1/2 the RAM On a Raspberry Pi Zero

Raspberry Pi Zero running the desktop

total used free shared buff/cache available
Mem: 429 172 61 4 196 202
Swap: 99 6 93    

Raspberry Pi Zero with the desktop disabled.

total used free shared buff/cache available
Mem: 429 49 265 1 113 329
Swap: 99 0 99    

YouTube video of this article


Revision History

Created 2022 11

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more