四开发板功耗对比
不多说,4块开发板的参数对比:香橙派 zero3,树莓派 3b(非3b+)、4b、5b。
空载,及限制不同最高频率下的满载功耗对比。
看起来,在不考虑性能的前提下,香橙派zero3的功耗控制简直完美,是吧?
但/but/pero…
完整阅读本篇»嗯,别的不说了,原生wechat(读文、图片视频传输、小程序)已经完全可用,视频也没问题。
飞书通过flatpak装的,音视频共享桌面OK;腾讯会议叫wemeet,初步测试共享桌面也是正常工作。WPS的话,也是用的AUR来的一个版本,除了粗体显示问题需要一些技术解决外,编辑文档流畅可用。
基于Wine(flatpak+PlayOnLinux)的Win32 Office 2010和Photoshop CS6,为了中文显示着实费了点劲(字体和注册表),如果只是英文版的话简直不要太容易。
走flatpak安装的kdenlive,第一次用,操作上不大习惯,但查一下资料还是能慢慢用起来。
PS:虽然flatpak的沙盒机制带上kde导致顶栏跟gnome不大一致,但这个沙盒封装了依赖感觉也不错的说,并且flatpak还能重设语言(与Arch不一致)。
完整阅读本篇»自从特殊时期的缺芯影响,如雨后春笋般萌发的国pi,周边生态肉眼可见的好起来;虽然差距依然明显,但显见差距逐步缩小,这里边主要有以下几个因素的助力:
入手一片香橙派zero3 2GB版,4核A53 1.51GHz,纯看参数的应该介于树莓派3b和4b之间。
普遍情况下,相比性能,我测硬件往往在意可靠性。所以别的不扯,先跑一周压测吧。
只是,鉴于嵌入式硬件基本都是flash存储,所以硬盘(tf或emmc)就不压了,除非专门测试存储介质寿命,否则多压几天就不剩啥了。
完整阅读本篇»Well, Windows x64 binaries now mostly seem to be working well on Wine (x64, Dynarec for ARM64) on Incus/LXC containers on Armbian aarch64 on an ARM SBC like RasPi or its counterparts with Rockchip RK3xxx series processors.
Btw, let’s celebrate the 1st LTS release of Incus, version 6.0.
在Linux平台使用wine运行win32程序?
Wine项目距今30多年历史了,完全不稀奇。
如果是跑在Linux arm64/aarch64上呢?
也还好……纯软件转译x86指令集,应该跑的像幻灯片吧?之前你不是KVM装过一次Win7 x64,玩成了行为艺术咩?
如果是一张价钱不足100块的RK3566 sbc,先跑Armbian,其上跑incus(lxc)容器,再跑Wine x64,最后运行Win64程序,然后我说除了启动慢点儿(毕竟emmc就那点io),运行还蛮流畅,您怎么想?
完整阅读本篇»Take a look at this if your innobackupex insists on eating up most (or all) of your root partition, as playing hide and seek with you especially.
近两天总收到奇怪的推送,磁盘占用超90%,没采取人为任何措施,又自动降至正常……就很离谱。去翻了一下云监控的磁盘使用率,发现居然是系统盘,而非数据盘(后者占用率不高,多日无明显变化),就更奇怪了。
前者么,不逮住问题发生时的话,根本无从查起;考虑其发生规律,基本跟mysql冷备的时间周期比较吻合。
所以先去看mysql冷备文件的状态,就开始出问题了(截图欠奉)。
好办,备份文件会定期rotate但log不会,不删就会一直存,看log就好。
一看不要紧,近两天备份都是失败告终。
1 2 3 4 5 6 |
.......... 240209 05:05:01 >> log scanned up to (58627078203151) 240209 05:05:03 >> log scanned up to (58627086878169) innobackupex: Error writing file '/tmp/xbtempPr6mT8' (Errcode: 28 - No space left on device) xtrabackup: Error: write to logfile failed xtrabackup: Error: xtrabackup_copy_logfile() failed. |
这里的 /tmp 就很迷,我印象中所有临时文件都不应该去系统默认的temp目录,索性检查一下。
完整阅读本篇»Let’s talk about migration from lxd to incus. As for the reason, well I guess we have seen too much of this kinda “show” in the past half decade (just like CentOS to Rocky) so here is what happened in case you’re interested.
Technically I won’t take this as a tutorial since with the well-prepared tool lxd-to-incus by Stéphane Graber (Author of both lxd and incus) there’s nothing to do but simply running it, then everything seems working well.
PS: Tested PASS on both Debian Bookworm AMD64 (on Linux KVM based vm) and Armbian Bookworm ARM64 (on RK3566 based SBC).
这些年,同类剧本真是没少看。一言不合就闭源,一言不合就拉分支,完全不新鲜,具体就不多说了,开工干活。其实吧,作者给了迁移工具 lxd-to-incus ,所以实话说没啥可干的,执行一下就可以验证迁移后的结果了。
先检查系统现状。Check the system status at first.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 |
# root @ bookworm-vm-host in ~ [17:55:15] $ uname -a Linux bookworm-vm-host 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux # root @ bookworm-vm-host in ~ [17:55:20] $ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" # root @ bookworm-vm-host in ~ [17:55:28] $ lxc --version 5.0.2 # root @ bookworm-vm-host in ~ [17:55:35] $ lxc list -c nsum4N +-------------+---------+-----------+--------------+------------------------+-----------+ | NAME | STATE | CPU USAGE | MEMORY USAGE | IPV4 | PROCESSES | +-------------+---------+-----------+--------------+------------------------+-----------+ | d10-test | RUNNING | 5s | 94.54MiB | 192.168.143.138 (eth0) | 6 | +-------------+---------+-----------+--------------+------------------------+-----------+ | d12-ngx | RUNNING | 6s | 107.81MiB | 192.168.143.2 (eth0) | 19 | +-------------+---------+-----------+--------------+------------------------+-----------+ | r8-app1 | RUNNING | 8s | 213.93MiB | 192.168.143.129 (eth0) | 235 | +-------------+---------+-----------+--------------+------------------------+-----------+ | u18-redmine | RUNNING | 19s | 402.67MiB | 192.168.143.158 (eth0) | 16 | +-------------+---------+-----------+--------------+------------------------+-----------+ # root @ bookworm-vm-host in ~ [17:55:39] $ |
然后根据文档,安装incus。Now install the incus (by Zabbly) according to the documentation.
从安装过程看,至少创建了一个用户,两个组,以及不少于6个systemd服务。
完整阅读本篇»