Git Product home page Git Product logo

armbian-onecloud's People

Contributors

hzyitc avatar kuoruan avatar mobius0526 avatar sydneyowl avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

armbian-onecloud's Issues

armbianEnv.txt 中的 `extraargs` 不生效

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

玩客云刷机保姆式教程,简单直接的写给你

=========================
下载镜像文件写入U盘,下载解压下面文件后
https://github.com/hzyitc/armbian-onecloud/files/8876513/s805_autoscript.zip
复制到BOOT分区就可以了。插上U盘到靠近网线的U口通电就好了。

我使用的不是精简底包,是powersee提供的底包,精简底包也应该没问题,那个能刷上去用哪个。
资源地址如下。https://pan.powersee.top/%E5%85%B1%E4%BA%AB%E6%96%87%E4%BB%B6%E5%A4%B9/%E7%8E%A9%E5%AE%A2%E4%BA%91/s805_flash_snail.img.xz
https://pan.powersee.top/
http://veger.ys168.com/

刷机工具:
https://androidmtk.com/download-amlogic-usb-burning-tool
j镜像写入工具:
https://www.alexpage.de/usb-image-tool/download/

建议不要先拆机,直接插双公头usb数据线即可
或者按住重置键开机,发现硬件即可刷机,如果出错
1.多试几次 2.换个USB口 3.重启机器 4.换个机器

短接刷机方法,请自行百度,需要拆机短接,版本不一样短接不一样,其余的一致。

HTOP 获取不到 CPU 温度 频率

            .-/+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

缺少文件?

cpu governor not seem to work

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.

QGKY6DT9(EF2CPBCDBLWN

action 修改 dts

对于V1.0的板子,您可以直接把dts中usb0的dr_mode改成host来启动该USB。

怎么用脚本实现呢?

RTL8211F rate 100M normal, 1000M abnormal

Board: v1.3
USB-OS: Armbian_22.05.0-trunk_Onecloud_focal_current_5.14.21

root@onecloud:# ethtool eth0|grep Speed
Speed: 1000Mb/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 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
root@onecloud:
# ethtool eth0|grep Speed
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

upgrade警告提示,并且没有最新的欢迎界面

使用的系统是:
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

玩客云控制灯的颜色,源码奉上

将下面的代码保存为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;
}

希望加入ntfs3内核模块支持

相信大家手头都有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

感谢大佬为玩客云付出这么多,经过一晚上的研究,我来写一篇简单入门教程吧

大佬的release分为u盘启动包和直刷包,下面主要说一下u盘启动包,下载下来之后直接用rufus写入u盘

1.先刷“u盘启动/emmc启动”自动识别底包,推荐大佬编译的eMMC.burn.img

https://github.com/hzyitc/u-boot-onecloud

2.想要写入emmc的,下载下面的文件,放入u盘的boot分区

https://github.com/raysworld/onecloud-emmc-install

整个仓库拉下来,重命名为install,放入boot分区,u盘系统启动后

cd /boot/install
./install.sh

3.直刷包我测试用2.1.6.8的usb burning可以正常刷入。2.2.4会卡在98%不动,然后提示roofs校验失败。是usb burning校验等待超时引起的,ttl里显示rom实际已经烧录成功,主板为1.3版。

修改bootargs,实现全程hdmi画面输出

我在刷入您的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
其实这个方法,适用于您的所有镜像版本。

把玩客云作为网络打印服务器,缺少usblp.ko模块

使用的当前最新固件,加载usblp.ko模块失败

# modprobe usblp
modprobe: FATAL: Module usblp not found in directory /lib/modules/5.18.19-meson

老大,能否调整一下内核参数,把usblp.ko也顺手编译进固件呢?非常感谢🙏啦
让我们继续向着压榨玩客云的价值迈进~~

代号bullseye版本的armbian安装openmediavault6.x失败

首先系统日志现在看不到了哦,我按了十几次都没成功我就放弃了,还有这个日志怎么看?按到99%就自动断开网络了,然后就连接不进ssh了,应该也看不到日志了吧?系统都进不去了,这里暂时只有一张当时保存的报错图。主要是报错后就进不去ssh,日志也看不到,迫不得已只有重新装系统,这里说明下omv6.x需要bullseye版本的前提下才能按[
omv6 x安装失败

hdmi不输出启动信息和终端登录界面

玩客云版本 v1.0,刷入8月20日的Armbian_22.08.0-trunk_Onecloud_bullseye_current_5.15.61.burn.img后,开机界面停留在uboot界面的boot from emmc,实际接入网线后可以正常获得ip地址ssh登录。

虽然登陆速度是恢复了,但是ssh服务好像还是有问题,如下

刷入的镜像版本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)

写入emmc报错

error
启动脚本请删除后缀png这是一个压缩包 7z
我下载了Armbian_22.08.0-trunk_Onecloud_bullseye_current_5.14.21_minimal.img,我尝试了网上的两个底包分别是768KB,也就是大家都叫的首选底包,另一个是s805_flash_snail.img底包,自己又找了一份启动脚本,共三份文件把emmc_autoscript,install.sh,s805_autoscript放到U盘的BOOT目录下,成功的从U盘启动,但是我发现我使用命令:sudo bash /boot/install.sh执行写入emmc时,发现提示错误如下
root@onecloud:~# sudo bash /boot/install.sh

Copy file to emmc script

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

重启设备之后,无法找到设备

由于手头上并没有TTL所以暂时不知道是什么问题,只能简略的说一下发现过程。
第一次,是在docker等服务运行正常近半个月之后,把外挂USB硬盘添加了开机自动挂载后重启测试发现无法启动,怀疑是fstab文件书写错误。于是重刷。
第二次,开机后未添加fstab文件,未安装docker。仅通过armbian-config安装OMV后自动重启后,发现仍无法启动。
这期间ping主机名onecloud都无法ping通,此外路由器后台也没有什么新设备上线的提示,所以判断系统没有正常启动成功,但是网线口的灯都是亮的,而且设备貌似会不定时重启,网线口的灯会灭一段时间后再次亮起。

由于没有TTL设备,没有办法提供日志文件,在此表示歉意。

FEEDBACK: is the USB closed to the HDMI working?

I'm trying to fix the USB closed to the HDMI in branch usb.

我正在在usb分支尝试修复靠近HDMIUSB

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-2028test-usb-ci-20220603-2029,测试靠近HDMIUSB能否正常使用。

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.

请使用下列模板回复。

Template

Board: V1.3
test-usb-ci-20220603-2028: ❌
test-usb-ci-20220603-2029: ✔️

刷了最新的u-boot-onecloud怎么启动?直接写入镜像到U盘无法启动了。

一直显示U盘启动中,复制s805的脚本进去也没有用了。
直刷的由于太大了刷新总是出错。

目前依然是使用我写的教程,1.3还是可以启动的。最新8月8号可用
刷的是完整版底包,精简版底包好像不可以?启动比较慢,写入后速度正常。
地址点击查看 #13
1.0版的建议使用
https://github.com/hzyitc/armbian-onecloud/releases/tag/fix-vcc_core-temportally-ci-20220630-0000

刷了两台mac地址都一样

mac地址要手动写进去吗?我看之前的教程都是在/etc/network/interfaces里边手动写,这两台拆机之后主板上没写mac地址,如何能获取到真实的mac地址?

希望加入usb Wi-Fi驱动支持

感谢付出,用到现在最好的版本,直刷真是太方便了!
lsusb能看到wifi,但是nmtui里搜不到无线,麻烦添加一下USB Wi-Fi的支持

Incorrent VCC_CORE cause boots fail or work unstably

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 时工作不稳定,故导致启动失败。

apt upgrade 时候会报错如下

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

安装fuse3时,系统报错

使用的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

Fix-vcc_core-temportally-CI 2022-06-28 00:53 CPU频率又读不到了

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:~#

异常退出登录状态, 但又不是完全退出

问题有些奇怪, 我在测试ssh的时候
发现会话被注销, 要求输入密码重新登录
但是输入密码又无法登录成功, 我确信没有输入错误
然后我疯狂敲 ls 按回车, 出现以下画面:

WechatIMG3

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.