Raspberry Pi Zero (raspberry-pi0)

Features
USB Networking	Works
Internal storage
SD card
Screen	Works
Multimedia
3D Acceleration
Camera Flash
Connectivity
WiFi	Works
Bluetooth	Works
NFC
Miscellaneous
FDE
USB OTG
HDMI/DP
Sensors
Magnetometer
Ambient Light
Proximity
Hall Effect
Haptics
Barometer

Raspberry Pi Foundation Raspberry Pi Zero
Manufacturer	Raspberry Pi Foundation
Name	Raspberry Pi Zero
Codename	raspberry-pi0
Released	2015
Type	single board computer
Hardware
Chipset	Broadcom BCM2835
CPU	ARM1176JZF-S @ 1 GHz
GPU	Broadcom VideoCore IV
Display	HDMI port
Storage	MicroSDHC slot
Memory	512 MB
Architecture	armhf
Software
Original software	Raspbian
postmarketOS
Category	testing
Pre-built images	no
Mainline	yes

WARNING: This device is not recommended for future use with postmarketOS due to its armhf architecture. Alpine Linux (the distribution that postmarketOS extends) pmaports#599 has been considering dropping it.
The processor of the device may support the armv7 architecture. If so, you can modify the device package and change the architecture accordingly.

Users owning this device

Blacklight
Drebrez
Halamix2
Lloir
Maciej (Notes: Not used currently)
Maff (Notes: 0 and 0W units, inc. one WD Labs PiDrive)
Neko (Notes: Two 0Ws floating around, one 0W is a USB gadget - maybe a perfect use for pmOS)
PiotrZPL (Notes: Security camera.)
Segfault (Notes: Zero W)
TravMurav
ZeroCool32 (Notes: Zero W, rev1.3)

Contributors

drebrez

Installation

1. Follow the steps on Installation_guide#Initialization

2. Choose the raspberry-pi0 device

3. Start the build process and install the completed image to a sdcard (replace /dev/sdX with the device for your sdcard)

$ ./pmbootstrap.py install --sdcard /dev/sdX

4. Place the sdcard into the Raspberry Pi and boot it

5. Connect a microUSB cable to the central microUSB port (with the USB label)

6. Let the RPI boot and then you should be able to connect using SSH

$ ssh user@172.16.42.1

Issues

3D Acceleration (GPU)

The vc4 module fails to load:

# dmesg | grep vc
[    0.000000] Kernel command line: 8250.nr_uarts=1 cma=256M bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:3D:4B:57 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=tty1 console=ttyS0,115200
[    0.674097] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[    0.675232] vc-sm: Videocore shared memory driver
[    0.716056] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    0.717968] [vc_sm_connected_init]: start
[    1.300516] [vc_sm_connected_init]: end - returning 0
[    2.594391] vc4-drm soc:gpu: failed to bind 20902000.hdmi (ops vc4_hdmi_ops [vc4]): -517
[    2.602801] vc4-drm soc:gpu: master bind failed: -517
[    2.992957] vc4-drm soc:gpu: failed to bind 20902000.hdmi (ops vc4_hdmi_ops [vc4]): -517
[    3.013847] vc4-drm soc:gpu: master bind failed: -517
[    3.021189] vc4-drm soc:gpu: failed to bind 20902000.hdmi (ops vc4_hdmi_ops [vc4]): -517
[    3.048315] vc4-drm soc:gpu: master bind failed: -517

Same result with both dtoverlay=vc4-kms-v3d and dtoverlay=vc4-fkms-v3d overlarys using gpu_mem=256

Photos

debug-shell
MATE
XFCE4
Weston