hzyitc / armbian-onecloud Goto Github PK
View Code? Open in Web Editor NEWThis project forked from armbian/build
Armbian for onecloud. 玩客云用armbian
This project forked from armbian/build
Armbian for onecloud. 玩客云用armbian
mac地址要手动写进去吗?我看之前的教程都是在/etc/network/interfaces里边手动写,这两台拆机之后主板上没写mac地址,如何能获取到真实的mac地址?
哪位大神知道具体操作?? 烦请指教一下,谢谢
如题,刷机以后,安装docker、青龙面板都是正常的,但是重启以后之前可用的端口都不再可用。重刷以后表现一致,开始都好用,重启就不行了。
将下面的代码保存为led.c
然后gcc led.c -o led
最后将编译后的led程序放入 /usr/bin
就可以运行以下命令,控制玩客云灯的显示颜色了,0是关闭,1是打开
led red 0
led blue 0
led green 1
#include <ctype.h>
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <fcntl.h>
#include <sys/types.h>
#include <sys/mman.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/select.h>
#include <pthread.h>
#include <unistd.h>
#include <sched.h>
#include <string.h>
#define PLPM_BASE 0xc8100014
#define __IO volatile
void *var_addr_satr=0;
unsigned int var_addr_size=0;
unsigned int *gpioaddr;
void *gpio_base= 0;
int gpio_init(void) {
int fd;
unsigned int addr_start,addr_offset;
unsigned int PageSize,PageMask;
fd = open("/dev/mem",O_RDWR);
if(fd < 0) {
return -1;
}
PageSize = sysconf(_SC_PAGESIZE);
PageMask = ~(PageSize-1);
//printf("take PageSize=%d\n",PageSize);
addr_start = PLPM_BASE & PageMask ;
addr_offset= PLPM_BASE & ~PageMask;
var_addr_size = PageSize*2;
var_addr_satr = (void*) mmap(0, var_addr_size, PROT_READ | PROT_WRITE, MAP_SHARED, fd, addr_start);
if(var_addr_satr == MAP_FAILED) {
return -1;
}
gpio_base = var_addr_satr;
gpio_base += addr_offset;
//printf("take var addr = 0x%8x\n",(unsigned int)var_addr_satr);
//printf("make gpio_base = 0x%8x\n",(unsigned int)gpio_base);
close(fd);
return 0;
}
int gpio_deinit(void) {
int fd;
fd = open("/dev/mem",O_RDWR);
if(fd < 0) {
return -1;
}
if(munmap(var_addr_satr,var_addr_size) == 0) {
//printf("remove var addr ok\n");
} else {
//printf("remove var addr erro\n");
}
close(fd);
return 0;
}
void red_on(void) {
unsigned int temp;
temp = *(gpioaddr+4)|0x00040000;
*(gpioaddr+4)=temp;
}
void red_off(void) {
*(gpioaddr+4) = *(gpioaddr+4)&(~0x00040000);
}
void red_toggle(void) {
unsigned char c;
c = (*(gpioaddr+4)&0x00040000)>>18;
if (c == 0) {
red_on();
} else {
red_off();
}
}
void green_on(void) {
*(gpioaddr+4) = *(gpioaddr+4)|0x00080000;
}
void green_off(void) {
*(gpioaddr+4) = *(gpioaddr+4)&(~0x00080000);
}
void green_toggle(void) {
unsigned char c;
c = (*(gpioaddr+4)&0x00080000)>>19;
if (c == 0) {
green_on();
} else {
green_off();
}
}
void blue_on(void) {
*(gpioaddr+4) = *(gpioaddr+4)|0x00100000;
}
void blue_off(void) {
*(gpioaddr+4) = *(gpioaddr+4)&(~0x00100000);
}
void blue_toggle(void) {
unsigned char c;
c = (*(gpioaddr+4)&0x00100000)>>20;
if (c == 0) {
blue_on();
} else {
blue_off();
}
}
unsigned char key_scan(void) {
unsigned char key=0;
key=((*(gpioaddr+5)&0x00000020)>>5);
return key;
}
int main(int argc,char * argv[]) {
if (argc < 2 || argc > 4) {
printf("led [red|green|blue] [0|1]\n");
return 1;
}
unsigned int temp;
if (gpio_init() != 0) {
printf("gpio_init failed\n");
return -1;
}
gpioaddr = (unsigned int *)gpio_base;
// Turn off GPIOAO_4,GPIOAO_5 reuse
temp = *gpioaddr&(~0x01800066);
*gpioaddr = temp;
// Enable GPIOAO_2,GPIOAO_3,GPIOAO_4 output,GPIOAO_5 input
temp = *(gpioaddr+4)&(~0x0000001c);
*(gpioaddr+4) = temp;
temp = *(gpioaddr+4)|0x00000020;
*(gpioaddr+4) = temp;
if (argc == 2) {
if (strcmp((const char*)argv[1],"red")==0)
red_toggle();
if (strcmp((const char*)argv[1],"green")==0)
green_toggle();
if (strcmp((const char*)argv[1],"blue")==0)
blue_toggle();
}
if (argc == 3) {
if (strcmp((const char*)argv[1],"red")==0) {
if (strcmp((const char*)argv[2],"0")==0) {
red_off();
} else {
red_on();
}
}
if (strcmp((const char*)argv[1],"green")==0) {
if (strcmp((const char*)argv[2],"0")==0) {
green_off();
} else {
green_on();
}
}
if (strcmp((const char*)argv[1],"blue")==0) {
if (strcmp((const char*)argv[2],"0")==0) {
blue_off();
} else {
blue_on();
}
}
}
gpio_deinit( );
return 0;
}
当我从windows转移到mac时, 对比windows, 我发现捅屁股的方式, windows可以识别, mac无法识别, 请问该如何连接?
使用的当前最新固件,加载usblp.ko模块失败
# modprobe usblp
modprobe: FATAL: Module usblp not found in directory /lib/modules/5.18.19-meson
老大,能否调整一下内核参数,把usblp.ko也顺手编译进固件呢?非常感谢🙏啦
让我们继续向着压榨玩客云的价值迈进~~
在官方库里没有找到【patch/kernel/archive/meson-{5.10,5.18}/support-xunlei-onecloud.patch】这个内核补丁。
刷入的镜像版本Armbian_22.08.0-trunk_Onecloud_bullseye_edge_5.18.0.burn.img
https://github.com/hzyitc/armbian-onecloud/releases/tag/ci-20220824-144151-UTC
我是在登陆ssh之后,输入的下面的命令,22端口的服务变成了由init提供,而正常的openssh是dead的:
# netstat -tpln|grep 22
tcp 0 0 192.168.2.29:53 0.0.0.0:* LISTEN 3224/dnsmasq
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 3224/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1/init
# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:sshd(8)
man:sshd_config(5)
# systemctl status sshd
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:sshd(8)
man:sshd_config(5)
https://www.right.com.cn/forum/thread-8237343-1-1.html
这个帖子的作者写了个s805_autoscript在0.fat,可以使用这种方法打包镜像吗?
powersee的玩客云固件算是很完善的固件了,就是不是最新版,用起来很好,但是想要一个可以编译的最新的固件
您看是否有值得参考的地方。
https://powersee.github.io/2021/01/wankeyun-server/
https://powersee.github.io/2021/02/wankeyun-2/
玩客云版本 v1.0,刷入8月20日的Armbian_22.08.0-trunk_Onecloud_bullseye_current_5.15.61.burn.img后,开机界面停留在uboot界面的boot from emmc,实际接入网线后可以正常获得ip地址ssh登录。
如题, 请教一下大佬, 强迫症看见新版本就想刷, 但是每次刷完又得重新配置, 有没有不重刷就可以更新的办法呢?
使用的8月15日的固件Armbian_22.08.0-trunk_Onecloud_bullseye_edge_5.18.0_minimal.burn.img
#apt install fuse3
Setting up fuse3 (3.10.3-2) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Processing triggers for initramfs-tools (0.140) ...
ln: failed to create hard link '/boot/initrd.img-5.18.0-rc3-meson.dpkg-bak' => '/boot/initrd.img-5.18.0-rc3-meson': Operation not permitted
update-initramfs: Generating /boot/initrd.img-5.18.0-rc3-meson
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for built-in driver r8169
update-initramfs: Converting to u-boot format
root@onecloud:# ethtool eth0|grep Speed# iperf3 -c 10.0.0.71 -t 5
Speed: 1000Mb/s
root@onecloud:
Connecting to host 10.0.0.71, port 5201
[ 5] local 10.0.0.168 port 46580 connected to 10.0.0.71 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 126 KBytes 1.03 Mbits/sec 11 1.41 KBytes
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 4 1.41 KBytes
[ 5] 2.00-3.00 sec 41.0 KBytes 336 Kbits/sec 6 1.41 KBytes
[ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 1 1.41 KBytes
[ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-5.00 sec 167 KBytes 273 Kbits/sec 22 sender
[ 5] 0.00-5.00 sec 127 KBytes 208 Kbits/sec receiver
iperf Done.
root@onecloud:~# iperf3 -s
Server listening on 5201
Accepted connection from 10.0.0.71, port 44558
[ 5] local 10.0.0.168 port 5201 connected to 10.0.0.71 port 44560
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 107 MBytes 899 Mbits/sec
[ 5] 1.00-2.00 sec 103 MBytes 860 Mbits/sec
[ 5] 2.00-3.00 sec 109 MBytes 912 Mbits/sec
[ 5] 3.00-4.00 sec 109 MBytes 912 Mbits/sec
[ 5] 4.00-5.00 sec 109 MBytes 912 Mbits/sec
[ 5] 5.00-5.01 sec 317 KBytes 449 Mbits/sec
[ ID] Interval Transfer Bitrate
[ 5] 0.00-5.01 sec 536 MBytes 898 Mbits/sec receiver
Server listening on 5201
root@onecloud:# ethtool -s eth0 speed 100 duplex full autoneg on# ethtool eth0|grep Speed
root@onecloud:
Speed: 100Mb/s
root@onecloud:~# iperf3 -c 10.0.0.71 -t 5
Connecting to host 10.0.0.71, port 5201
[ 5] local 10.0.0.168 port 46584 connected to 10.0.0.71 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 11.4 MBytes 95.8 Mbits/sec 0 97.6 KBytes
[ 5] 1.00-2.00 sec 11.4 MBytes 95.4 Mbits/sec 0 115 KBytes
[ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 0 126 KBytes
[ 5] 3.00-4.00 sec 11.3 MBytes 94.8 Mbits/sec 0 126 KBytes
[ 5] 4.00-5.00 sec 11.1 MBytes 93.3 Mbits/sec 0 126 KBytes
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-5.00 sec 56.4 MBytes 94.6 Mbits/sec 0 sender
[ 5] 0.00-5.01 sec 56.2 MBytes 94.1 Mbits/sec receiver
iperf Done.
root@onecloud:~# iperf3 -s
Server listening on 5201
Accepted connection from 10.0.0.71, port 44562
[ 5] local 10.0.0.168 port 5201 connected to 10.0.0.71 port 44564
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 11.2 MBytes 94.0 Mbits/sec
[ 5] 1.00-2.00 sec 11.2 MBytes 94.1 Mbits/sec
[ 5] 2.00-3.00 sec 11.2 MBytes 94.1 Mbits/sec
[ 5] 3.00-4.00 sec 11.2 MBytes 94.1 Mbits/sec
[ 5] 4.00-5.00 sec 11.2 MBytes 94.1 Mbits/sec
[ 5] 5.00-5.00 sec 29.7 KBytes 82.3 Mbits/sec
[ ID] Interval Transfer Bitrate
[ 5] 0.00-5.00 sec 56.1 MBytes 94.1 Mbits/sec receiver
如题,安装 Home Assistant Supervised 的时候依赖 apparmor
https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md#supported-operating-system-system-dependencies-and-versions
感谢付出,用到现在最好的版本,直刷真是太方便了!
lsusb能看到wifi,但是nmtui里搜不到无线,麻烦添加一下USB Wi-Fi的支持
Setting up nala (0.9.1) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for initramfs-tools (0.140) ...
ln: failed to create hard link '/boot/initrd.img-5.18.0-rc3-meson.dpkg-bak' => '/boot/initrd.img-5.18.0-rc3-meson': Operation not permitted
update-initramfs: Generating /boot/initrd.img-5.18.0-rc3-meson
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for built-in driver r8169
update-initramfs: Converting to u-boot format
edge和edge minimal的区别是啥?xfce知道是差了个桌面,那么普通版edge和minimal的edge版差了啥?
最新的固件刷入机器后,需要等待很长时间,ssh才能偶尔连接成功。
大佬可不可以分享一下晶晨做线刷包的方法,自己配置好的系统想做成线刷包。
相信大家手头都有ntfs格式的移动硬盘,但是当前内核不支持ntfs
自从5.15内核开始,linux已经实现了内核级的ntfs支持,希望老大在新版本的镜像中加入ntfs原生支持
https://linux.cn/article-14810-1.html
当前镜像版本中的/boot/config-5.18.0-rc3-meson有关ntfs的内核选项设定如下:
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
# CONFIG_NTFS3_FS is not set
希望未来的镜像版本调整为:
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
CONFIG_NTFS3_FS=y
编译网卡驱动时需要headers,不知能否提供一下deb包?
使用的系统是:
09.07版本的
Armbian_22.11.0-trunk_Onecloud_bullseye_edge_5.18.19_minimal.burn.img
upgrade的时候出现如下警告提示,不知道是咋回事,有没有大佬指点一下?
通过upgrade升级了两台旧镜像的设备,发现登录ssh之后有欢迎界面了,但是新刷的0907的镜像没有欢迎界面。
ln: failed to create hard link '/boot/initrd.img-5.18.19-meson.dpkg-bak' => '/boot/initrd.img-5.18.19-meson': Operation not permitted
update-initramfs: Generating /boot/initrd.img-5.18.19-meson
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for built-in driver r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for built-in driver r8169
update-initramfs: Converting to u-boot format
最新9.21版本docker无法启动。删掉的9.18版本也无法启动docker。现在用9.14版可以正常启动docker。
有点不知道下哪个好。。
由于手头上并没有TTL所以暂时不知道是什么问题,只能简略的说一下发现过程。
第一次,是在docker等服务运行正常近半个月之后,把外挂USB硬盘添加了开机自动挂载后重启测试发现无法启动,怀疑是fstab文件书写错误。于是重刷。
第二次,开机后未添加fstab文件,未安装docker。仅通过armbian-config安装OMV后自动重启后,发现仍无法启动。
这期间ping主机名onecloud都无法ping通,此外路由器后台也没有什么新设备上线的提示,所以判断系统没有正常启动成功,但是网线口的灯都是亮的,而且设备貌似会不定时重启,网线口的灯会灭一段时间后再次亮起。
由于没有TTL设备,没有办法提供日志文件,在此表示歉意。
1.0的板
root@onecloud:~# neofetch
_,met$$$$$gg. root@onecloud
,g$$$$$$$$$$$$$$$P. -------------
,g$$P" """Y$$.". OS: Debian GNU/Linux 11 (bullseye) armv7l
,$$P' `$$$. Host: Xunlei OneCloud
',$$P ,ggs. `$$b: Kernel: 5.18.0-rc3-meson
`d$$' ,$P"' . $$$ Uptime: 10 mins
$$P d$' , $$P Packages: 334 (dpkg)
$$: $$. - ,d$$' Shell: bash 5.1.4
$$; Y$b._ _,d$P' Terminal: /dev/pts/0
Y$$. `.`"Y$$$$P"' CPU: Amlogic Meson platform (4)
`$$b "-.__ Memory: 54MiB / 993MiB
`Y$$
`Y$$.
`$$b.
`Y$$b.
`"Y$b._
`"""
root@onecloud:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat: /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: No such file or directory
root@onecloud:~#
wifi主模块焊上去之后应该不需要加焊多少多少电容啥的吧,板子上都没有那么多预留?
搜索看了一下,估计加焊几个电容电感啥的就应该可以搞定了。
cat /boot/armbianEnv.txt
extraargs=apparmor=1 security=apparmor systemd.unified_cgroup_hierarchy=0
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
dmesg 中
Kernel command line: root=/dev/mmcblk1p2 rootwait rw console=ttyAML0,115200n8 no_console_suspend consoleblank=0
我在刷入您的Armbian_22.08.0-trunk_Onecloud_jammy_edge_5.18.0_minimal.burn.img和Armbian_22.08.0-trunk_Onecloud_bullseye_edge_5.18.0_minimal.burn.img文件之后,修改了boot.cmd里的引导参数,重新生成boot.scr之后,设备加电开机后,hdmi全程有画面输出,可以看到系统文件的引导过程。
附上我的bootargs参数,供您参考:
rootfstype=ext4 rootflags=data=writeback rootwait rw console=ttyAML0,115200n8 console=tty0 fsck.repair=yes net.ifnames=0 ipv6.disable=1 logo=osd1,loaded,0x7900000,${hdmimode},full
其实这个方法,适用于您的所有镜像版本。
fork了armbian官方仓库,但是机型找不到玩客云,要怎么用官方仓库编译啊
对于V1.0的板子,您可以直接把dts中usb0的dr_mode改成host来启动该USB。
怎么用脚本实现呢?
Modify partition
Format partition
mount: /mnt/mmcblk1p1: wrong fs type, bad option, bad superblock on /dev/mmcblk1p1, missing codepage or helper progr am, or other error.
Copy BOOT
^C^X^C
https://github.com/hzyitc/u-boot-onecloud
https://github.com/raysworld/onecloud-emmc-install
cd /boot/install
./install.sh
请问大佬,27、28、29连续更新,都有解决了哪些问题?
The board use PWM_D
to adjust VCC_CORE
. But we don't driver it.
板子使用 PWM_D
来调节 VCC_CORE
。 但我们没有驱动它。
Fixed in branch fix-vcc_core-temportally temportally.
在 fix-vcc_core-temportally分支 临时修复.
In V1.3 board
vcc_core
is 1.1V, but in V1.0 board
it's 1.0V. So CPU
doesn't work well in 1.5GHz and the boot fails.
在 V1.3板子
上 vcc_core
是 1.1V,但在 V1.0板子
上 vcc_core
是 1.0V。所以 CPU
在 1.5GHz 时工作不稳定,故导致启动失败。
.-/+oossssoo+/-. root@aml-s812
`:+ssssssssssssssssss+:` -------------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 20.04.1 LTS armv7l
.ossssssssssssssssssdMMMNysssso. Host: OneCloud
/ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 5.9.0-rc7-aml-s812
+ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 34 mins
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 493 (dpkg)
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 5.0.17
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Terminal: /dev/pts/0
ossyNMMMNyMMhsssssssssssssshmmmhssssssso CPU: Amlogic Meson platform (4) @ 600MHz
ossyNMMMNyMMhsssssssssssssshmmmhssssssso Memory: 192MiB / 989MiB
+sssshhhyNMMNyssssssssssssyNMMMysssssss+
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
+sssssssssdmydMMMMMMMMddddyssssssss+
/ssssssssssshdmNNNNmyNMMMMhssssss/
.ossssssssssssssssssdMMMNysssso.
-+sssssssssssssssssyyyssss+-
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
root@aml-s812:~# cat /sys/class/thermal/thermal_zone0/temp \
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
42812
ondemand
这位的版本功能正常
leo357449107
-------------
█ █ █ █ █ █ █ █ █ █ █ OS: Armbian (22.05.0-trunk) armv7l
███████████████████████ Host: Xunlei OneCloud
▄▄██ ██▄▄ Kernel: 5.18.0-rc3-meson
▄▄██ ███████████ ██▄▄ Uptime: 5 days, 13 hours, 13 mins
▄▄██ ██ ██ ██▄▄ Packages: 531 (dpkg)
▄▄██ ██ ██ ██▄▄ Shell: bash 5.1.4
▄▄██ ██ ██ ██▄▄ Terminal: /dev/pts/0
▄▄██ █████████████ ██▄▄ CPU: Amlogic Meson platform (4)
▄▄██ ██ ██ ██▄▄ Memory: 732MiB / 993MiB
▄▄██ ██ ██ ██▄▄
▄▄██ ██ ██ ██▄▄
▄▄██ ██▄▄
███████████████████████
█ █ █ █ █ █ █ █ █ █ █
cat /sys/class/thermal/thermal_zone0/temp \
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat: /sys/class/thermal/thermal_zone0/temp: Invalid argument
cat: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: No such file or directory
缺少文件?
Jun 01 01:46:20 onecloud systemd[1]: Starting LSB: set CPUFreq kernel parameters...
Jun 01 01:46:20 onecloud cpufrequtils[662]: * CPUFreq Utilities: Setting ondemand CPUFreq governor...
Jun 01 01:46:20 onecloud cpufrequtils[662]: * disabled, governor not available...
Jun 01 01:46:20 onecloud cpufrequtils[662]: ...done.
Jun 01 01:46:20 onecloud systemd[1]: Started LSB: set CPUFreq kernel parameters.
I'm trying to fix the USB
closed to the HDMI
in branch usb.
我正在在usb分支尝试修复靠近HDMI
的USB
。
Please try test-usb-ci-20220603-2028 and test-usb-ci-20220603-2029 to check whether USB
closed to the HDMI
working.
请使用test-usb-ci-20220603-2028和test-usb-ci-20220603-2029,测试靠近HDMI
的USB
能否正常使用。
For V1.0 board
, both of them should work.
对于V1.0的板子
,这两者 应该都能正常工作。
For V1.3 board
, only the second one should work.
对于V1.3的板子
,应该 只有后者 能正常工作。
Please the following template to reply.
请使用下列模板回复。
Board: V1.3
test-usb-ci-20220603-2028: ❌
test-usb-ci-20220603-2029: ✔️
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.