Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1

#1 Re: ARM Builds » init system is failing » 2026-05-29 09:42:55

MProG10

Odd. I haven't touched this flag. This is the command I issued.

debootstrap --foreign --arch=arm64 stable /tmp/devuan [url]http://deb.devuan.org/merged[/url]

Could be related to the mirror? I know http://deb.devuan.org/devuan is another mirror, though I don't use.

#2 Re: ARM Builds » init system is failing » 2026-05-28 13:43:39

MProG10

Thank you for the help. As you pointed out, the init system loads udev. udev was missing. After installing the package, the system is booting successfully.

This is odd. How come udev was missing? I installed from Debootstrap. Maybe a bug in Debootstrap?

#3 Re: ARM Builds » init system is failing » 2026-05-28 12:33:29

MProG10

This is an init script in an initramfs. Android is booted from an initramfs. I'm using the proprietary bootloader. The kernel does load, and does boot with Busybox init, but is failing with System V init. I don't have a serial setup. All I have is adbd.

I tried running /etc/init.d/rc manually. Nothing regarding devtmpfs is logged.

#4 Re: ARM Builds » init system is failing » 2026-05-28 11:35:25

MProG10

I tried messing with the kernel boot arguments. No dice. This is my current kernel boot arguments.

console=tty0,115200 loglevel=7

I was hoping loglevel=7 to log init messages. No dice. Tried including root=/dev/mmcblk0p54 as argument. No dice.

This device is running kernel 3.18. Here are the sources and defconfig. And here's the script I use to boot Devuan GNU/Linux.

#!/bin/sh

mount -T /fstab -a
mdev -s
mount /dev/mmcblk0p54 /mnt
exec switch_root /mnt /sbin/init

Note this other Android device is running kernel 3.10. The failure is unlikely to be related to the kernel version.

#5 ARM Builds » init system is failing » 2026-05-27 14:11:13

MProG10
Replies: 9

Hello. I'm writing this post in requesting assistance booting Devuan GNU/Linux on an Android device. This is an ARM64 device. Upon running the init system, the system doesn't mount devtmpfs. The init system is failing. I do have CONFIG_DEVTMPFS set.

Do you happen to know which are the required kernel configurations for a successful boot? I believe I'm missing a kernel configuration, since I had success on another Android device. This other device is ARM-based.

Unfortunately, I don't have much logs to read. And I know for a fact the init system is failing, since running

adb ls /dev/

returns an empty directory. Do you happen to know of a method to show init debug messages?

From a chroot environment, I see the init system doesn't mount devtmpfs either.

Pages: 1

Board footer

Forum Software