Posts by JohnBoyz

    Because I could rarely use the test images this thread is about, I tried the most recent nightly from CoreELEC on my 905x2 X96 max 2G/16G box this morning.

    I am very pleasantly surprised at the result ...... particularly as this is the first nightly to support this box ....

    wireless is not presently working

    the SD card will not boot from SD slot but can be booted from SD to USB adapter in the USB3 slot

    For my use case ...... watching 1080 Live TV and recorded video etc .... it is actually functional now!

    I use it to view live TV from a server running tvheadend, and the stored videos/movies on several devices.

    What a surprise! I am also impressed with the display quality of this box when compared to others I have used and tried, at or near the same price point.

    I hope this is seen for what it is ..... not a promotional thing for CE but something that might help others with problems using their x96 Max boxes at the present time.

    X96 max 2G/16G 100Mb/s NIC

    Tested 20190712 AMLG12.arm but no connection through the NIC.

    20190611 AMLG12.aarch64 image is still the only one that gave me a NIC connection to LAN/internet.

    This is the info from that working image

    Sorry, had misunderstood.

    This morning used latest nightly and rmii.dtb LibreELEC-AMLG12.arm-9.80-nightly-20190702-d73a8a3-box.img.gz

    It booted with network up.

    No sound - options are greyed out

    Video problems with Live TV worse than reported above for older image.

    Video displays only while other graphic present on screen, such as info, and requires a button press to display.

    So when compared to the old image I referenced above it is less functional.

    Neither of course have wifi but the older image had sound and better video behaviour in my use/test case of Live TV.

    I don't know if that is at all helpful ..... other suggestions welcome.

    As an experiment, having the latest 2019-07-01 installed and running without working on-board NIC, I copied the 2019-06-11 arm .tar to it and rebooted.

    It 'updated' and when booting the NIC was connected.

    I think that is the last image on which the NIC worked with this box.

    Maybe balbes150 can find what the difference might be?


    Both Android and Systemd are strangers to me, so no I am bouncing about in the hope I can catch on to something. ;)

    I have done a fresh write of each of the images released.

    None of the more recent ones have provided a connection for me.

    No, nothing shows up in Kodi ..... and I can view the switch LEDs the box is plugged into and observe there that there is an attempt to make a connection but no communication (one of three LEDs light). The USB->Ethernet device has no such problem.

    All works when running the older image I mentioned previously.

    It might appear that something this depends on is missing from the build/kernel. No routing?

    At least for the moment I can ssh into the box and run some diagnostics ..... if someone has suggestions ..... using the borrowed USB NIC.


    Forgot to mention ..... yes I edit the .ini file ;)

    Just tried the 2019-07-01 S905x2 image

    No ethernet on board.

    Using borrowed USB to Ethernet adapter I was able to connect to repo.

    No wifi.

    Got a connection to the LE repo this time.

    DVB-T channels from server (uses hdhomerun tuners) do not play video, but do have sound.

    DVB-S channels some play ..... have not checked all (previously only a % played correctly) ...... tuners are Digibit R1 Sat>IP DVB-S/2

    I managed to get some info from logs.

    The first output is from the previously working NIC

    The second output when using the 2019-06-30 nonworking image

    8:38 LibreELEC systemd[1]: Found device /sys/subsystem/net/devices/eth0.
    Apr 11 17:28:38 LibreELEC systemd[1]: Starting Configure eth0 MAC address...
    Apr 11 17:28:38 LibreELEC kernel: meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
    Apr 11 17:28:38 LibreELEC kernel: meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
    Apr 11 17:28:38 LibreELEC systemd[1]: Started Configure eth0 MAC address.
    Apr 11 17:28:39 LibreELEC connmand[573]: eth0 {create} index 2 type 1 <ETHER>
    Apr 11 17:28:39 LibreELEC connmand[573]: eth0 {update} flags 4099 <UP>
    Apr 11 17:28:39 LibreELEC connmand[573]: eth0 {newlink} index 2 address 90:0E:B3:01:FE:4D mtu 1500
    Apr 11 17:28:39 LibreELEC connmand[573]: eth0 {newlink} index 2 operstate 2 <DOWN>
    Apr 11 17:28:39 LibreELEC connmand[573]: Adding interface eth0 [ ethernet ]


    I also used that image and still I do not get an ethernet connection.

    How can one determine what ethernet chip is in the device?


    EDIT: I borrowed a USB to Ethernet adapter to get eth1

    LibreELEC:~ # dmesg | grep eth0
    [   10.774490] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
    [   10.774507] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
    LibreELEC:~ #  
    LibreELEC:~ # dmesg | grep eth1
    [   11.119849] ax88179_178a 2-1:1.0 eth1: register 'ax88179_178a' at, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:ad:cf:06
    [   13.396399] ax88179_178a 2-1:1.0 eth1: ax88179 - Link status is: 1
    [   13.432155] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    LibreELEC:~ #

    2019-06-29 LibreELEC-AMLG12.arm-9.80-devel-20190629211026-f9ecb5d-s905x2.img.gz

    X96 Max 2G/16G 100M NIC used xxx-rmii.dtb

    Similar result to previous image ...... initial attempt at network connection but fails.

    Although the NIC is enabled when booted there is no connection, nor any possibility to

    enable a connection to be made manually.


    I borrowed a USB to ethernet adapter and it worked to connect to LAN.

    Unfortunately I cannot connect to LibreElec repository to install some addons. :(


    X96 Max 2g/16G 100M NIC

    Boots ok. NIC seems to connect to switch, goes off and then seems to be present again, except no data connection present.

    In the settings the NIC is 'Active' but no connection is available.

    It seems to me that the NIC is good initially during boot, with a proper connection (based on switch LEDs), but goes off and then comes back on again but without a connection.


    I went back to the aarch image from 2019-06-11 and that one provides a solid connection during boot as it did previously.