Unable to use network

Which Khadas SBC do you use?

VIM3 pro board V13 system V12

Which system do you use? Android, Ubuntu, OOWOW or others?

OOWOW, CoreELEC, Android

Which version of system do you use? Khadas official images, self built images, or others?

Khadas official - vim3-android-9-32bit-v231122.img.xz
vim3-coreelec-20.0-nexus.emmc.kresq
CoreELEC official

Please describe your issue below:

Unable to get working network under Android vim3-android-9-32bit-v231122 or official CoreELEC Nexus ng images. The adapter sets wrong DHCP settings automatically and the adapter can not connect if manual correcting the settings.
Only vim3-coreelec-20.0-nexus.emmc.kresq or CoreElec Nexus ng 20.0 or later works without problem.
Is that a known problem or my device is dying? Could my router dysfunction?

Post a console log of your issue below:

dmesg CoreElec 20.4 with 20.0 DTB booting

Hello @karmantyu

You have issues when only Android in the emmc and boot to Android system ?

Yes. I have the issues when Android installed to emmc, CoreELEC booting from SD card, CoreELEC installed to emmc dual to Android or standalone.
Only CoreELEC Nexus ng 20.0 is OK.

Tried also erasing spi, erasing partitions and content in emmc, factory reset device in oowow.
Oowow has network access. It receives dhcp settings correctly.

CoreELEC Amlogic-no aarch64 21.0 Omega nightly 20240223 is also working just fine. Is there any news why the official Android image’s network not working?

Decompiled CoreELEC Amlogic.ng 20.0 dtb and Amlogic.ng 20.2 dtb files and the single difference which makes ethernet adapter not working is:
***** 0.dts
pinctrl-0 = <0x18>;
auto_cali_idx = <0x01>;
phandle = <0x84>;
***** 2.dts
pinctrl-0 = <0x18>;
auto_cali_idx = <0x00>;
phandle = <0x84>;


I’m sure this change in dtb makes my VIM3’s ethernet not working after Nexus 20.0.
Could somebody help me out why is this change is necessary?
I’m not sure how to compile dtb’s for the different CoreELEC releases for personal use if only my VIM3 is affected for some particular reason.

I’ve got help from CoreELEC forum. Here it is a temporary solution how to mitigate the ethernet problem:

You can change **auto_cali_idx** in dtb by command below and will stick it until next update. Then you need to run commands again.

mount -o remount,rw /flash
fdtget -t i /flash/dtb.img /ethernet@ff3f0000 auto_cali_idx
fdtput -t i /flash/dtb.img /ethernet@ff3f0000 auto_cali_idx 1
fdtget -t i /flash/dtb.img /ethernet@ff3f0000 auto_cali_idx
mount -o remount,ro /flash
reboot

It is not for Android but at least CoreELEC working.

why is it still unfixed?

Do you have the same problem?

yes. I see the diy fix, but its bad to lost it after every update.

I’ve added the necessary lines only to /storage/.config/autostart.sh so the modification happens automatically on every reboot. I’ve no problem since.

1 Like

Hello @telenova

Next release will fix this issue.

1 Like