phier

Hi, there is almost 0 documentation how to update u-boot; where to flash (dd) it, if it does support boot from rootfs on ZFS etc. Regarding the ZFS; here I assume /boot has to be on ext4/vfat and rest of the rootfs (/) as ZFS to make it works? Is there any way to flash more details on this part? I found files as following but no idea... /usr/lib/linux-u-boot-current-bananapi_21.05.1_armhf/u-boot-sunxi-with-spl.bin root@bananapi:/usr/lib/u-boot# pwd /usr/lib/u-boot root@bananapi:/usr/lib/u-boot# ls Bananapi_defconfig LICENSE platform_install.sh Also I wanted to do simple update; to make u-boot boot from /dev/mmcblk0p2 instead of rootfs that was place originally on /dev/mmcblk0p1; /dev/mmcblk0p2 is identical copy of /dev/mmcblk0p1 Thanks Edit> seems that details are stored here platform_install.sh; But how/where i can re-compile file u-boot-sunxi-with-spl.bin so that it will boot from /dev/mmcblk0p2 instead of /dev/mmcblk0p1; or is that based on the Boot flag set on partition? so i assume in my case i have to pass $1 = /usr/lib/linux-u-boot-current-bananapi_21.05.1_armhf $2 = /dev/mmcblk0 DIR=/usr/lib/linux-u-boot-current-bananapi_21.05.1_armhf write_uboot_platform () { dd if=/dev/zero of=$2 bs=1k count=1023 seek=1 status=noxfer > /dev/null 2>&1; dd if=$1/u-boot-sunxi-with-spl.bin of=$2 bs=1024 seek=8 status=noxfer > /dev/null 2>&1 } setup_write_uboot_platform () { if grep -q "ubootpart" /proc/cmdline; then local tmp=$(cat /proc/cmdline); tmp="${tmp##*ubootpart=}"; tmp="${tmp%% *}"; [[ -n $tmp ]] && local part=$(findfs PARTUUID=$tmp 2>/dev/null); [[ -n $part ]] && local dev=$(lsblk -n -o PKNAME $part 2>/dev/null); [[ -n $dev ]] && DEVICE="/dev/$dev"; else if [[ -f /var/lib/armbian/force_search_uboot ]]; then for dev in $(lsblk -d -n -p -o NAME); do if grep -q 'eGON.BT0' <(dd if=$dev bs=32 skip=256 count=1 status=none); then echo "SPL signature found on $dev" 1>&2; DEVICE=$dev; break; fi; done; fi; fi }

@hexdump i installed latest ubuntu - armbian on sd card; then i shrinked original partition rootfs; created now one; copied data from shrinked to the new one. And i want to boot from that new one. ie if sd card was sdf1 now its sdf1 (old rootfs) sdf2 (new rootfs) And i want make uboot boot from sdf2 thanks i think boot/boot.scr has to be also updated ? setenv devnum "0" setenv rootdev "/dev/mmcblk${devnum}p1" i believe uboot has to be somehow recompiled to point to /dev/mmcblk0p2 instead of /dev/mmcblk0p1

@hexdump so i do not need to configure / compile anything? all the control of uboot is done via that armbianEnv.txt - ie i only edit that file and thats it? thanks @hexdump it doesnt work at all. can someone advice here? thanks

hello, what exactly has to be done / how if I want to change a roofs partition for uboot? I can see its written inside these two files... but i cant see how to change that ... if i can directly edit these two files or something has to be executed... armbianEnv.txt boot.scr thanks

Hello, i saw a post regarding ZFS > zfs What is the current state of ZFS support? Is it a stable to run ZFS as FS for root fs only on SD card (16-32GB)? I need that for an easy backup on FS level using send/rec commands. But as we know xu4 is 32bit only - > maybe problem with stability - stability 32bit official solution but for rpi4 Or maybe is there a point to use zfs for root fs at all? what about LMV? thanks

Hi, im getting confused.. whats the point of armbian OS if it doesnt work properly after default install? I have banan pi m1+ and i did default install as per description... i chosen Xenian ubuntu vanila. After initial boot my log is full of messages as : [ 129.562637] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000a, err: -16[ 129.580018] brcmfmac: brcmf_sdiod_set_sbaddr_window: failed at addr: 0x1000a Those messages are appearing every second or so... Also im surprised that noone reported that issue. Whats the point of that distro then? I tried bananian and everything worked smoothly... Needles to say that i have banana pi m1+ and the board doesnt have yellow PIN ... its black.