Rock Pi S CRUX-ARM (aarch64)

Source based Linux distribution CRUX-ARM adhering to ideology keep it simple , has its own package system, also supports the port system.

the image building system now supports slaсkwarearm, slarm64, crux-arm


In:    serial
Out:   serial
Err:   serial
Model: Radxa ROCK Pi S
rockchip_dnl_key_pressed read board id failed
Net:   eth0: ethernet@ff4e0000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1688 bytes read in 5 ms (329.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
54 bytes read in 4 ms (12.7 KiB/s)
53884 bytes read in 8 ms (6.4 MiB/s)
28723712 bytes read in 1222 ms (22.4 MiB/s)
libfdt fdt_getprop(): FDT_ERR_NOTFOUND
Failed to load '/boot/uInitrd'
Moving Image from 0x680000 to 0x800000, end=2400000
## Flattened Device Tree blob at 02800000
   Booting using the fdt blob at 0x2800000
ERROR: reserving fdt memory region failed (addr=0 size=0)
   Loading Device Tree to 000000001debb000, end 000000001df30fff ... OK

Starting kernel ...

[    1.646112] rockchip-pinctrl pinctrl: pin gpio1-22 already requested by ff0c0000.serial; cannot claim for ff140000.spi
[    1.658179] rockchip-pinctrl pinctrl: pin-54 (ff140000.spi) status -22
[    1.665509] rockchip-pinctrl pinctrl: could not request pin 54 (gpio1-22) from group spi2-miso  on device rockchip-pinctrl
[    1.677900] rockchip-spi ff140000.spi: Error applying setting, reverse things back
[    3.295822] rk_gmac-dwmac ff4e0000.ethernet: Can not read property: tx_delay.
[    3.305840] rk_gmac-dwmac ff4e0000.ethernet: set tx_delay to 0x30
[    3.315652] rk_gmac-dwmac ff4e0000.ethernet: Can not read property: rx_delay.
[    3.323845] rk_gmac-dwmac ff4e0000.ethernet: set rx_delay to 0x10

CRUX-ARM 64b (rock-pi-s) (ttyS2)

rock-pi-s login: root
You are required to change your password immediately (administrator enforced).
New password:
Retype new password:
 ___  ___  _ _  _ _  ___  ___  ___  _____
|  _||  _|| | ||_'_||___|| .'||  _||     |
|___||_|  |___||_,_|     |__,||_|  |_|_|_|
                _           _
 ___  ___  ___ | |_    ___ |_|   ___
|  _|| . ||  _|| '_|  | . || |  |_ -|
|_|  |___||___||_,_|  |  _||_|  |___|

1 Like


What is the intent of this build?

Thank you,


It is a compact distribution kit with quite extensive ports, the distribution kit itself is not overloaded with system logic and scripts.
Goal, to introduce the given distribution and its philosophy, as well as easy use on development boards.
If you remove unused firmware and modules, you can fit in 1GB nand.

Can it be used to boot to ram?
Use cases:

  • Abrupt poweroff: Since the hard disk is only momentarily used in read-only mode during boot, then never touched again, there are few or no negative consequences of an abrupt poweroff. If a system is used where power is inconsistent, or the system is regularly used in a context where fast shutoffs are required, this is very handy.
  • Privacy: Anything you do in this session are lost when you reboot or power off. This is great for kiosks or other systems where permanent modification are not desired.

With proper configuration, this can be implemented in any Linux distribution.
For this it is better to put fs in read mode, and make tmp and / var / log in tmpfs.