ophub
commented
1 year ago 你下载这个镜像测试下，使用的u-boot和dts文件都是来自 https://github.com/cm9vdA/build-linux 大佬的仓库。测试好了再把sw799合并到一个共用。
Closed r1172464137 closed 1 year ago
ophub
commented
1 year ago 你下载这个镜像测试下，使用的u-boot和dts文件都是来自 https://github.com/cm9vdA/build-linux 大佬的仓库。测试好了再把sw799合并到一个共用。
r1172464137
commented
1 year ago
不行
r1172464137
commented
1 year ago U-Boot TPL 2022.07 (Oct 18 2023 - 10:03:11)
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2022.07 (Oct 18 2023 - 10:03:11 +0800)
Trying to boot from MMC2
U-Boot 2022.07 (Oct 18 2023 - 10:03:11 +0800)
SoC: Rockchip rk3399
Reset cause: POR
Model: Fine3399
DRAM: 3.9 GiB
PMIC: RK808
Core: 278 devices, 29 uclasses, devicetree: separate
MMC: mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Fine3399
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
3252 bytes read in 11 ms (288.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
265 bytes read in 9 ms (28.3 KiB/s)
16866283 bytes read in 1612 ms (10 MiB/s)
33923584 bytes read in 3225 ms (10 MiB/s)
78941 bytes read in 25 ms (3 MiB/s)
Failed to load '/dtb/rockchip/overlay/rk3399-fixup.scr'
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=4340000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 16866219 Bytes = 16.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f0efe000, end f1f13bab ... OK
Loading Device Tree to 00000000f0e82000, end 00000000f0efdfff ... OK
Starting kernel ...
efi_free_pool: illegal free 0x00000000f0f16040
efi_free_pool: illegal free 0x00000000f0f13040
efi_free_pool: illegal free 0x00000000f0f11040
[ 2.947628] Internal error: Oops: 0000000086000005 [#1] SMP
[ 2.948138] Modules linked in:
[ 2.948417] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G B 6.1.58-ophub #1
[ 2.949120] Hardware name: Fine3399 (DT)
[ 2.949471] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.950089] pc : 0x0
[ 2.950294] lr : rcu_core+0x1bc/0x500
[ 2.950629] sp : ffffffc00a153ed0
[ 2.950925] x29: ffffffc00a153ed0 x28: ffffffc00810faac x27: 0000000000000000
[ 2.951565] x26: ffffff80f7f43f38 x25: ffffffc009e8d7c0 x24: 000000000000000a
[ 2.952205] x23: 0000000000000003 x22: ffffffc00a153f40 x21: ffffff80006af000
[ 2.952847] x20: ffffff80f7f43ec0 x19: 0000000000000004 x18: 000000000000017d
[ 2.953488] x17: ffffffc0ee573000 x16: ffffffc00a150000 x15: 0000000000000000
[ 2.954128] x14: ffffff80006af000 x13: 00000000000003ee x12: 0000000000000000
[ 2.954768] x11: 0000000000000003 x10: ffffffc009d8eaa0 x9 : ffffff80f7f49318
[ 2.955408] x8 : fffffffe00233e08 x7 : 0000000000000000 x6 : 0000000000000001
[ 2.956050] x5 : ffffff80f7f49300 x4 : 0000000000000000 x3 : 0000000000000000
[ 2.956722] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff8001cfe000
[ 2.957397] Call trace:
[ 2.957635] 0x0
[ 2.957824] rcu_core_si+0x10/0x20
[ 2.958156] _stext+0x10c/0x290
[ 2.958466] ____do_softirq+0x10/0x20
[ 2.958823] call_on_irq_stack+0x24/0x58
[ 2.959204] do_softirq_own_stack+0x1c/0x30
[ 2.959605] irq_exit_rcu+0x7c/0xa4
[ 2.959945] el1_interrupt+0x4c/0xb0
[ 2.960294] el1h_64_irq_handler+0x18/0x2c
[ 2.960689] el1h_64_irq+0x74/0x78
[ 2.961019] cpuidle_enter_state+0x138/0x2f0
[ 2.961432] cpuidle_enter+0x40/0x60
[ 2.961780] do_idle+0x1c8/0x240
[ 2.962102] cpu_startup_entry+0x38/0x40
[ 2.962484] secondary_start_kernel+0x144/0x184
[ 2.962923] __secondary_switched+0xb0/0xb4
[ 2.963336] Code: bad PC value
[ 2.963633] ---[ end trace 0000000000000000 ]---
[ 2.964064] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[ 2.964691] SMP: stopping secondary CPUs
[ 2.965201] Kernel Offset: disabled
[ 2.965529] CPU features: 0x80000,20824084,0000421b
[ 2.965984] Memory Limit: none
[ 2.966281] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---U-Boot TPL 2022.07 (Oct 18 2023 - 10:03:11) Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2022.07 (Oct 18 2023 - 10:03:11 +0800) Trying to boot from MMC2 U-Boot 2022.07 (Oct 18 2023 - 10:03:11 +0800) SoC: Rockchip rk3399 Reset cause: POR Model: Fine3399 DRAM: 3.9 GiB PMIC: RK808 Core: 278 devices, 29 uclasses, devicetree: separate MMC: mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Fine3399 Net: Error: ethernet@fe300000 address not set. No ethernet found. Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 3252 bytes read in 11 ms (288.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 265 bytes read in 9 ms (28.3 KiB/s) 16866283 bytes read in 1612 ms (10 MiB/s) 33923584 bytes read in 3225 ms (10 MiB/s) 78941 bytes read in 25 ms (3 MiB/s) Failed to load '/dtb/rockchip/overlay/rk3399-fixup.scr' Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=4340000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16866219 Bytes = 16.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f0efe000, end f1f13bab ... OK Loading Device Tree to 00000000f0e82000, end 00000000f0efdfff ... OK Starting kernel ... efi_free_pool: illegal free 0x00000000f0f16040 efi_free_pool: illegal free 0x00000000f0f13040 efi_free_pool: illegal free 0x00000000f0f11040 [ 2.947628] Internal error: Oops: 0000000086000005 [#1] SMP [ 2.948138] Modules linked in: [ 2.948417] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G B 6.1.58-ophub #1 [ 2.949120] Hardware name: Fine3399 (DT) [ 2.949471] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.950089] pc : 0x0 [ 2.950294] lr : rcu_core+0x1bc/0x500 [ 2.950629] sp : ffffffc00a153ed0 [ 2.950925] x29: ffffffc00a153ed0 x28: ffffffc00810faac x27: 0000000000000000 [ 2.951565] x26: ffffff80f7f43f38 x25: ffffffc009e8d7c0 x24: 000000000000000a [ 2.952205] x23: 0000000000000003 x22: ffffffc00a153f40 x21: ffffff80006af000 [ 2.952847] x20: ffffff80f7f43ec0 x19: 0000000000000004 x18: 000000000000017d [ 2.953488] x17: ffffffc0ee573000 x16: ffffffc00a150000 x15: 0000000000000000 [ 2.954128] x14: ffffff80006af000 x13: 00000000000003ee x12: 0000000000000000 [ 2.954768] x11: 0000000000000003 x10: ffffffc009d8eaa0 x9 : ffffff80f7f49318 [ 2.955408] x8 : fffffffe00233e08 x7 : 0000000000000000 x6 : 0000000000000001 [ 2.956050] x5 : ffffff80f7f49300 x4 : 0000000000000000 x3 : 0000000000000000 [ 2.956722] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff8001cfe000 [ 2.957397] Call trace: [ 2.957635] 0x0 [ 2.957824] rcu_core_si+0x10/0x20 [ 2.958156] _stext+0x10c/0x290 [ 2.958466] ____do_softirq+0x10/0x20 [ 2.958823] call_on_irq_stack+0x24/0x58 [ 2.959204] do_softirq_own_stack+0x1c/0x30 [ 2.959605] irq_exit_rcu+0x7c/0xa4 [ 2.959945] el1_interrupt+0x4c/0xb0 [ 2.960294] el1h_64_irq_handler+0x18/0x2c [ 2.960689] el1h_64_irq+0x74/0x78 [ 2.961019] cpuidle_enter_state+0x138/0x2f0 [ 2.961432] cpuidle_enter+0x40/0x60 [ 2.961780] do_idle+0x1c8/0x240 [ 2.962102] cpu_startup_entry+0x38/0x40 [ 2.962484] secondary_start_kernel+0x144/0x184 [ 2.962923] __secondary_switched+0xb0/0xb4 [ 2.963336] Code: bad PC value [ 2.963633] ---[ end trace 0000000000000000 ]--- [ 2.964064] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 2.964691] SMP: stopping secondary CPUs [ 2.965201] Kernel Offset: disabled [ 2.965529] CPU features: 0x80000,20824084,0000421b [ 2.965984] Memory Limit: none [ 2.966281] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---
这是我用openwrt仓库打包固件的启动日志，我再试试armbian
r1172464137
commented
1 year ago armbian log
U-Boot TPL 2022.07 (Oct 18 2023 - 10:03:11)
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2022.07 (Oct 18 2023 - 10:03:11 +0800)
Trying to boot from MMC2
U-Boot 2022.07 (Oct 18 2023 - 10:03:11 +0800)
SoC: Rockchip rk3399
Reset cause: POR
Model: Fine3399
DRAM: 3.9 GiB
PMIC: RK808
Core: 278 devices, 29 uclasses, devicetree: separate
MMC: mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Fine3399
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
3252 bytes read in 12 ms (264.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
269 bytes read in 8 ms (32.2 KiB/s)
16866283 bytes read in 1613 ms (10 MiB/s)
33923584 bytes read in 3225 ms (10 MiB/s)
78941 bytes read in 28 ms (2.7 MiB/s)
Failed to load '/dtb/rockchip/overlay/rk3399-fixup.scr'
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=4340000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 16866219 Bytes = 16.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f0efe000, end f1f13bab ... OK
Loading Device Tree to 00000000f0e82000, end 00000000f0efdfff ... OK
Starting kernel ...
efi_free_pool: illegal free 0x00000000f0f16040
efi_free_pool: illegal free 0x00000000f0f13040
efi_free_pool: illegal free 0x00000000f0f11040
U-Boot TPL 2022.07 (Oct 18 2023 - 10:03:11)
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2022.07 (Oct 18 2023 - 10:03:11 +0800)
Trying to boot from MMC2
U-Boot 2022.07 (Oct 18 2023 - 10:03:11 +0800)
SoC: Rockchip rk3399
Reset cause: POR
Model: Fine3399
DRAM: 3.9 GiB
PMIC: RK808
Core: 278 devices, 29 uclasses, devicetree: separate
MMC: mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Fine3399
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
3252 bytes read in 12 ms (264.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
269 bytes read in 8 ms (32.2 KiB/s)
16866283 bytes read in 1613 ms (10 MiB/s)
33923584 bytes read in 3225 ms (10 MiB/s)
78941 bytes read in 28 ms (2.7 MiB/s)
Failed to load '/dtb/rockchip/overlay/rk3399-fixup.scr'
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=4340000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 16866219 Bytes = 16.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f0efe000, end f1f13bab ... OK
Loading Device Tree to 00000000f0e82000, end 00000000f0efdfff ... OK
Starting kernel ...
efi_free_pool: illegal free 0x00000000f0f16040
efi_free_pool: illegal free 0x00000000f0f13040
efi_free_pool: illegal free 0x00000000f0f11040
U-Boot TPL 2022.07 (Oct 18 2023 - 10:03:11)
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2022.07 (Oct 18 2023 - 10:03:11 +0800)
Trying to boot from MMC2
U-Boot 2022.07 (Oct 18 2023 - 10:03:11 +0800)
SoC: Rockchip rk3399
Reset cause: POR
Model: Fine3399
DRAM: 3.9 GiB
PMIC: RK808
Core: 278 devices, 29 uclasses, devicetree: separate
MMC: mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Fine3399
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
3252 bytes read in 12 ms (264.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
269 bytes read in 8 ms (32.2 KiB/s)
16866283 bytes read in 1613 ms (10 MiB/s)
33923584 bytes read in 3225 ms (10 MiB/s)
78941 bytes read in 28 ms (2.7 MiB/s)
Failed to load '/dtb/rockchip/overlay/rk3399-fixup.scr'
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=4340000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 16866219 Bytes = 16.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f0efe000, end f1f13bab ... OK
Loading Device Tree to 00000000f0e82000, end 00000000f0efdfff ... OK
Starting kernel ...
efi_free_pool: illegal free 0x00000000f0f16040
efi_free_pool: illegal free 0x00000000f0f13040
efi_free_pool: illegal free 0x00000000f0f11040内核恐慌，你使用sw799的固件可以正常启动？
r1172464137
commented
1 year ago 可以
ophub
commented
1 year ago 如果方便挂载img修改的话，你试试把rk3399-bozz-sw799.dtb 重命名成rk3399-fine3399.dtb，更换这个dtb试试？
r1172464137
commented
1 year ago 我等会儿试下
ophub
commented
1 year ago rk3399-bozz-sw799.dtb 这个有dts源码没？我还说好容易有rk3399-fine3399.dts了，用这个呢
r1172464137
commented
1 year ago build-linux仓库有个bsp的dts，不知道是不是你说的那个
ophub
commented
1 year ago https://github.com/cm9vdA/build-linux/blob/master/boot/dts/rockchip/bsp/rk3399-fine3399.dts
我上面使用的是这个，你说的是哪个？
我回头删除了这个fine3399吧，把之前的sw799改名下，你找到dts了发给我下
r1172464137
commented
1 year ago https://github.com/cm9vdA/build-linux/blob/master/boot/dts/rockchip/bsp/rk3399-fine3399.dts
我上面使用的是这个，你说的是哪个？
我回头删除了这个fine3399吧，把之前的sw799改名下，你找到dts了发给我下
行
r1172464137
commented
1 year ago r1172464137
commented
1 year ago 再试试
这次八成行
r1172464137
commented
1 year ago ophub
commented
1 year ago r1172464137
commented
1 year ago 电脑暂时g了送去修了，暂时无法测试。 但根据群友测试，armbian和openwrt均可以开机，但无法获取ip地址，初步推测是网卡没驱动成功。 具体的得等我电脑回来才能搞
r1172464137
commented
1 year ago Fine3399是rumu3f设计的一个多用途嵌入式主板，采用bozztek的SW799系列核心板，处理器为RK3399。
Fine3399资料网站: https://gitee.com/opengisbook/Fine3399-Official
长风大佬的dts提交(其中有SPI Flash和屏幕的定义，但被注释了): cm9vdA/build-linux@ab3e4f5
我建议依然使用该dts。经过我的测试，kernel panic的出现仅为个例（30次就出现了一次，还有一次卡在了网卡设置那），但在设备长时间未上电的情况下再上电极易会造成内核恐慌。之后就会很少出现这个问题。 所以我建议在使用这个dts的时候在boot.cmd中的bootargs环境变量中加入panic参数以便于自动重启。
ophub
commented
1 year ago 你使用的是哪个u-boot？cm9vdA的还是你后面发的？这几个文件你测试好了，包括相关文件的修改发给我一套你测试好的组合。
r1172464137
commented
1 year ago 内核: https://github.com/r1172464137/kernel/releases/download/kernel_stable/5.15.137.tar.gz uboot: uboot.zip dts: https://github.com/cm9vdA/build-linux/commit/ab3e4f56c5738e274b6200172816062648a44698
其中内核暂时不推荐使用5.15，这两天测试了5.15和6.1的内核发现5.15更稳定，几乎不会出现任何问题，6.1问题就有点多了(5.4和和5.10没测试)。 还有顺便说下openwrt-update-rockchip这个升级不了，具体原因是loop0p2挂载不上,具体日志如下，我也看了下升级脚本，尝试自己手动升级，但还是一样的错误，等下我来贴个更具体的日志
dmesg
[ 700.671390] loop0: detected capacity change from 0 to 2654208
[ 700.673190] loop0: p1 p2
[ 700.963534] EXT4-fs (loop0p1): mounted filesystem with ordered data mode. Opts: . Quota mode: none.
[ 704.913944] EXT4-fs (loop0p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[ 704.920211] BTRFS warning: duplicate device /dev/loop0p2 devid 1 generation 17 scanned by mount (10866)root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
udev 512.0K 0 512.0K 0% /dev
tmpfs 387.4M 636.0K 386.7M 0% /run
/dev/mmcblk2p2 1023.0M 538.4M 384.8M 58% /
tmpfs 1.9G 25.0M 1.9G 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
cgroup 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/mmcblk2p1 222.8M 71.7M 145.9M 33% /boot
/dev/mmcblk2p3 1023.0M 3.4M 1010.0M 0% /mnt/mmcblk2p3
/dev/mmcblk2p4 55.4G 1.3G 54.1G 2% /mnt/mmcblk2p4
/dev/mmcblk2p4 55.4G 1.3G 54.1G 2% /mnt/mmcblk2p4/docker脚本日志
mount: /mnt/mmcblk2p4/root: mount(2) system call failed: File exists. dmesg(1) may have more information after failed mount system call.你是不是写错了？推荐使用5.15内核，你说这个稳定？
u-boot我使用你的更新了仓库的文件了，dts我先推送到f大的仓库，以后有更新再优化。
r1172464137
commented
1 year ago 你是不是写错了？推荐使用5.15内核，你说这个稳定？
u-boot我使用你的更新了仓库的文件了，dts我先推送到f大的仓库，以后有更新再优化。
前两天我把Ubuntu和debian的镜像都测试过了，Ubuntu配6.1启动20次有2,3次启动不了，debian配6.1简直就是没法看，10次就3次能启动成功，5.15+Ubuntu或者debian倒是没什么问题，基本每次都能启动成功
ophub
commented
1 year ago 那我就改下内核，默认5.15得了。 我已经调整成了5.15.y了，几个固件都重新编译了一下。
ophub
commented
1 year ago 你上面说的loop0p2挂载不上的问题，你手动安装（或宝盒插件安装，设置里选择共享分区格式为BTRFS)时最后一步选择p4分区格式时选择BTRFS，不选ext4。再试试，错误显示挂载选项参数不对，你用哪个op源码编的？
r1172464137
commented
1 year ago lede，immoraltal，官方我都试过，用的是armvirt或者armsr的固件打的包，打包的时候rootfs的分区就是btrfs的，用maskrom的方式刷入固件，尝试晶晨宝盒与手动脚本升级的时候也是用btrfs的挂载方式。
我手动升级时挂载loop0p2的命令为:
mount -t btrfs -o ro,compress=zstd:6 /dev/loop0p2 /mnt/mmcblk2p4/root安装时，mmcblk2p4这个选择btrfs格式，上面的日志显示你p4这个选择的是ext4格式。
r1172464137
commented
1 year ago 我等下试下
r1172464137
commented
1 year ago 设置了btrfs
操作日志:
root@OpenWrt:~# mkfs.btrfs /dev/mmcblk2p4
btrfs-progs v6.5.1
See https://btrfs.readthedocs.io for more information.
ERROR: /dev/mmcblk2p4 appears to contain an existing filesystem (ext4)
ERROR: use the -f option to force overwrite of /dev/mmcblk2p4
root@OpenWrt:~# mkfs.btrfs -f /dev/mmcblk2p4
btrfs-progs v6.5.1
See https://btrfs.readthedocs.io for more information.
Performing full device TRIM /dev/mmcblk2p4 (55.35GiB) ...
NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)
Label: (null)
UUID: 654a112d-a64e-46c5-aff9-bd69c425065a
Node size: 16384
Sector size: 4096
Filesystem size: 55.35GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 1.00GiB
System: DUP 8.00MiB
SSD detected: yes
Zoned device: no
Incompat features: extref, skinny-metadata, no-holes, free-space-tree
Runtime features: free-space-tree
Checksum: crc32c
Number of devices: 1
Devices:
ID SIZE PATH
1 55.35GiB /dev/mmcblk2p4
root@OpenWrt:~# mountmount -t btrfs -o ro,compress=zstd:6 /dev/mmcblk2p /mnt/mmcblk2p4/
mmcblk2p1 mmcblk2p2 mmcblk2p3 mmcblk2p4
root@OpenWrt:~# mount -t btrfs -o rw,compress=zstd:6 /dev/mmcblk2p4 /mnt/mmcblk2p4/
root@OpenWrt:~# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
mmcblk2
├─mmcblk2p1 ext4 BOOT b65b6241-f5b3-4e91-a69d-b4fb26673e26 145.9M 32% /boot
├─mmcblk2p2 btrfs ROOTFS efd617f5-6948-429f-824c-9b9a9e4c0944 664.4M 24% /
├─mmcblk2p3 btrfs MMC_ROOTFS2 dcd2f06c-d217-4caa-b517-78c23b7b0edf 1010M 0% /mnt/mmcblk2p3
└─mmcblk2p4 btrfs 654a112d-a64e-46c5-aff9-bd69c425065a 53.3G 0% /mnt/mmcblk2p4
mmcblk2boot0
mmcblk2boot1
root@OpenWrt:~# openwrt-update-rockchip
Current device: Fine3399 [ rk3399 ]
Update using [ openwrt_official_rockchip_fine3399_k5.15.137_2023.10.28.img.gz ] file. Please wait a moment ...
Start update from [ openwrt_official_rockchip_fine3399_k5.15.137_2023.10.28.img ]
Whether to backup and restore the current config files? y/n [y]
mknod: /dev/loop0p1: File exists
mknod: /dev/loop0p2: File exists
The loopdev is /dev/loop0, wait 3 seconds ...
umount /dev/loop0p1 ... ok
mount /dev/loop0p1 -> /mnt/mmcblk2p4/boot ... ok
mount /dev/loop0p2 -> /mnt/mmcblk2p4/root ... mount: /mnt/mmcblk2p4/root: mount(2) system call failed: File exists.
dmesg(1) may have more information after failed mount system call.
mount faileddmes日志:
[ 818.521291] BTRFS: device fsid 654a112d-a64e-46c5-aff9-bd69c425065a devid 1 transid 6 /dev/mmcblk2p4 scanned by mkfs.btrfs (32326)
[ 854.419654] BTRFS info (device mmcblk2p4): using crc32c (crc32c-generic) checksum algorithm
[ 854.419695] BTRFS info (device mmcblk2p4): setting incompat feature flag for COMPRESS_ZSTD (0x10)
[ 854.419706] BTRFS info (device mmcblk2p4): use zstd compression, level 6
[ 854.419715] BTRFS info (device mmcblk2p4): using free space tree
[ 854.419721] BTRFS info (device mmcblk2p4): has skinny extents
[ 854.419727] BTRFS info (device mmcblk2p4): flagging fs with big metadata feature
[ 854.428223] BTRFS info (device mmcblk2p4): enabling ssd optimizations
[ 854.428728] BTRFS info (device mmcblk2p4): checking UUID tree
[ 956.578361] loop0: detected capacity change from 0 to 2654208
[ 956.579651] loop0: p1 p2
[ 956.864135] EXT4-fs (loop0p1): mounted filesystem with ordered data mode. Opts: . Quota mode: none.
[ 960.904319] EXT4-fs (loop0p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[ 960.910139] BTRFS warning: duplicate device /dev/loop0p2 devid 1 generation 20 scanned by mount (6303)其中的ext4的日志应该是与loop0p1挂载的/mnt/mmcblk2p4/boot有关
r1172464137
commented
1 year ago 尝试手动升级的日志
root@OpenWrt:~# cd /mnt/mmcblk2p4
root@OpenWrt:/mnt/mmcblk2p4# losetup -f -P
boot/
openwrt_official_rockchip_fine3399_k5.15.137_2023.10.28.img
root/
root@OpenWrt:/mnt/mmcblk2p4# losetup -f -P openwrt_official_rockchip_fine3399_k5.15.137_2023.10.28.img
root@OpenWrt:/mnt/mmcblk2p4# losetup | grep "${IMG_NAME}" | awk '{print $1}'
NAME
/dev/loop0
root@OpenWrt:/mnt/mmcblk2p4# umount /dev/loop0
loop0 loop0p1 loop0p2
root@OpenWrt:/mnt/mmcblk2p4# umount /dev/loop0
loop0 loop0p1 loop0p2
root@OpenWrt:/mnt/mmcblk2p4# umount /dev/loop0p1
root@OpenWrt:/mnt/mmcblk2p4# umount /dev/loop0p2
umount: /dev/loop0p2: not mounted.
root@OpenWrt:/mnt/mmcblk2p4# mount -t ext4 -o ro /dev/loop0p1 /mnt/mmcblk2p4/boot/
root@OpenWrt:/mnt/mmcblk2p4# mount -t btrfs -o ro,compress=zstd:6 /dev/loop0p2 /mnt/mmcblk2p4/root
mount: /mnt/mmcblk2p4/root: mount(2) system call failed: File exists.
dmesg(1) may have more information after failed mount system call.
root@OpenWrt:/mnt/mmcblk2p4# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
├─loop0p1 ext4 BOOT b65b6241-f5b3-4e91-a69d-b4fb26673e26 145.9M 32% /mnt/mmcblk2p4/boot
└─loop0p2 btrfs ROOTFS efd617f5-6948-429f-824c-9b9a9e4c0944
mmcblk2
├─mmcblk2p1 ext4 BOOT b65b6241-f5b3-4e91-a69d-b4fb26673e26 145.9M 32% /boot
├─mmcblk2p2 btrfs ROOTFS efd617f5-6948-429f-824c-9b9a9e4c0944 664.4M 24% /
├─mmcblk2p3 btrfs MMC_ROOTFS2 dcd2f06c-d217-4caa-b517-78c23b7b0edf 1010M 0% /mnt/mmcblk2p3
└─mmcblk2p4 btrfs 654a112d-a64e-46c5-aff9-bd69c425065a 52.9G 1% /mnt/mmcblk2p4
mmcblk2boot0
mmcblk2boot1你改了安装脚本？p2怎么才600m？p3是1000m，这两个都不是原版安装脚本的分区结果。
r1172464137
commented
1 year ago 没改安装脚本，我安装上就是这么大，我重新划分下试试
r1172464137
commented
1 year ago 你改了安装脚本？p2怎么才600m？p3是1000m，这两个都不是原版安装脚本的分区结果。
你说的安装脚本是把镜像刻到u盘，然后再用脚本写入到emmc里吗
ophub
commented
1 year ago 你的bootfs和rootfs大小都和默认不一样。
手动挂载不需要加那些参数，简单卸载，格式化，挂载即可。有些参数op不一定认，和armbian不一样，op有些软件包是减配版。
umount -l /dev/mmcblk2p3
mkfs.btrfs /dev/mmcblk2p3 -f
mount /dev/mmcblk2p3 /mnt/mmcblk2p3tf/dd，或者rktool写入，应该都不会改变了p1/p2/p3的大小
r1172464137
commented
1 year ago 我用的这个
r1172464137
commented
1 year ago root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
udev 512.0K 0 512.0K 0% /dev
tmpfs 387.4M 616.0K 386.8M 0% /run
/dev/mmcblk2p2 1023.0M 287.9M 625.4M 32% /
tmpfs 1.9G 22.2M 1.9G 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
cgroup 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/mmcblk2p2 1023.0M 287.9M 625.4M 32% /opt/docker
/dev/mmcblk2p1 222.8M 71.7M 145.9M 33% /boot
/dev/mmcblk2p4 55.4G 1.3G 52.1G 2% /mnt/mmcblk2p4
/dev/mmcblk2p3 1023.0M 3.5M 903.8M 0% /mnt/mmcblk2p3这个分区正常，应该可以正常更新。 docker现在挂载在root根分区会导致满盘了，把docker目录改到p4里（正常情况下脚本会自动指向p4,不用人工调整）
ophub
commented
1 year ago _lede_的我测试手动挂载这个img也失败了，看来这个镜像有问题，我换了_official_的测试通过了。
2个不同源码编译的镜像，更新时应该选择不保留配置更新，这2个版本差异明显，配置文件不通用，我忘记取消勾选了，可能重启后会配置错乱，你重新刷吧。
dutong0321
commented
1 year ago 上次SW799烧录后板子没有成功启动，期待大佬早日完美适配。
r1172464137
commented
1 year ago 上次SW799烧录后板子没有成功启动，期待大佬早日完美适配。
你是双网口底板吗
dutong0321
commented
1 year ago 上次SW799烧录后板子没有成功启动，期待大佬早日完美适配。
你是双网口底板吗
不是，单网口的，bozz带的那个版本的
r1172464137
commented
1 year ago 上次SW799烧录后板子没有成功启动，期待大佬早日完美适配。
你是双网口底板吗
不是，单网口的，bozz带的那个版本的
那不是有sw799的版本吗，这个专门适配fine3399的
dutong0321
commented
1 year ago http://www.bozztek.com/index.php/article/show/aid/839/lang/cn SW7990K VER1.4(带核心板SW799A VER1.2) 模型：SW7990K VER1.4(带核心板SW799A VER1.2)
SW799烧录进去没有成功，本来打算等更名后，看看能不能适配了我的底板，或者到时候实在不行，买上个FINE3399的底板
r1172464137
commented
1 year ago 你可以尝试用5.15的内核给sw799打下包，毕竟6.1的fine3399很多时候也很难启动成功，5.15会好一些
dutong0321
commented
1 year ago 哦哦，感谢帮忙，等摸完鱼回家试试😀
icyleaf
commented
11 months ago 我刷了好几个 5.15 不同系统的 ext4/btrfs 固件，目前遇到几个问题：
以上问题在 armbian bozz 固件正常，这个固件的问题是 hdmi 输出不正常；更新 apt 后重启系统就无法重启。请问大家有遇到过吗？
更详细的信息发布在 gist 上。
gdanmac
commented
5 months ago bozz 这板子 有新的内核吗
ophub
commented
5 months ago 现在6.6.y，6.1.y，5.15.y都添加了，你试试fine3399
gdanmac
commented
5 months ago 现在6.6.y，6.1.y，5.15.y都添加了，你试试fine3399
感谢大佬 ，SW799可以通用fine3399的固件吗？
Fine3399是rumu3f设计的一个多用途嵌入式主板，采用bozztek的SW799系列核心板，处理器为RK3399。
Fine3399资料网站: https://gitee.com/opengisbook/Fine3399-Official
长风大佬的dts提交(其中有SPI Flash和屏幕的定义，但被注释了): https://github.com/cm9vdA/build-linux/commit/ab3e4f56c5738e274b6200172816062648a44698