Open mcerveny opened 2 years ago
Not a bug. Those binaries are part of the external firmware, not the internal. The current firmware relies on a chroot rootfs that contains the necessary elements of the firmware. The internal firmware is only used to boot the device and fails if the chroot rootfs cannot be mounted and successfully chroot to it.
The reason for this is that firmware updates can be simply dropped by replacing the rukafs firmware on the SD card instead of having to flash the device.
Of course a more convenient way to do this would be to have a full firmware booting from the SD card, but that's a different goal that we will investigate later on.
Not a bug ? Startup should call "/etc/init.d/S49alsa" after (or inside) "/etc/init.d/S50launcher" in choot and "/etc/init.d/S49alsa" should be removed from stripped root on spi-nand/rkflash if you handle alsa sound elsewhere (from your rootfs_ps5000_20210806.img).
Not a bug ?
Fair point, a bug is a bug.
Startup should call "/etc/init.d/S49alsa" after (or inside) "/etc/init.d/S50launcher" in choot and "/etc/init.d/S49alsa" should be removed from stripped root on spi-nand/rkflash if you handle alsa sound elsewhere (from your rootfs_ps5000_20210806.img).
Fair enough. We will remove those unused init scripts once we get to clean everything up. In the meantime, let us know if you manage to get the system to boot from the SDcard.
And feel free to open a PR if you want to fix this.
Describe the bug
/etc/init.d/S49alsa
(stripped rootfs from/dev/rkflash0p4
) fails to callalsactl
andamixer
./tmp/rootfs/usr/sbin/alsactl
and/tmp/rootfs/usr/bin/amixer
exist on rootfs from sdcard (/mnt/sdcard/rukafs -> /tmp/rootfs/,
mounted by/etc/init.d/S50launcher
)Custom Firmware version: ruka_cfw_3.0_beta_1_20210806
Boot output: