Posts by dtech

Quote from MakaaiD

I have not noticed any boot time change between USB boot (multiboot) and SDcard only boot.

Unfortunately, I don't know what boot scripts you actually use, since you said you didn't use the toothpick method again. The boot order may also be different, so the information is unfortunately not relevant.

By the way, it might be device specific, but for me it takes 10 seconds for the USB ports to be scanned, which is a lot for me.

Quote from MakaaiD

Normally, once boot, I always keep it on or on standby mode & use remote to wake-up.

In this build, power-off have only 3 option (power off, custom shutdown & restart), don't have 4th option for suspend (sleep). I had to override in setting - power saving - Force suspend instead of poweroff .

For many devices, standby mode is not the default or is not available at all. This is also a uboot-specific property defined by the manufacturer. (By the way, this "Force suspend instead of poweroff" is only available in my builds, because it's my own solution.)

And, if someone boots from an internal NAND/eMMC, they always have to wait to scan the USB unnecessarily. And, since many people can't even use the suspend option, every start will take forever. This is not good, so we need an intermediate solution that is acceptable to everyone, and I am currently working on this.

The original 3-script solution is unnecessarily overcomplicated. I'm currently testing the single-script solution and I introduced a small modification, so the USB boot is inactive by default, but it can be simply activated by an fw_setenv enableusbboot 1 command.

Quote from MakaaiD

I installed docket but how to install portainer? It's not in add-on. Needs to use CLI?

It is recommended to use the CLI, but there are many places describing how to use it, so I don't want to write complex documentation for this.

mkdir /storage/.config/dockers
docker run \
 --name=portainer \
 --restart unless-stopped \
 -v /var/run/docker.sock:/var/run/docker.sock \
 -v /storage/.config/dockers/portainer/data:/data \
 -p 9000:9000 \
 -d portainer/portainer-ce

Quote from MakaaiD

From your attachment, unzipped 3 files in root folder ( aml_autoscript file replaced ) of USB & booted straight from USB flash-drive. I already had multiboot activated from previous installed so I do NOT have to use toothpick first time.

Thanks for the test, maybe I will restore these boot scripts on the 3rdParty k200 and n200 images.

Edit:

In the meantime, I tested it and now it works for me too, but whether I boot from USB (or not), it causes +10 seconds in the boot time, which I think is too much. With the current script, the time elapsed until the LibreELEC logo appeared on the M8S+ from power-on was 14 seconds, with the restored multiboot scripts it was 24 seconds.

Basically, I don't know how many people would use USB boot, but I'm strongly thinking about reworking these bootscripts because I don't want to restore them in their current state.

Quote from chewitt

... it looks like the same "search for boot files" stuff used everywhere.

I'd still appreciate some links, because many of the developers building S8X2 on the old BSP kernel have simply deleted their GitHub repos. (Demetris, balbes150, etc.)

By the way, if these are really the affected files, then I indicate that I removed them because none of my boxes were able to boot from USB (omitted u-boot function?), despite the above scripts. For this reason, I deleted them, and only the aml_autoscript remained, without the USB boot option, because the original 3-script solution increased the start of the boxes by about 10 seconds, and this was unacceptable to me.

MakaaiD Please try these boot scripts with my image: https://libreelec.dtech.hu/.upload/s8x2-old-bootscripts.zip
Of course, the toothpick method will be necessary again to load them.

Quote from chewitt

It's basically the same "search for stuff on SD, USB, eMMC" sequence that AMLGX uses, only looking for older filenames.

Are you actually talking about these scripts?

MakaaiD

Unfortunately, I don't know anything about multiboot, so if you can send me some link or description, I would appreciate it.

dnmnhat

Based on the entire log, it really seems that the file system is damaged or the memory card is faulty. For example, the LibreELEC Settings add-on also reports errors, which is also not a good sign. As chewitt suggested, please try making another SD card and boot from it.

Quote from Lirk

Display Spoiler

https://paste.libreelec.tv/premium-hawk.log

Based on the log, reinitialization of the SDIO bus fails, but I don't really understand why.

Was this a clean install? Because based on the amount of installed addons, I wouldn't guess that.

If you have upgraded from a previous system or restored a backup from an older system, I would definitely recommend performing a clean installation. Also, if the dtb you are using comes from an external source, that could also be a reason. Only use dtbs from the device_trees directory.

Quote from Lirk

chip:0xa9a6. It looks like AP6236?

Nope, it is just an AP6212.

If you definitely want to send a log under my version, please send a link generated by the pastekodi command instead.

Quote from bidi

I have a board that looks like an MXQ HD18Q, but the Wi-Fi doesn't work because the Wi-Fi chip is different (S9082H). Is there a chance you could add a driver?

S9082-series wifi chips are probably clones and there is no open source driver available for them unfortunately.

Quote from Lirk

I don't know, but vendor determined by MAC is "AMPAK".

That's why it would be good to have the relevant part of a kernel log from a previous working system.

For example: dmesg | grep dhd

(If it's really Ampak, which is actually an SDIO wifi+bt combo adapter based on Broadcom chips.)

Quote from Lirk

1. Doesn't work WIFI module, as in previous LE versions (16.x to 17.x). According to MAC Address range: 44:2C:05:00:00:00 - 44:2C:05:FF:FF:FF, vendor is "AMPAK". I tried to run LE with different device trees, working without WIFI support was: gxbb_p200_1G_100M.dtb, gxbb_p200_1G_100M_RealtekWiFi.dtb, gxbb_p200_1G_wetek_hub.dtb, gxbb_p200_k1_plus.dtb. But WIFI work on LE13 with "meson-gxbb-nexbox-a95x.dtb" device tree.

2. Properly working software deinterlace on SD resolutions was from 16.x to 17.x versions, but from 18.x version it work with frame dropping.

3. From 18.x version doesn't work OK button, but it fixed with this solution manually: RE: Ok button doesn't work on H1 remote

You have written a lot of things, but there is not much meaningful information in it.

What box do you have? And specifically, what kind of WiFi chip is in your box?

If you could send me a log, both from the previous working and the currently non-working versions, I might be able to help.

Updated statement of Docker support for LibreELEC-AML v9.2 (LTS)

The current version is now available via auto-update channel, as well as via the links in the leading post, and support extends to 3rdParty images as well.

The Docker binary has been added to the repository, but the LinuxServer.io repository addon was not added, because the 32-bit ARM images are no longer updated:

32-bit Arm Deprecation Notice | Info :: LinuxServer.io

As we previously announced, due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we have now deprecated all 32-bit Arm…

info.linuxserver.io

Quote from Rizwan

Is there DVB drivers issue possible ?

I don't think so, but I still don't understand exactly what the error above means, because you still haven't sent a log.

Does it produce this between boots if connected to the same TV and same input?

A log would be good for both cases, when the relevant resolution appears and when it doesn't.

Quote from Rizwan

Sometime UHD res showing whitelist and other time disappear, what is the reason for wp2 ?

Unfortunately, I have no idea, I haven't seen anything like it before.

First of all, I would recommend changing the HDMI cable, but since the S905 SoC (GXBB) in WP2 only meets the HDMI 1.4 specification, even the cable can't be the cause.

Quote from Rizwan

any other advantage can I get now after this slight higher version

If this was meant to be a question (because the question mark is missing), then it is quite difficult to summarize.

Quite a lot has been added since the last release of the official LE 9.2.6: several amlogic specific patches added, many built-in packages updated, certificates updated, quite a few addons also updated, external binary addons added (e.g. tvheadend v4.3), Leia-related Youtube addon repo added (this is also constantly updated), etc.

If you have the patience for it, you can read the changelog in the leading post.

Quote from Rizwan

I used arrowed file, asked u in previous post, is there any device tree issue ?

Okay, you used the correct file when updating. A device tree issue is not possible, because the dtb will also be updated.

However, you didn't answer my other question, which is also just as important:

Quote from dtech

Did the tuner finally appear on the adapter page after you changed the driver?

DVB driver change: Add-ons -> Program add-ons -> LibreELEC Module Drivers

And you could also send a link generated by pastekodi needs to be run on console, hopefully something will be revealed from the logs.

Quote from Rizwan

My all scanned channels showing in kodi, but, not playing, I restore my backup for all settings, nothing works,

Did the tuner finally appear on the adapter page after you changed the driver?

Also, please confirm that you updated your box using WeTek_Play_2 update tar image and not Generic_S905.

Quote from Rizwan

tvheadend no tvadapter showing

I don't remember what DVB driver addons were present in version 9.0, so I recommend that you select another one under 9.2.

Add-ons -> Program add-ons -> LibreELEC Module Drivers