Werner

Hey there, for quite a while I was using my Station P1 aka T-Firefly ROC-RK3399-PC-PLUS (with a nice case welded around) as crude NAS and wanted to do something new. However for unknown reason I cannot boot from microSD. I am used to that the Armbian boot loader should switch to microSD when detected so other OS can be used. Does not work though. It always starts booting from SPI which is fine in theory and then jumps to eMMC which boots fine. With SD inside it does the same. If I remove the eMMC module u-boot stucks to PXE which obviously fails and then drops to U-Boot shell. I played with that shell for a while including recovery steps (https://docs.armbian.com/User-Guide_Recovery/) (but with correct baud rate) but wasn't successful. On bootz it complains about kernel magic or ARM64 kernel magic, depending on usage of bootz or booti. Tried erasing SPI but was not successful doing that. rkdeveloptool in maskrom mode stated it erased something but did not change anything. From within Bullseye the SPI flash seems not to be visible. I assume it should be /dev/mtd0 or something? Kind a running out of ideas... Images on microSD I tried were 23.02 edge, 22.12 current and 22.02 current.

SSH is always listening on port 22. Suggesting to hook up a serial console. Best, easiest and cheapest way to debug issues with booting and connectivity since this has to always work.

Panfork is under heavy development/cutting edge so issues are to be expected. Alternative would be to use Rockchip proprietary binary blobs but they seem not to work very well either. On the bottom line nothing Armbian can fix (easily).

15Mbaud? Are you sure it is not 1.5Mbaud?

Just as a general experience from myself I never had good success on any kind of converter adapters regarding DP, HDMI, DVI or VGA when using with ARM boards. No idea what the cause is. Maybe general lack in drivers to mitigate such configurations... If somehow possible try to connect native.

Did you leave the microSD in after move? Booting directly from USB is not possible afaik but you can have the boot loader on sd which then boots from USB.

Scroll down and check for other download variants.

Probably related to

Tried using extraargs= in /boot/armbianEnv.txt?

Check output/debug folder for further clues. Try building from armbian-next branch.

FYI you are using both unsupported build and userspace.

Either use dpkg to remove "hold" of all firmware packages or apt install armbian-config

moved to userspace

Maybe because OPi simply forked and rebranded our config utility

Maybe the user account needs to be added to xrdp or similar usergroup for permission?

Try using code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install script.

Raise issue on vendor forums. moved fixed tag

It may, depending on your choice.

https://forum.armbian.com/terms

tried armbian-install?

Neither a tutorial nor a howto but a request. Moved.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

https://github.com/armbian/build/issues/4765 Please share your opinion on that directly on Github.

split

No, there is no easy way to switch to stable No, there isn't anything bad besides the message about being WIP Yes, you will receive updates.