Jump to content

Werner

Administrators
  • Posts

    5651
  • Joined

  • Last visited

Everything posted by Werner

  1. moved to beginner. User seems unsure which board they actually use (r6s vs 5rc).
  2. If there are no pre-built version available, use the build framework to create your own: https://docs.armbian.com/Developer-Guide_Build-Preparation/
  3. This is more or less expected for current since the HDMI implementation in this LTS version is very basic/incomplete. Features were and still are in development and did not make it into this version. If you need desktop use edge or vendor.
  4. armbian-config is still able to handle overlays, though in some cases it might not works. Not an issue though since it can be easily done manually as well. Check /boot/dtb/rockchip/overlay for the available overlays. You need the rk3588 ones. Check if the overlay_prefix in /boot/armbianEnv.txt is correct. Might be necessary to change to rockchip. Then simply add the overlays you want like this (example): overlays=rk3588-i2c8-m2
  5. the bootloader needs to be installed on emmc separately. armbian-install usually takes care of that. How to debug boot issues: https://debug.armbian.de
  6. Github build repository is only for framework bugs, building Armbian to say. Firefox is userspace and issues when running Armbian are to be reported here in forums.
  7. We can discuss including this into CLI/desktop images. Not for minimal.
  8. split into new topic due to off-topic
  9. https://github.com/armbian/build/blob/main/config/boards/bigtreetech-cb2.conf Config is there. If there is no pre-made build available use the framework to create your own. This is what it's made for.
  10. The driver seems to be already included. If I check my kernel (vendor rk35xx) config I see CONFIG_VIDEO_OV13855=y.
  11. Alright, didn't know they are still there. Well as mentioned media won't receive any further updates since all functionally is merged into standard branches. Anyway, Rock64 is rk3399 I think and you should be good to go with mainline kernel, either current which is 6.12.y or edge which is 6.14-rc7 atm. The branches at https://github.com/armbian/linux-rockchip are made from Rockchip BSP code and mostly for rk35xx socs. I don't think there is much work there for rk3399.
  12. moved Where did you get those? media branch has been abandoned for over a year now.
  13. Hi this warning tells you that it is up to you to do a risk assessment if you are fine with the fact, that the device's status is unknown to the Armbian team, that it may break with an upcoming update or never receive an update at all.
  14. Alright. Yes, there seems to be some issue with the naming of the overlays which required editing armbianEnv by hand. It is hard to keep up with the continously changing world of SoCs and kernels where latter, especially on mainline, often even lacking basic overlays since close to nobody deals with this.
  15. As guessed you did not switch to vendor kernel and tried using a vendor kernel overlay with mainline kernel. But glad you figured it out what changes are necessary in order to make it work. Feel free to send the working overlay the build framework so it is included by default. mainline still lacks lots of overlays.
  16. Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  17. These overlays are most likely not made to be used with mainline kernel. I suggest to retry with vendor kernel. Standard overlays for it have been pushed yesterday:https://github.com/armbian/linux-rockchip/pull/345/files
  18. excerpts are useless. Provide full logs with the curl command suggested.
  19. Try oldarchive https://fi.mirror.armbian.de/oldarchive/helios4/archive/
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines