Armin

June 16, 2020

2 hours ago, ThatUnknownGuy said:
Is there a way to enable WiFi on X96 Air?

I can see the wireless networks via
armbian-config
but I can't connect.

I have also an X96 Air (4/32 Go) and with armbian-config, I'm not able to see the wireless network:

my view

And into my report with "armbianmonitor -u", I can see a warning with the Bluetooth / Wireless chipset (rtl8822cs):

my report

What's your Bluetooth / Wireless chipset ?

Which dtb file did you select ?

Thanks in advance

June 16, 2020

11 hours ago, vanngocan said:

I am trying to install Armbian on Eachlink X3 Mini. I use image Armbian_20.05.6_Arm-64_bullseye_current_5.7.2_desktop_20200612.img with dtb file meson-sm1-sei610-ethfix.dtb (this is what I used for my X96 Air box).

It booted well from usb. However, ethernet does not work
Is there any way to fix this ethernet issue?

meson-sm1-sei610-ethfix.dtb solves some ethernet issues of meson-sm1-sei610.dtb (Eth0 visible but no connection).

What'is the result of ifconfig command ?

Please to try other dtb file !

June 16, 2020

2 hours ago, Ulwan Irfandi said:

Hi mate,
I'm using x96 max plus with s905x3 too... But always got error like this.

Hello,

I think you have this error with Android update method !!!

Not possible to boot with toothpick method on X96 Max ?

June 15, 2020

1 hour ago, nexbox said:

can you please provide the link to download this image?

Here, if I'm right !

But, for a 1st trial, the good way is to try the most recent version (link on the 1st page)

June 8, 2020

14 hours ago, Yeoj Henrie said:

I made a copy of u-boot.sd and renamed it to u-boot.ext and now it is stuck in a boot loop. I tried doing it on a usb but using u-boot.usb instead of u-boot.sd and it only boots to android. Are there any way I can make ethernet working because I don't have a keyboard to log in or type in commands. Maybe make a script that does "sudo ethtool –s eth0 speed 100 duplex full autoneg on" but I don't know how to do it by adding a file or using a pc

Ok, that means for your box, forget the way of the file boot.ext or boot.usb.

If you have tried without success the DTB file with ethernet fix (meson-sm1-sei610-ethfix.dtb), then the command "sudo ethtool –s eth0 speed 100 duplex full autoneg on" doesn't help you because these value are the same than meson-sm1-sei610-ethfix.dtb.

I think you need to know the name of your Ethernet chipset to find the right drivers of it. Without keyboard, you can check directly on the PCB of the box or with a keyboard, you make this command "armbianmonitor -u" and check into the created report (example: http://ix.io/2oEe).

June 7, 2020

28 minutes ago, Teddybee said:

Thanks. I did it that way as well. It is not working on my box, but if I plug the sd card with reader in the usb, and copy the u-boot.usb to .ext, it was working. At least the colours are fixed, but the ethernet still bad.
Have you done anything else with the ethernet? I have tried the

sudo ethtool –s [device_name] speed 100 duplex full autoneg on

, without luck.

Sorry to read that.

With meson-sm1-sei610-ethfix.dtb, the speed is already fixed to 100Mb. This is why your command with ethtool didn't change the issue. You can check the parameters with ifconfig.

No, I didn't change any parameter with meson-sm1-sei610-ethfix.dtb.

No other way to check with each DTB file into Amlogic folder !

June 7, 2020

4 hours ago, Teddybee said:

What kind of meson-sm1-sei610-ethfix.dtb have you used? I am struggling the same issue, but if I rename the u-boot.sd, the box is stuck in boot loop (reboots every 2 seconds).

This one from Ciprian28: https://forum.armbian.com/topic/12988-armbian-for-amlogic-s905x3/page/4/?tab=comments#comment-97143

Don't forget to declare it into uEnv.txt

Spoiler

LINUX=/zImage
INITRD=/uInitrd

# rk-3399
#FDT=/dtb/rockchip/rk3399-rock-pi-4.dtb
#FDT=/dtb/rockchip/rk3399-nanopc-t4.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

# rk-3328
#FDT=/dtb/rockchip/rk3328-box-trn9.dtb
#FDT=/dtb/rockchip/rk3328-box.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

# aw h6
#FDT=/dtb/allwinner/sun50i-h6-tanix-tx6.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mem=2048M video=HDMI-A-1:e

# aml s9xxx
FDT=/dtb/amlogic/meson-sm1-sei610-ethfix.dtb
#FDT=/dtb/amlogic/meson-g12b-ugoos-am6-no-cvbs.dtb
#FDT=/dtb/amlogic/meson-g12b-odroid-n2.dtb
APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

You shouldn't rename u-boot.sd but copy it before and after rename this copie to u-boot.ext

That means on the SD card, you have the u-boot.sd file and the u-boot.ext file

June 7, 2020

2 hours ago, Yeoj Henrie Sayadi said:

Hello! I have X88PRO-S905X3-D4-V1.0. I used meson-sm1-sei610.dtb and the ethernet does not work. I tried using the eth fix dtb and tried making a script that makes the auto negotiation off on startup and the ethernet still does not work. Please help

I was facing to the same Ethernet issue with meson-sm1-sei610-ethfix.dtb and the problem has been solved when I have copied file u-boot.sd to u-boot.ext on the SD card.

I don't understand the reason because I was thinking that you need to add the "u-boot.ext" file if the system doesn't want to boot or color issue but not for an ethernet issue.

Maybe @balbes150 can confirm the relation between this missing file and some others issues.

May 28, 2020

More details about the boot issue (SD ou USB support, toothpick or android update method, blackscreen or error message...) will be appreciated !

To simplify, describe all steps that you have done to try to install Armbian (maybe as this kind of detailled example: I know this is mine ! :beer: )

May 28, 2020

On 5/26/2020 at 1:40 PM, rapsacw said:

My experience so far with tv boxes;

......

X96air (s905x3, 4/64GB): installs to emmc, stable under any load, runs all versions >5.40?, best by far (so far).

Great news !!! I have chosen this box (X96air, s905x3, 4/32GB) a little bit by chance. I wanted the SoC S905x3 and 4G of RAM. The best price (~35€) was for it !

I have installed Armbian Buster since 1 week (connected 24h/24) but without loag (only domotic server but without scenarios) and for the moment, no issue !

Do you have modify the cooling (heatsink) ? Currently, my temperature is 47°.

Moreover, If you have any tips for this box (wireless, bluetooth, ethernet (currently fixed at 100Mb)....), I would appreciate it if you could share.

Greetings

May 27, 2020

On 5/26/2020 at 2:29 PM, SteeMan said:

If your question is must you update, the answer is no. However, I wouldn't understand why you would not want to update. One of the reasons to adopt Armbian is because it should provide you with regular security updates and critical bug fixes, like any regular linux distribution on an x86 platform. Armbian isn't just a static firmware that gets something running on a box/sbc but a more mainstream linux experience with updates. Anyone who runs systems (especially exposed to the public internet) should in my opinion be concerned with security updates and fixes as a priority.

Now having said that, the base ubuntu or debian will get you security updates and fixes for the majority of the system, however linux kernel updates will come from Armbian. While support for those kernel updates for Balbes TV box builds has improved significantly over the last few months, there may still be an occasional issue.

So, with armbian-config command, "enable armbian upgrades" is enough to have a system up to date ?

May 26, 2020

On 5/19/2020 at 7:56 PM, Armin said:

meson-sm1-sei610-ethfix.dtb (from Ciprian28) ==> Boot OK and Ethernet OK (already fixed at 100Mb)

Hello,

I have done a new installation with Buster (Armbian_20.05.4_Arm-64_buster_current_5.7.0-rc6_20200519.img with meson-sm1-sei610-ethfix.dtb) because for my domotic system (Jeedom), buster is recommanded.

Now, this is OK but I need to know if I must update regulary my "Buster system" ?

If Yes, the dedicated command is:

sudo apt-get --allow-releaseinfo-change update

May 25, 2020

22 hours ago, kajboj said:

So basically to avoid the blinking screen on my Tanix TX9s I need to boot the box with the hdmi cable unplugged. After say 2s after i turn on the box i need to plug in the hdmi cable and the screen stays on. This process has to be repeated everytime i boot the box.

Hello,

I'm not an expert and could imagine that the problem is on the auto-detection of the HDMI screen into the boot.ini but you have spoken about a post from @balbes150 to try without HDMI cable plugged during the 2 first seconds of the boot, that means @balbes150 has a best view than me related to the issue.

Please to wait his feedback !

During this time, you can try another kernel for example.

May 25, 2020

14 hours ago, P.P.A. said:

I bought a X96 Air the other day, and installed Armbian on it using meson-sm1-sei610-ethfix.dtb. Ethernet works, and it runs fine (I haven't tested HDMI audio because I'm using it as a headless server), however WiFi/BT does not.

From browsing this and other threads, I gathered that these boxes may have different WiFi chips, and to get it working requires identifying the chip used, and then finding the proper drivers for it (forgive my layman's vocabulary here)… and that this involves the dtb files.

How do I find out what chip my box uses? Do I need to open it up and simply look for the component? Trial and error by testing a few likely candidates for this particular model?

I think you will be able to find the wireless chipset with this command:

armbianmonitor -u

Into my report, I suppose that the wireless ( + Bluetooth = combo) chipset is rtl8822cs

May 23, 2020

13 hours ago, kajboj said:

Hi Armin,

I followed the following post

The Tanix TX9s is an AML s912 box so i didn't flash uboot. I just flashed the armbian image mentioned in my first post then i edited uEnv.txt to point to the correct dtb file. Finally i booted from the SD card using the toothpick method.

Am I missing a uboot step?

I had some issues (and not only color as mentioned) without to do it: If you are starting the system from an SD card, you need to copy file u-boot.sd to u-boot.ext,

Normally, the file u-boot.sd is already on your SD card and there is no risk to try it !

You can also try another dtb file: example ?

May 22, 2020

On 5/22/2020 at 12:07 AM, kajboj said:

Hi all,

I've got a Tanix TX9s on stock android hooked up with a Full HD TV which works just fine.

I flashed an SD card with the latest img (Armbian_20.05.4_Arm-64_bionic_current_5.7.0-rc6_20200518.img) and boot it via toothpick method. The system seems to boot fine and I could ssh to it too but there is a problem with the output from the HDMI (or at least that's my opinion). The screen shows the OS booting for say 1s and it goes black (like no signal) and after 2s the screen comes back again, then after 1s the screen goes blank again and comes back again and it keeps going like this forever. Despite the screen going on and off the OS seems to be working.

I tried all the gxm dtbs but still same output on the screen. Is there something I can try to fix this issue? Thanks in advance.

Hello,

Did you make this step ?

Copy u-boot.sd to u-boot.ext

May 21, 2020

Hello,

After I'm using the meson-g12a-x96-max-no-cvbs DTB file with forcing the ethernet speed to 100Mb (sudo ethtool –s [device_name] speed 100 duplex full autoneg on) but after several tests, the ethernet connection was not stable (poor download speed).

Therefore, I have tried several DTB file with SD card booting and best results were confirmed with meson-sm1-sei610-ethfix.dtb.

To avoid to transfer the SD installation to eMMC, I have choosen to add the DTB file and Edit uEnv.txt directly on the eMMC.

PS: @balbes150, you can move the posts here (from comment-101922 to comment-101969).

Greetings

May 19, 2020

24 minutes ago, SteeMan said:

I should have looked a bit closer at what you did, you were root so that wasn't the issue. You really need to learn basic linux commands. 'cd dtb' is what you wanted to do, not 'cd /dtb'

Yes, you're right, I got tangled. Now, this is OK ! :thumbup:

@balbes150, maybe this is better if I create a specific topic for my issues and if you can move these posts on it ?

May 19, 2020

26 minutes ago, SteeMan said:

(you should see the contents of your emmc boot directory here, now you can edit the uEnv.txt file, copy to this directory any dtb you wish, etc)

$ umount /dev/mmcblk2p1

(un-mount the disk when you are done, shutdown, pull the sd card and reboot to emmc)

I can not access to dtb directory

Spoiler

root@arm-64:~/tmp# ls
armbian_first_run.txt.template dtb
boot.bmp emmc_autoscript
boot.cmd emmc_autoscript.cmd
boot.cmd.aw initrd.img-5.7.0-rc6-arm-64
boot-desktop.png System.map-5.7.0-rc6-arm-64
boot-emmc.cmd 'System Volume Information'
boot-emmc.cmd.aw u-boot.emmc
boot-emmc.scr.aw u-boot.ext
boot.ini u-boot.usb
boot.scr uEnv.txt
boot.scr.aw uInitrd
config-5.7.0-rc6-arm-64 zImage
root@arm-64:~/tmp# cd /dtb
-bash: cd: /dtb: No such file or directory

It's in blue

May 19, 2020

1 hour ago, SteeMan said:

while running from the sd card, mount the /boot partition on the emmc and edit the uEnv.txt file on the emmc directly.

I suppose that witht the commande mount /boot is from SD Card and not from eMMC ?

So, I think I have found how to mount eMMC partition:

root@arm-64:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1      179:0    0 59.5G  0 disk
├─mmcblk1p1  179:1    0  512M  0 part /boot
└─mmcblk1p2  179:2    0 58.4G  0 part /
mmcblk2      179:32   0 29.1G  0 disk
├─mmcblk2p1  179:33   0  488M  0 part
└─mmcblk2p2  179:34   0   28G  0 part
mmcblk2boot0 179:64   0    4M  1 disk
mmcblk2boot1 179:96   0    4M  1 disk
zram0        254:0    0   50M  0 disk /var/log
zram1        254:1    0    1G  0 disk [SWAP]
root@arm-64:~# mount /dev/mmcblk2p2 /mnt

root@arm-64:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1      179:0    0 59.5G  0 disk
├─mmcblk1p1  179:1    0  512M  0 part /boot
└─mmcblk1p2  179:2    0 58.4G  0 part /
mmcblk2      179:32   0 29.1G  0 disk
├─mmcblk2p1  179:33   0  488M  0 part
└─mmcblk2p2  179:34   0   28G  0 part /mnt
mmcblk2boot0 179:64   0    4M  1 disk
mmcblk2boot1 179:96   0    4M  1 disk
zram0        254:0    0   50M  0 disk /var/log
zram1        254:1    0    1G  0 disk [SWAP]
root@arm-64:~# cd /mnt
root@arm-64:/mnt#

How can I copy meson-sm1-sei610-ethfix.dtb from SD Card to same folder on eMMC ?

May 19, 2020

52 minutes ago, SteeMan said:

To test the different DTBs, you will need to use the working sd card you have from earlier.

I have tried:

- meson-g12a-x96-max-rmii.dtb ==> Boot OK but Ethernet NOK (cannot get device settings from ethtool eth0 command)

- meson-g12b-ugoos-am6-no-cvbs.dtb ==> Boot NOK (stays on green screen)
- meson-g12b-odroid-n2.dtb ==> Boot NOK (stays on green screen)

- meson-sm1-sei610-ethfix.dtb (from Ciprian28) ==> Boot OK and Ethernet OK (already fixed at 100Mb)

Now, How Can I test deeper the ethernet connection ?

May 19, 2020

1 hour ago, SteeMan said:

Have you tried all of the dtb files to see if any of them support your ethernet setup without needing to make manual changes? From above it looks like you are using: meson-g12a-x96-max-no-cvbs.dtb. I would suggest you try meson-g12a-x96-max-rmii.dtb which is a 100Mb ethernet version of the meson-g112a-x96-max.dtb file.

Good to see that you have made overall progress today on your box.

To be honest, when I read your comment, I was not "hot" to follow your recommendations because I suppose that I make the manual change only 1x and this is fix definitively.

But, I have tried to install a French domotic server (Jeedom) but I have some troubles with ethernet connection:

Spoiler

After this operation, 6,481 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com bionic/main arm64 libapr1 arm64 1.6.3-2 [75.8 kB]
Get:2 http://ports.ubuntu.com bionic/main arm64 libaprutil1 arm64 1.6.1-2 [74.7 kB]
Get:3 http://ports.ubuntu.com bionic/main arm64 libaprutil1-dbd-sqlite3 arm64 1.6.1-2 [9,836 B]
Err:4 http://ports.ubuntu.com bionic/main arm64 libaprutil1-ldap arm64 1.6.1-2
Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable) Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out [IP: 91.189.88.150 80]

Therefore, I will try your suggestion: meson-g12a-x96-max-rmii.dtb

After booting on SD card:

- How can I test deeply the ethernet connection (before to transfer the installtion on the eMMC) ?

- When this is OK, Can I make directly the installation on the eMMC over the previous one ?

May 19, 2020

On my X96 Air, I have installed Armbian (without desktop) like this:

1. Boot from SD card: https://forum.armbian.com/topic/12988-armbian-for-amlogic-s905x3/page/7/?tab=comments#comment-101885

2. Boot from eMMC: https://forum.armbian.com/topic/12988-armbian-for-amlogic-s905x3/page/8/?tab=comments#comment-101897

May 19, 2020

"armbianmonitor -u" from my box: http://ix.io/2mI6

May 19, 2020

You're right, the u-boo.sd was already existing into the boot folder.

So, I have done the installation on eMMC like this:

sudo su root
cd /root
./install-aml.sh

And find the result:

Spoiler

root@arm-64:~# ./install-aml.sh
Start script create MBR and filesystem
/dev/mmcblk2
Start backup u-boot default
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.10851 s, 38.7 MB/s
Start create MBR and partittion
Start restore u-boot
442+0 records in
442+0 records out
442 bytes copied, 0.00293262 s, 151 kB/s
8191+0 records in
8191+0 records out
4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.431306 s, 9.7 MB/s
Done
Start copy system for eMMC.
Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
done.
Cppying BOOT...done.
Edit init config...done.
Formatting ROOT partition...
e2fsck 1.44.1 (24-Mar-2018)
ROOT_EMMC: clean, 11/1835008 files, 159229/7337728 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
Create MEDIA
Create MNT
Copy OPT
Create PROC
Copy ROOT
Create RUN
Copy SBIN
Copy SELINUX
Copy SRV
Create SYS
Create TMP
Copy USR
Copy VAR
Copy fstab
*******************************************
Complete copy OS to eMMC
*******************************************
root@arm-64:~# root@arm-64:~# ./install-aml.sh
Start copy system for eMMC.
Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
done.
Cppying BOOT...done.
Edit init config...done.
Formatting ROOT partition...
e2fsck 1.44.1 (24-Mar-2018)
ROOT_EMMC: clean, 11/1835008 files, 159229/7337728 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
Create MEDIA
Create MNT
Copy OPT
Create PROC
Copy ROOT
Create RUN
Copy SBIN
Copy SELINUX
Copy SRV
Create SYS
Create TMP
Copy USR
Copy VAR
Copy fstab
*******************************************
Complete copy OS to eMMC
*******************************************
root@arm-64:~#

But to copy this report from PuTTY, I have selected the text and done a right-clic (wrong idea) because This is execute a kind of script:

Spoiler

*******************************************
Complete copy OS to eMMC
*******************************************
root@arm-64:~#
root@arm-64:~#: command not found
root@arm-64:~# Start script create MBR and filesystem

Command 'Start' not found, did you mean:

command 'tart' from deb tart

Try: apt install <deb name>

root@arm-64:~# /dev/mmcblk2
bash: /dev/mmcblk2: Permission denied
root@arm-64:~# Start backup u-boot default

Command 'Start' not found, did you mean:

command 'tart' from deb tart

Try: apt install <deb name>

root@arm-64:~# 4+0 records in
4+0: command not found
root@arm-64:~# 4+0 records out
4+0: command not found
root@arm-64:~# 4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.10851 s, 38.7 MB/s
bash: syntax error near unexpected token `('
root@arm-64:~# Start create MBR and partittion

Command 'Start' not found, did you mean:

command 'tart' from deb tart

Try: apt install <deb name>

root@arm-64:~# Start restore u-boot

Command 'Start' not found, did you mean:

command 'tart' from deb tart

Try: apt install <deb name>

root@arm-64:~# 442+0 records in
442+0: command not found
root@arm-64:~# 442+0 records out
442+0: command not found
root@arm-64:~# 442 bytes copied, 0.00293262 s, 151 kB/s
442: command not found
root@arm-64:~# 8191+0 records in
8191+0: command not found
root@arm-64:~# 8191+0 records out
8191+0: command not found
root@arm-64:~# 4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.431306 s, 9.7 MB/s
bash: syntax error near unexpected token `('
root@arm-64:~# Done

Command 'Done' not found, did you mean:

command 'one' from deb opennebula

Try: apt install <deb name>

root@arm-64:~# Start copy system for eMMC.

Command 'Start' not found, did you mean:

command 'tart' from deb tart

Try: apt install <deb name>

root@arm-64:~# Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
bash: syntax error near unexpected token `('
root@arm-64:~# done.
^[done.: command not found
root@arm-64:~# Cppying BOOT...done.
Cppying: command not found
root@arm-64:~# Edit init config...done.

Command 'Edit' not found, did you mean:

command 'edit' from deb mime-support

Try: apt install <deb name>

root@arm-64:~# Formatting ROOT partition...
Formatting: command not found
root@arm-64:~# e2fsck 1.44.1 (24-Mar-2018)
bash: syntax error near unexpected token `('
root@arm-64:~# ROOT_EMMC: clean, 11/1835008 files, 159229/7337728 blocks
ROOT_EMMC:: command not found
root@arm-64:~# done.
done.: command not found
root@arm-64:~# Copying ROOTFS.
Copying: command not found
root@arm-64:~# Copy BIN

Command 'Copy' not found, did you mean: