MattWestB Posted June 23, 2022 Posted June 23, 2022 Great thanks @jock and CO !! | _ \| |/ /___ /___ // |( _ ) | __ ) _____ __ | |_) | ' / |_ \ |_ \| |/ _ \ | _ \ / _ \ \/ / | _ <| . \ ___) |__) | | (_) | | |_) | (_) > < |_| \_\_|\_\____/____/|_|\___/ |____/ \___/_/\_\ Welcome to Armbian 22.08.0-trunk Jammy with Linux 5.18.6-rockchip64 HA is up and ruing with ZHA and one Open Thread border router and looks working OK 😘 (upgraded production Ubuntu 22.04 with new kernel on eMMC without testing on SD-Card) 1 Quote
Jason Duhamell Posted June 23, 2022 Posted June 23, 2022 3 hours ago, jock said: UPDATE!! Hello, I'm pleased to announce that rk3318 CSC configuration has been accepted into mainline kernel!. This means that next Armbian release (probably August) will provide regular kernel upgrades offered by Armbian ecosystem via normal apt upgrade command. Until then, please stay stick to the usual manual upgrade! But there is something more: new update for the rk3318/rk3328 images! Most important changes: Kernel upgraded to version v5.18.6 Memory clock set to 667 MHz (was 333 MHz), providing a nice boost in general, desktop and GPU performance; despite this works fine on my board I always warn you to test images first via sdcard Introduces MGLRU patches from @yuzhaogoogle (you can read about here and search google for more details), which should provide much snappier experience especially on low-memory devices You can find the images and deb packages for upgrades browsing the directory pointed on first page as usual. You can visit the Armbian MGLRU topic, if you have questions about the features or kernel issues (like crash dumps which involve kswapd, for example) This is great news! 2 Quote
paradigman Posted June 23, 2022 Posted June 23, 2022 (edited) @jock : you did a great job, congratulations! 👍 I tried the new image today and (I think thanks to the clock change) I saw a 20% increase in speed during the operation of the box. I was hoping that the new image, with its many minor fixes, would also help my Wi-Fi connection problem. Unfortunately, I have not seen any improvement in this area. The relevant part of the dmesg output is: [ 10.099047] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [ 10.099438] usbcore: registered new interface driver brcmfmac [ 10.100554] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.rockchip,rk3318-box.bin failed with error -2 [ 10.304233] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [ 10.304394] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 10.304865] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e Edited June 23, 2022 by paradigman 1 Quote
Willy Moto Posted June 24, 2022 Posted June 24, 2022 12 hours ago, jock said: UPDATE!! Hello, I'm pleased to announce that rk3318 CSC configuration has been accepted into mainline kernel!. This means that next Armbian release (probably August) will provide regular kernel upgrades offered by Armbian ecosystem via normal apt upgrade command. Until then, please stay stick to the usual manual upgrade! But there is something more: new update for the rk3318/rk3328 images! Most important changes: Kernel upgraded to version v5.18.6 Memory clock set to 667 MHz (was 333 MHz), providing a nice boost in general, desktop and GPU performance; despite this works fine on my board I always warn you to test images first via sdcard Introduces MGLRU patches from @yuzhaogoogle (you can read about here and search google for more details), which should provide much snappier experience especially on low-memory devices You can find the images and deb packages for upgrades browsing the directory pointed on first page as usual. You can visit the Armbian MGLRU topic, if you have questions about the features or kernel issues (like crash dumps which involve kswapd, for example) I tried to install the kernel upgrade manually using the DEB downloaded from: https://users.armbian.com/jock/rk3318/upgrade/ Also running "sudo apt-upgrade" at the same time. But the system was unable to boot afterwards. In the past, manual kernel upgrade ( Armbian 22.05 trunk build & beforehand), it used to work every time without issue. I will try to get a console screen and see if I can get some error message for debugging analysis. Thanks. 0 Quote
jock Posted June 24, 2022 Author Posted June 24, 2022 9 hours ago, Willy Moto said: Also running "sudo apt-upgrade" at the same time. But the system was unable to boot afterwards. That's exactly the reason the automatic upgrades must not be run, and instead manual installation with deb packages is the way to go. Did you run apt-mark hold on kernel and dtb packages as stated in the first post before running this? 0 Quote
Willy Moto Posted June 24, 2022 Posted June 24, 2022 26 minutes ago, jock said: That's exactly the reason the automatic upgrades must not be run, and instead manual installation with deb packages is the way to go. Did you run apt-mark hold on kernel and dtb packages as stated in the first post before running this? I was sure apt-mark hold was already run. That should leave all the kernel packages not upgraded by apt-get upgrade command. Let me check the console screen for sure. Be right back. 0 Quote
jock Posted June 24, 2022 Author Posted June 24, 2022 2 minutes ago, Willy Moto said: I was sure apt-mark hold was already run. That should leave all the kernel packages not upgraded by apt-get upgrade command. Let me check the console screen for sure. Be right back. Then I hope the deb packages didn't break your installation 😔 The serial adapter could surely tell more. 0 Quote
Willy Moto Posted June 24, 2022 Posted June 24, 2022 @jock No worries. I knew pretty well the risk involved in running a CSC + still-in-bring-up Armbian build for an unsupported TV box device. You did great no matter what. I think whatever the cause, I managed to corrupt the ETH0 network driver. Here are some screen dump I got from an output console. 0 Quote
Willy Moto Posted June 24, 2022 Posted June 24, 2022 @jock I just realized the previous Armbian Builds were based on Current-branch Kernel, while the latest Armbian Build is based on Edge-branch Kernel. 09/04/2022 19:20 237,289,900 Armbian_22.02.0-trunk_Rk3318-box_bullseye_current_5.15.25_minimal.img.xz 30/04/2022 00:13 248,048,016 Armbian_22.05.0-trunk_Rk3318-box_bullseye_current_5.15.35_minimal.img.xz 24/06/2022 12:23 248,776,832 Armbian_22.08.0-trunk_Rk3318-box_bullseye_edge_5.18.6_minimal.img.xz Would it cause any problem for manually running apt install to install the DEB Kernel package this way, as it would be switching to a different Kernel-branch? Just a thought. 0 Quote
MX10.AC2N Posted June 24, 2022 Posted June 24, 2022 Hi @jock Congrats..! I upgrade with your *.deb and there is some error dpkg -i *.deb (Reading database ... 188694 files and directories currently installed.) Preparing to unpack armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb ... Unpacking armbian-bsp-cli-rk3318-box (22.08.0-trunk) over (22.05.0-trunk) ... Preparing to unpack linux-dtb-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-dtb-edge-rockchip64 (22.08.0-trunk) ... Selecting previously unselected package linux-headers-edge-rockchip64. Preparing to unpack linux-headers-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-headers-edge-rockchip64 (22.08.0-trunk) ... Preparing to unpack linux-image-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-image-edge-rockchip64 (22.08.0-trunk) ... Setting up armbian-bsp-cli-rk3318-box (22.08.0-trunk) ... Setting up linux-dtb-edge-rockchip64 (22.08.0-trunk) ... Setting up linux-headers-edge-rockchip64 (22.08.0-trunk) ... Compiling headers - please wait ... scripts/sign-file.c: In function ‘display_openssl_errors’: scripts/sign-file.c:89:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 89 | while ((e = ERR_get_error_line(&file, &line))) { | ^~~~~ In file included from scripts/sign-file.c:29: /usr/include/openssl/err.h:411:15: note: declared here 411 | unsigned long ERR_get_error_line(const char **file, int *line); | ^~~~~~~~~~~~~~~~~~ scripts/sign-file.c: In function ‘drain_openssl_errors’: scripts/sign-file.c:102:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 102 | while (ERR_get_error_line(&file, &line)) {} | ^~~~~ In file included from scripts/sign-file.c:29: /usr/include/openssl/err.h:411:15: note: declared here 411 | unsigned long ERR_get_error_line(const char **file, int *line); | ^~~~~~~~~~~~~~~~~~ scripts/sign-file.c: In function ‘read_private_key’: scripts/sign-file.c:142:17: warning: ‘ENGINE_load_builtin_engines’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 142 | ENGINE_load_builtin_engines(); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:358:28: note: declared here 358 | OSSL_DEPRECATEDIN_3_0 void ENGINE_load_builtin_engines(void); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ scripts/sign-file.c:144:17: warning: ‘ENGINE_by_id’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 144 | e = ENGINE_by_id("pkcs11"); | ^ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:336:31: note: declared here 336 | OSSL_DEPRECATEDIN_3_0 ENGINE *ENGINE_by_id(const char *id); | ^~~~~~~~~~~~ scripts/sign-file.c:146:17: warning: ‘ENGINE_init’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 146 | if (ENGINE_init(e)) | ^~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:620:27: note: declared here 620 | OSSL_DEPRECATEDIN_3_0 int ENGINE_init(ENGINE *e); | ^~~~~~~~~~~ scripts/sign-file.c:151:25: warning: ‘ENGINE_ctrl_cmd_string’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 151 | ERR(!ENGINE_ctrl_cmd_string(e, "PIN", key_pass, 0), | ^~~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:479:5: note: declared here 479 | int ENGINE_ctrl_cmd_string(ENGINE *e, const char *cmd_name, const char *arg, | ^~~~~~~~~~~~~~~~~~~~~~ scripts/sign-file.c:153:17: warning: ‘ENGINE_load_private_key’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 153 | private_key = ENGINE_load_private_key(e, private_key_name, | ^~~~~~~~~~~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:638:11: note: declared here 638 | EVP_PKEY *ENGINE_load_private_key(ENGINE *e, const char *key_id, | ^~~~~~~~~~~~~~~~~~~~~~~ Setting up linux-image-edge-rockchip64 (22.08.0-trunk) ... * dkms: running auto installation service for kernel 5.18.6-rockchip64 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j4 KERNELRELEASE=5.18.6-rockchip64 all KERNEL_SRC=/lib/modules/5.18.6-rockchip64/build.....(bad exit status: 2) ERROR (dkms apport): binary package for anbox-ashmem: 1 not found Error! Bad return status for module build on kernel: 5.18.6-rockchip64 (aarch64) Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j4 KERNELRELEASE=5.18.6-rockchip64 all KERNEL_SRC=/lib/modules/5.18.6-rockchip64/build.....(bad exit status: 2) ERROR (dkms apport): binary package for anbox-binder: 1 not found Error! Bad return status for module build on kernel: 5.18.6-rockchip64 (aarch64) Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. [ OK ] update-initramfs: Generating /boot/initrd.img-5.18.6-rockchip64 update-initramfs: Converting to u-boot format Processing triggers for initramfs-tools (0.140ubuntu13) ... update-initramfs: Generating /boot/initrd.img-5.18.6-rockchip64 update-initramfs: Converting to u-boot format root@MX10-TvBox:~/kernel_update# Reboot is Ok. Thank again..! 0 Quote
Willy Moto Posted June 24, 2022 Posted June 24, 2022 @jock I have just tried to erase the eMMC, and then re-installed the latest Armbian 22.08 trunk build from scratch. 1) Unfortunately, it appears the latest edge Kernel 5.18.6 is unstable, at least for my TV box -- which is a H96 Max+ 4GB RAM/32GB EMMC model. Running rk3318-config and after reboot, the system produced some sort of error similar to previous screen, as in attached (I chose unlisted for led option). 2) By comparison, I fell back to previous Armbian 22.05 trunk build ( 5.15.35 current kernel ), on the same TV box. Running rk3318-config and after reboot, the system did not produce any error and running fine (I chose unlisted for led option). I guess it's either my H96 Max+ TV box sucks, or the 5.18.6 edge Kernel is pushing too far for my hardware configuration (ie. my TV box still sucks 🤣 ). Anyway, I fallback to the previous CSC Armbian version for now. Thanks. 1 Quote
MX10.AC2N Posted June 25, 2022 Posted June 25, 2022 (edited) Hi @jock This morning, my box is freezed.. With kernel 5.15.35 I never had any freeze despite non-stop use over several days (I remember working for more than 14 days, without worries..) I reboot, launch sudo nala update and my system freeze again.. Kernel 5.18.6 upgrade over 5.15.35 on Ubuntu desktop release (Emmc install) freeze on my RK3328.. ╭─ Updating Package List ─────────────────────────────────────────────────────── │No Change: https://cli.github.com/packages stable InRelease │ │No Change: http://ports.ubuntu.com jammy-security InRelease │ │No Change: http://ports.ubuntu.com jammy-updates InRelease │ │No Change: http://ports.ubuntu.com jammy-backports InRelease │ │No Change: http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRel…│ │No Change: https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu jammy InR…│ │No Change: http://deb.volian.org/volian scar InRelease │ │No Change: https://ryanfortner.github.io/box64-debs/debian ./ InRelease │ │No Change: http://ftp.tu-chemnitz.de/pub/linux/ubuntu-ports jammy InRelease │ │No Change: https://mirror.kumi.systems/ubuntu-ports jammy InRelease │ │No Change: http://armbian.systemonachip.net/apt jammy InRelease │ │Fetched 0 B in 7s (0 B/s) │ ╰─────────────────────────────────────────────────────────────────────────────── The following 31 packages can be upgraded: armbian-config (22.05.1) -> (22.05.3) armbian-firmware (22.05.1) -> (22.05.3) armbian-jammy-desktop-xfce (22.05.1) -> (22.05.3) armbian-zsh (22.05.1) -> (22.05.3) box64 (0.1.9+20220620.f78c5a2-1) -> (0.1.9+20220622.501ab2b-1) evince (42.1-3) -> (42.3-0ubuntu1) evince-common (42.1-3) -> (42.3-0ubuntu1) fonts-opensymbol (2:102.12+LibO7.3.3-0ubuntu0.22.04.1) -> (2:102.12+LibO7.3.4-0ubuntu0.22.04.1) gh (2.12.1) -> (2.13.0) gir1.2-gnomedesktop-3.0 (42.1-0ubuntu1) -> (42.2-0ubuntu1) gir1.2-nm-1.0 (1.36.6-0ubuntu1) -> (1.36.6-0ubuntu2) gnome-desktop3-data (42.1-0ubuntu1) -> (42.2-0ubuntu1) gnome-shell (42.1-0ubuntu0.1) -> (42.2-0ubuntu0.2) gnome-shell-common (42.1-0ubuntu0.1) -> (42.2-0ubuntu0.2) gvfs (1.48.1-4) -> (1.48.2-0ubuntu1) gvfs-backends (1.48.1-4) -> (1.48.2-0ubuntu1) gvfs-common (1.48.1-4) -> (1.48.2-0ubuntu1) gvfs-daemons (1.48.1-4) -> (1.48.2-0ubuntu1) gvfs-libs (1.48.1-4) -> (1.48.2-0ubuntu1) libevdocument3-4 (42.1-3) -> (42.3-0ubuntu1) libevview3-3 (42.1-3) -> (42.3-0ubuntu1) libgnome-desktop-3-19 (42.1-0ubuntu1) -> (42.2-0ubuntu1) libldap-2.5-0 (2.5.11+dfsg-1~exp1ubuntu3.1) -> (2.5.12+dfsg-0ubuntu0.22.04.1) libnm0 (1.36.6-0ubuntu1) -> (1.36.6-0ubuntu2) linux-dtb-current-rockchip64 (22.05.0-trunk) -> (22.05.3) linux-headers-current-rockchip64 (22.05.1) -> (22.05.3) linux-image-current-rockchip64 (22.05.0-trunk) -> (22.05.3) linux-libc-dev (22.05.1) -> (22.05.3) network-manager (1.36.6-0ubuntu1) -> (1.36.6-0ubuntu2) ruby-xmlrpc (0.3.2-1) -> (0.3.2-1ubuntu0.1) wpasupplicant (2:2.10-6ubuntu1) -> (2:2.10-6ubuntu2) There are headers updates, do we also need "apt-mark hold linux-headers-*-rockchip64" in addition of "apt-mark hold linux-image-*-rockchip64 linux-dtb-*-rockchip64" as mentioned in the first post Could you keep in https://users.armbian.com/jock/rk3318/upgrade/ 5.15.y kernel Thank Edit: dmesg output => https://pastebin.com/dWTmChfK Edited June 25, 2022 by MX10.AC2N 0 Quote
MX10.AC2N Posted June 25, 2022 Posted June 25, 2022 I can upgrade without launch desktop, just upgrade with SSH session The following packages were kept back: Nala was unable to determine why these were held: linux-dtb-current-rockchip64, linux-headers-current-rockchip64, linux-image-current-rockchip64 Do you want to continue? [Y/n] y ============================================================================================================== Installing ============================================================================================================== Package: Version: Size: ruby-webrick 1.7.0-3 52 kB ============================================================================================================== Upgrading ============================================================================================================== Package: Old Version: New Version: Size: armbian-config 22.05.1 22.05.3 127 kB armbian-firmware 22.05.1 22.05.3 8.1 MB armbian-jammy-desktop-xfce 22.05.1 22.05.3 16.3 MB armbian-zsh 22.05.1 22.05.3 2.4 MB box64 0.1.9+20220620.f78c5a2 0.1.9+20220622.501ab2b 2.0 MB -1 -1 evince 42.1-3 42.3-0ubuntu1 290 kB evince-common 42.1-3 42.3-0ubuntu1 130 kB fonts-opensymbol 2:102.12+LibO7.3.3-0ub 2:102.12+LibO7.3.4-0ub 101 kB untu0.22.04.1 untu0.22.04.1 gh 2.12.1 2.13.0 7.3 MB gir1.2-gnomedesktop-3.0 42.1-0ubuntu1 42.2-0ubuntu1 10 kB gir1.2-nm-1.0 1.36.6-0ubuntu1 1.36.6-0ubuntu2 84 kB gnome-desktop3-data 42.1-0ubuntu1 42.2-0ubuntu1 23 kB gnome-shell 42.1-0ubuntu0.1 42.2-0ubuntu0.2 859 kB gnome-shell-common 42.1-0ubuntu0.1 42.2-0ubuntu0.2 184 kB gvfs 1.48.1-4 1.48.2-0ubuntu1 114 kB gvfs-backends 1.48.1-4 1.48.2-0ubuntu1 368 kB gvfs-common 1.48.1-4 1.48.2-0ubuntu1 10 kB gvfs-daemons 1.48.1-4 1.48.2-0ubuntu1 116 kB gvfs-libs 1.48.1-4 1.48.2-0ubuntu1 110 kB libevdocument3-4 42.1-3 42.3-0ubuntu1 174 kB libevview3-3 42.1-3 42.3-0ubuntu1 139 kB libgnome-desktop-3-19 42.1-0ubuntu1 42.2-0ubuntu1 116 kB libldap-2.5-0 2.5.11+dfsg-1~exp1ubun 2.5.12+dfsg-0ubuntu0.2 181 kB tu3.1 2.04.1 libnm0 1.36.6-0ubuntu1 1.36.6-0ubuntu2 445 kB linux-libc-dev 22.05.1 22.05.3 1.2 MB network-manager 1.36.6-0ubuntu1 1.36.6-0ubuntu2 2.1 MB ruby-xmlrpc 0.3.2-1 0.3.2-1ubuntu0.1 25 kB wpasupplicant 2:2.10-6ubuntu1 2:2.10-6ubuntu2 1.5 MB ============================================================================================================== Summary ============================================================================================================== Install 1 Packages Upgrade 28 Packages Total download size 44.5 MB Disk space required 37 kB Do you want to continue? [Y/n] y ╭─ Downloading… ─────────────────────────────────────────────────────────────────────────────────────────────╮ │ Total Packages: 29/29 │ │ Last Completed: armbian-firmware_22.05.3_all.deb │ │ Time Remaining: 0:00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 44.5/44.5 MB • 1.5 MB/s │ ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭─ Updating Packages ────────────────────────────────────────────────────────────────────────────────────────╮ │Setting up: gvfs-common (1.48.2-0ubuntu1) │ │Setting up: ruby-xmlrpc (0.3.2-1ubuntu0.1) │ │Setting up: fonts-opensymbol (2:102.12+LibO7.3.4-0ubuntu0.22.04.1) │ │Setting up: libevview3-3:arm64 (42.3-0ubuntu1) │ │Setting up: network-manager (1.36.6-0ubuntu2) │ │Setting up: gir1.2-gnomedesktop-3.0:arm64 (42.2-0ubuntu1) │ │Setting up: gvfs-libs:arm64 (1.48.2-0ubuntu1) │ │Setting up: evince (42.3-0ubuntu1) │ │Setting up: gvfs-daemons (1.48.2-0ubuntu1) │ │Setting up: gvfs:arm64 (1.48.2-0ubuntu1) │ │Setting up: gvfs-backends (1.48.2-0ubuntu1) │ │Processing: triggers for mailcap (3.70+nmu1ubuntu1) │ │Processing: triggers for fontconfig (2.13.1-4.2ubuntu5) │ │Processing: triggers for desktop-file-utils (0.26-1ubuntu3) │ │Processing: triggers for hicolor-icon-theme (0.17-2) │ │Processing: triggers for libglib2.0-0:arm64 (2.72.1-1) │ │Processing: triggers for libc-bin (2.35-0ubuntu3) │ │Processing: triggers for man-db (2.10.2-1) │ │Processing: triggers for dbus (1.12.20-2ubuntu4) │ │Setting up: gnome-shell (42.2-0ubuntu0.2) │ │╭──────────────────────────────────────────────────────────────────────────────────────────────────────────╮│ ││✔ Running dpkg … ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 0:00:00 • 59/59││ │╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯│ ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Notice: The following packages require a reboot. network-manager gnome-shell Finished Successfully The reboot did not work, I had to unplug the box electrically. Then the start was able to be carried out correctly. But there is some BUG in dmesg output, see [ 41.723417] BUG: Bad page map in process date pte:7efffce56a3fc3 pmd:80000001434f003 [ 41.730496] addr:0000ffffb87c6000 vm_flags:00000071 anon_vma:0000000000000000 mapping:ffff000009f79098 index:5c6 [ 41.738424] file:locale-archive fault:filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage ... [ 41.836942] BUG: Bad rss-counter state mm:000000002e7e9236 type:MM_FILEPAGES val:1 complete dmesg output after upgrade => https://pastebin.com/Pra9U9bg 0 Quote
jock Posted June 25, 2022 Author Posted June 25, 2022 @Willy Moto @MX10.AC2N I have the suspect that the issue may be related to memory clocks. I thought it was safe to bump yo 667Mhz since DDR memories are commonly 667 or 800 MHz on our boards. I will provide a binary bootloader that could be overwritten to restore 333MHz memory clock, so we can at least isolate if the problem is the memory clock or the v5.18 kernel. I'm writing this message right from my box and it is working just fine, it's uptime is 2 days and has survived a full kernel compilation and various firefox sessions. A way to detect if there are memory issues can be installing memtester package via apt and running it with memtester 512M to at least verify that memory clocks are safe. @MX10.AC2N please also verify that you stiil have rk3318-box-led-conf3 overlay in /boot/armbianEnv.txt: that was essential to make your box stable. I have no reason to believe it has been removed, but in case it needs to be reinstated. 0 Quote
jock Posted June 25, 2022 Author Posted June 25, 2022 @MX10.AC2N @Willy Moto Ok I managed to compile just the idbloader that does the DDR initialization to 333 MHz. This is the binary with the 333MHz ddrbin: idbloader.img And you can install from the box itself on the eMMC (should be suitable for @MX10.AC2N, mmcblk2 should be the eMMC, but please verify!) installation doing: dd if=idbloader.img of=/dev/mmcblk2 bs=32k seek=1 && sync Or you can boot into multitool (this should be the case for @Willy Moto) and do the same via shell. Of course you need to transfer the file on multitool FAT partition, boot with multitool and then mount the FAT partition manually via shell. 0 Quote
MX10.AC2N Posted June 25, 2022 Posted June 25, 2022 Hi @jock My system freeze again after 1h30 with nothing run except just SSH session with htop.. I reboot and launch memtester 512M root@MX10-TvBox:~# cat /boot/armbianEnv.txt verbosity=10 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3318-box.dtb rootdev=UUID=0d128a4b-0147-40e3-a8ef-d0595c8c1837 rootfstype=ext4 console=both overlays=rk3318-box-cpu-hs rk3318-box-emmc-ddr rk3318-box-emmc-hs200 rk3318-box-led-conf3 rk3318-box-wlan-ext rk3328-opp-1.4ghz rk3328-opp-1.5ghz usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@MX10-TvBox:~# memtester 512M memtester version 4.5.1 (64-bit) Copyright (C) 2001-2020 Charles Cazabon. Licensed under the GNU General Public License version 2 (only). pagesize is 4096 pagesizemask is 0xfffffffffffff000 want 512MB (536870912 bytes) got 512MB (536870912 bytes), trying mlock ...locked. Loop 1: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : ok Bit Spread : ok Bit Flip : ok Walking Ones : ok Walking Zeroes : ok 8-bit Writes : ok 16-bit Writes : ok Loop 2: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : ok Bit Spread : ok Bit Flip : ok Walking Ones : ok Walking Zeroes : ok 8-bit Writes : ok 16-bit Writes : ok Loop 3: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : ok Bit Spread : ok Bit Flip : ok Walking Ones : ok Walking Zeroes : ok 8-bit Writes : ok 16-bit Writes : ok 0 Quote
jock Posted June 25, 2022 Author Posted June 25, 2022 @MX10.AC2N ok, you didn't tell if you installed the 333MHz idbloader or not... Also notice that you are overclocking the rk3328 with 1.4 and 1.5ghz speed bins... 0 Quote
MX10.AC2N Posted June 25, 2022 Posted June 25, 2022 @jock I not install the 333MHz idbloader.. And the overclocking for 1.4 and 1.5 ghz has no effect, I can't select this frequency in armbian-config only 1.3ghz has max value.. Memtester seem run correctly. 0 Quote
jock Posted June 25, 2022 Author Posted June 25, 2022 @MX10.AC2N Honestly I don't know what you exactly did with those commands... I see that you installed the upgrade packages manually with dpkg (it is better to use apt, as suggested), then you reinstalled back armbian rockchip64-current package via apt, as I see in your nala log: ... linux-dtb-current-rockchip64 (22.05.0-trunk) -> (22.05.3) linux-headers-current-rockchip64 (22.05.1) -> (22.05.3) linux-image-current-rockchip64 (22.05.0-trunk) -> (22.05.3) ... but this shows that you never really had the manual upgrades really installed. You should have 22.08.0-trunk installed, as stated during manual installation with dpkg): (Reading database ... 188694 files and directories currently installed.) Preparing to unpack armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb ... Unpacking armbian-bsp-cli-rk3318-box (22.08.0-trunk) over (22.05.0-trunk) ... Preparing to unpack linux-dtb-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-dtb-edge-rockchip64 (22.08.0-trunk) ... Selecting previously unselected package linux-headers-edge-rockchip64. Preparing to unpack linux-headers-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-headers-edge-rockchip64 (22.08.0-trunk) ... Preparing to unpack linux-image-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-image-edge-rockchip64 (22.08.0-trunk) ... Setting up armbian-bsp-cli-rk3318-box (22.08.0-trunk) ... Setting up linux-dtb-edge-rockchip64 (22.08.0-trunk) ... Setting up linux-headers-edge-rockchip64 (22.08.0-trunk) ... So now I don't really know what is your current setup. I published again v5.15 kernel packages: https://users.armbian.com/jock/rk3318/upgrade/v5.15/ but, if this does not fix, consider to restore a backup if you did any. 0 Quote
MX10.AC2N Posted June 26, 2022 Posted June 26, 2022 Hi @jock I don't quite understand what happened. I just installed the .deb files (with the "dpkg -i *.deb" command) on top of the ubuntu desktop kernel 5.15.35 release. Nothing more, maybe the problem is that I Tried to install Anbox before (without success by the way).. This morning I ran the command "sudo apt reinstall ./*.deb" root@192.168.1.200's password: ____ _ ____________ _ ___ ____ | _ \| |/ /___ /___ // |( _ ) | __ ) _____ __ | |_) | ' / |_ \ |_ \| |/ _ \ | _ \ / _ \ \/ / | _ <| . \ ___) |__) | | (_) | | |_) | (_) > < |_| \_\_|\_\____/____/|_|\___/ |____/ \___/_/\_\ Welcome to Armbian 22.08.0-trunk Jammy with Linux 5.18.6-rockchip64 No end-user support: built from trunk System load: 79% Up time: 1 min Memory usage: 7% of 3.88G IP: 192.168.1.200 CPU temp: 50°C Usage of /: 23% of 29G [ General system configuration (beta): armbian-config ] Last login: Sat Jun 25 09:59:54 2022 from 192.168.1.230 root@MX10-TvBox:~/kernel_update# sudo apt reinstall ./*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'armbian-bsp-cli-rk3318-box' instead of './armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb' Note, selecting 'linux-dtb-edge-rockchip64' instead of './linux-dtb-edge-rockchip64_22.08.0-trunk_arm64.deb' Note, selecting 'linux-headers-edge-rockchip64' instead of './linux-headers-edge-rockchip64_22.08.0-trunk_arm64.deb' Note, selecting 'linux-image-edge-rockchip64' instead of './linux-image-edge-rockchip64_22.08.0-trunk_arm64.deb' 0 upgraded, 0 newly installed, 4 reinstalled, 0 to remove and 3 not upgraded. Need to get 0 B/60.7 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 /root/kernel_update/armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb armbian-bsp-cli-rk3318-box arm64 22.08.0-trunk [424 kB] Get:2 /root/kernel_update/linux-dtb-edge-rockchip64_22.08.0-trunk_arm64.deb linux-dtb-edge-rockchip64 arm64 22.08.0-trunk [432 kB] Get:3 /root/kernel_update/linux-headers-edge-rockchip64_22.08.0-trunk_arm64.deb linux-headers-edge-rockchip64 arm64 22.08.0-trunk [12.3 MB] Get:4 /root/kernel_update/linux-image-edge-rockchip64_22.08.0-trunk_arm64.deb linux-image-edge-rockchip64 arm64 22.08.0-trunk [47.6 MB] (Reading database ... 218343 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb ... Unpacking armbian-bsp-cli-rk3318-box (22.08.0-trunk) over (22.08.0-trunk) ... Preparing to unpack .../linux-dtb-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-dtb-edge-rockchip64 (22.08.0-trunk) over (22.08.0-trunk) ... Preparing to unpack .../linux-headers-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-headers-edge-rockchip64 (22.08.0-trunk) over (22.08.0-trunk) ... Preparing to unpack .../linux-image-edge-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-image-edge-rockchip64 (22.08.0-trunk) over (22.08.0-trunk) ... Setting up linux-dtb-edge-rockchip64 (22.08.0-trunk) ... Setting up armbian-bsp-cli-rk3318-box (22.08.0-trunk) ... Setting up linux-image-edge-rockchip64 (22.08.0-trunk) ... * dkms: running auto installation service for kernel 5.18.6-rockchip64 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j4 KERNELRELEASE=5.18.6-rockchip64 all KERNEL_SRC=/lib/modules/5.18.6-rockchip64/build....(bad exit status: 2) ERROR (dkms apport): binary package for anbox-ashmem: 1 not found Error! Bad return status for module build on kernel: 5.18.6-rockchip64 (aarch64) Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j4 KERNELRELEASE=5.18.6-rockchip64 all KERNEL_SRC=/lib/modules/5.18.6-rockchip64/build.....(bad exit status: 2) ERROR (dkms apport): binary package for anbox-binder: 1 not found Error! Bad return status for module build on kernel: 5.18.6-rockchip64 (aarch64) Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. [ OK ] update-initramfs: Generating /boot/initrd.img-5.18.6-rockchip64 update-initramfs: Converting to u-boot format Setting up linux-headers-edge-rockchip64 (22.08.0-trunk) ... Compiling headers - please wait ... during IPA pass: inline scripts/dtc/treesource.c: In function ‘write_tree_source_node’: scripts/dtc/treesource.c:242:33: internal compiler error: Segmentation fault 242 | write_propval_int(f, p, chunk_len, 4); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0xaf83f7 internal_error(char const*, ...) ???:0 0xde1a6f insert_decl_map(copy_body_data*, tree_node*, tree_node*) ???:0 0xdea787 remap_type(tree_node*, copy_body_data*) ???:0 0xc22423 walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*), void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*, tree_node* (*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*), void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*)) ???:0 0xe0826f walk_gimple_op(gimple*, tree_node* (*)(tree_node**, int*, void*), walk_stmt_info*) ???:0 0xe245fb optimize_inline_calls(tree_node*) ???:0 0xe22ab7 inline_transform(cgraph_node*) ???:0 0x123e65f execute_all_ipa_transforms(bool) ???:0 0x12015ab cgraph_node::expand() ???:0 0x11b97db symbol_table::compile() ???:0 0x11b6983 symbol_table::finalize_compilation_unit() ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions. make[1]: *** [scripts/Makefile.host:112: scripts/dtc/treesource.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [Makefile:1397: scripts_dtc] Error 2 Processing triggers for initramfs-tools (0.140ubuntu13) ... update-initramfs: Generating /boot/initrd.img-5.18.6-rockchip64 update-initramfs: Converting to u-boot format N: Download is performed unsandboxed as root as file '/root/kernel_update/armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) root@MX10-TvBox:~/kernel_update# I'm probably going to have to start from scratch but if you have an idea to put everything in order I'm a taker.. Thank you again for all this work accomplished.. 0 Quote
jock Posted June 26, 2022 Author Posted June 26, 2022 @MX10.AC2N There seems to be this anbox driver module that is installed as a dkms module and it fails the module rebuilding. Now I don't know if it is due to some missing bits in kernel headers or the anbox driver module does something bad on itself, but you should try first to remove it from the dkms list (this guide may be helpfui) and then reinstall the packages; they should not give you errors. But yet, it looks like from the apt output that 22.08.0-trunk packages ARE already installed, so I don't understand the previous logs. If your box is still unstable, you may try to install the 333MHz idbloader, if you are still unstable, then you need to revert back to v5.15 because something is broken elsewhere. BTW, from memtester output, it looks to me that the DDR is not suffering the 667MHz clock, at least it is not completely broken but indeed there can be more subtle problems. You may also revert back to kernel v5.15 and keep the 667MHz loader, installing back only linux-image-* and linux-headers-* packages, but your mileage may vary. 0 Quote
MX10.AC2N Posted June 26, 2022 Posted June 26, 2022 (edited) Well I switched to 5.15.y But I still get errors when compiling Headers root@MX10-TvBox:~/kernel_update/5.15.y# apt install ./*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'linux-dtb-current-rockchip64' instead of './linux-dtb-current-rockchip64_22.08.0-trunk_arm64.deb' Note, selecting 'linux-headers-current-rockchip64' instead of './linux-headers-current-rockchip64_22.08.0-trunk_arm64.deb' Note, selecting 'linux-image-current-rockchip64' instead of './linux-image-current-rockchip64_22.08.0-trunk_arm64.deb' Note, selecting 'linux-u-boot-rk3318-box-current' instead of './linux-u-boot-current-rk3318-box_22.08.0-trunk_arm64.deb' The following held packages will be changed: linux-dtb-current-rockchip64 linux-headers-current-rockchip64 linux-image-current-rockchip64 The following packages will be upgraded: linux-dtb-current-rockchip64 linux-headers-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-rk3318-box-current 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/59.5 MB of archives. After this operation, 4,458 kB disk space will be freed. Do you want to continue? [Y/n] Y Get:1 /root/kernel_update/5.15.y/linux-dtb-current-rockchip64_22.08.0-trunk_arm64.deb linux-dtb-current-rockchip64 arm64 22.08.0-trunk [379 kB] Get:2 /root/kernel_update/5.15.y/linux-headers-current-rockchip64_22.08.0-trunk_arm64.deb linux-headers-current-rockchip64 arm64 22.08.0-trunk [12.0 MB] Get:3 /root/kernel_update/5.15.y/linux-image-current-rockchip64_22.08.0-trunk_arm64.deb linux-image-current-rockchip64 arm64 22.08.0-trunk [46.9 MB] Get:4 /root/kernel_update/5.15.y/linux-u-boot-current-rk3318-box_22.08.0-trunk_arm64.deb linux-u-boot-rk3318-box-current arm64 22.08.0-trunk [319 kB] (Reading database ... 218343 files and directories currently installed.) Preparing to unpack .../linux-dtb-current-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-dtb-current-rockchip64 (22.08.0-trunk) over (22.05.0-trunk) ... Preparing to unpack .../linux-headers-current-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-headers-current-rockchip64 (22.08.0-trunk) over (22.05.1) ... Preparing to unpack .../linux-image-current-rockchip64_22.08.0-trunk_arm64.deb ... Unpacking linux-image-current-rockchip64 (22.08.0-trunk) over (22.05.0-trunk) ... Preparing to unpack .../linux-u-boot-current-rk3318-box_22.08.0-trunk_arm64.deb ... Unpacking linux-u-boot-rk3318-box-current (22.08.0-trunk) over (22.05.0-trunk) ... Setting up linux-u-boot-rk3318-box-current (22.08.0-trunk) ... Setting up linux-image-current-rockchip64 (22.08.0-trunk) ... * dkms: running auto installation service for kernel 5.15.49-rockchip64 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j4 KERNELRELEASE=5.15.49-rockchip64 all KERNEL_SRC=/lib/modules/5.15.49-rockchip64/build...... cleaning build area... ashmem_linux.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.49-rockchip64/updates/dkms/ depmod........ Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j4 KERNELRELEASE=5.15.49-rockchip64 all KERNEL_SRC=/lib/modules/5.15.49-rockchip64/build.....(bad exit status: 2) ERROR (dkms apport): binary package for anbox-binder: 1 not found Error! Bad return status for module build on kernel: 5.15.49-rockchip64 (aarch64) Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. [ OK ] update-initramfs: Generating /boot/initrd.img-5.15.49-rockchip64 update-initramfs: Converting to u-boot format Remove unused generated file: /boot/initrd.img-5.15.35-rockchip64 Remove unused generated file: /boot/uInitrd-5.15.35-rockchip64 Setting up linux-dtb-current-rockchip64 (22.08.0-trunk) ... Setting up linux-headers-current-rockchip64 (22.08.0-trunk) ... Compiling headers - please wait ... during GIMPLE pass: pre scripts/dtc/checks.c: In function ‘check_pci_device_reg’: scripts/dtc/checks.c:882:13: internal compiler error: Segmentation fault 882 | static void check_pci_device_reg(struct check *c, struct dt_info *dti, struct node *node) | ^~~~~~~~~~~~~~~~~~~~ 0xaf83f7 internal_error(char const*, ...) ???:0 0xe637f3 compute_may_aliases() ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions. make[1]: *** [scripts/Makefile.host:112: scripts/dtc/checks.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [Makefile:1430: scripts_dtc] Error 2 N: Download is performed unsandboxed as root as file '/root/kernel_update/5.15.y/linux-dtb-current-rockchip64_22.08.0-trunk_arm64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) The "reboot" command fails.. I had to electrically unplug the box twice for it to restart.. login as: root root@192.168.1.200's password: ____ _ ____________ _ ___ ____ | _ \| |/ /___ /___ // |( _ ) | __ ) _____ __ | |_) | ' / |_ \ |_ \| |/ _ \ | _ \ / _ \ \/ / | _ <| . \ ___) |__) | | (_) | | |_) | (_) > < |_| \_\_|\_\____/____/|_|\___/ |____/ \___/_/\_\ Welcome to Armbian 22.08.0-trunk Jammy with Linux 5.15.49-rockchip64 No end-user support: built from trunk System load: 78% Up time: 1 min Memory usage: 6% of 3.88G IP: 192.168.1.200 CPU temp: 49°C Usage of /: 23% of 29G [ General system configuration (beta): armbian-config ] Last login: Sun Jun 26 10:51:10 2022 from 192.168.1.230 root@MX10-TvBox:~# edit : And damn my system freezes again.. Reboot and launch "apt upgrade" =>The following packages will be upgraded: armbian-config armbian-firmware armbian-zsh box64 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Then remove dkms anbox module, but I note all the same that the ashmen module could be installed with this kernel.. (interesting..) the binder module on the other hand is in error. root@MX10-TvBox:/boot# dkms status anbox-ashmem/1, 5.15.49-rockchip64, aarch64: installed anbox-binder/1: added root@MX10-TvBox:/boot# dkms remove anbox-ashmem/1 Module anbox-ashmem-1 for kernel 5.15.49-rockchip64 (aarch64). Before uninstall, this module version was ACTIVE on this kernel. ashmem_linux.ko.xz: - Uninstallation - Deleting from: /lib/modules/5.15.49-rockchip64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod.......... Deleting module anbox-ashmem-1 completely from the DKMS tree. root@MX10-TvBox:/boot# dkms remove anbox-binder/1 Error! There is no instance of anbox-binder 1 for kernel 5.15.49-rockchip64 (aarch64) located in the DKMS tree. root@MX10-TvBox:/boot# dkms remove anbox-binder/1 --all Deleting module anbox-binder-1 completely from the DKMS tree. root@MX10-TvBox:/boot# dkms status root@MX10-TvBox:/boot# My box has been running for 20 minutes now, hoping that it is stable.. I also remove overlays for 1.4ghz and 1.5ghz.. But why can't I set to 1.5ghz when I have an RK3328..? Edited June 26, 2022 by MX10.AC2N 0 Quote
jock Posted June 26, 2022 Author Posted June 26, 2022 @MX10.AC2NI see that you installed have several dkms modules, plus gcc is giving a segmentation fault and suggests to report the bug; can't say anything more, everything here seems not related at all with armbian and upgrade packages, the upgrade just triggered the dkms modules rebuilding, but the root cause does not seem to be related with the upgrade packages. The reason of the instabilities of the board should be investigated though... 0 Quote
zero48 Posted June 26, 2022 Posted June 26, 2022 On 6/23/2022 at 11:08 AM, paradigman said: I have attached the data sheet for the chip. The thing I wrote above really works is that you can connect another I2C device to the two appropriate pins on the chip. However, this is not enough, you need to use the OpenVFD driver (in place compile) and modify it in small dips to be able to send commands to the other device. FD6551_Datasheet.pdf 687.93 kB · 1 download Thanks for this. 0 Quote
MX10.AC2N Posted June 26, 2022 Posted June 26, 2022 (edited) Come on, this time I restarted on the SD card which had served me during the installation on the EMMC, Kernel 5.15.35 and where I had not yet tried the installation of Anbox. So I try the upgrade around 5.18.6 and again I have two errors first with Headers and then with armbian-bsp-cli-rk3318-box_22.08.0-trunk_arm64.deb Setting up linux-headers-edge-rockchip64 (22.08.0-trunk) ... Compiling headers - please wait ... scripts/sign-file.c: In function ‘display_openssl_errors’: scripts/sign-file.c:89:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 89 | while ((e = ERR_get_error_line(&file, &line))) { | ^~~~~ In file included from scripts/sign-file.c:29: /usr/include/openssl/err.h:411:15: note: declared here 411 | unsigned long ERR_get_error_line(const char **file, int *line); | ^~~~~~~~~~~~~~~~~~ scripts/sign-file.c: In function ‘drain_openssl_errors’: scripts/sign-file.c:102:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 102 | while (ERR_get_error_line(&file, &line)) {} | ^~~~~ In file included from scripts/sign-file.c:29: /usr/include/openssl/err.h:411:15: note: declared here 411 | unsigned long ERR_get_error_line(const char **file, int *line); | ^~~~~~~~~~~~~~~~~~ scripts/sign-file.c: In function ‘read_private_key’: scripts/sign-file.c:142:17: warning: ‘ENGINE_load_builtin_engines’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 142 | ENGINE_load_builtin_engines(); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:358:28: note: declared here 358 | OSSL_DEPRECATEDIN_3_0 void ENGINE_load_builtin_engines(void); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ scripts/sign-file.c:144:17: warning: ‘ENGINE_by_id’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 144 | e = ENGINE_by_id("pkcs11"); | ^ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:336:31: note: declared here 336 | OSSL_DEPRECATEDIN_3_0 ENGINE *ENGINE_by_id(const char *id); | ^~~~~~~~~~~~ scripts/sign-file.c:146:17: warning: ‘ENGINE_init’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 146 | if (ENGINE_init(e)) | ^~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:620:27: note: declared here 620 | OSSL_DEPRECATEDIN_3_0 int ENGINE_init(ENGINE *e); | ^~~~~~~~~~~ scripts/sign-file.c:151:25: warning: ‘ENGINE_ctrl_cmd_string’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 151 | ERR(!ENGINE_ctrl_cmd_string(e, "PIN", key_pass, 0), | ^~~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:479:5: note: declared here 479 | int ENGINE_ctrl_cmd_string(ENGINE *e, const char *cmd_name, const char *arg, | ^~~~~~~~~~~~~~~~~~~~~~ scripts/sign-file.c:153:17: warning: ‘ENGINE_load_private_key’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 153 | private_key = ENGINE_load_private_key(e, private_key_name, | ^~~~~~~~~~~ In file included from scripts/sign-file.c:30: /usr/include/openssl/engine.h:638:11: note: declared here 638 | EVP_PKEY *ENGINE_load_private_key(ENGINE *e, const char *key_id, | ^~~~~~~~~~~~~~~~~~~~~~~ after reboot I try again install linux-headers Setting up linux-headers-edge-rockchip64 (22.08.0-trunk) ... Compiling headers - please wait ... during GIMPLE pass: einline scripts/dtc/treesource.c: In function ‘write_propval’: scripts/dtc/treesource.c:270:9: internal compiler error: Segmentation fault 270 | fprintf(f, "\n"); | ^~~~~~~~~~~~~~~~ 0xaf83f7 internal_error(char const*, ...) ???:0 0xde1a6f insert_decl_map(copy_body_data*, tree_node*, tree_node*) ???:0 0xe245fb optimize_inline_calls(tree_node*) ???:0 0xde8f77 early_inliner(function*) ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions. make[1]: *** [scripts/Makefile.host:112: scripts/dtc/treesource.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [Makefile:1397: scripts_dtc] Error 2 Log ended: 2022-06-26 17:53:23 and I reinstall on my Emmc but just after complete flash, the system freeze again..(maybe caused by my sd-card cause it's A2) So I reboot on Emmc with 5.18.6, start desktop launch firefox and go on youtube but when I launch a video firefox is killed.. The system run from 40min. But I think that a freeze will soon happen .. How can I know what is problematic, is there a log file that can help or software maybe ..? armbianmonitor -u => http://ix.io/40X2 Edited June 26, 2022 by MX10.AC2N 0 Quote
jock Posted June 26, 2022 Author Posted June 26, 2022 @MX10.AC2N well, despite the openssl warnings, gcc is crashing with a segmentation fault... gcc comes with the ubuntu jammy, so if it crashes it's not a mistake of the update. Firefox being killed... don't know, maybe is due to unstable system, I don't see anything suspect in the logs you sent, either there are no segmentation faults and no out-of-memory process kills. May I suggest you to use 1.1Ghz device in rk3318-config and see if system works better? 0 Quote
MX10.AC2N Posted June 26, 2022 Posted June 26, 2022 Thank @jock The system run from 2h15 now without freeze with just ssh connection and htop launched.. I'll wait until tomorrow morning to see if the system is still running.. For operation under 1.1ghz it would not really be an update since it worked without any particular problem in 1.3ghz with kernel 5.15.35 0 Quote
paradigman Posted June 27, 2022 Posted June 27, 2022 Sorry to bring up this topic again, but today almost every h96 max box is produced with this new 2734c wireless chip. I've tried everything that is possible with software, but can't connect to the wifi network. I think it would be necessary to make a new overlay specifically for this. I'm not a hardware expert, could any of you make this? Maybe you don't need a box like this, since other images were already modified in 2019, maybe you can take it out of it: https://forum.freaktab.com/node/789155 0 Quote
MX10.AC2N Posted June 27, 2022 Posted June 27, 2022 Hi @jock After 3h47 of operation, system freezed again. Reboot and there is some update Start-Date: 2022-06-27 08:08:26 Commandline: apt upgrade Upgrade: udev:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3), libnss-myhostname:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3), libpam-systemd:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3), libsystemd0:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3), systemd:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3), libudev1:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3), systemd-sysv:arm64 (249.11-0ubuntu3.1, 249.11-0ubuntu3.3) End-Date: 2022-06-27 08:09:43 Wait and see.. If the system freezes again, I'll try 1.1 GHz but the RK3328 is designed to run at 1.4 GHz and can accept 1.5 GHz normally. Maybe I need to change something in dtb as I can add 1.4ghz and 1.5ghz overlays but in armbian-config I can't select those values only 1296Mhz has maximum value. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.