Jump to content

Werner

Administrators
  • 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
  1. We don't deal with Android here. Ask vendor or at some place like xda developer forums.
  2. edit /boot/armbianEnv.txt and set verbosity to 7 to get an idea about what happens inside.
  3. This should work too. Debug boot issues: https://debug.armbian.de Related perhaps: https://github.com/armbian/build/pull/8994
  4. Just boot from microsd and then use armbian-install to move image to spi/nvme directly attached?
  5. We don't support 3rd party forks. Ask at the place where you got this OS from.
  6. 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.
  7. Not all possible kernel-userspace combinations are built and/or exposed. If you cannot find what you are looking for, DIY: https://github.com/armbian/build/
  8. debug boot issues: https://debug.armbian.de
  9. 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.
  10. Werner

    Deleted

    orangepi5 and 6 have nothing in common. double-check what you are actually talking about. Also there is no 0.9.9 rknpu stuff. 5.10 bsp has been abandoned long ago.
  11. not recommended for rockchip socs since it cannot handle the rather high baud rate of 1.5Mbaud. Use FT232, CH340 or CP2104 instead.
  12. 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
  13. 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines