Firefox deb version freezed when try to play video

george

@mainbord
Coolpi4b and cm5 evb currently support mainline kernels above 6.8, but laptops do not support mainline kernels due to eDP display drivers. So it will be a little later. Currently undergoing debugging. Looking forward to the next main version being released. Thank you for your support.

mainbord

@george
May be you can add build recipe here, it will be a good advertise
https://github.com/manjaro-arm

plumlis

Actully not only video playing decode issue.
But also some display area shutter issue while scrolling.
Disable GPU accelaration. everthing looks fine now.

Will this be solved in kernel 6.1 BSP?
How is the status of kernel 6.1 now? When will we see it?

I tried to compile kernel by myself ftom cool pi github 6.1 stan rkr1 branch but failed.

plumlis

Is it safe to install newer version mesa?
I saw that new version mesa have many panfrost related fixes.

george

@plumlis
The kernel version 6.1 will support it and is currently being adapted.

plumlis

@george okay. hope kernel 6.1 will release soon.

And thanks for your hard work.

plumlis

@george

Hey George. Could you have some USB Disk brands recomand to use as Boot drive?

I tried many Sandisk 3.0 and all of them don't work. Only one 16GB USB(No brand) disk can boot up. But it can't be use as fedora image( It's 17GB )

george

@plumlis
Let me briefly introduce the current situation of the NAND flash industry. The best A-class die is used as a high-capacity and high-value storage device for first tier brands such as SSDs and EMMCs. The worse one is used for second tier brands such as EMMCs and NAND FLASH, and the worse one is used for a large number of bad fast devices. The 8GB capacity can be reduced to 4G or 2G for USB drives or T cards. There is even worse junk die, which will appear on the T card that costs a few yuan on Mouduoduo. So if doing system mirroring, it is recommended to use SSD or SATA portable hard drives, as both performance and reliability are the best.

plumlis

@george I knew that.
But the point is I can't find a usb stick to make this fedora image boot up.
Wiki said only usb 2.0 disk can be boot up.

I tested all my usb 3.0/2.0 devices. Only one usb 2.0 stick can be booted. But it's 16GB, fedora image is 17GB and can't write to it.

I just asked you to recommand a usb device can be boot up.

george

@plumlis
Suggest updating uboot to the latest version and then trying USB BOOT. The latest development branch has been optimized for some USB drives. Of course, you can also write images to EMMC through UMS.

plumlis

@george It seems I have to compile boot loader first?

https://cool-pi.com/topic/380/cool-pi-4b-cm5-linux-system-support-compile-u-boot

Following this guide.

Ubuntu 24.04 don't have python2, can't compile directly, annoying

george

@plumlis

sudo ln -s /usr/bin/python3.12 /usr/bin/python

plumlis

@george

Already did. Seems it doesn't work.

$./build-uboot.sh cm5-notebook

## make rk3588_coolpicm5_notebook_defconfig -j16
#
# configuration written to .config
#
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk.dep
  CFG     spl/u-boot.cfg
  CFG     tpl/u-boot.cfg
  GEN     spl/include/autoconf.mk
  GEN     include/autoconf.mk
  GEN     tpl/include/autoconf.mk
  CHK     include/config/uboot.release
  CHK     include/generated/timestamp_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  CHK     include/config.h
  CFG     u-boot.cfg
  CHK     include/generated/version_autogenerated.h
  CHK     include/generated/generic-asm-offsets.h
  CHK     include/generated/asm-offsets.h
  HOSTCC  tools/mkenvimage.o
  HOSTCC  tools/fit_image.o
  HOSTCC  tools/image-host.o
  HOSTCC  tools/dumpimage.o
  HOSTCC  tools/mkimage.o
  HOSTCC  tools/rockchip/boot_merger.o
  HOSTCC  tools/rockchip/loaderimage.o
  HOSTLD  tools/loaderimage
tools/rockchip/boot_merger.c: In function ‘mergeBoot’:
tools/rockchip/boot_merger.c:700:43: warning: ‘%s’ directive output may be truncated writing up to 813 bytes into a region of size 5 [-Wformat-truncation=]
  700 |         snprintf(buffer, sizeof(buffer), "%s", chip);
      |                                           ^~
......
  742 |                 chipType = convertChipType(chip + 2);
      |                            ~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/stdio.h:980,
                 from ././include/compiler.h:25,
                 from <command-line>:
In function ‘snprintf’,
    inlined from ‘convertChipType’ at tools/rockchip/boot_merger.c:700:2,
    inlined from ‘getChipType’ at tools/rockchip/boot_merger.c:742:14,
    inlined from ‘getBoothdr’ at tools/rockchip/boot_merger.c:761:18,
    inlined from ‘mergeBoot’ at tools/rockchip/boot_merger.c:830:2:
/usr/include/aarch64-linux-gnu/bits/stdio2.h:54:10: note: ‘__builtin_snprintf’ output between 1 and 814 bytes into a destination of size 5
   54 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   55 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   56 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
In function ‘wide2str’,
    inlined from ‘unpackBoot’ at tools/rockchip/boot_merger.c:955:3,
    inlined from ‘main’ at tools/rockchip/boot_merger.c:1072:8:
tools/rockchip/boot_merger.c:895:18: warning: array subscript 20 is outside array bounds of ‘char[20]’ [-Warray-bounds=]
  895 |         str[len] = 0;
      |         ~~~~~~~~~^~~
tools/rockchip/boot_merger.c: In function ‘main’:
tools/rockchip/boot_merger.c:933:14: note: at offset 20 into object ‘name’ of size 20
  933 |         char name[MAX_NAME_LEN];
      |              ^~~~
  HOSTLD  tools/boot_merger
  HOSTLD  tools/mkenvimage
  HOSTLD  tools/dumpimage
  HOSTLD  tools/mkimage
  CC      arch/arm/cpu/armv8/fwcall.o
  CC      common/main.o
  LD      arch/arm/cpu/armv8/built-in.o
  CC      cmd/version.o
  LD      common/built-in.o
  CC      lib/display_options.o
  LD      cmd/built-in.o
  LD      lib/built-in.o
  LD      u-boot
/usr/bin/aarch64-linux-gnu-ld.bfd: warning: u-boot has a LOAD segment with RWX permissions
  OBJCOPY u-boot.srec
  OBJCOPY u-boot-nodtb.bin
  SYM     u-boot.sym
make[2]: 'arch/arm/dts/rk3588-cp5-x8.dtb' is up to date.
  COPY    u-boot.dtb
start=$(/usr/bin/aarch64-linux-gnu-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' '); end=$(/usr/bin/aarch64-linux-gnu-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x00200000 $start $end
  CAT     u-boot-dtb.bin
  MKIMAGE u-boot.img
  MKIMAGE u-boot-dtb.img
  COPY    u-boot-dtb-kern.bin
  ALIGN   u-boot-dtb-kern.bin
  CAT     u-boot.bin
  CC      spl/common/spl/spl.o
  CC      spl/arch/arm/cpu/armv8/fwcall.o
  COPY    spl/u-boot-spl.dtb
  CC      tpl/arch/arm/cpu/armv8/fwcall.o
  LD      spl/arch/arm/cpu/armv8/built-in.o
  CC      tpl/arch/arm/mach-rockchip/tpl.o
  LD      tpl/arch/arm/cpu/armv8/built-in.o
  CC      spl/lib/display_options.o
  LD      tpl/arch/arm/mach-rockchip/built-in.o
  LD      spl/common/spl/built-in.o
  LD      spl/lib/built-in.o
  LD      tpl/u-boot-tpl
/usr/bin/aarch64-linux-gnu-ld.bfd: warning: u-boot-tpl has a LOAD segment with RWX permissions
  OBJCOPY tpl/u-boot-tpl-nodtb.bin
  COPY    tpl/u-boot-tpl.bin
  LD      spl/u-boot-spl
/usr/bin/aarch64-linux-gnu-ld.bfd: warning: u-boot-spl has a LOAD segment with RWX permissions
  OBJCOPY spl/u-boot-spl-nodtb.bin
  CAT     spl/u-boot-spl-dtb.bin
  COPY    spl/u-boot-spl.bin
  CFGCHK  u-boot.cfg
ERROR: No python2

$ python
Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

george

@plumlis
The following is what I have compiled and can be used directly.
RKDevTool_v3.13_for_window.rar

plumlis

@george thanks.
The only way to upgrade uboot is following this guide?

https://forum.cool-pi.com/topic/162/how-to-upgrade-the-boot-loader-of-coolpi-4b

short two pins and conect to PC to upgrade loader?

george

This post is deleted!

george

@plumlis
Follow the steps below to operate:
1.USB cable for TYPEC interface and X86 computer connection
2. Run sudo reboot loader on the shell，The machine will enter loader mode, as shown in the following figure

3. Click on the tool to force entry into maskrom mode

4. Check the option to force writing by address

5. Burning, the machine will automatically restart after completion

plumlis

@george Nice, I'll try it.

Btw I finally figured out why my USB Disk can't boot up.

The the fedora image you gave me have Boot up info in cmdline like this:

rootfs=LABLE=writable

And my EMMC also has a parttion labled writable(dafault).

So actually it booted up from usb disk, but set writable lable on emmc as root, So I boot back to my ubuntu. That mislanding me ths USB disk can't be boot up.

I changed to rootfs=UUID=(my usb disk UUID). And I can boot into fedora image now.

george

@plumlis
You can change the EMMC label to writable1 or another name.

plumlis

Upgrade finished, Seems boot up speed much faster than before.

Will play around with fedora image.

BTW I compiled kernel 6.1 from github https://github.com/yanyitech/coolpi-kernel kernel 6.1 branch and It can't boot up.

Hope new kernel will come soon.

Many thanks for your help.