Closed HoYin90 closed 1 year ago
EMMC启动:
_ _ ____ ___ ___ ____ _ _____
/ \ _ __ ___ | | / ___|/ _ \ / _ \| ___|| |___ / __ _
/ _ \ | '_ ` _ \| | \___ \ (_) | | | |___ \| | |_ \ / _` |
/ ___ \| | | | | | | ___) \__, | |_| |___) | |___) | (_| |
/_/ \_\_| |_| |_|_| |____/ /_/ \___/|____/|_|____/ \__,_|
Welcome to Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o
System load: 14% Up time: 0 min
Memory usage: 8% of 1.91G IP: 192.168.1.12
CPU temp: 44°C Usage of /: 9% of 14G
RX today: 231.9 KiB
Last login: Sun Nov 27 00:44:17 2022 from 192.168.1.89
root@lepotato:~#
root@lepotato:~#
root@lepotato:~# df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 196M 3.3M 193M 2% /run
/dev/mmcblk2p2 14G 1.3G 13G 9% /
tmpfs 978M 0 978M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 978M 4.0K 978M 1% /tmp
/dev/mmcblk2p1 252M 100M 152M 40% /boot
/dev/zram1 47M 1.7M 42M 4% /var/log
tmpfs 196M 0 196M 0% /run/user/0
root@lepotato:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 0 1 2 3
maximum transition latency: 50.0 us.
hardware limits: 1000 MHz - 1.80 GHz
available frequency steps: 1000 MHz, 1.20 GHz, 1.40 GHz, 1.51 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz
available cpufreq governors: powersave, conservative, userspace, ondemand, performance, schedutil
current policy: frequency should be within 1.40 GHz and 1.80 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency is 1.80 GHz (asserted by call to hardware).
有内核失速(CPU STALL)问题的同学可以试一下我编译这个固件在你们的能适用不
EMMC启动: __ __ / \ | | / |/ \ / | || |_ / / \ | ' ` | | _ \ (_) | | | | | | | \ / ` | / | | | | | | | ) , | || |_) | |) | (| | /_/ _| || ||| |**/ // /|**_/||__/ ,_|
Welcome to Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o
System load: 14% Up time: 0 min Memory usage: 8% of 1.91G IP: 192.168.1.12 CPU temp: 44°C Usage of /: 9% of 14G RX today: 231.9 KiB
Last login: Sun Nov 27 00:44:17 2022 from 192.168.1.89 root@lepotato:~# root@lepotato:~# root@lepotato:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 196M 3.3M 193M 2% /run /dev/mmcblk2p2 14G 1.3G 13G 9% / tmpfs 978M 0 978M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 978M 4.0K 978M 1% /tmp /dev/mmcblk2p1 252M 100M 152M 40% /boot /dev/zram1 47M 1.7M 42M 4% /var/log tmpfs 196M 0 196M 0% /run/user/0 root@lepotato:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 50.0 us. hardware limits: 1000 MHz - 1.80 GHz available frequency steps: 1000 MHz, 1.20 GHz, 1.40 GHz, 1.51 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz available cpufreq governors: powersave, conservative, userspace, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 1.80 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 1.80 GHz (asserted by call to hardware).
docker能安装成功吗,青龙能装上不
EMMC启动: __ __ / \ | | / |/ \ / | || |_ / / \ | ' ` | | _ \ (_) | | | | | | | \ / ` | / | | | | | | | ) , | || |_) | |_) | (| | // | || ||| |/ // _/|****/|_|__/ ,_| Welcome to Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o System load: 14% Up time: 0 min Memory usage: 8% of 1.91G IP: 192.168.1.12 CPU temp: 44°C Usage of /: 9% of 14G RX today: 231.9 KiB Last login: Sun Nov 27 00:44:17 2022 from 192.168.1.89 root@lepotato:~# root@lepotato:~# root@lepotato:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 196M 3.3M 193M 2% /run /dev/mmcblk2p2 14G 1.3G 13G 9% / tmpfs 978M 0 978M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 978M 4.0K 978M 1% /tmp /dev/mmcblk2p1 252M 100M 152M 40% /boot /dev/zram1 47M 1.7M 42M 4% /var/log tmpfs 196M 0 196M 0% /run/user/0 root@lepotato:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 50.0 us. hardware limits: 1000 MHz - 1.80 GHz available frequency steps: 1000 MHz, 1.20 GHz, 1.40 GHz, 1.51 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz available cpufreq governors: powersave, conservative, userspace, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 1.80 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 1.80 GHz (asserted by call to hardware).
docker能安装成功吗,青龙能装上不
docker 能装,不知道你们说的青龙是什么,好吃吗?:)
EMMC启动: __ __ / \ | | / |/ \ / | || |_ / / \ | ' ` | | _ \ (_) | | | | | | | \ / ` | / | | | | | | | ) , | || |_) | |_) | (| | // | || ||| |/ // _/|****/|_|__/ ,_| Welcome to Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o System load: 14% Up time: 0 min Memory usage: 8% of 1.91G IP: 192.168.1.12 CPU temp: 44°C Usage of /: 9% of 14G RX today: 231.9 KiB Last login: Sun Nov 27 00:44:17 2022 from 192.168.1.89 root@lepotato:~# root@lepotato:~# root@lepotato:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 196M 3.3M 193M 2% /run /dev/mmcblk2p2 14G 1.3G 13G 9% / tmpfs 978M 0 978M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 978M 4.0K 978M 1% /tmp /dev/mmcblk2p1 252M 100M 152M 40% /boot /dev/zram1 47M 1.7M 42M 4% /var/log tmpfs 196M 0 196M 0% /run/user/0 root@lepotato:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 50.0 us. hardware limits: 1000 MHz - 1.80 GHz available frequency steps: 1000 MHz, 1.20 GHz, 1.40 GHz, 1.51 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz available cpufreq governors: powersave, conservative, userspace, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 1.80 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 1.80 GHz (asserted by call to hardware).
docker能安装成功吗,青龙能装上不
docker 能装,不知道你们说的青龙是什么,好吃吗?:)
肯定好吃啊,我突然发现装成功了,真是薛定谔
EMMC启动: __ __ / \ | | / |/ \ / | || |_ / / \ | ' ` | | _ \ (_) | | | | | | | \ / ` | / | | | | | | | ) , | || |_) | |_) | (| | // | || ||| |/ // _/|****/|_|__/ ,_| Welcome to Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o System load: 14% Up time: 0 min Memory usage: 8% of 1.91G IP: 192.168.1.12 CPU temp: 44°C Usage of /: 9% of 14G RX today: 231.9 KiB Last login: Sun Nov 27 00:44:17 2022 from 192.168.1.89 root@lepotato:~# root@lepotato:~# root@lepotato:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 196M 3.3M 193M 2% /run /dev/mmcblk2p2 14G 1.3G 13G 9% / tmpfs 978M 0 978M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 978M 4.0K 978M 1% /tmp /dev/mmcblk2p1 252M 100M 152M 40% /boot /dev/zram1 47M 1.7M 42M 4% /var/log tmpfs 196M 0 196M 0% /run/user/0 root@lepotato:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 50.0 us. hardware limits: 1000 MHz - 1.80 GHz available frequency steps: 1000 MHz, 1.20 GHz, 1.40 GHz, 1.51 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz available cpufreq governors: powersave, conservative, userspace, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 1.80 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 1.80 GHz (asserted by call to hardware).
docker能安装成功吗,青龙能装上不
docker 能装,不知道你们说的青龙是什么,好吃吗?:)
肯定好吃啊,我突然发现装成功了,真是薛定谔
淡定,经得住测试的才是好东西,盒子的世界太多小问题了。。。
EMMC启动: __ __ / \ | | / |/ \ / | || |_ / / \ | ' ` | | _ \ (_) | | | | | | | \ / ` | / | | | | | | | ) , | || |_) | |_) | (| | // | || ||| |/ // _/|****/|_|__/ ,_| Welcome to Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o System load: 14% Up time: 0 min Memory usage: 8% of 1.91G IP: 192.168.1.12 CPU temp: 44°C Usage of /: 9% of 14G RX today: 231.9 KiB Last login: Sun Nov 27 00:44:17 2022 from 192.168.1.89 root@lepotato:~# root@lepotato:~# root@lepotato:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 196M 3.3M 193M 2% /run /dev/mmcblk2p2 14G 1.3G 13G 9% / tmpfs 978M 0 978M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 978M 4.0K 978M 1% /tmp /dev/mmcblk2p1 252M 100M 152M 40% /boot /dev/zram1 47M 1.7M 42M 4% /var/log tmpfs 196M 0 196M 0% /run/user/0 root@lepotato:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 50.0 us. hardware limits: 1000 MHz - 1.80 GHz available frequency steps: 1000 MHz, 1.20 GHz, 1.40 GHz, 1.51 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz available cpufreq governors: powersave, conservative, userspace, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 1.80 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 1.80 GHz (asserted by call to hardware).
docker能安装成功吗,青龙能装上不
docker 能装,不知道你们说的青龙是什么,好吃吗?:)
肯定好吃啊,我突然发现装成功了,真是薛定谔
淡定,经得住测试的才是好东西,盒子的世界太多小问题了。。。
经不住。。。刚又报恐慌。。。死机了
经不住。。。刚又报恐慌。。。死机了
那没辙了,不知道是个体差异太大还是我的盒子没经过真正的考验
经不住。。。刚又报恐慌。。。死机了
那没辙了,不知道是个体差异太大还是我的盒子没经过真正的考验
只要安装青龙就会报恐慌
经不住。。。刚又报恐慌。。。死机了
那没辙了,不知道是个体差异太大还是我的盒子没经过真正的考验
只要安装青龙就会报恐慌
怎么装,我试试看会不会报
经不住。。。刚又报恐慌。。。死机了
那没辙了,不知道是个体差异太大还是我的盒子没经过真正的考验
只要安装青龙就会报恐慌
怎么装,我试试看会不会报
docker run -dit \ -v $PWD/ql:/ql/data \ -p 5700:5700 \ --name qinglong \ --hostname qinglong \ --restart unless-stopped \ whyour/qinglong:latest
经不住。。。刚又报恐慌。。。死机了
那没辙了,不知道是个体差异太大还是我的盒子没经过真正的考验
只要安装青龙就会报恐慌
怎么装,我试试看会不会报
docker run -dit -v $PWD/ql:/ql/data -p 5700:5700 --name qinglong --hostname qinglong --restart unless-stopped whyour/qinglong:latest
安装完,之后呢?
经不住。。。刚又报恐慌。。。死机了
那没辙了,不知道是个体差异太大还是我的盒子没经过真正的考验
只要安装青龙就会报恐慌
怎么装,我试试看会不会报
docker run -dit -v $PWD/ql:/ql/data -p 5700:5700 --name qinglong --hostname qinglong --restart unless-stopped whyour/qinglong:latest
安装完,之后呢?
访问 ip:5700
访问 ip:5700
没这些冬冬,弄不了
访问 ip:5700
没这些冬冬,弄不了
可以跳过的啊
我现在重启板子之后又没报那鬼东西了,真的好薛定谔,希望能稳定吧,我在怀疑会不会是电压不稳定导致的
可以跳过的啊
跳过了。。
可以跳过的啊
跳过了。。
然后可以百度了
然后可以百度了
不熟悉这个的业务,所以无法重现你那边的问题。哈哈
然后可以百度了
不熟悉这个的业务,所以无法重现你那边的问题。哈哈
也许是板子不一样吧
也许是板子不一样吧
我们中出了一块假的m401a,哈
然后可以百度了
不熟悉这个的业务,所以无法重现你那边的问题。哈哈
把你先刷包发我一下,512401880@qq.com
也许是板子不一样吧
我们中出了一块假的m401a,哈
你的是伪造的
512401880@qq.com
发了,你折腾一下吧
发了,你折腾一下吧
搞
我刚又重刷固件装一编5.15,网卡\写入emmc等等都正常。
盒子:m401A (无标注任何地方的版本) 固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 dtb: meson-g12a-s905l3a-m401a.dtb 发行版: Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o
======================= 1,u盘启动 把我编译的m401a的dtb放到U盘目录 \dtb\amlogic\下 修改U盘下uEnv.txt文件: FDT=/dtb/amlogic/meson-g12a-s905l3a-m401a.dtb 2.写入EMMC /etc/amlogic_model_database.conf里增加一行: 306 :M401A :s905l3a :meson-g12a-s905l3a-m401a.dtb :u-boot-e900v22c.bin :NA :NA :meson-g12a :s905l3a :no
然后不带参数写入emmc:armbian-install
这个包果然稳定,从刷包到安装docker,一气呵成
说句题外话,你们的m401a能玩coreelec和emuelec吗,我选g12a_s905x2_2g.dtb不能启动。
我刚又重刷固件装一编5.15,网卡\写入emmc等等都正常。
盒子:m401A (无标注任何地方的版本) 固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 dtb: meson-g12a-s905l3a-m401a.dtb 发行版: Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o
======================= 1,u盘启动 把我编译的m401a的dtb放到U盘目录 \dtb\amlogic\下 修改U盘下uEnv.txt文件: FDT=/dtb/amlogic/meson-g12a-s905l3a-m401a.dtb 2.写入EMMC /etc/amlogic_model_database.conf里增加一行: 306 :M401A :s905l3a :meson-g12a-s905l3a-m401a.dtb :u-boot-e900v22c.bin :NA :NA :meson-g12a :s905l3a :no
然后不带参数写入emmc:armbian-install
这个dtb替换到我刷好EMMC的盒子里启动和网络都没问题,系统5.15.76,挂几天测试下稳定性
我刚又重刷固件装一编5.15,网卡\写入emmc等等都正常。
盒子:m401A (无标注任何地方的版本) 固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 dtb: meson-g12a-s905l3a-m401a.dtb 发行版: Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o
======================= 1,u盘启动 把我编译的m401a的dtb放到U盘目录 \dtb\amlogic\下 修改U盘下uEnv.txt文件: FDT=/dtb/amlogic/meson-g12a-s905l3a-m401a.dtb 2.写入EMMC /etc/amlogic_model_database.conf里增加一行: 306 :M401A :s905l3a :meson-g12a-s905l3a-m401a.dtb :u-boot-e900v22c.bin :NA :NA :meson-g12a :s905l3a :no
然后不带参数写入emmc:armbian-install
真是痛苦……我这边问题依旧,照样抛恐慌……心碎了都
我刚又重刷固件装一编5.15,网卡\写入emmc等等都正常。 盒子:m401A (无标注任何地方的版本) 固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 dtb: meson-g12a-s905l3a-m401a.dtb 发行版: Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o ======================= 1,u盘启动 把我编译的m401a的dtb放到U盘目录 \dtb\amlogic\下 修改U盘下uEnv.txt文件: FDT=/dtb/amlogic/meson-g12a-s905l3a-m401a.dtb 2.写入EMMC /etc/amlogic_model_database.conf里增加一行: 306 :M401A :s905l3a :meson-g12a-s905l3a-m401a.dtb :u-boot-e900v22c.bin :NA :NA :meson-g12a :s905l3a :no 然后不带参数写入emmc:armbian-install meson-g12a-s905l3a-m401a.zip
真是痛苦……我这边问题依旧,照样抛恐慌……心碎了都
这个没法避免了,我也还是遇到,看后续吧,不过已经变少了
我刚又重刷固件装一编5.15,网卡\写入emmc等等都正常。 盒子:m401A (无标注任何地方的版本) 固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 dtb: meson-g12a-s905l3a-m401a.dtb 发行版: Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o ======================= 1,u盘启动 把我编译的m401a的dtb放到U盘目录 \dtb\amlogic\下 修改U盘下uEnv.txt文件: FDT=/dtb/amlogic/meson-g12a-s905l3a-m401a.dtb 2.写入EMMC /etc/amlogic_model_database.conf里增加一行: 306 :M401A :s905l3a :meson-g12a-s905l3a-m401a.dtb :u-boot-e900v22c.bin :NA :NA :meson-g12a :s905l3a :no 然后不带参数写入emmc:armbian-install meson-g12a-s905l3a-m401a.zip
真是痛苦……我这边问题依旧,照样抛恐慌……心碎了都
这个没法避免了,我也还是遇到,看后续吧,不过已经变少了
这盒子实在是玄学 ……
我刚又重刷固件装一编5.15,网卡\写入emmc等等都正常。 盒子:m401A (无标注任何地方的版本) 固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 dtb: meson-g12a-s905l3a-m401a.dtb 发行版: Armbian 22.08.10 Jammy with Linux 5.15.79-flippy-78+o ======================= 1,u盘启动 把我编译的m401a的dtb放到U盘目录 \dtb\amlogic\下 修改U盘下uEnv.txt文件: FDT=/dtb/amlogic/meson-g12a-s905l3a-m401a.dtb 2.写入EMMC /etc/amlogic_model_database.conf里增加一行: 306 :M401A :s905l3a :meson-g12a-s905l3a-m401a.dtb :u-boot-e900v22c.bin :NA :NA :meson-g12a :s905l3a :no 然后不带参数写入emmc:armbian-install meson-g12a-s905l3a-m401a.zip
真是痛苦……我这边问题依旧,照样抛恐慌……心碎了都
发下用的安卓包,armbian,dtb等等,看看哪种配合稳定 目前我这边5.10系列不死机,5.15随机死,都是跑Docker+Hassio
同志们,我的江苏m401a似乎正常了 各种灵异恐慌似乎都是cpu频率跑高了导致的 魔改了一下janko888(https://github.com/ophub/amlogic-s9xxx-armbian/issues/732#issuecomment-1328081842) 改的m401a.dtb,把cpu最高频率定在1704mhz,目前写入emmc一切正常。 meson-g12a-s905l3a-m401a-js.zip
大概步骤:
1.线刷安卓固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包
2.u盘写入: Armbian_22.11.0_Aml_s905l3a_jammy_5.15.80_server_2022.11.26.img
3.放入新的dtb,修改uEnv,u-boot用u200的改名
到这里应该就可以顺利U盘启动了
4.nano /etc/amlogic_model_database.conf,修改或添加306
306:M401A :s905l3a :meson-g12a-s905l3a-m401a-js.dtb :u-boot-u200.bin :NA :NA :meson-g12a :s905l3a :no
5.nano /sbin/armbian-install,找到s905l3a "${boxid}" -eq "305"那一串
305改成306;BLANK=68;BOOT=1024;BLANK2=290
elif [[ "${AMLOGIC_SOC}" == "s905l3a" && "${boxid}" -eq "306" ]]; then
BLANK1="68"
BOOT="1024"
BLANK2="290"
这里数字是专门去读了第一步安卓固件写入后的分区并整理来的
6.armbian-install写入emmc
7.启动后会发现ssh经常启动失败,搜到了#721,把/etc/custom_service/start_service.sh中以下几行注释掉解决
# Start ssh service
#[[ -d "/var/run/sshd" ]] || mkdir -p -m0755 /var/run/sshd
#[[ -f "/etc/init.d/ssh" ]] && /etc/init.d/ssh start 2>/dev/null
8.ip获取奇奇怪怪,偶尔会拿到多个ip但任意一个都连不上,最后路由器绑定静态ip解决。
目前装上docker hass node-red mqtt,一天过去了没有任何报错 各位手头m401a疑似体质不好的可以试试看 于是现在有个小问题,我要如何再次从u盘启动……我记得前几天有看到某个人发了解决方案,但突然找不到了……
同志们,我的江苏m401a似乎正常了 各种灵异恐慌似乎都是cpu频率跑高了导致的 魔改了一下janko888(https://github.com/ophub/amlogic-s9xxx-armbian/issues/732#issuecomment-1328081842) 改的m401a.dtb,把cpu最高频率定在1704mhz,目前写入emmc一切正常。 meson-g12a-s905l3a-m401a-js.zip
大概步骤: 1.线刷安卓固件:江苏版M401A_晶晨S905L3A_2+16G_安卓9_原厂官改_开启ROOT_线刷固件包 2.u盘写入: Armbian_22.11.0_Aml_s905l3a_jammy_5.15.80_server_2022.11.26.img 3.放入新的dtb,修改uEnv,u-boot用u200的改名 到这里应该就可以顺利U盘启动了 4.nano /etc/amlogic_model_database.conf,修改或添加306
306:M401A :s905l3a :meson-g12a-s905l3a-m401a-js.dtb :u-boot-u200.bin :NA :NA :meson-g12a :s905l3a :no
5.nano /sbin/armbian-install,找到s905l3a "${boxid}" -eq "305"那一串 305改成306;BLANK=68;BOOT=1024;BLANK2=290elif [[ "${AMLOGIC_SOC}" == "s905l3a" && "${boxid}" -eq "306" ]]; then BLANK1="68" BOOT="1024" BLANK2="290"
这里数字是专门去读了第一步安卓固件写入后的分区并整理来的
6.armbian-install写入emmc 7.启动后会发现ssh经常启动失败,搜到了#721,把/etc/custom_service/start_service.sh中以下几行注释掉解决
# Start ssh service #[[ -d "/var/run/sshd" ]] || mkdir -p -m0755 /var/run/sshd #[[ -f "/etc/init.d/ssh" ]] && /etc/init.d/ssh start 2>/dev/null
8.ip获取奇奇怪怪,偶尔会拿到多个ip但任意一个都连不上,最后路由器绑定静态ip解决。
目前装上docker hass node-red mqtt,一天过去了没有任何报错 各位手头m401a疑似体质不好的可以试试看 于是现在有个小问题,我要如何再次从u盘启动……我记得前几天有看到某个人发了解决方案,但突然找不到了……
牛逼啊,u盘启动可以按复位键啊
Ssh启动失败是新版本镜像的问题,前两天的版本没问题的
目前装上docker hass node-red mqtt,一天过去了没有任何报错 各位手头m401a疑似体质不好的可以试试看 于是现在有个小问题,我要如何再次从u盘启动……我记得前几天有看到某个人发了解决方案,但突然找不到了……
试一下在emmc的系统里执行 cp /boot/u-boot-e900v22c.bin /boot/u-boot.emmc cp /boot/u-boot-u200.bin /boot/u-boot.ext
重启后应该可以usb\emmc自由切换了
306 `306:M401A :s905l3a :meson-g12a-s905l3a-m401a-js.dtb :u-boot-u200.bin :NA :NA :meson-g12a :s905l3a :no
1.这里的uboot配置,在目前的安装逻辑实际上无效。 ` 5.nano /sbin/armbian-install,找到s905l3a "${boxid}" -eq "305"那一串 305改成306;BLANK=68;BOOT=1024;BLANK2=290
elif [[ "${AMLOGIC_SOC}" == "s905l3a" && "${boxid}" -eq "306" ]]; then BLANK1="68" BOOT="1024" BLANK2="290"
2.这里分区在版本引入ampart工具后,也没有必要专门配置了,会自动优化的
目前装上docker hass node-red mqtt,一天过去了没有任何报错 各位手头m401a疑似体质不好的可以试试看 于是现在有个小问题,我要如何再次从u盘启动……我记得前几天有看到某个人发了解决方案,但突然找不到了……
试一下在emmc的系统里执行 cp /boot/u-boot-e900v22c.bin /boot/u-boot.emmc cp /boot/u-boot-u200.bin /boot/u-boot.ext
重启后应该可以usb\emmc自由切换了
这个貌似不能用了,奇怪,我昨天在测试6.0.内核Emmc退回usb的时候成功的,难道之前有其它操作影响了结果?
刚想想昨天O大跟我聊到频率的事情,秃发灵感,对比了s700k提供的原厂频率表,发觉还是忽略了一点比较重要的,电压值差异(不是进制表示法的差异),原厂频率表大部分频点的电压都比现有的基于u200的高,所以电压不足,有可能是慌乱问题之源。但同时这样又难解析bokeylee同学测试的在1704比较稳定的现象。
基本上u200除了1800和1000频点相同外,其它频点都低于原厂频率表电压表。。。
@janko888 根据s700k提供的安卓系统dts,cpu频率如下:
6250000 250000000 500000000 667000000 1000000000 1200000000 1398000000 1512000000 1608000000 1704000000 1800000000
把cpu频率设置改一下,把现在的不可用频率的设置改成可用频率的写法,留几个1000-1704的。
用禁止的写法,会继承了u200的更高频率,比如2108,1908等不在你禁用列表的都会启用了。 把leds里面的缩进调整一下。用tab键一个函数统一缩进一下。
高频的出现在311的dtb上,这边继承u200的应该没有高频。 现在小范围测试一下看看反馈?不急于频繁提交修改,以加大成上游审核工作。 现在整理了一份根据这个表的新dtb,有勇士敢一起测试一下不。提高电压有点风险。
10%左右的调整是安全的,前几天f大把rock5b的cpu频率也加压了,有些出厂低频用户可以通过加压获得。rock5b随机抽奖,cpu分5个档位,用这个方法都调成了一等奖的频率。
10%左右的调整是安全的,前几天f大把rock5b的cpu频率也加压了,有些出厂低频用户可以通过加压获得。rock5b随机抽奖,cpu分5个档位,用这个方法都调成了一等奖的频率。
收到,尽量以稳健策略为本,似乎这个板子个体体质差异比较大。
10%左右的调整是安全的,前几天f大把rock5b的cpu频率也加压了,有些出厂低频用户可以通过加压获得。rock5b随机抽奖,cpu分5个档位,用这个方法都调成了一等奖的频率。
银行账户能引进这个随机策略么:)
银行经常用,这叫通货膨胀
目前装上docker hass node-red mqtt,一天过去了没有任何报错 各位手头m401a疑似体质不好的可以试试看 于是现在有个小问题,我要如何再次从u盘启动……我记得前几天有看到某个人发了解决方案,但突然找不到了……
试一下在emmc的系统里执行 cp /boot/u-boot-e900v22c.bin /boot/u-boot.emmc cp /boot/u-boot-u200.bin /boot/u-boot.ext
重启后应该可以usb\emmc自由切换了
我是5.10系列刷入EMMC后没法从U盘启动了,也能用这个试试?5.15系列完全没问题
原厂固件的dt.img里有四个dtb,我分别贴一下,甚至有最高1.5Ghz的灰烬版。
# meson-g12a-u212-1g.dts
cpu_opp_table0 {
compatible = "operating-points-v2";
opp-shared;
phandle = <0xd>;
opp00 {
opp-hz = <0x0 0x5f5e100>;
opp-microvolt = <0xb2778>;
};
opp01 {
opp-hz = <0x0 0xee6b280>;
opp-microvolt = <0xb2778>;
};
opp02 {
opp-hz = <0x0 0x1dcd6500>;
opp-microvolt = <0xb2778>;
};
opp03 {
opp-hz = <0x0 0x27c19cc0>;
opp-microvolt = <0xb2778>;
};
opp04 {
opp-hz = <0x0 0x3b9aca00>;
opp-microvolt = <0xb2778>;
};
opp05 {
opp-hz = <0x0 0x47868c00>;
opp-microvolt = <0xb9ca8>;
};
opp06 {
opp-hz = <0x0 0x5353c980>;
opp-microvolt = <0xc11d8>;
};
opp07 {
opp-hz = <0x0 0x5a1f4a00>;
opp-microvolt = <0xcae18>;
};
opp08 {
opp-hz = <0x0 0x5fd82200>;
opp-microvolt = <0xd4a58>;
};
opp09 {
opp-hz = <0x0 0x6590fa00>;
opp-microvolt = <0xe0da8>;
};
opp10 {
opp-hz = <0x0 0x6b49d200>;
opp-microvolt = <0xef808>;
};
};
# meson-g12a-u212-2g.dts
cpu_opp_table0 {
compatible = "operating-points-v2";
opp-shared;
phandle = <0xd>;
opp00 {
opp-hz = <0x0 0x5f5e100>;
opp-microvolt = <0xb2778>;
};
opp01 {
opp-hz = <0x0 0xee6b280>;
opp-microvolt = <0xb2778>;
};
opp02 {
opp-hz = <0x0 0x1dcd6500>;
opp-microvolt = <0xb2778>;
};
opp03 {
opp-hz = <0x0 0x27c19cc0>;
opp-microvolt = <0xb2778>;
};
opp04 {
opp-hz = <0x0 0x3b9aca00>;
opp-microvolt = <0xb2778>;
};
opp05 {
opp-hz = <0x0 0x47868c00>;
opp-microvolt = <0xb9ca8>;
};
opp06 {
opp-hz = <0x0 0x5353c980>;
opp-microvolt = <0xc11d8>;
};
opp07 {
opp-hz = <0x0 0x5a1f4a00>;
opp-microvolt = <0xcae18>;
};
opp08 {
opp-hz = <0x0 0x5fd82200>;
opp-microvolt = <0xd4a58>;
};
opp09 {
opp-hz = <0x0 0x6590fa00>;
opp-microvolt = <0xe0da8>;
};
opp10 {
opp-hz = <0x0 0x6b49d200>;
opp-microvolt = <0xef808>;
};
};
# meson-g12a-u212-2gvddee.dts
cpu_opp_table0 {
compatible = "operating-points-v2";
opp-shared;
phandle = <0xd>;
opp00 {
opp-hz = <0x0 0x5f5e100>;
opp-microvolt = <0xcd528>;
};
opp01 {
opp-hz = <0x0 0xee6b280>;
opp-microvolt = <0xcd528>;
};
opp02 {
opp-hz = <0x0 0x1dcd6500>;
opp-microvolt = <0xcd528>;
};
opp03 {
opp-hz = <0x0 0x27c19cc0>;
opp-microvolt = <0xcd528>;
};
opp04 {
opp-hz = <0x0 0x3b9aca00>;
opp-microvolt = <0xcd528>;
};
opp05 {
opp-hz = <0x0 0x47868c00>;
opp-microvolt = <0xcd528>;
};
opp06 {
opp-hz = <0x0 0x5353c980>;
opp-microvolt = <0xcd528>;
};
opp07 {
opp-hz = <0x0 0x5a1f4a00>;
opp-microvolt = <0xcd528>;
};
};
# meson-sm1-ac213-2g.dts
cpu_opp_table0 {
compatible = "operating-points-v2";
opp-shared;
phandle = <0xd>;
opp00 {
opp-hz = <0x0 0x5f5e100>;
opp-microvolt = <0xb98c0>;
};
opp01 {
opp-hz = <0x0 0xee6b280>;
opp-microvolt = <0xb98c0>;
};
opp02 {
opp-hz = <0x0 0x1dcd6500>;
opp-microvolt = <0xb98c0>;
};
opp03 {
opp-hz = <0x0 0x27c19cc0>;
opp-microvolt = <0xbe6e0>;
};
opp04 {
opp-hz = <0x0 0x3b9aca00>;
opp-microvolt = <0xc3500>;
};
opp05 {
opp-hz = <0x0 0x47868c00>;
opp-microvolt = <0xc5c10>;
};
opp06 {
opp-hz = <0x0 0x53af5700>;
opp-microvolt = <0xc8320>;
};
opp07 {
opp-hz = <0x0 0x59682f00>;
opp-microvolt = <0xcaa30>;
};
opp08 {
opp-hz = <0x0 0x5fd82200>;
opp-microvolt = <0xd1f60>;
};
opp09 {
opp-hz = <0x0 0x6590fa00>;
opp-microvolt = <0xdbba0>;
};
opp10 {
opp-hz = <0x0 0x6b49d200>;
opp-microvolt = <0xe57e0>;
};
opp11 {
opp-hz = <0x0 0x71b9c500>;
opp-microvolt = <0xf4240>;
};
};
目前装上docker hass node-red mqtt,一天过去了没有任何报错 各位手头m401a疑似体质不好的可以试试看 于是现在有个小问题,我要如何再次从u盘启动……我记得前几天有看到某个人发了解决方案,但突然找不到了……
试一下在emmc的系统里执行 cp /boot/u-boot-e900v22c.bin /boot/u-boot.emmc cp /boot/u-boot-u200.bin /boot/u-boot.ext
重启后应该可以usb\emmc自由切换了
已测试,5.10.156无效,用的你昨天发的dtb ,meson-g12a-s905l3a-m401a.zip
306 `306:M401A :s905l3a :meson-g12a-s905l3a-m401a-js.dtb :u-boot-u200.bin :NA :NA :meson-g12a :s905l3a :no
1.这里的uboot配置,在目前的安装逻辑实际上无效。 ` 5.nano /sbin/armbian-install,找到s905l3a "${boxid}" -eq "305"那一串 305改成306;BLANK=68;BOOT=1024;BLANK2=290
elif [[ "${AMLOGIC_SOC}" == "s905l3a" && "${boxid}" -eq "306" ]]; then BLANK1="68" BOOT="1024" BLANK2="290"
2.这里分区在版本引入ampart工具后,也没有必要专门配置了,会自动优化的
谢谢大佬哈哈,目前还半懵懂状态,折腾盒子让我想起了折腾黑苹果的时候。 你第一点说的uboot设置无效的意思是安装脚本现在已经不读取那一项设置了吗? 电压问题昨天我也留意到了,不过发现1800的电压设定和原厂一样之后,感觉应该还是体质问题就没再去折腾,有时间再作死一下加压看看效果 至于u盘启动问题,昨晚翻了另一篇issue,把u盘的boot.ini boot.cmd搬到了emmc,再在for devtype...前面插了一句usb start。现在可以自由切换usb和emmc了。
Device Information | 设备信息
Armbian Version | 系统版本
Describe the bug | 问题描述 虽然刷入成功,但内存显示不对,M401a在安卓系统显示是2G内存![image](https://user-images.githubusercontent.com/16831855/204040118-e404ebcd-8504-4908-ada8-6a47180a585b.png)