- 1 General information
- 2 Specific troubleshooting pages
- 3 Port/device troubleshooting
- 3.1 References
- 3.2 Porting process, preparation and various information
- 3.2.1 My device runs the Linux kernel (e.g. Android), but the vendor does not provide the source
- 3.2.2 My Android device does not have partition labels, how do I know where to put the boot.img file etc?
- 3.2.3 Serial Console Debug Cable (early boot debugging)
- 3.2.4 Proprietary blobs
- 3.2.5 Force reboot
- 3.3 Errors on the device
- 3.3.1 Touch screen device present but not outputting any touch events
- 3.3.2 CHARGING MODE: error starting charging-sdl
- 3.3.3 During initramfs generation: "modprobe: WARNING: Module drm not found in directory /lib/modules/..."
- 3.3.4 Phone shows the telnet message, a black screen, or doesn't leave the bootloader or Samsung/Google/... splash screen
- 3.3.5 I have ported postmarketOS to my device and the screen doesn't get updated
- 3.3.6 Device reboots
- 3.3.7 SSH / udev / touch screen do not work
- 3.3.8 I can't access the framebuffer device
- 3.3.9 "if running weston from ssh, use --tty to specify a tty"
- 3.3.10 Weston and fbsplash -s <image> do not work
- 3.4 Flashing problems
- 4 pmbootstrap and build related errors
- 4.1 Alpine, chroots and pmbootstrap
- 4.1.1 pmbootstrap is broken! But it worked yesterday!
- 4.1.2 ERROR: This device does not exist anymore, check <https://postmarketos.org/renamed> to see if it was renamed
- 4.1.3 BusyBox does something different than the standard tool for the job, and this breaks building my package!
- 4.1.4 WARNING: No provider for dependency...
- 4.1.5 ERROR: busybox-1.27.0-r1.post-install: script exited with error 127
- 4.1.6 ERROR: /mnt/pmbootstrap-packages/x86_64/qemu-user-static-repack-2.8-r6.apk: UNTRUSTED signature
- 4.1.7 Installed version newer than the version in the repositories
- 4.1.8 It's not installing my changed package
- 4.1.9 Newer version in binary package repositories than in aports folder
- 4.1.10 mkbootimg: error: argument --dt: can't open '/boot/dt.img'
- 4.1.11 Permission denied: .../pmbootstrap/work/chroot_native/proc/1/cwd'
- 4.1.12 can't create /dev/null: Permission denied
- 4.1.13 cp: write error: No space left on device (during file transfer from chrooted environment to target image)
- 4.2 Build errors
- 4.2.1 Errors with grsec-based kernel on the host system
- 4.2.2 Errors with ecryptfs
- 4.2.3 musl-*/busybox-static-* fails to build with a 404 error
- 4.2.4 sh: can't create /proc/sys/fs/binfmt_misc/register: nonexistent directory
- 4.2.5 du: unrecognized option: summarize
- 4.2.6 Packaging for aarch64: ./config.guess: unable to guess system type
- 4.2.7 ERROR: ... BAD archive
- 4.2.8 CROSS_COMPILE_ARM32 not defined or empty, the compat vDSO will not be built
- 4.3 Errors while running pmbootstrap on non-x86_64 arches
- 4.1 Alpine, chroots and pmbootstrap
- 5 Troubleshooting steps kept around for historical reference
- Always look at the log file for a detailed error message:
- Make sure, that you have the latest version. Your bug may already be fixed.
- Please report the bugs you have found in the issues, so we can fix them.
- Syslog is enabled, and will log to shared memory once the OS has booted. It can be read with the
logreadtool in BusyBox. The syslog is currently not preserved across reboots.
Specific troubleshooting pages
- Troubleshooting:boot - Troubleshooting the boot process, figuring out if your device boots
- Troubleshooting:display - Troubleshooting display issues
- Troubleshooting:HID buttons - Troubleshooting on-device buttons
- Troubleshooting:host - Troubleshooting the host system
- Troubleshooting:kernel - Common kernel building related issues and how to fix them
- Troubleshooting osk-sdl
- Troubleshooting:Xorg - Troubleshooting problems with Xorg
- Troubleshooting:QEMU - Debugging problems with
- Troubleshooting:dependencies - A guide to resolving
Could not find dependencyerrors coming from pmbootstrap, as well as
unsatisfiable constraintserrors coming from apk.
- Troubleshooting:grsec (TL;DR: doesn't work)
- Run pmbootstrap on non-x86_64 arches
Porting process, preparation and various information
My device runs the Linux kernel (e.g. Android), but the vendor does not provide the source
- Ask kindly via e-mail.
- If they don't provide the source, team up with gpl-violations.org. You have the legal right to get the source, because the Linux kernel is under the GPLv2!
- Consider building generic kernel for your device.
- Another option is using prebuilt kernels
My Android device does not have partition labels, how do I know where to put the boot.img file etc?
- Search online for the partitions, they are probably documented somewhere.
- Try to dump all partitions. Run `file` on them, it should roughly tell you the contents. If that does not help, run binwalk.
- file output: check if it is a kernel (vmlinuz),
boot.imgfile or just "data".
- In case you have "data", don't flash anything there, we probably can't generate that format yet. Please open an issue in GitHub or ask on the channel.
- file output: check if it is a kernel (vmlinuz),
- You can also look at recovery zips from other Android ROMs, that were released for your device. Extract it and look at
META-INF/com/google/android/updater-script, search for commands starting with
run_program("/sbin/busybox", "dd", they are for flashing partitions.
- In one example, there was
run_program("/sbin/busybox", "dd", "if=/tmp/boot.blob", "of=/dev/block/mmcblk0p4");, which means that a
boot.blobfile gets flashed to
boot.blobfile is also in the recovery zip - run the
fileprogram on it (see above).
- In one example, there was
Serial Console Debug Cable (early boot debugging)
For some devices it's possible to get early boot output using a debug cable that provides access to the UART. Unfortunately manufacturers do not use to publish the details and it is end users who in some cases have figured it out:
- Here is one such cable for Nexus 4 and another for Nexus 5.
- This article goes a step further with Google Nexus devices.
- This guide explains how to create one for a Samsung devices with a micro usb socket.
- Sony has published information about how to access the UART port on their Xperia series.
- The Replicant wiki has useful information on this as well.
On fastboot devices, you may have to enable UART debugging with
fastboot oem uart-on.
By default, all output from the initramfs get redirected to
/pmOS_init.log. If you want the output through the debug cable you need to add
PMOS_NO_OUTPUT_REDIRECT to your kernel command line.
See Serial debugging
Many devices require proprietary blobs for enabling certain peripherals (wifi/bluetooth/cellular/GPS). These repositories appear to contain blobs for a large percentage of devices out there.
On some phones, you can hold down the power button for ten seconds to force a reboot. If that does not work: On other phones, you have to hold the power button down for a full minute (or hold it together with volume down). On some phones, it might take even longer (3 minutes or so).
You can also give from console
echo b > /proc/sysrq-trigger.
Errors on the device
Touch screen device present but not outputting any touch events
For some devices (at least motorola-shamu and motorola-lux), the touch screen I2C device is present but not activated at boot, and must be activated before it produces any output.
For the motorola-lux, this is done in the following way:
echo 1 > /sys/devices/soc.0/78b8000.i2c/i2c-4/4-0020/drv_irq
The path to the correct touch device depends on the device. This can be added to an initfs hook to activate the touch screen automatically at boot.
CHARGING MODE: error starting charging-sdl
When attaching the power cable while the device is off, Android devices boot into a special "charging mode". postmarketOS's charging-sdl display does not work yet on all devices.
To debug the issue, follow instructions at Inspecting the initramfs including activating the initramfs-extra, then execute
start_charging_mode in the shell.
During initramfs generation: "modprobe: WARNING: Module drm not found in directory /lib/modules/..."
This means, that a module can not be put in an initramfs. When you are not using a mainline kernel, it is likely that there are no modules configured, but the code is built directly into the kernel. This means, it is expected and can be ignored.
Phone shows the telnet message, a black screen, or doesn't leave the bootloader or Samsung/Google/... splash screen
I have ported postmarketOS to my device and the screen doesn't get updated
There is a known bug where if you execute
cat /sys/class/graphics/fb0/modes > /sys/class/graphics/fb0/mode exactly one frame is drawn, and the screen isn't updated otherwise.
- If your device always reboots after the same time (e.g. 2 minutes) after booting, you probably need to feed (or disable) a watchdog. Try to search your kernel config for watchdog, and also the internet for watchdog + your phone name.
- Android: The kernel config option
CONFIG_ANDROID_LOW_MEMORY_KILLERmay cause reboots. Please check if you have disabled it. If this helps you, please let us know, so we can consider checking for this option.
- Android: it is possible to get the
dmesglog from just before the crash after the reboot if you enable some kernel options.
SSH / udev / touch screen do not work
- Make sure that
DEVTMPFSis enabled in your kernel config. Do not enable
I can't access the framebuffer device
cat /dev/random > /dev/fb0returns:
cat: write error: No such device
- This could be caused by a proprietary 3d driver enabled in the kernel config. Try to disable it (the actual config options may be different).
"if running weston from ssh, use --tty to specify a tty"
Specify a tty in weston's commandline. The correct syntax is:
Weston and fbsplash -s <image> do not work
If Weston returns an error because it could not access
/dev/tty1, even when you specify it on the command line as above, you may need to enable Virtual Terminals in the kernel config.
You can enable
pmbootstrap menuconfig and checking under Device Drivers -> Character devices -> Virtual terminal
Invalid sparse file format at header magic
In some devices (e.g.: bullhead, titan), when flashing the system (
pmbootstrap flasher flash_rootfs), it works but fastboot complains of
Invalid sparse file format at header magic.
$ ./pmbootstrap.py flasher flash_rootfs [23:02:58] (native) install android-tools [23:02:58] (native) flash rootfs image target reported max download size of 536870912 bytes Invalid sparse file format at header magic sending sparse 'system' 1/1 (274101 KB)... OKAY [ 9.452s] writing 'system' 1/1... OKAY [ 12.584s] finished. total time: 22.036s [23:03:20] Done
It happens when your device expects a sparse system image. The workaround is as follows:
To do this, edit the file in ./local/var/pmbootstrap/cache_git/pmaports/device/your_device_name/deviceinfo and add
deviceinfo_flash_sparse="true". When finished, run
"pmbootstrap install" to rebuild the file system
For more information, see issue #299
Heimdall: Flashing fails at 7%
You might also be getting the error "ERROR: Failed to confirm end of file transfer sequence"
FAILED (remote: Unknown chunk type)
This is a bootloader limitation. Flash with netcat as a workaround, or use this wiki's search feature to come up with more related information. Feel free to organize this in a better way, but this should be a good starting point. See also #1735.
flasher (fastboot) is stuck in < waiting for any device >
If that does not help, it might be necessary to set the
flash_fastboot_vendor_id in your deviceinfo (this was necessary for the Amazon Kindle Fire HDX). Try to search the web for your device name and "fastboot vendor id".
If you were previously able to use fastboot and it stopped working, sometimes
pmbootstrap shutdown to restart the chroot helps (#1633). Also try to reboot the device into fastboot again.
Alpine, chroots and pmbootstrap
pmbootstrap is broken! But it worked yesterday!
Sorry! Revert to the last commit, that was known to work (git checkout $commit) and report an issue, if there is not already one. Consult with others in the IRC/matrix channel to find out, which commit was the last one that worked.
ERROR: This device does not exist anymore, check <https://postmarketos.org/renamed> to see if it was renamed
One case where this might happen is if you remove pmbootstrap's work path, and then run a
pmbootstrap init. As you might notice it is still remembering values and devices from previous executions.
To solve this you need to remove (or rename)
~/.config/pmbootstrap.cfg). After doing so
pmbootstrap init should work fine.
BusyBox does something different than the standard tool for the job, and this breaks building my package!
Example: unzip in BusyBox doesn't extract symlinks like the normal unzip implementation (#82).
Solution: Simply add
unzip to the makedepends in the APKBUILD, and the "real" unzip will be used (or in that case, try to get the sources in another archive format, such as
WARNING: No provider for dependency...
Normal behavior. it means, that your "user" repository (the repository with all custom compiled packaged from pmOS, such as your device package and kernel) does not have the dependencies from the official Alpine Linux repositories (such as
htop, ...) when indexing it. But these dependencies are in the official repositories, so they will be found when you try to install something. Usually the package indexing is done on all repositories at once in Alpine (then you wouldn't get the error), but pmOS does it only on the "user" repository.
ERROR: busybox-1.27.0-r1.post-install: script exited with error 127
Programs running in (foreign arch) chroots cannot be executed. See #1972.
ERROR: /mnt/pmbootstrap-packages/x86_64/qemu-user-static-repack-2.8-r6.apk: UNTRUSTED signature
You don't have your own package signing key imported, which gets generated when you compile a package for the first time. pmbootstrap should automatically import it, but when you hit
^C during that, it may go wrong.
Your generated key is in
~/.local/var/pmbootstrap/config_abuild, all imported keys are in
A quick fix is deleting all packages:
./pmbootstrap zap -p
See issue #270 for more information and don't hesitate to reopen if this didn't work for you.
Installed version newer than the version in the repositories
You have a program installed in one of your chroots with a higher version, than what is available in the binary package repositories (either from upstream or the packages you have built yourself).
Example how this can happen:
- Git branch switch to one which increased the version of
- Install it in a chroot (e.g. by running
- Branch switched to
- All packages got zapped, but not the chroots
postmarketos-mkinitfsagain (this time it has a lower version count!)
Solution: Simply zap your chroot! When it gets set up again, it will use the current package version.
It's not installing my changed package
You have changed a package but it's using the one from the repository and not your changed build.
You probably didn't build it or not for the correct architecture.
pmbootstrap build defaults to
x86_64 architecture, if you need that package on your device, use the
Newer version in binary package repositories than in aports folder
You have built a package earlier, and the branch you are currently working in has a lower version in the aports folder.
Example how this can happen:
- Git branch switch to a feature branch which increased the version of
- Switch to
- Run just about any
pmbootstrapcommand, it will print this warning:
Package 'postmarketos-mkinitfs' in your aports folder has version X, but the binary package repositories already have version Y
pmbootstrap zap -m to delete the mismatched binary packages.
Note: If that does not help it, you can manually delete that specific packages from your aports folder:
sudo rm ~/.local/var/pmbootstrap/packages/*/postmarketos-mkinitfs*.apk and run
pmbootstrap index to re-index all packages. See also: #466, #474
mkbootimg: error: argument --dt: can't open '/boot/dt.img'
This happens when you have
deviceinfo_bootimg_qcdt enabled (which is correct when pmbootstrap generated it that way), but your kernel does not generate the
Please adjust your kernel
APKBUILD as follows:
- extend your
build()function like this
- and your
package()function like that
See #688 for a plan to automatically generate the linux APKBUILD right.
Permission denied: .../pmbootstrap/work/chroot_native/proc/1/cwd'
It looks like you have created your work folder as:
pmbootstrap is the folder with the checked out source code. That is not supported. Please run
pmbootstrap shutdown, then delete that folder, then run
pmbootstrap init again and choose another work folder (e.g.
After that it should work - if this still does not resolve it, please open up an issue in the GitLab issue tracker.
/dev/null: Permission denied
Make sure that your working directory is mounted correctly. This can happen when working over NFS, or when you mounted the drive your working directory is on trough the file explorer (if that's the case,
umount it, and
mount it manually). This can probably happen on every drive mounted with
nosuid or similar.
cp: write error: No space left on device (during file transfer from chrooted environment to target image)
This issue is triggered when
pmbootstrap determines the wrong size for the target image, as it is unfortunately very hard to calculate the correct size independent of the filesystem on which the chroot resides. Some examples for this: #1916; #928 where more elaborate information can be found.
While fixing the problem seems impossible for every configuration, there is a workaround available (#1904 and its associated merge request): Use the
--extra-space option of
pmbootstrap to specify extra space on the resulting image file in MB. Just play around with the value until it works for you. You can specify the value also through
pmbootstrap init in its Additional options.
Errors with grsec-based kernel on the host system
Errors with ecryptfs
When your "work" folder is inside an ecryptfs mounted folder,
/dev/random may not work inside the chroot and you may have other issues. Try to move your work folder to another location, you can use
/tmp to test if this resolves the issue. You can change the location in
pmbootstrap init. See also: #61. (This doesn't seem to be an issue with newer versions of ecryptfs anymore.)
busybox-static-* fails to build with a 404 error
pmbootstrap aportgen musl-armhf musl-aarch64 musl-x86_64. The reason why this fails from time to time is, that we use Alpine's binary
musl lib c package for
aarch64 in the native chroot, to get the cross-compiler working. So the download URL inside the
aports/cross/musl-*/APKBUILD file must be in sync with the upstream version. This pmbootstrap command safely gets the new version, uses
apk to verify the signature of the package, generates the hash, and updates the
APKBUILD file. To make sure, that
pmbootstrap aportgen receives the latest
musl version, delete your HTTP cache right before by executing this command:
pmbootstrap zap -hc. Don't bother making a pull-request for this, as the fix is really trivial (see this commit). Just report it as issue, if it happens.
sh: can't create /proc/sys/fs/binfmt_misc/register: nonexistent directory
This issue is known to happen in Alpine Virt hardened and Void Linux. These commands should fix it:
sudo modprobe binfmt_misc sudo mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
If it still does not work, it is probably not supported by your host Linux distribution's kernel (
CONFIG_BINFMT_MISC). Try to use another kernel.
du: unrecognized option: summarize
If you are using Alpine Linux and you encounter this issue, you will need to install the
sudo apk add coreutils
Packaging for aarch64: ./config.guess: unable to guess system type
This happens in packages built with autoconf (./configure; make; make install), when it ships an outdated config.guess file in the source code. Adjust your APKBUILD's
prepare() function like done in #698.
ERROR: ... BAD archive
pmbootstrap log shows something similar to the following:
(005853) [22:25:47] (native) % apk --no-progress add -u qemu-user-static-repack qemu-user-static-repack-binfmt WARNING: Ignoring /mnt/pmbootstrap-packages/x86_64/APKINDEX.tar.gz: No such file or directory (1/2) Installing qemu-user-static-repack (2.8-r9) ERROR: qemu-user-static-repack-2.8-r9: BAD archive (2/2) Installing qemu-user-static-repack-binfmt (2.8-r9) 1 error; 20 MiB in 36 packages (005853) [22:25:53] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...then downloading a package (in this case
qemu-user-static-repack) failed. Please delete the broken package and try it again:
$ cd ~/.local/var/pmbootstrap/ # go into your work folder, as specified in 'pmbootstrap init' $ sudo rm -v cache_apk_*/qemu-user-static-repack-* # adjust the failing package name accordingly
CROSS_COMPILE_ARM32 not defined or empty, the compat vDSO will not be built
CONFIG_COMPAT_VDSO in kernel config.
Errors while running pmbootstrap on non-x86_64 arches
If you get
Can't build 'binutils-or1k-elf' for architecture aarch64, see Run pmbootstrap on non-x86_64 arches.
Troubleshooting steps kept around for historical reference
pmbootstrap builds packages that it should download from the binary repo/that are already built
Try to disable the "timestamp based rebuilds" feature in "pmbootstrap init" as a workaround and please report this as a bug. We need the following for the bug report:
- *enable* timestamp based rebuilds
pmbootstrap -v install(let it run until it starts building the package it should not build)
pmbootstrap log(we need the log from here!)