Jump to content

balbes150

Members
  • Posts

    4436
  • Joined

  • Last visited

Everything posted by balbes150

  1. Judging from the conclusion of the command "printenv" on your Board uses a standard u-boot, which can use a universal multiload. You can try to activate multi-boot with Android (as it is on all TV boxes) ? And then show the output of the "printenv" command again.
  2. This is not output from u-boot. You need to stop starting the system from u-boot and only then execute the "printenv" command.
  3. You do not have a root directory mounted. What partition size is /dev/data ?
  4. To reduce the size of memory reservations, you need to change the dtb file and the kernel configuration. What exact image of Armbian do you use ? What version of the firmware in the eMMC ? What exact model and what dtb file is used ?
  5. No, you don't need to install Android. You need to rerun the Armbian installation from the same USB drive.
  6. I need to see the output of the "printenv" command from u-boot. Need to leave to run u-boot and execute the command "printenv" and "help". The result is shown here.
  7. Re-run the installation. When you first install the changed sections.
  8. A new u-boot is needed to run kernel 4.9. I checked on my Tronsmart Vega S96 (S912) - with the dtb from VIM2 and the new u-boot system working with the 4.9 core.
  9. Use only *image.deb and * dtb.deb. Package firmware is used for Wi-Fi (if it does not work with the current batch firmware 5.41)
  10. I don't keep old images (of too many). Maybe someone of the users has them. Or you can try to install an older kernel from the options. https://yadi.sk/d/LBA4bXk_32RGZ6
  11. You set the normal cooling system (radiator + fan+modification of the housing for access of air) ?
  12. For the new 4.9 kernel, you can only use dtb files from an image (from the /dtb directory). Any of firmware with Android 7 (it uses a kernel 4.9). Dtb files from kernel 3.14 are not compatible with kernel 4.9. Thank you for offering me help. But I had already decided this question.
  13. Have you downloaded the WiFi module ? Command from root "modprobe dhd" or " modprobe wifi_dummy".
  14. Are you familiar with Linux commands ? The easiest solution is to run on a Linux PC, connect the new card (8Gb), create two partitions on it with labels BOOT (about 90-100 MB) and ROOTFS (everything else). Connect the old card (16 GB) and copy all the files from the old card to the new one from the root user.
  15. With this option, you need to deal with your sources for the wifi module.
  16. To modify partitions, you must modify the dtb file. And change the installation script so that it takes into account the partition name change.
  17. You have the s812. The message about chip 805 refers to the bootloader that is part of the image. What steps did you take ? Why do you start u-boot from SD card ? Did you remove the regular u-boot from NAND ?
  18. You only need to connect three contacts. Gnd Tx Rx
  19. On the Board of the TV box should be the contacts for connecting the UART. This is usually 4 contact. The photo does not show the entire cost.
  20. The latest version of kernel packages (20180216) can be installed as you wrote. In this version of the deb packages have all the wifi modules. In previous versions of deb packages (< 20180216), this was not the case. The complete set of modules could only be obtained from the image. I don't have network repositories for installing packages yet.
  21. If multi-boot is enabled, then (to start the system from external media) you can use any media (SD or USB).
  22. Try to use the image 20180216. In the kernel with updated modules WiFi and added module sv6051. I pay attention all, in connection with change of sources, the module name for qca9377 changed, now it is called "wlan".
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines