Build the minimal Debian SD image¶
For a complete Pocket system on SD or internal storage, start with
N810 Setup. That guide uses n810-build-sd and
n810-build-internal, with a kernel matched to each kit's partition identity.
The commands on this page build the older minimal Debian image, with
different output files and a separate desktop installation. Do not mix the
minimal image's write/boot commands with a complete Pocket kit.
Build a personalized Debian armel SD image, write it to a removable card, and boot the N810 temporarily with the matching kernel. Keep the stock boot route available during initial checks.
The image contains Debian, kernel modules, device firmware, USB networking, touch setup, the internal keyboard layer, power indicators, and zram. Pocket, its graphics release, and desktop autostart are still separate installation steps. Building this image does not establish a complete first-install Pocket desktop.
The Makefile runs the SD builder and guarded card writer. For an install without an SD card, use the tested macOS writer and kernel-flash steps in N810 Setup. The app's RAM-installer route still needs hardware acceptance.
Before you begin¶
Have the following ready:
- An N810 (RX-44) and its power supply.
- Docker with Linux containers and ARM emulation, Make, and a repository checkout. Docker Desktop supplies ARM emulation on macOS.
- Your Ed25519 SSH public key (
id_ed25519.pub). - A removable SD card larger than the selected image and a card reader.
- A Linux host or USB-attached Linux VM with
0xFFFFfor the tablet boot step.
The default image uses a 2 GiB root partition. The first build downloads the kernel source, compiler packages and Debian packages. Allow enough space in Docker for those inputs and the generated image.
1. Build the image¶
From the repository root, run:
The command downloads the pinned Wi-Fi and Bluetooth firmware and verifies the
hashes. It caches verified downloads in the Docker volume n810-sd-firmware.
For firmware from your own Maemo backup, add its directory:
That directory can contain initfs.jffs2 and optionally rootfs.jffs2 (data-only
JFFS2 partition images), or extracted 3826.arm and bc4fw.bin files. The builder
reads it without modifying it. Available backup files take precedence over
public downloads. Add SD_FIRMWARE_OFFLINE=1 to require firmware from the backup
or verified cache. Debian package downloads still need network access.
See the firmware reference for exact sources, accepted formats and license findings.
When prompted, enter and confirm a password for the nokia account. Use this
password for console login and sudo. SSH uses your supplied public key.
Wait for the export completion message. The kit is in dist/n810-sd/:
n810-sd.img: the complete card image.n810-kernel-ramboot.bin: the matching kernel for temporary boot.n810-root.ext4andn810-modules.tar.gz: the filesystem and modules.BUILD.json,FIRMWARE.json,INSTALLATION.json, andBOOT.txt: checksums and kit metadata.
Keep this directory private; the filesystem contains your account's password hash. Choose a new directory for subsequent builds. For a 4 GiB root partition:
make sd-image SSH_PUBLIC_KEY="$HOME/.ssh/id_ed25519.pub" \
SD_OUTPUT="$HOME/n810-sd-personal" SD_SIZE_MIB=4096
SD_SIZE_MIB accepts 1024 through 8191. SD_USER changes the account name and
SD_JOBS sets kernel compilation parallelism. Docker reuses matching compiler
and kernel layers. Use the chosen output directory in the following commands.
2. Write the card¶
On macOS, identify the removable whole disk with diskutil list and diskutil
info diskN. From the repository root, run a read-only preflight, replacing
diskN with the current identifier:
Check the reported card size and name. To erase and write that card:
The writer checks the image checksum and removable SD identity, then requires
you to type ERASE diskN. It unmounts, writes, and ejects the card. The disk
identifier can change after reconnection. Never reuse it without checking.
On Linux, use the following manual path:
On the Linux host, insert the card and identify its whole-disk path with
lsblk. Unmount its partitions. Confirm the disk path before writing; this
operation overwrites the card. For a card identified as /dev/sdX:
Reinsert the card. Confirm that it has one ext4 partition, then compare its UUID
with BUILD.json. Run sudo e2fsck -fn /dev/sdX1 on the unmounted partition.
A card exposed as /dev/mmcblkN uses that whole-disk name for writing and
/dev/mmcblkNp1 for the partition check.
3. Boot the matching kernel¶
Insert the card into the N810 and connect it to the Linux flasher host.
Put the tablet into Nokia update mode. Check that 0xFFFF identifies an RX-44,
then choose either a temporary RAM boot or a permanent kernel flash. The first
choice leaves the stored boot kernel alone; the second replaces it. Both use the
matching root image on the removable card and leave the internal eMMC partition
table alone. Check that the kernel's root device in BUILD.json resolves to the
prepared card on this tablet before a permanent flash.
For a temporary RAM boot:
This is the documented temporary RAM-load operation. For a permanent kernel flash and reboot, use the documented flash operation:
The kernel expects the SD root at/dev/mmcblk0p1. If boot stops at root mounting,
check the tablet's card enumeration and the matching kernel package before
proceeding.
4. Set up touch and log in¶
First boot opens touchscreen setup on the tablet's console. If an existing
Maemo pointercal file is available, move the stylus over the preview targets
press Enter to finish the preview, and confirm whether the pointer follows it accurately. Otherwise, press Enter
and tap the five white crosses as they appear. The tool checks the fitted
mapping and saves a Pocket calibration profile.
You can type skip to continue to login and calibrate later. Log in as nokia
with the password chosen during the build. To repeat setup:
To collect a fresh calibration, run sudo n810-setup-touch --recalibrate from
the tablet's text console. The tool temporarily owns the framebuffer; close
any graphical desktop before running it. After login, check uname -r and
ls /lib/modules against the kernel release in BUILD.json.
The first-boot input reference explains which Maemo settings can be reused, where the calibration profile is saved, and the remaining wireless firmware and device checks.
5. Connect over USB SSH¶
If the tablet exposes usb0 at 192.168.10.1, identify the corresponding Linux
host interface with ip -br link. Configure that interface:
sudo ip address add 192.168.10.2/24 dev <HOST_USB_INTERFACE>
sudo ip link set <HOST_USB_INTERFACE> up
ping -c 3 192.168.10.1
At the tablet console, run
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub. Compare that fingerprint with
the first SSH connection prompt on the host, then connect:
The first boot of this generic image still needs attended tablet acceptance. Use the status page to check the current installation coverage.
6. Configure Wi-Fi and Bluetooth¶
The image includes the firmware, p54 and Nokia Bluetooth modules, BlueZ, and Wi-Fi configuration tools. On the tablet, check the detected interfaces:
On your computer, create wpa_supplicant-wlan0.conf with your own two-letter
country code, SSID and WPA-Personal password. For example, replace each
placeholder in this template:
country=YOUR_COUNTRY_CODE
network={
ssid="YOUR_NETWORK_NAME"
psk="YOUR_NETWORK_PASSWORD" # Replace this example locally.
key_mgmt=WPA-PSK
}
Keep that file private. From the computer, copy it over the verified SSH link:
On the tablet, install it with owner-only permissions, remove the transfer copy, and start the managed service:
sudo install -d -m 700 /etc/wpa_supplicant
sudo install -m 600 ~/wpa_supplicant-wlan0.conf /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
rm ~/wpa_supplicant-wlan0.conf
Use bluetoothctl to power on the controller and pair your devices. If a
controller is absent, inspect systemctl status n810-bluetooth-address.service
and journalctl -u bluetooth.service along with the kernel log. The firmware
reference records the startup dependencies and device-validation boundary.