Search the Community

Test version of the Armbian+EDK2 system (UEFI\grub) is available. The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard To use this option. Download the EDK2 image. https://users.armbian.com/balbes150/edk2/ https://disk.yandex.ru/d/kK6KIqHShRHLyw Unpack and burn to SD card. Download the Armbian image (kernel 6.1.0-rc7), For Station M2 https://disk.yandex.ru/d/C4Ql9v0BvhKPjQ For Station P2 https://disk.yandex.ru/d/5XuGz9WgF7FGCg unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options). Connect the SD card and USB drive. Turn on the power. If the system does not start immediately, go to settings and select the device to start. On the EDK2 boot screen, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel. If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch. If desired, you can place the entire system on an SD card, but additional steps will be required at startup. At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console. That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000. https://github.com/150balbes/edk2_uefi

Hi FireFly station P2 on Armbian 22.11 Bullseye XFCE does not work on a 4K monitor. When turned on, ripples appear on the screen. Examples of images from links. The same problem at station M2. station m2 and station p2 do not work on a 4k monitor both

Maybe someone will be interested in it. https://bbs.stationpc.com/forum.php?mod=viewthread&tid=343&extra=page%3D1%26filter%3Dauthor%26orderby%3Dlastpost The uniqueness of this model is in the mechanism of a very simple installation of a standard SATA SSD drive. p.s. According to information from one client who uses this equipment in serious industrial operation - P2 worked without problems for many days with a full load (24\7) in harsh conditions without failures and failures, at the same time, they tried to use R4S, which froze and turned off after 20 hours.

Hello! I have Firefly Station P2 (I use this images - https://users.armbian.com/balbes150/rk3568/) And everything is OK except for one problem: I can't see NVM disk when booting kernel 5.X, 6.X. Yet on kernel 4.X I can see nvm. Please help, what should I do to use nvm with 5.X kernel? Some output: root@station-p2:~# uname -r 6.0.0-rc4-media root@station-p2:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 14.8G 0 disk mmcblk0p1 179:1 0 14.7G 0 part /var/log.hdd / mmcblk1 179:32 0 29.1G 0 disk mmcblk1p1 179:33 0 28.8G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 252:0 0 1.9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk root@station-p2:~# lspci root@station-p2:~# --- root@station-p2:~# uname -r 5.19.7-station-p2 root@station-p2:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 14.8G 0 disk mmcblk0p1 179:1 0 14.7G 0 part /var/log.hdd / mmcblk1 179:32 0 29.1G 0 disk mmcblk1p1 179:33 0 28.8G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 252:0 0 1.9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk root@station-p2:~# lspci root@station-p2:~# --- root@station-p2:~# uname -r 4.19.219-station-p2 root@station-p2:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 32M 0 disk mmcblk0 179:0 0 29.1G 0 disk mmcblk0p1 179:1 0 28.8G 0 part mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk mmcblk1 179:96 0 14.8G 0 disk mmcblk1p1 179:97 0 14.7G 0 part /var/log.hdd / zram0 254:0 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk nvme0n1p1 259:1 0 4M 0 part nvme0n1p2 259:2 0 4M 0 part nvme0n1p3 259:3 0 64M 0 part nvme0n1p4 259:4 0 64M 0 part nvme0n1p5 259:5 0 32M 0 part nvme0n1p6 259:6 0 2.7G 0 part nvme0n1p7 259:7 0 235.6G 0 part root@station-p2:~# lspci 0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01) 0002:21:00.0 Non-Volatile memory controller: Sandisk Corp PC SN520 NVMe SSD (rev 01)

In distributions that include 4.x series kernels, pcie is detected and the built-in broadcom wireless chip is functional with the wl driver. I would like to move to a 5.x series kernel, but I noticed that pcie is not detected at all, and though wifi is detected with the brcmfmac driver, it will not function to scan or connect to anything. I grabbed the latest image from this week (have tried many previous, including building my own armbian image) but no luck. Has anyone gotten these items to work with a 5 series kernel?

By pure accident, I discovered that Ctrl-Alt-F1 while the P2 is booting brings up more options on mine that allows the deletion of firmware and clearing of emmc. I have not done it but the menus are there.

Howdy With a p2 that already had ubuntu installed on the ssd using the firefly technique, it seemed time to upgrade using to armbian. Installing the new uboot went fine. It is not clear how to confirm it. The command did not error. However using the jammy 22.08 images, the uuid does not appear to be on the SD card. At this time I do not have a serial cable. However the image shows sum of the situation. Any help appreciated including advice on rj45 to serial cable. Thanks.

The instructions at the P2 page cannot be followed. The image at the link does not contain the p2-station-update-uboot script. I have tried using the Station OS multi-boot thing but that didn't work either. What is the correct way to do it now?