Posts by dtech

  • Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    Quote from SerGioTenerife

    Thank you so much for everything, but it no longer proves anything, that I don't have much time.

    Thanks a lot for everything.

    I'm sorry I couldn't really help you.

    The truth is, I’m also trying to provide support for devices I’ve never had at all. And since I can't test these myself that way, and I can't debug any errors myself on them, so it's really just a remote series of experiments. And if something failed, it’s actually just a waste of time for me too. Unfortunately, I never know if actually I made a mistake or the tester messed up something. That’s when I usually come with this sentence: "Are you sure you did exactly that...?" Although I may have actually screwed up something.

    Unfortunately, I start to get a little tired of these. :(

    --

    Edit:

    Which snapsot image did you test? "20210901" or "20210903"? Unfortunately, this is by no means an insignificant parameter.

    For snapshots, the main version number matters much less, the build date matters first.

  • Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    There are new snapshot images for Minix-based devices: Index of /snapshots/20210906/

    Quote from Momantai

    - Every time I try to stop, it freezes... doesnt matter what I command then, just a reboot to make it alive again;

    Okay, I replaced the platform_init script with the one I modified for M8S+.

    This was preceded by quite a long experimentation, but there it finally solved the freeze on the M8S+.

    Although it didn’t work on n200 (MXIII-based) devices, that’s why I didn’t apply it to anything other than M8S+ because I can’t test.

    I would ask you to test it please.

    Quote from Momantai

    There´ s no sign if it is on or off - the led is dead;

    Unfortunately, I cannot comment on this. I use the datrh solution. Did it work under his image?

    Quote from Momantai

    As far as I´ ve seen, the player isn´ t as smooth as before - some image tearing during playback.

    Let's see now if the new initramfs script solved this as well. If not, I would like clarification as to which videos are not playing properly.

  • Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    Quote from blackride

    And last build 9.2.8.2 (also bluetooth don't work)

    I don't know why rtl8723bs doesn't work even though it's turned back on.

    Code: linux.arm.conf
    ...
CONFIG_RTL8723BS=m
...

    Neither the external nor the internal module works. I don't know why, but I'm going crazy about it! :cursing:

    ...

    Okay, maybe we have one more option, so please send the output from these commands under the old 9.2.8.1:

    Code
    cat /sys/class/net/wlan0/device/vendor
cat /sys/class/net/wlan0/device/device

    I need to know the vendor ID and the product ID of the integrated wireless/bluetooth SDIO module.

  • Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    In the previous log, you almost misled me because the adapter connected for the second time was the V4:

    These require completely different kernel modules:

    V4 -> 0bda:8178 (rtl8192cu)

    V5 -> 2357:0107 (rtl8192eu)

    I will try to find out why it does not load the module for the V5 (rtl8192eu).

    In your CE log the trace looks very ugly after connecting the USB wifi device:

    https://paste.kodi.tv/idowabezoh

    That looks pretty sick. =O

    Quote from blackride

    i update LE with version 9.8.2.1 on 9.2.8.2 via tar archive.

    The numbers were mixed up again: 9.2.8.1 -> 9.8.2.1 (Translator malfunction?)

    However, if you could check the current image with V4, that would be good, because it also got a new driver.

    If it doesn't work, I will go back to the old one.

  • Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    Quote from blackride

    I update 9.8.2.1 via *.tar* and no changes.

    The version number (9.2.8.2) has changed a bit, but it's okay. ^^

    The Amlogic project branch of CE 9.2.7 "non-ng" build contains exactly the same driver, so it's a little weird.

    I need more information, so you should follow exactly the following steps:

    1. Start the box without connecting the USB stick.
    2. dmesg -c
      This prints the dmesg and also deletes it. From now on, only recent changes are relevant.
    3. cat /etc/os-release | grep PRETTY_NAME
    4. lsmod | grep cfg80211
    5. Now connect the USB wifi adapter.
    6. dmesg -c
    7. lsmod | grep cfg80211

    I connected the TL-WN722N v1 to my M8Q as an example, but I would expect something similar:

    Code
    M8Q:~ # dmesg -c
...
M8Q:~ # cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="LibreELEC (dtech): 9.2.8.2"
M8Q:~ # lsmod | grep cfg80211
cfg80211              206547  1 8188eu

    The USB device is now connected...

    If this is possible, you should do this under my image on your MXIII-clone as well as from the other box under CE with same USB wifi stick.

    By the way, I also ordered a WN821N today, the version will unfortunately only be revealed if it is in my hands.

  • Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    Quote from blackride

    Are you can add driver for rtl8192eu in your builds?

    My builds are already contain this driver in this package "RTL8192EU-aml".

    Code: projects/MXIII-S8X2/options
    ...
  # e.g. ADDITIONAL_DRIVERS="DRIVER1 DRIVER2"
    ADDITIONAL_DRIVERS="gpu-aml RTL8192CU-aml RTL8192DU RTL8192EU-aml RTL8812AU RTL8188EU-aml mt7601u-aml"
...

    Could you send a dmesg and an lsusb output from your MXIII-clone when the WN821N is connected during the whole boot process?

  • Help with Mecool K1 Plus

    Quote from bumerc

    There are KI Plus boards with an S905 processor. A photo of someone else's board does not explain the difference between the two different boot ROM logs.

    S905??? No!!!

    It is definitely GXL, not GXBB. So the SoC is S905D (or X/W/L).

    See the first post in this topic (same message was at the first time):

    Quote from creited

    GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;

    Second time... Your bootloader also contains this string:

    Code
    "Built : 15:21:58, Mar 26 2020. gxl g486bc38 - gongwei.chen@droid11-sz"

    Check the screenshot from PuTTY:

    Quote from PuTTY window

    GXL:fixed PLL lock failed

    BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;

    So, what is the next question?