Jump to content

balbes150

Members
  • Posts

    4436
  • Joined

  • Last visited

Everything posted by balbes150

  1. Do I understand correctly, to test your new packages, need to build a version of Bullseye + a new kernel (with patches for LE) ? By the way, are you planning to build new packages with the latest developments for KODI-19 ?
  2. Models with new RK chips are interesting, but such issues need to be resolved through the project manager @Igor
  3. The current version does not support installation in eMMC. Do not try to do this.
  4. Good news. Full-fledged working images (20210827) of ArmbianTV for P2 and M2 are ready. All the equipment works in them and you can start and configure the system via an HDMI monitor and a keyboard/mouse. M2 https://disk.yandex.ru/d/OBDO8BU2y1M6ug https://users.armbian.com/balbes150/rk3566/ P2 https://disk.yandex.ru/d/neKXsYolKXgLzg https://users.armbian.com/balbes150/rk3568/
  5. Good news. Full-fledged working images (20210826) of ArmbianTV for P2 are ready. All the equipment works in them and you can start and configure the system via an HDMI monitor and a keyboard/mouse.
  6. This is the only TV box for which there was previously minimal support.
  7. These are the worst chips that should be avoided in every possible way. There is no support for them.
  8. For those who are interested in reducing the price of Firefly RK3566\rk3568 boards. I am trying to convince Firefly representatives of the need to add rk3566\rk3568 boards without the eMMC module to the line of products sold. This will significantly reduce the price. This is especially noticeable on the variants of the eMMC module with 64\128GB. For those who plan to use these models with SATA or NVMe (after the version of the u-boot loader for SPI is finalized, for direct launch with SATA\NVMe). At the first stage, to fully start the entire system with SATA\NVMe, you can use the bootloader from the SD card. I invite everyone interested to express their opinion, so that Firefly representatives could assess the prospect of such an option for delivery.
  9. The primary version of Armbian test images for Firefly Station P2 rk3568. You can see the details in this topic. https://bbs.stationpc.com/forum.php?mod=viewthread&tid=209&extra=page%3D1%26filter%3Dauthor%26orderby%3Dlastpost screen https://disk.yandex.ru/i/o6j6W7myad9qqw
  10. All patches that do not conflict are included.
  11. I collected the Ubuntu version from official Firefly sources with minor edits (to see the kernel and u-boot sources). Now the next step is to create a Armbian test system with a legacy core for M2 and P2.
  12. I received samples of P2 and M2. the first impressions are very positive. I checked the launch of the official versions of Ubuntu 18.04 from Fyrefly. Everything starts and works from the SD card. The startup process is very simple, I downloaded the image, unpacked it, wrote it to the SD card, connected it to P2\M2, turned on the power and the system automatically updated the bootloader in eMMC, rebooted and the Ubuntu system automatically started from the SD card (the regular Station system in eMMC is saved and works if there is no SD card). I really liked the mechanism for connecting SATA devices (SSD\HDD) to P2, it is very simple. I immediately connected a 240GB SSD drive. It was automatically detected and appeared in the system. WiFi antennas on P2 are full-fledged and large, they obviously did not save money here and will ensure proper operation.
  13. Carefully read the first message of the topic (this is specially highlighted in red). The topic is closed.
  14. Those interested can buy Station P2 \ M2 models or separate roc-rk3566-pc and roc-rk3568-pc boards. https://www.firefly.store/goods.php?id=140 https://www.firefly.store/goods.php?id=142 https://www.firefly.store/goods.php?id=145 https://www.firefly.store/goods.php?id=147
  15. To add M2 and P2 support to Armbian, need to have this equipment available. To date, I do not have this equipment. A Firefly representative promised to send it, but I do not know when this will happen.
  16. Update Legacy kernel to 4.9.201
  17. This is an outdated startup option (using boot.scr and armbianENV.txt), I use extlinux. conf. You need to use a different configuration mechanism. I don't use this functionality, so I won't tell you what to do.
  18. Sorry, I won't be able to attend, there are urgent personal matters in the family at this time.:)
  19. Edit or delete the parameter (mem=2048M) from /boot/extlinux/extlinux.conf. It is used to limit the size of RAM to ensure that the system starts on any H6 models (there are models that cannot automatically determine the memory size correctly and do not start).
  20. @jmmc https://github.com/armbian/build/pull/2971
  21. @JMCCIn all the latest versions with the Current kernel, I use the full package of patches from LE for RK (3328\3399\3288) and AW H6. I.e., this kernel has all the latest functions for HW (decoding, sound, 4K etc). It may be interesting for you to try to build test versions of the media package using the 5.x core with all the new acceleration features. If you are interested, I can create a PR for the new core. By the way, these patches work perfectly as a single core with a common configuration for all RK3399\rk3328\rk3288\h6\jetson-nano. I.e., these patches and the core configuration can be used as a single core for the entire ARM64 platform. In the logic of patches (names) I used the option that was previously discussed - the names begin with a digital index, which provides easy integration of additional patches for any platform and easy updating of patches when an update is released in the original patches of the LE build system.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines