Closed CarlKuhligk closed 2 years ago
your motherboard soc is s905x3
, not s905x.
The firmware has already brought meson-sm1-x96-max-plus.dtb
, you can choose 501
or 503
when installing with armbian-install.
If it is used in usb, manually modify the dtb in /boot/uEnv.txt to meson-sm1-x96-max-plus.dtb
and restart.
The above operations such as uploading and replacing dtb are incorrect. You do not need to replace dtb, nor do you need dd operations. Your methods of operation are wrong. Please refer to the documentation in my repository, the usage of other firmware is not universal.
You if the test 501
option is not available, try the 503
, a newly discovered variant that uses the IP1001M chip: meson-sm1-x96-max-plus-ip1001m.dtb
https://github.com/ophub/amlogic-s9xxx-armbian/blob/66b57255ae407d68a69067795cc99825e5802400/build-armbian/common-files/rootfs/etc/amlogic_model_database.conf#L57
https://github.com/ophub/amlogic-s9xxx-armbian#armbian-firmware-instructions
Thanks for the quick reply!
503x was a typing mistake, my fault.
On the picture you can see that my board (PCB Version: Q5X3_141V4.1 20112
) dont have an ethernet controller.
I will reset the hole device with the original firmware. Then i will try out the documented installation procedure again.
@CarlKuhligk
Is yours a 100M NIC? Modify the dtb name in /boot/uEnv.txt to the above, and test them separately. Feedback your test results.
Firmware X96Max_Plus_Q1_20201209-1630
and X96Max_Plus_100_20201125-1731
works fine, only problems with Bluetooth and WIFI in the Androidsystem, Ethernet works.
All other Firmware Version don't work at all.
I tested all x96 dtb-Files, only your suggested meson-sm1-x96-air.dtb
worked if i boot from sd-card.
Ethernet dont work if install it to emmc and run it.
U-Boot 2021.07-rc3-00183-gd6e1cdad51-dirty (May 31 2021 - 22:33:28 +0800) x96-max-plus
Model: AMedia X96 Max+
SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2)
DRAM: 3.8 GiB
MMC: sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2
Loading Environment from nowhere... OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@ff3f0000
Hit any key to stop autoboot: 0
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
ip a
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 9e:61:dd:65:17:aa brd ff:ff:ff:ff:ff:ff permaddr 5a:a7:11:67:4d:4f
inet 192.168.212.86/24 brd 192.168.212.255 scope global dynamic eth0
valid_lft 863981sec preferred_lft 863981sec
inet 192.168.212.87/24 brd 192.168.212.255 scope global secondary dynamic noprefixroute eth0
valid_lft 863985sec preferred_lft 863985sec
inet6 fe80::9c61:ddff:fe65:17aa/64 scope link noprefixroute
valid_lft forever preferred_lft forever
ifdown eth0
/etc/network/if-down.d/resolved: 12: mystatedir: not found
Killed old client process
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/9e:61:dd:65:17:aa
Sending on LPF/eth0/9e:61:dd:65:17:aa
Sending on Socket/fallback
DHCPRELEASE of 192.168.212.86 on eth0 to 192.168.212.1 port 67 (xid=0x14028e72)
[ 113.396864] meson8b-dwmac ff3f0000.ethernet eth0: Link is Down
ifup eth0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
[ 145.421625] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.1:08] driver [Meson G12A Internal PHY] (irq=37)
[ 145.437608] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 145.442018] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 145.448761] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rmii link mode
Listening on LPF/eth0/9e:61:dd:65:17:aa
Sending on LPF/eth0/9e:61:dd:65:17:aa
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x1db91504)
[ 146.908451] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x1db91504)
DHCPOFFER of 192.168.212.86 from 192.168.212.1
DHCPREQUEST for 192.168.212.86 on eth0 to 255.255.255.255 port 67 (xid=0x415b91d)
DHCPACK of 192.168.212.86 from 192.168.212.1 (xid=0x1db91504)
bound to 192.168.212.86 -- renewal in 346217 seconds.
/etc/network/if-up.d/resolved: 12: mystatedir: not found
[ 11.477476] systemd[1]: Starting Journal Service...
[ 11.599434] systemd[1]: Started Journal Service.
[ 11.650017] systemd-journald[878]: Received client request to flush runtime journal.
[ 14.596784] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 14.608818] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
[ 14.614756] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 14.910087] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 14.922217] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
[ 14.928204] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 15.026759] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 15.039086] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
[ 15.044984] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 15.150099] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 15.162547] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
[ 15.168424] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 15.256796] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 15.269474] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
[ 15.275259] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
I'm not an expert with all of these SoC´s, how could I identify my board as meson-sm1-x96-air
?
The installation to emmc must change stomting fundametely.
If i boot from sd card again ethernet dont work anymore.
After flashing the original image again ethernet works if i boot from sd card.
Installing option 516
causes the exact same behavior.
root@armbian:~# armbian-install
[ STEPS ] Start install armbian to emmc...
[ STEPS ] Start initializing the environment...
[ INFO ] DEV_EMMC: [ /dev/mmcblk2 ]
[ STEPS ] Start selecting device...
--------------------------------------------------------------------------------------
ID SOC MODEL DTB
--------------------------------------------------------------------------------------
101 s905d Phicomm-N1 meson-gxl-s905d-phicomm-n1.dtb
102 s905d Phicomm-N1-(DMA-thresh) meson-gxl-s905d-phicomm-n1-thresh.dtb
103 s905x HG680P-&-TBee meson-gxl-s905x-p212.dtb
104 s905w X96-Mini-&-TX3-Mini meson-gxl-s905w-tx3-mini.dtb
105 s905d MECOOL-KI-Pro meson-gxl-s905d-mecool-ki-pro.dtb
106 s905x T95 meson-gxl-s905x-p212.dtb
107 s905x B860H meson-gxl-s905x-b860h.dtb
201 s912 Octopus-Planet meson-gxm-octopus-planet.dtb
202 s912 Octopus-Planet-(FAKE) meson-gxm-octopus-planet.dtb
203 s912 H96-Pro-Plus meson-gxm-octopus-planet.dtb
204 s912 Tanix-TX92 meson-gxm-octopus-planet.dtb
205 s912 VORKE-Z6-Plus meson-gxm-octopus-planet.dtb
206 s912 MECOOL-M8S-Pro-L meson-gxm-q201.dtb
207 s912 T95Z-Plus meson-gxm-t95z-plus.dtb
208 s912 TX9-Pro meson-gxm-tx9-pro.dtb
209 s912 Nexbox-A1-&-A95X meson-gxm-nexbox-a1.dtb
301 s905x2 X96-Max-4GB meson-g12a-x96-max.dtb
302 s905x2 X96-Max-2GB meson-g12a-x96-max-rmii.dtb
303 s905x2 MECOOL-KM3-4G meson-g12a-sei510.dtb
304 s905l3a E900V22C-D meson-g12a-s905l3a-e900v22c.dtb
401 s922x Beelink-GT-King meson-g12b-gtking.dtb
402 s922x Beelink-GT-King-Pro meson-g12b-gtking-pro.dtb
403 s922x Beelink-GT-King-Pro-H meson-g12b-gtking-pro-h.dtb
404 s922x Beelink-GT-King-Pro-Rev_A meson-g12b-gtking-pro.dtb
405 s922x Hardkernel-ODroid-N2 meson-g12b-odroid-n2.dtb
406 s922x UGOOS-AM6-Plus meson-g12b-ugoos-am6.dtb
407 a311d Khadas-VIM3 meson-g12b-a311d-khadas-vim3.dtb
501 s905x3 X96-Max+ meson-sm1-x96-max-plus.dtb
502 s905x3 X96-Max+-(OverClock) meson-sm1-x96-max-plus-oc.dtb
503 s905x3 X96-Max+-(IP1001M-phy) meson-sm1-x96-max-plus-ip1001m.dtb
504 s905x3 X96-Max+-Q2 meson-sm1-x96-max-plus-q2.dtb
505 s905x3 HK1-Box meson-sm1-hk1box-vontar-x3.dtb
506 s905x3 HK1-Box-(OverClock) meson-sm1-hk1box-vontar-x3-oc.dtb
507 s905x3 H96-Max-X3 meson-sm1-h96-max-x3.dtb
508 s905x3 H96-Max-X3-(OverClock) meson-sm1-h96-max-x3-oc.dtb
509 s905x3 Ugoos-X3 meson-sm1-ugoos-x3.dtb
510 s905x3 Ugoos-X3-(OverClock) meson-sm1-ugoos-x3-oc.dtb
511 s905x3 TX3-1Gb meson-sm1-tx3-qz.dtb
512 s905x3 TX3-1Gb-(OverClock) meson-sm1-tx3-qz-oc.dtb
513 s905x3 TX3-100Mb meson-sm1-tx3-bz.dtb
514 s905x3 TX3-100Mb-(OverClock) meson-sm1-tx3-bz-oc.dtb
515 s905x3 X96-Air-1Gb meson-sm1-x96-air-gbit.dtb
516 s905x3 X96-Air-100Mb meson-sm1-x96-air.dtb
517 s905x3 X96-Air-Q1000 meson-sm1-x96-max-plus-q2.dtb
518 s905x3 A95XF3-Air-1Gb meson-sm1-a95xf3-air-gbit.dtb
519 s905x3 A95XF3-Air-100Mb meson-sm1-a95xf3-air.dtb
0 Other Customize Enter-custom-dtb-name
--------------------------------------------------------------------------------------
[ OPTIONS ] Please Input ID: 516
[ INFO ] Input Box ID: [ 516 ]
[ INFO ] FDTFILE: [ meson-sm1-x96-air.dtb ]
[ INFO ] UBOOT_OVERLOAD: [ u-boot-x96maxplus.bin ]
[ INFO ] K510: [ 1 ]
[ STEPS ] Start selecting file system type...
-----------------------------------------------
ID TYPE
-----------------------------------------------
1 ext4
2 btrfs
-----------------------------------------------
[ OPTIONS ] Please Input ID: 2
[ INFO ] Input Type ID: [ 2 ]
[ INFO ] The type of file system: [ btrfs ]
[ STEPS ] Start creating eMMC partition...
[ INFO ] Start backup default bootloader.
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.249315 s, 16.8 MB/s
1+0 records in
1+0 records out
512 bytes copied, 0.00220497 s, 232 kB/s
[ INFO ] Start create MBR and partittion.
[ 98.507886] mmcblk2:
[ 98.644880] mmcblk2: p1
[ 98.828384] mmcblk2: p1 p2
[ INFO ] Write Mainline bootloader: [ /usr/lib/u-boot/x96maxplus-u-boot.bin.sd.bin ]
444+0 records in
444+0 records out
444 bytes copied, 0.00432139 s, 103 kB/s
[ 98.858077] mmcblk2: p1 p2
2170+1 records in
2170+1 records out
1111408 bytes (1.1 MB, 1.1 MiB) copied, 0.102386 s, 10.9 MB/s
[ STEPS ] Start processing the bootfs partition...
[ INFO ] Formatting BOOTFS partition.
mkfs.fat 4.2 (2021-01-31)
[ INFO ] Start copy BOOTFS partition data.
[ INFO ] Generate the new uEnv.txt file.
[ INFO ] Copy [ u-boot-x96maxplus.bin ] to u-boot.emmc
[ STEPS ] Start processing the rootfs partition...
[ INFO ] Formatting ROOTFS partition.
btrfs-progs v5.16.2
See http://btrfs.wiki.kernel.org for more information.
Performing full device TRIM /dev/mmcblk2p2 (27.79GiB) ...
NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)
Label: ROOTFS_EMMC
UUID: 77224756-7bb9-406e-a217-80dfa1425051
Node siz[ 108.845509] BTRFS: device label ROOTFS_EMMC devid 1 transid 6 /dev/mmcblk2p2 scanned by mkfs.btrfs (3686)
e: 16384
Sector size: 4096
Filesystem size: 27.79GiB
Block group profiles:
Data: single 8.00MiB
Metadata: single 8.00MiB
System: single 4.00MiB
SSD detected: yes
Zoned device: no
Incompat features: extref, skinny-metadata, no-holes
Runtime features: free-space-tree
Checksum: crc32c
Number of devices: 1
Devices:
ID SIZE PATH
1 27.79GiB /dev/mmcblk2p2
[ 111.864590] BTRFS info (device mmcblk2p2): flagging fs with big metadata feature
[ 111.866474] BTRFS info (device mmcblk2p2): setting incompat feature flag for COMPRESS_ZSTD (0x10)
[ 111.875276] BTRFS info (device mmcblk2p2): use zstd compression, level 6
[ 111.881906] BTRFS info (device mmcblk2p2): using free space tree
[ 111.887840] BTRFS info (device mmcblk2p2): has skinny extents
[ 111.897714] BTRFS info (device mmcblk2p2): enabling ssd optimizations
[ 111.900345] BTRFS info (device mmcblk2p2): checking UUID tree
[ INFO ] Start copy ROOTFS partition data.
[ INFO ] Copy the [ etc ] directory.
[ INFO ] Copy the [ home ] directory.
[ INFO ] Copy the [ lib64 ] directory.
[ INFO ] Copy the [ opt ] directory.
[ INFO ] Copy the [ root ] directory.
[ INFO ] Copy the [ selinux ] directory.
[ INFO ] Copy the [ srv ] directory.
[ INFO ] Copy the [ usr ] directory.
[ INFO ] Copy the [ var ] directory.
[ INFO ] Generate the new fstab file.
[ INFO ] Update the relevant parameters.
[ SUCCESS ] Successful installed, please unplug the USB, re-insert the power supply to start the armbian.
Ethernet-Error still the same
[ 14.319416] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 14.332725] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
[ 14.340821] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 14.609364] meson8b-dwmac ff3f0000.ethernet eth0: validation of rmii with support 0000000,00000000,00006280 and advertisement 0000000,00000000,00006280 failed: -22
[ 14.622838] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
Discovered following:
Flash original firmware
boot from sd card FDTFILE:meson-sm1-x96-air.dtb
-> ethernet work well (rebooting 5 times, behavior don't change)
install armbian to emmc option 516
booting from emmc -> ethernet dont work (rebooting 5 times, behavior don't change)
boot from sd card FDTFILE:meson-sm1-x96-air.dtb
again - ethernet dont work (rebooting 5 times, behavior don't change)
installing option 518
or 519
(i know makes no sense, im just tryout and found something, maybe worth it?)
booting from emmc - as expected don't boot at all, makes sense because 518,519
its made for different soc. BUT
boot from sd card FDTFILE:meson-sm1-x96-air.dtb
-> ethernet works again ! (rebooting 5 times, behavior don't change)
Why does it now work again? What has changed?
The difference between option 516, 501-504
and 518,519
is the MAINLINE_UBOOT
ignoring FDTFILE
and ANDROID_UBOOT
.
I can only guess, the MAINLINE_UBOOT
gets removed while installing option 518
.
Can the x96maxplus-u-boot.bin.sd.bin
file causes the issue?
# 1. Brush back to the original Android TV system, so that the bootloader can be restored
# 2. Re-flash the sd card
# 3. Add a line to /etc/amlogic_model_database.conf, numbered 700, as follows:
700:A95XF3 Air 1Gb:s905x3:meson-sm1-a95xf3-air-gbit.dtb:u-boot-x96maxplus.bin:NA:NA
# 4. Select 700 when installing
This should be fine, you can give feedback after testing.
I tried your suggestion, but im running in to bootloader problems after installation. It seems to me that the bootloader forces sd-card boot?, if i hold the reset button, the android system starts.
I tested the hole day, but no success with different configurations. Maybe you have an idea what is going on.
You must flash back to the original Android system first, otherwise the subsequent reinstallation will be invalid
You must download today's firmware, the previous one is invalid
After booting from usb, select 505
Hello, I really appreciate your work. I wanted to install Armbian on my X96Max+. Everything worked fine except the ethernet. I saw some pictures in question issues, my board don't have a IC. I'm not familiar with the s905x, I guess it will have a build in controller.
Waht i did:
used sd card: Samsung 64GB EVO Plus U3 flash tool: balenaEtcher-Portable-1.7.9 (running as administrator)
burning image Armbian_22.08.0_Aml_s905x3_jammy_5.10.123_server_2022.06.17.img
reinsert sd card checking boot files
enabled multiboot with toothpick method
inserted sd card
inserted power connector boot log file - first boot from sd card.txt
reboot
armbian-install
install log - reboot + install armbian from sd card.txt
unplugged power
removed sd card
inserted power connector start from emmc - booting from emmc.txt
Errors that correlate to ethernet
https://github.com/ophub/amlogic-s9xxx-armbian/blob/main/build-armbian/armbian-docs/amlogic_model_database.md Says ANDROID_UBOOT hk1box-bootloader.img, at least some information, but i have no idea waht to do.
I read a lot of threads about hk1box-bootloader.img but i couldn't found helpful information.
Tried this from https://forum.armbian.com/topic/15376-methods-to-fix-x96-max-pluss905x3-gigabit-ethernet-problem/
The result of these steps is that the device don't boot.
Im not sure if I found the "right" hk1box-bootloader.img because it's not available.
What did I forget to get ethernet working?