Try unplugging all devices from USB ports and try to run LE with all USB connectors.
Posts by balbes150
-
-
When i insert SD card or USB stick device boots to libreelec error message.
How can i activate multiboot in the image and the box?1. What image do you use ?
2. What is the content of the error ? -
thank you for responding i kept the aml_autoscript in this time(i get you now keep in the file and if goes to boot loop after inital first time use remove) and recieced this error report device T8 AML V2 S812 best regards sir you and all the devs total respect, picture of error report attached.Multiboot you have now been activated. Try to write the image to a USB flash drive and run from it (activate multiboot NO longer need, You already have it enabled).
Had a go, boots ok, Wireless doesnt even appear as an option to turn on in Librelec settings, bluetooth also doesnt work if turned on, and wired network fails to obtain an ip from dhcp (due to the different lan chipset obviously)Yet I have no options. If You are familiar with Linux, you can run Armbian and there to run all the tests to find a working configuration. Then it can be transferred to the LE.
-
Do NOT remove the script aml_autoscript. The first launch of the toothpick should be with this file. This script delete only the case that after the first use the system to fixate and constantly restarts itself.
-
The only difference in the set of files for the firmware and dtb. If Your equipment all works is to change it makes no sense.
-
Will your build works with it?You can check yourself. Start from external media may not change how the internal memory (firmware). If not appropriate, just shut off external media with this version of the LE and use the same system.
[hr]Display More
I would just like to thank you for your work on this release, it really is appreciated!I have a MXIII-G 2/8 with Android 5, I thought I was going to have to get a new box if I wanted to run Kodi 17 but you have made it possible !
A couple of small questions....
I dont want to install to internal as having Android is useful, I’m happy to boot from SD, however is it possible to “reboot from NAND” as in kszaq’s build for the 90x boxes...
Also I cant seem to get the box to suspend it only seems to want to power off, is this normal or is there anything I can do about it?1. Reboot in NAND previously worked, I'll check.
2. These regimes essentially depend on the firmware and settings of the kernel and dtb. You need to have the same model, is to find a solution. -
Hey balbes50, thanks for all your hard work on this. Works perfect on MXIII-G 2/8GB.
Just wondering if you plan to release version with Kodi 17.1 Final as opposed to the RC
It is now possible to have a part of the image a set of different files for remotes from different models of TV boxes. Just choose that option and rename it on the media in the default name (remote.conf). If you want, what would Your version of the configuration file was part of the image to send it to me, I will add in the next version.
[hr]Used latest image in T8 AML V2 S812 re,oved aml script as instructed and used used toothpick method and encountered this any ideas?
Describe in detail the steps You are doing.
[hr]
Loaded up on a new usb drive, no wifi, no bluetooth,Try image labeling M8S. There are changes for WiFi and BT. Not the fact that will work, but there is a chance.
-
image LAN100 (Test\20170326)
-
Option image LAN100 - in the Assembly process when it is ready, I will. All sources from which I gather can be found here.
-
Version M8S Test\20170326 (collected on the basis of AlexElec). There is a possibility that can work brcm4335. Anyone can test this possibility.
-
I put together a new version of the test image LAN1000 20170326. Please check this option on the subject of the work WiFi. In the coming days, I hope to get another test image for Minix.
-
Anything for bcm4335?I hope that next week will be a test version with this chip.
Will this delete android (nand flash)?:When running from external media , the firmware in the internal memory remains unchanged. Note that to run my image, you need to activate the multi-boot from that image. This error happens when you don't have the same version of multi-boot and the settings in the image LE. As You activate the multiboot ?
-
Test version LAN1000 (Test\20170324). Contrast MXIII_Plus in the Appendix the basic data for dtb s802\s812 and another set of files for WiFi and BT. Please to those who will test - write which model and that of iron works or does not work.
-
Updated image 20170322 for MXIII_Plus and compatible models. Images for the other options can come later. To complete verification, the principles of dtb remain the same (because of the probability of the lack of necessary support in the firmware of other models).
As far as I know you have to modify u-boot for S8xx devices to support a separate dtb file. Or boot using booti but then you'll be only able to boot from SD card.U-boot S812 (tronsmart MXIII_Plus it is exactly) there are teams that can use for individual download dtb data. But the main problem is that there is no command that allows to record these data separately from the image "boot.img". As I understand it, the teams separate read dtb, take the data from the image. Maybe I'm wrong, but the team booti is used for aarch64 and s812 it is not in u-boot. The command bootm works well with split data (kernel \ initrd \ dtb). I'm using it in production systems with Linux s812\802\805. By the way, I obnovil images Armbian for s812. Those interested can try them. The details are here.
Armbian for Amlogic S802/S812 - Page 2 - Amlogic - Armbian forum
p.s.
There is a solution to the problem with the lack of a separate team entry dtb. If you add in the composition of the image LE utility (e.g. mkbootimg or similar), which will allow you to collect "boot.img" from a running system (before you capture the image in the internal memory) of the current kernel and the correct dtb with which the system was able to boot from external media. On Armbian I've checked in the manual mode it works (don't have time to automate this process a script). -
You stole my announcement.
I'm just dealing with the issue. And I hope that in the images, which I plan to publish soon, will this support. Common core with a set of separate dtb files for the different models. But there's a caveat - I'm not sure that all TV boxes have firmware support this mode in u-boot. -
For easier debugging, support WiFi, I have collected new images Armnian (Ubuntu Mate). This system is NOT yet intended for full video playback. This way is convenient for debugging and testing of the various modules and settings. To use. To download an image, burn to media, you can activate the multi-boot. All operations in the same way as when using LE. Pay attention to one difference - to start, you must be sure to manually add the correct dtb file (dtb.img) to the root of the FAT partition (you can choose from existing files on the media in the directory dtb). For WiFi settings you need from the terminal to boot to the desired module. For example "sudo modrobe dhd". Details initial settings Armbian to run the system can be read on the forum Armbian (the principles are the same for all models s8xxx and s9xxx). That would make work wifi network, You can freely in the working system to change\add configuration files to add / change files, firmware, etc. once You get a working configuration, it will be possible to port it to LE and assemble a working image LE.
-
I hope to be able next week to find the time to assemble a new variant with partial error correction.
-
Test 20170301