balbes150

  • Posts

    3561
  • Joined

  • Last visited

Everything posted by balbes150

  1. New version 20210920 with support for installation in eMMC\NVMe\SATA. For details of the use, see the corresponding topics. m2 https://bbs.stationpc.com/thread-211-2-1.html p2 https://bbs.stationpc.com/thread-209-1-1.html
  2. New version of images 20210915-edge with 5.15.0-rc1 kernel. Please note, this version does not have an HDMI output, control is performed via SSH or UART. The wired network works, both LAN1 and LAN2 interfaces work on P2, M2 - LAN1. Please note that this is the primary test version and unpredictable behaviors are possible.
  3. I connected the NVMe module to P2 , the system sees it and can work with it. Which image and which DTB are you using ? Here is the output of "fdisk -l", which clearly shows the presence of NVMe in the system. Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NE-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Armbian 21.11.0-trunk Hirsute ttyFIQ0 station-m2 login: root Password: ____ _ _ _ __ __ ____ / ___|| |_ __ _| |_(_) ___ _ __ | \/ |___ \ \___ \| __/ _` | __| |/ _ \| '_ \ | |\/| | __) | ___) | || (_| | |_| | (_) | | | | | | | |/ __/ |____/ \__\__,_|\__|_|\___/|_| |_| |_| |_|_____| Welcome to Armbian 21.11.0-trunk Hirsute with Linux 4.19.193 No end-user support: built from trunk System load: 62% Up time: 0 min Memory usage: 6% of 3.68G IP: 192.168.1.39 CPU temp: 30�°C Usage of /: 32% of 15G [ 2 security updates available, 7 updates total: apt upgrade ] Last check: 2021-09-08 14:13 Last login: Wed Sep 8 14:13:42 UTC 2021 on ttyFIQ0 root@station-m2:~# fdisk -l Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mtdblock0: 32 MiB, 33554432 bytes, 65536 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk0: 29.12 GiB, 31268536320 bytes, 61071360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 1E020000-0000-406A-8000-113E00001CED Device Start End Sectors Size Type /dev/mmcblk0p1 16384 24575 8192 4M unknown /dev/mmcblk0p2 24576 32767 8192 4M unknown /dev/mmcblk0p3 32768 40959 8192 4M unknown /dev/mmcblk0p4 40960 49151 8192 4M unknown /dev/mmcblk0p5 49152 51199 2048 1M unknown /dev/mmcblk0p6 51200 116735 65536 32M unknown /dev/mmcblk0p7 116736 124927 8192 4M unknown /dev/mmcblk0p8 124928 321535 196608 96M unknown /dev/mmcblk0p9 321536 1107967 786432 384M unknown /dev/mmcblk0p10 1107968 1894399 786432 384M unknown /dev/mmcblk0p11 1894400 1927167 32768 16M unknown /dev/mmcblk0p12 1927168 8300543 6373376 3G unknown /dev/mmcblk0p13 8300544 9349119 1048576 512M unknown /dev/mmcblk0p14 9349120 61071326 51722207 24.7G unknown Disk /dev/mmcblk1: 14.87 GiB, 15962472448 bytes, 31176704 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: BE4EF038-2CF8-46BD-8D6E-05E4769B6502 Device Start End Sectors Size Type /dev/mmcblk1p1 32768 65535 32768 16M Linux filesystem /dev/mmcblk1p2 65536 30834687 30769152 14.7G EFI System Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NE-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@station-m2:~#
  4. ver 20210907 kernel 4.9.210 and 5.10.62
  5. We are talking about the kernel Station-current (which now uses all the patches for LE).
  6. I asked about this because I want to understand if it makes sense to support a new kernel now. If you have no plans to use it, I want to reduce the number of different cores and remove it from support (remove it from the official build system, so as not to produce unnecessary entities).
  7. 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 ?
  8. Models with new RK chips are interesting, but such issues need to be resolved through the project manager @Igor
  9. The current version does not support installation in eMMC. Do not try to do this.
  10. 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/
  11. 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.
  12. This is the only TV box for which there was previously minimal support.
  13. These are the worst chips that should be avoided in every possible way. There is no support for them.
  14. 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.
  15. 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
  16. All patches that do not conflict are included.
  17. 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.
  18. 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.
  19. Carefully read the first message of the topic (this is specially highlighted in red). The topic is closed.