All Activity

This stream auto-updates     

  1. Past hour
  2. When I try to do the same, chrooting fails with: chroot: failed to run command ‘/bin/bash’: No such file or directory So I wonder, how that chroot should work anyhow, as in /bin and /usr/bin are now ARM-binaries, while the compiling host needs amd64 binaries.
  3. For the first time I hear that in China there are problems with obtaining images from the y-disk. I communicate with Khadas developers from China and they regularly download and test my images on all Khadas products. If you really want to help integrate all versions into a single build branch, you can take up the tvboxes branch. @Igor did the primary work, but he and I do not have enough time to bring everything to full readiness. By the way, how do you plan to run your image on VIM ?
  4. Kodi with KMS/DRM/GBM backend only Tried MPV, but it didn't seem to work . Looks like MPV is not supported we're tweaking the sources and scripts to release a new RetrOrangePi version , so hopefully a working tutorial will be available soon
  5. meson64-dev is 5.3-rc, you can build image yourself. amlogic burning tool is not support, you can use dd to SDcard, and finally install to emmc, khadas vendor image will be removed completely.
  6. Today
  7. I didn't see armbian tvbox branch is already support S905x, when I submit Khadas VIM1 patches, and your image is not accessable in China.
  8. see the first line in my initial message: Armbianmonitor:
  9. Strange ... I've a Pine64, OPiWin and OlinuxinoA64 and none of them got the issue since months ... Maybe @smaeul can give more details since he is the author of the latest patch ?
  10. Good news! Did you manage to do this only for Kodi or also for MPV? In any case, I will be glad to your tutorial.
  11. Hi there, RetrOrangePi developer here. You will definitely get the perfect solution from Jernej, but this is just to keep your hopes high, achieved by experimenting with several sources so i will need some time to get documentation and tutorials straight
  12. He my video about what's new on the Rock Pi 4, and mainline Armbian + Panfrost
  13. One question. The Armbian build system is already overloaded with a bunch of different options. Why multiply entities ? For all Khadas models, there are already perfectly working Armbian images. I propose to merge this topic with this.
  14. Dear olivluca, I read "man gpio". There no command "set"! May be need to use command "write"? And I dont know, how can understand what pin need activate for supply CSI of OrangePiPcPlus??? PL10? PG11? where can I to read it? I'm really afraid to give voltage on wrong pin!
  15. No, key patch for lima desktop support is submitted for review, I don;t try it, and don't know how far it from merged.
  16. from amlogic maillist, 4K support is still under develop, right?
  17. Armbian support for Khadas VIM1 is merged, you can build image your self. Note: after install to EMMC, this will completely remove vendor image.
  18. I followed all the threads and checked all the config settings, I have this and all the others you usually ask enabled. and for the record, it happened again this morning.
  19. This driver work in userspace driver in linux kernel work in kernelspace iam trying build mesa 3d driver from stable packages
  20. The WIP image, on a usb key, works well on two 1080p screens (Sony TV and Samsung monitor). There are only strange images and colors between the integrated bootloader and the kernel starting like on your 7" screen. As a server image, it seems to work well and after install armbian-config, I was able to configure the board as easily as other sbcs supported by armbian. I suppose that simply halting the board is not possible since it reboots when you ask for it.
  21. I won't use the backplane. The main issue is that the RAID controller is located there and not on the original motherboard, and I can't interact with it (physically difficult, and, ironically enough, it's an Armada chip with very poor documentation preventing me from running FreeNAS on the thing in the first place). I'll just go with cables as-is for now, and if ever, I'll try to make a custom PCB with just passthrough Power / SATA. I do want to use the existing status LEDs though, at least. The rest of my plans would be to use the buttons as well (interfacing them with GPIO, but not sure what scenarios I want to have here), re-route the front USB, and maybe have another identical 1.3" OLED screen on the I²C bus to "fill" the Qnap front display cutout. No idea how feasible all of this is; it should all fit, but cable management is likely to be very tricky.
  22. If content is somehow changed, numbers will be different.
  23. Could be - as once one gets into secure boot - one of the ARM chips I'm working on right now - it has a separate boot processor that is underneath the application space (e.g. Linux) - in my case, it's another core - ARM11 vs the ARMv7A that the OS runs on. There are OTP's and/or eFuses that are popped depending on the SoC, along with the stored keys. That's all I can say right now (forrest gump voice)
  24. Should be in the upstream repo's... So use apt to purge ntp, and install chrony... chrony is a good solution. Folks might also want to look at ntpsec packages... sfx
  1. Load more activity