armbian-install, wifi, ethernet not working on x96 mini (s905w)
box-automation1 opened this issue · comments
Before You Open ISSUE, Make Sure You have Read Armbian Firmware Instructions and Documentation
Describe the bug
- I booted Armbian_22.11.0_Aml_s905w_jammy_5.15.73_server_2022.10.13.img.gz from SD card by renaming
u-boot-s905x-s912.bin
tou-boot.ext
andextlinux.conf.bak
toextlinux.conf
- While Loading, it notifies that wifi, ethernet failed to load. ( see screenshot below )
- armbian-install complains that there is no onboard emmc present. ( see screenshot below )
Expected behavior
- Wifi, ethernet should load during startup.
- armbian-install should install armbian to x96 mini emmc.
Screenshots
- Kernel Version: 5.15.73
- Release: jammy
- Edition: server
Device (please complete the following information):
- SOC: S095w
- Brand: none
- Model: x96 mini
Additional context
- Wifi works with external usb adapter TP Link Archer T3U( mediatek chip )
- Last rom flashed was Android 9 Stock Rom
- Photos of my box below:
Can you show your /dev folder?
The Sv6051 wifi chip seems don't have a driver in the kernel, it's normal that wifi don't work.
Don't rename extlinux.conf.bak, don't rename u-boot, can you send me the tutorial address where you see these 2 operations.
Try to modify the dtb name:
vi /boot/uEnv.txt
Modify the name of the dtb file
Test the following 2 files separately
meson-sm1-sei610.dtb
meson-g12a-x96-max-rmii.dtb
sync && reboot
Can you show your /dev folder? The Sv6051 wifi chip seems don't have a driver in the kernel, it's normal that wifi don't work.
Don't rename extlinux.conf.bak, don't rename u-boot, can you send me the tutorial address where you see these 2 operations.
I realized that renaming u-boot-s905x-s912.bin
to u-boot.ext
is not needed but the system fails to boot without renaming extlinux.conf.bak
to extlinux.conf
( check attached photo below )
It only boots if I rename extlinux.conf.bak
to extlinux.conf
Test the following 2 files separately
meson-sm1-sei610.dtb
meson-g12a-x96-max-rmii.dtb
Tried both of them, none work. The system boots, but armbian-install complains that there is no emmc present and wifi doesn't work.
Can you show your /dev folder? The Sv6051 wifi chip seems don't have a driver in the kernel, it's normal that wifi don't work.
I see. There's only one mmcblk under your /dev and it seems like your sd card. Your internal emmc wasn't recognized by the system. Strange 🤔
try meson-gxl-s905w-p281.dtb
lsblk
The u-boot.ext
was unnecessary, my fault.
If you use extlinux.conf, modify dtb in both his and uEnv.txt files.
Will try modifying in both and report.
u-boot is not needed, you will cause a lot of errors if you add it. For unknown devices, do not add these unwanted files arbitrarily.
Yes, the system boots without u-boot.
But it doesn't boot if I don't rename extlinux.conf.bak, This error
meson-gxl-s905x-p212.dtb
meson-gxl-s905w-p281.dtb
Test these public version files to see which one can drive your wired network card.
Can you show your /dev folder? The Sv6051 wifi chip seems don't have a driver in the kernel, it's normal that wifi don't work.
I see. There's only one mmcblk under your /dev and it seems like your sd card. Your internal emmc wasn't recognized by the system. Strange 🤔
Yes, it completely fails to detect the internal emmc.
There is no independent network card chip on the motherboard, which is integrated by the soc.
Do you know which NIC driver the box needs?
There is no independent network card chip on the motherboard, which is integrated by the soc.
Do you know which NIC driver the box needs?
I'll check if wifi works on bables150's firmware to confirm. On another note, the wifi isn't related with the emmc not being detected right?
There is no independent network card chip on the motherboard, which is integrated by the soc.
Do you know which NIC driver the box needs?I'll check if wifi works on bables150's firmware to confirm. On another note, the wifi isn't related with the emmc not being detected right?
Yeah, doesn't work on that either, I checked on armbian forums, and more users faced similar with sv6051/sv6051p(ssv6051/ssv6051p) wifi chips.
There is a driver for sv6051/p, but it's for 3.x kernel and the driver is poorly written and needs to be re-written for 5.x kernel.
So apparently wifi will be completely dead and I'll have to use my wifi adaptor for that. I'm fine with that for now, but is there any solution for the emmc not being detected?
try below instruction for detect internal EMMC:
sudo apt-get install device-tree-compiler
dtc -I dtb -O dts -o meson-gxl-s905w-p281.dts meson-gxl-s905w-p281.dtb
edit this file searching for "mmc@74000" block
max-frequency = <0x5f5e100>;
5f5e100 in hex = 100000000 in dec
edit it to 0x2faf080, 50000000 in dec
dtc -I dts -O dtb -o meson-gxl-s905w-p281.dtb meson-gxl-s905w-p281.dts
try below instruction for detect internal EMMC:
sudo apt-get install device-tree-compiler
dtc -I dtb -O dts -o meson-gxl-s905w-p281.dts meson-gxl-s905w-p281.dtb
edit this file searching for "mmc@74000" block max-frequency = <0x5f5e100>; 5f5e100 in hex = 100000000 in dec edit it to 0x2faf080, 50000000 in dec
dtc -I dts -O dtb -o meson-gxl-s905w-p281.dtb meson-gxl-s905w-p281.dts
Thanks a lot, install to emmc works.
meson-gxl-s905w-p281.zip
@ophub could the above dtb be added in source(for x96 mini) with @TThanhXuan as author ?
Thanks for sharing, I will add your two names to the dts source code.
Did you test that both wired and wireless work?
meson-gxl-s905w-x96-mini.dtb.zip
I compiled it according to the above revisions. After you download it, unzip it, upload it to the /boot/dtb/amlogic
directory, change the previous two configuration files(extlinux.conf
& uEnv.txt
), and restart the test to see if it is correct.
You download the dtb file in the above post and test feedback, no problem. I submitted it to the unifreq kernel source repository.
meson-gxl-s905w-x96-mini.dts
// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
* Copyright (c) 2018 Martin Blumenstingl <martin.blumenstingl@googlemail.com>.
* Based on meson-gxl-s905d-p231.dts:
* - Copyright (c) 2016 Endless Computers, Inc.
* Author: Carlo Caione <carlo@endlessm.com>
* github.com/TThanhXuan, github.com/box-automation1, github.com/unifreq
*/
/dts-v1/;
#include "meson-gxl-s905w-p281.dts"
/ {
compatible = "amlogic,p281", "amlogic,s905w", "amlogic,meson-gxl";
model = "X96 mini";
};
/* eMMC */
&sd_emmc_c {
max-frequency = <50000000>;
};
Did you test that both wired and wireless work?
This only fixes armbian-install
Wifi cannot be fixed due to missing drivers :( [ Need to rewrite drivers from 3.xx kernel to 5.xx )
Works with armbian-install. lsblk
also detects internal emmc
Is the wired network card working?
Strange, just found this issue, but my old version downloaded here can detect emmc directly.
Same X96 mini with S905W 2+16G, inferior CPU can only go up to 1.2G.
Installed to emmc and running for about one year...
uname -a Linux X96mini 5.4.184-flippy-70+o #395 SMP PREEMPT Fri Mar 11 22:39:41 CST 2022 aarch64 aarch64 aarch64 GNU/Linux
cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=lepotato
BOARD_NAME="Aml s905w"
BOARDFAMILY=meson-gxl
BUILD_REPOSITORY_URL=https://github.com/armbian/build.git
BUILD_REPOSITORY_COMMIT=2daf351
VERSION=22.05.0-trunk
LINUXFAMILY=meson64
ARCH=arm64
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=current
x96 mini emmc中已经安装来armbian系统想重装,需要先擦除emmc中都系统才能从U盘中启动吗?
如果usb无法启动,把emmc里/boot下的boot.src和boot.cmd改个名字就无法从emmc启动了,也就会从usb启动了
那你就线刷会安卓吧
那你就线刷会安卓吧
好的,感谢回复。
Just installed armbian with kernel version 6.1.34 on a X96-Mini. Setup went smooth following the suggestions on this issue.
However, the system is only recognising 923Mb of RAM instead of the 2Gb the board has.
Do you have any idea why this might be happening @ophub ?
armbian-update -k 6.1.33
Try updating other kernels
armbian-update -k 6.1.33
Try updating other kernels
Tried it, but it didn't work ai'm afraid
https://github.com/ophub/kernel/releases/tag/kernel_stable
Try updating other kernels
Just installed armbian with kernel version 6.1.34 on a X96-Mini. Setup went smooth following the suggestions on this issue. However, the system is only recognising 923Mb of RAM instead of the 2Gb the board has. Do you have any idea why this might be happening @ophub ?
I have this exact same issue. I have 2 x96 mini. One of them shows up as 2gb ram and other shows up as 1gb only. In android, both of them show up as 2gb ram.
I've noticed something weird though. On the 2gb box, the ram utilization is ~600mb and on the box that falsely shows up as 1gb, the ram utilization is exactly half, i.e. ~300mb. These observations were made by running both the boxes side-by-side. Ram measurements in both cases are directly after boot.
Another observation is with a desktop environment running with the same video playback on both the boxes. The first box reported 1400mb ram usage and the second box reported exactly half (~700mb) ram usage with the same desktop environment and same video playback.
This makes me believe that the entire ram is being used, but the software reports utlization by a ratio of 0.5
Just to note, to avoid confusion, the account box-automation1 is mine, and the images posted above of the box is the one that works correctly (software reports 2gb ram)
Same issue with x96 mini. Wired interface is working, but wireless interface is not existed. It is under the latest kernel version "6.1.34". @ophub
$ uname -a
Linux armbian 6.1.34-ophub #1 SMP Thu Jun 15 22:19:25 EDT 2023 aarch64 aarch64 aarch64 GNU/Linux
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
link/tunnel6 :: brd :: permaddr 5613:86a2:308::
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a2:b1:d2:61:69:b1 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.81/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
valid_lft 85651sec preferred_lft 85651sec
inet6 fe80::9d9e:d5f0:9339:a2a5/64 scope link noprefixroute
valid_lft forever preferred_lft forever
What version of the kernel did you have before you could use the wireless function normally?
您好!现在x906mini安装ambian,只需要uenv.rext中指定dtb就可以了,不需要其他多余的操作?
对
谢谢您的回复,一会把盒子折腾起来。
I have the same TV BOX, but need a desktop version,
I try this image : Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img
I see this tutorial https://youtu.be/WngZ4ncBQM8?feature=shared
but my TV BOX do not boot nothing, i press my AV buttom from inside for boot but nothing
any idea?
ussing this server version can install desktop ?
- Now try ussing: Armbian_23.08.0_amlogic_s905w_lunar_6.1.50_server_2023.09.02.img
- who these files i need to rename to u-boot.ext , but need edit text file extlinux.conf.bak
extlinux.conf.bak , text inside:
armbian-software
201
armbian-software 201
201 ?
Your system files are not downloaded here, use the method to check in the downloaded post.
Your system files are not downloaded here, use the method to check in the downloaded post.
I need the desktop version,
the link is died:
Give me a real link
I will use this links https://mirror-us-phx1.armbian.airframes.io/dl/aml-s9xx-box/archive/?sort=time&order=asc
Hello @ophub, I need some help!
I'm trying to run boot mode from tf sd card and my x96 mini with two scenarios:
- Add my
meson-gxl-s905w-x96-mini.dtb
to the uEnv.txt and renameu-boot-s905x-s912.bin
tou-boot.ext
- the result continues reloads with x96 logo blinking - Add my
meson-gxl-s905w-x96-mini.dtb
to the uEnv.txt - screen goes black and my monitor goes sleep mode as no signal is coming
Please, can u advise what I did wrong? Or what can I do else?
UPD
Never mind, it was a problem of my monitor. It doesn't want to work with terminal/boot mode.
however, can u help me to setup wifi? Any external or internal. Seem like armbian does not see my external usb wifi as well :(
internal wifi could not be working.
found how to enable my RLT8188GU
here is the link for those how is looking too.
For future users that can't achieve an install (no boot with the sd card like other users).
Check out the chip inside is really S905W. I received a X96mini with a H313 CPU, batch from october 2023.
Trying with USB and SD and various variations but I only get to the Android bootloader on my older X96-mini.
The only difference I can think of is that I previously installed CoreELEC on the emmc, which is still working for normal booting. Is this a known issue with some easy way to get Armbian boot from USB/SD anyways?