-
Posts
5650 -
Joined
-
Last visited
Other groups
Management
Contributor/Maintainer
Profile Information
-
Gender
Male
-
Location
Federal republic of Germany
Contact Methods
-
Website URL
https://github.com/EvilOlaf
-
Github
EvilOlaf
-
Discord
werner
Recent Profile Visitors
39716 profile views
-
We don't deal with Android here. Ask vendor or at some place like xda developer forums.
-
edit /boot/armbianEnv.txt and set verbosity to 7 to get an idea about what happens inside.
-
This should work too. Debug boot issues: https://debug.armbian.de Related perhaps: https://github.com/armbian/build/pull/8994
-
Can you provide logs?
-
Just boot from microsd and then use armbian-install to move image to spi/nvme directly attached?
-
Because they sell you the hardware only. Their software support is very poorly made since for the price they cannot afford proper software support and - even more important - maintenance. They leave this burden to - mostly unpaid - random developers across the world like us. At least I'd go for a device with Standard Support which the Ultra and Max hasn't: https://www.armbian.com/download/?device_support=Standard support For the raspberry you would need additional hardware (an AI kit I guess). No clue though about how they both perform in comparsion. For RK3588 you have two choices for now: The rockchip bsp implementation and https://github.com/rockchip-linux/rknn-toolkit2. Or using 6.18 kernel using the reverse engineered Rocket driver and latest bleeding edge mesa to get npu access. I personally did not play with either of these options and have no intention to do so for the moment.
-
debug boot issues: https://debug.armbian.de
-
current isn't a good option for rk3588/s devices. At this point of time barely any support for this SoC was mainlined. And it seems like later revisions introduced a regression causing a crash. Since 6.18 may become next LTS kernel it will replace current current kernel at some point. So better go for an edge based image instead.
-
You should check uboot logs if the dtbo is loaded correctly. You can get those using a debug serial console. If you don't know what that is or how to connect: https://debug.armbian.de
-
https://github.com/armbian/build/blob/main/config/boards/retroidpocket-rp5.csc https://github.com/armbian/build/blob/main/config/boards/retroidpocket-rpmini.csc You can build images on your own. https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained
