Posts by Capt.Insano

Quote from Sholander

I never use DHCP pool for my devices, always set static IP addresses, so cannot offer advice.

Try turning DHCP off on your box and give it static addresses for IPv4, Gateway and DNS servers. Make sure that the router has free static addresses outside of DHCP pool.

This are my ethernet adapter settings on my box:

(Router DHCP pool -> 192.168.1.100 - 192.168.1.200; ie all adresses outside of this pool are free)

DHCP -> Off

IPv4 -> 192.168.1.25

Subnet mask -> 255.255.255.0

Gateway -> 192.168.1.1

DNS Server 1 -> 192.168.1.1

DNS Server 2 -> 8.8.8.8

DNS Server 3 -> 1.1.1.1

With such settings everything works fine over ethernet on all my devices...

Display More

In all tests so far, I have had my dd-wrt router assign a static IP to the device outside of the DHCP pool. I have tried the T95Z Plus with either dhcp and manual settings. No dice.

Interestingly: When I used your dtb as above it changed the MAC address of ethernet port. That dtb might be very specific to your device.

I am about to pull the dtb.img from my Android ROM which works perfectly.

Quote from Sholander

Here is the LINK to gxm_q201 dtb images. They are for mentioned CoreElec versions and I don't think they will work on @wrextasy bulds

I used the above linked "gxm_q201_3g_gbit.dtb" as follows:

1. Armbian (kernel 3.14): Boots successfully but no wifi or ethernet

2. LibreELEC-S912.arm-18.0_20180601.img (this thread): no boot (black screen)

3. CoreElec (CoreELEC-S912.arm-8.90.2) : Boots, Wifi Works, Ethernet appears but only gets an IP address outside of my network (169.254.25.133, when my IP range is 192.168.1.x) and is useless.

Any further advice would be much appreciated. As you can see, I am willing to test anything and report!!

Thanks for all help so far!

Quote from Sholander

Now I have a special q201 dtb.img with 1gb ethernet which works with CoreElec versions 8.90.1 and 8.90.2. (Latest CE 8.90.3 needs again new dtb.img)

Did not try it this new dtb.img with Armbian. If you want I can upload it so you can try it out...

Please upload it and at least I can try it with either this or Wrxtasy's 8.2.4.1 LibreElec.

Thanks a million!

P.S.: How does one go aout developing new device trees? (q201 w. 1gb ethernet)

OK,

Downloaded Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img.

1. It booted without manually changing any dtb.img.

2. Booted without any wifi and ethernet again non-responsive

3. "fw_printenv" command again listed "aml_dt=gxm_q201_unsupport"

4. manually moved "gxm_q200_3g.dtb" to root as "dtb.img"

5. No Boot (black screen after T95Z Logo)

6. manually moved "gxm_q201_3g.dtb" to root as "dtb.img"

7. Booted but again no wifi, no ethernet

What should I try next?

Quote from balbes150

Try to run one of the Armbian (Mate\XFCE) variants from an external media and see how the network works with different dtb. Armbian is a normal Linux installation and it can easily change and store different settings for Internet and to check network performance. Boot to activate is no longer necessary (it is common with Libreelec of my assemblies).

I downloaded your Armbian build: Armbian_5.44_S9xxx_Ubuntu_xenial_4.16.1_mate_20180515

1. It would not boot at all on my T95Z Plus unless I manually put the meson-gxm-q200.dtb on the root of the SD as dtb.img

2. After booting, wifi works but again eth0 is non-responsive.

3. I tried other device trees:

meson-gxm-q200.dtb
meson-gxm-q201.dtb
meson-gxm-khadas-vim2.dtb
meson-gxm-nexbox-a1.dtb
meson-gxm-rbox-pro.dtb
meson-gxm-vega-s96.dtb

None of them allowed my ethernet to work.

I am falling down the rabbit hole trying to fix this problem. From posts I found about S912 on armbian.com I followed your recommendations balbes150 and ran "fw_printenv"

LibreELEC:~ # fw_printenv
EnableSelinux=permissive
active_slot=_a
aml_dt=gxm_q201_unsupport
baudrate=115200
boot_part=boot
bootcmd=run start_autoscript; run storeboot;
bootdelay=1
bootfromnand=0
bootfromrecovery=0
cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};setenv serial ${usid};fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi;
cvbs_drv=0
cvbsmode=576cvbs
display_bpp=16
display_color_bg=0
display_color_fg=0xffff
display_color_index=16
display_height=1080
display_layer=osd1
display_width=1920
dtb_mem_addr=0x1000000
ethaddr=00:15:18:01:81:31
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi;
fb_addr=0x3d800000
fb_height=1080
fb_width=1920
fdt_high=0x20000000
firstboot=0
gatewayip=10.18.9.1
hdmimode=1080p60hz
hdmitx_rgb=0
hostname=arm_gxbb
init_display=osd open;osd clear;imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale
initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000
ipaddr=10.18.9.97
jtag=apao
loadaddr=1080000
netmask=255.255.255.0
outputmode=1080p60hz
preboot=run bcb_cmd; run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;run upgrade_sadckey;run upgrade_key;forceupdate;run switch_bootmode;
recovery_from_flash=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if itest ${upgrade_step} == 3; then if ext4load mmc 1:2 ${dtb_mem_addr} /recovery/dtb.img; then echo cache dtb.img loaded; fi;if ext4load mmc 1:2 ${loadaddr} /recovery/recovery.img; then echo cache recovery.img loaded; wipeisb; bootm ${loadaddr}; fi;else fi;if imgread kernel ${recovery_part} ${loadaddr} ${recovery_offset}; then wipeisb; bootm ${loadaddr}; fi;
recovery_from_sdcard=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
recovery_from_udisk=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
recovery_offset=0
recovery_part=recovery
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serverip=10.18.9.113
start_autoscript=if usb start ; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;
start_mmc_autoscript=if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi;
start_usb_autoscript=if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 1 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 2 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 3 1020000 s905_autoscript; then autoscr 1020000; fi;
storeargs=setenv bootargs ${initargs} androidboot.selinux=${EnableSelinux} logo=${display_layer},loaded,${fb_addr},${outputmode} maxcpus=${maxcpus} vout=${outputmode},enable hdmimode=${hdmimode} cvbsmode=${cvbsmode} hdmitx=${cecconfig},hdmitx_rgb=${hdmitx_rgb}  cvbsdrv=${cvbs_drv} androidboot.firstboot=${firstboot} jtag=${jtag}; setenv bootargs ${bootargs} androidboot.hardware=amlogic;run cmdline_keys;setenv bootargs ${bootargs} androidboot.slot_suffix=${active_slot};
storeboot=echo Booting...; if unifykey get usid; then  setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if unifykey get mac; then setenv bootargs ${bootargs} mac=${ethaddr};fi;if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;run update;
switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then run recovery_from_flash;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = cold_boot; then run try_auto_burn; else if test ${reboot_mode} = fastboot; then fastboot;fi;fi;fi;fi;
try_auto_burn=update 700 750;
update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;
upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else fi;
upgrade_key=if gpio input GPIOAO_2; then echo detect upgrade key; sleep 1;if gpio input GPIOAO_2; then run update; fi;fi;
upgrade_sadckey=saradc open 0; echo detect sadckey ....;if saradc get_in_range 0 0x50; then sleep 1; if saradc get_in_range 0 0x50; then echo update by key...; run update; fi;fi;bcb_cmd=get_valid_slot;
upgrade_step=2
usb_burning=update 1000
wipe_cache=successful
wipe_data=successful

Is it normal that, as above: "aml_dt=gxm_q201_unsupport" even though I have the gxm_q200_3g.dtb in place on SD root as dtb.img?

Could this explain why my ethernet is completely messed up?

Quote from balbes150

If you have any problems with the hardware, be sure to check the use of different dtb from the image.

Thanks for the advice, I used the gxm_q200_3g.dtb device tree: (S912, Gigabit Ethernet, 3GB Ram)

The USB works but the wired connection again just appeared and disappeared without allowing me to connect.

I have posted a dmesg | paste here if it could help solve the problem: http://ix.io/1cq3

As a temporary solution, I followed the advice in this thread : https://forum.libreelec.tv/thread/11877-t95z-plus-3-32gb-display-and-network-problems-under-8-90-

which said to issue the following command to reduce the gigabit ethernet connection to 100Mbit:

echo 'ethtool -s eth0 speed 100 duplex full' >> /storage/.config/autostart.sh

This allows the ethernet port to remain active and to even get an IP address from my router.

Any suggestion on fixing the problem rather than reducing my ethernet port speeds would be much appreciated!

Edit: I spoke too soon. The ethernet is incredible unstable even after the above "fix" command and completely drops after a few minutes. If I then disconnect and reconnect via the libreelec settings it reports an IP address that is not part of my network and is useless. I also tried the gxm_q201_3g.dtb device tree and the ethernet is again not seen at all.

Just as a point: the ethernet works flawlessly in Android so I do not think it is faulty hardware.

Similar problem here as directly above:

Device: T95Z Plus (S912, 3GB Ram, Gigabit ethernet)

1. I downloaded the most recent (LibreELEC-S912.arm-18.0_20180601.img) at time of writing. Used Win32 disk imager to write to freshly formatted SD.

2. Rebooted using "reboot update" from terminal emulator to ensure multiboot was updated.

3. LibreElec booted but no USB keyboard/remote support

4. Removed the stock dtb.img from the sd card and tried again

5. LibreElec booted and my USB remote/keyboard worked perfectly but no ethernet connection appears under Settings/LibreElec/Connections

6. Reboot device

7. eth0 appears under Settings/LibreElec/Connections but when I choose to connect it disappears.

Any advice on getting ethernet working here?

Am I correct in having no dtb.img in the root of the SD card?

Any help greatly appreciated

Any update on this?

I have used the

echo 'ethtool -s eth0 speed 100 duplex full' >> /storage/.config/autostart.sh

command do enable ethernet connection, but I am aware that this means no gigabit speeds.

Any hope this can be fixed in device tree settings?

Thanks