X96 Max Plus A100 no LAN after installing on eMMC #121
Comments
Click to show pictures of the board
|
|
Your network card cannot be used, indicating that there is no network card driver. What is your network card chip? IP1001M?The network card chip IP1001M can be used in Android, but the mainline kernel has not been driven yet. |
|
Thank you for your answer. Do you have a suggestion how to find out what chip it is? What i assume could be it on the board does not have any readable text, and in the dmesg output, the dtb or the /sys/ tree of the Android system i don't see anything like that. X96Max_Plus_A100_20210608-1518.img Android dmesg
X96Max_Plus_A100_20210608-1518.img Android dtb
As I mentioned, when booting from USB while Android is installed, the network card works. |
|
The IP1001M network card can be used on Android, and the manufacturer has made integrated customization. However, this driver is not currently available in the Linux kernel, so it cannot be used in armbian. You can look at the code and model number on the motherboard's network card chip. Supported network cards can be found in the kernel source code: https://github.com/unifreq/linux-5.15.y/tree/main/drivers/net/ethernet |
|
Look at these 2 articles, did you buy a counterfeit product? https://discourse.coreelec.org/t/x96-max-plus-a100-how-to-identify-a-fake-device/16457 |
Hello, I have a few X96 Max Plus boxes, the Android Firmware is X96Max_Plus_A100_20210608-1518.img.
Printed on the board is "Q5X3_141 V4.1 20112".
I can't reliably boot from SD card (can randomly rarely get it to boot some images on some SD cards some times, reflashing and pressing the toothpick button 10+ times sometimes works, sometimes not), but booting from USB works. (booting from SD card works after installing bootloader on the eMMC)
I managed to get eth0 working when booting from USB, but it seems breaks after replacing the bootloader on the eMMC.
After replacing the bootloader on the eMMC it even breaks LAN when booting from USB again.
Details:
with Image: Armbian_22.02.0_Aml_s905x3_focal_5.4.180_2022.02.19.0051.img.gz
booting from USB with default dtb in uEnv.txt FDT=/dtb/amlogic/meson-sm1-x96-max-plus-100m.dtb
dmesg|grep eth
booting from USB with meson-sm1-x96-max-plus.dtb
dmesg|grep eth
booting from USB with meson-sm1-sei610.dtb
dmesg|grep eth
booting from USB with meson-sm1-sei610_578.dtb (inspired by #95)
dmesg|grep eth
armbian-install (selecting 51: X96 Max+)
booting from eMMC, default dtb is meson-sm1-x96-max-plus.dtb
dmesg|grep eth
booting from eMMC with meson-sm1-sei610.dtb
dmesg|grep eth
booting from USB with meson-sm1-x96-max-plus.dtb (after installing on eMMC)
dmesg|grep eth
booting from USB with meson-sm1-sei610.dtb (after installing on eMMC)
dmesg|grep eth
I also get this output from the bootloader on the screen when booting after armbian-install:
U-Boot output
I also tried the kernel 5.10 image, but results were similar (didn't retest for this issue).
I also tried upgrading to the newest kernel 5.16.10 (at time of testing), it most notably made the HDMI use the resolution of the connected monitor, however it didn't make the LAN work when installed on eMMC. (I believe it actually lowered the reliability of the LAN connection previously when booting from USB, but i have no accurate test of that)
I also tried to install the Android bootloader instead of mainline with "armbian-install no", because i read somewhere else that the hk1 bootloader works better, and that fits the filename of the Android Bootloader in the table for 51:X96 Max+: hk1box-bootloader.img.
However, that bricked the box :(.
In the U-Boot Output it is aware of the ethernet interface, i assume for PXE support.
Where do the U-Boot blobs come from? Can i compile the exact same myself, but leave out ethernet support, does that make any sense?
If it doesn't touch the ethernet with wrong parameters it may not mess it up. Or is the initialization by the bootloader actually required?
Do you have any suggestions that could help me get the Ethernet working?
Thank you.
The text was updated successfully, but these errors were encountered: