tenox

Thank you!!! Do I just apt update && upgrade to it or do I have to reinstall?

Yes. This only works in two cases: 1. Multi Boot Enabled 2. eMMC is wiped clean, no StationOS If StationOS is present on eMMC, SD card won't boot. At least not with Armbian.

This is not 100% correct. You still don't get my point: When StationOS is on eMMC, SD card WILL NOT BOOT without Multi Boot enabled. Inserting Armbian SD card on vanilla factory brand new P2 with StationOS will do nothing. Won't boot. For the second (5.x boot) I had to enable multi boot, erase eMMC, erase multi boot and then it will boot from SD card.

https://pastebin.com/raw/Yypz78PD

Of course: https://pastebin.com/raw/D9JmUHCt This P2 has a SD card inserted containing the UBOOT UPDATE, Armbian 21.11.0 trunk, hirsute legacy 4.19.193 image.

Thank you for your answer. However I have got a second P2, brand new factory unopened. I have written uboot updater "special version" of armbian to SD card. It doesn't boot. It just keeps booting to StationOS every time. My question still remains, what is the "official" way of booting armbian on a vanilla factory new device 3. Start the system, perform the initial configuration (answer the questions). this simply doesn't work without activating multiboot.

Yes very carefully. 1. Download a special version of the image from the link. 2. Unpack, write to the SD card. 3. Start the system, perform the initial configuration (answer the questions). 4. to start the update procedure, run the command The problem is that #3 doesn't work unless you turn on multi-boot. Then after #4 you need to disable multi-boot for normal Armbian to work.

Unrelated question. How do you "officially" boot to Armbian on Stationpc P2? Even with SD card inserted the system always boots to StationOS. I installed Armbian by enabling multi boot, booting to older Armbian, writing the vendor update then removing multiboot. Is this the official way?

You gave me this link to download latest armbian but it only has altlinux and armbiantv

Only has AltLinux and ArmbianTV

Vanilla Armbian Bullseye Edge from the website, FIRSTSECTOR=8192: root@station-p2:~# e2fsck /dev/mmcblk1p1 e2fsck 1.46.2 (28-Feb-2021) Superblock has an invalid journal (inode 8). Clear<y>? cancelled! Replaced FIRSTSECTOR=8192 with 32768: root@station-p2:~# e2fsck /dev/mmcblk1p1 e2fsck 1.46.2 (28-Feb-2021) /dev/mmcblk1p1: clean, 45607/1888656 files, 533295/7553024 blocks

Yup... root@station-p2:/usr/sbin# diff /mnt1/usr/sbin/nand-sata-install /usr/sbin/nand-sata-install 33c33,40 < FIRSTSECTOR=32768 --- > case ${LINUXFAMILY} in > rk3328|rk3399|rk35xx|rockchip64|rockpis|station|media) > FIRSTSECTOR=32768 > ;; > *) > FIRSTSECTOR=8192 > ;; > esac (/ is website version /mnt1 is trunk) When used the script from trunk on website image everything worked correctly.

These are for M2 not P2. But I tried this: https://users.armbian.com/balbes150/rk3568/ Works fine! It does install to eMMC no problem!! Thank so much! Just FYI went back and tried Bullseye and Jammy from Armbian website again and they create a corrupted ext4 on eMMC. root@station-p2:~# e2fsck /dev/mmcblk1p1 e2fsck 1.46.2 (28-Feb-2021) Superblock has an invalid journal (inode 8). Clear<y>? cancelled! e2fsck: The journal superblock is corrupt while checking journal for /dev/mmcblk1p1 e2fsck: Cannot proceed with file system check

from the armbian website Armbian 22.02 Jammy Kernel 5.16.y, Size: 366Mb, Updated: Feb 27, 2022 when it boots from SD card it says this: Armbian 22.02.1 Jammy ttyS2 station-p2 login: Welcome to Armbian 22.02.1 Jammy with bleeding edge Linux 5.16.11-media

I have erased Station OS from eMMC and removed multi-boot. Right now I can boot the "new" armbian (kernel 5.x) from SD card. It will not boot 4.x at all, including the one with /vendor folder to update uboot. So I have booted 5.x from SD, mounted the older 4.x image with /vendor folder and ran `p2-station-update-uboot`. Installed armbian to emmc via `nand-sata-insatll`. After power off/on: U-Boot SPL board init U-Boot SPL 2017.09-armbian (Sep 19 2021 - 21:20:22) unknown raw ID phN unrecognized JEDEC id bytes: 00, 00, 00 Trying to boot from MMC2 MMC error: The cmd index is 1, ret is -110 Card did not respond to voltage select! mmc_init: -95, time 9 spl: mmc init failed with error: -95 Trying to boot from MMC1 ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(5938a9cdfc...) + OK ## Checking uboot 0x00a00000 ... sha256 Bad hash: 4649d697ab55dddedb4d4a2ef080dfd8eceb70dcdb0da31f4ca951732e55e3d8 error! Bad hash value for 'hash' hash node in 'uboot' image node Trying fit image at 0x5000 sector Not fit magic SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### # Reset the board to bootrom # UPDATE: I think there is some issue with the nand-sata-install script from Armbian 5.x. When I format using ext4 and I try to mount or e2fsck /dev/mmcblk1p1 root@station-p2:~# e2fsck /dev/mmcblk1p1 e2fsck 1.46.5 (30-Dec-2021) Superblock has an invalid journal (inode 8). Clear<y>? If I choose btrfs instead of ext4 the script creates two partitions, I'm able to boot kernel from eMMC! However it dies after this: [ 5.181075] mmcblk1: mmc1:0001 Y2P032 29.1 GiB [ 5.194255] mmcblk1: p1 p2 [ 5.196575] mmcblk1boot0: mmc1:0001 Y2P032 4.00 MiB [ 5.200741] mmcblk1boot1: mmc1:0001 Y2P032 4.00 MiB [ 5.207358] mmcblk1rpmb: mmc1:0001 Y2P032 16.0 MiB, chardev (237:0) [ 5.667554] BTRFS: device fsid 291ef1d2-93a5-4f17-8565-19d20bbaa6e9 devid 1 transid 14 /dev/mmcblk1p2 scanned by btrfs (244) [ 5.777238] BTRFS info (device mmcblk1p2): flagging fs with big metadata feature [ 5.778377] BTRFS error (device mmcblk1p2): unrecognized mount option 'data=writeback' [ 5.779706] BTRFS error (device mmcblk1p2): open_ctree failed Maybe my hardware has an issue?!