July 2, 20233 yr Rk3588 boards now share the same linuxfamily as rk3568 and rk3566 boards. It means rockchip-rk3588 kernel won't get update longer. Here is some steps for migration: sudo sed -i 's/LINUXFAMILY=rockchip-rk3588/LINUXFAMILY=rk35xx/g' /etc/armbian-release sudo apt update sudo apt install linux-image-legacy-rk35xx linux-dtb-legacy-rk35xx linux-headers-legacy-rk35xx sudo apt remove linux-image-legacy-rockchip-rk3588 linux-dtb-legacy-rockchip-rk3588 linux-headers-legacy-rockchip-rk3588 NOTE: The steps are currently for beta branch only. Don't try on stable branch.
July 4, 20233 yr So what are the implications for this decision? Can we be optimistic that if RK3566/68 SOC's are to get mainline kernel support then the RK3588 will also get it? Or are we looking at another SOC that will essentially remain stuck in limbo because of a stalled manufacturer kernel development?
July 4, 20233 yr On 7/2/2023 at 10:46 PM, Efe Çetin said: Here is some steps for migration: [...] Does this work for a 23.02 system ? I just gave it a try and - although I didn't get any errors from apt - the system didn't boot afterwards. EDIT: forgot to mention this was done on a OrangePi 5 system (installed with Ubuntu Jammy 23.02 release/image). Edited July 4, 20233 yr by mitu
July 4, 20233 yr I had the same problem with a Jammy setup on a 5 plus. Does the image build "./compile.sh" already include the new kernel setup, or is there even a prebuild image to download?
July 4, 20233 yr Author @SvOlli it includes new rk35xx kernel @compent rk3588 is aldready supported in mainline. I think this decision is to manage kernels easily. (Rk3588 and rk35xx kernels was using the same repo) @mitu i followed steps for my old beta trunk image and it worked. Let me check what's wrong with 23.02
July 5, 20233 yr Author Sorry for not booting systems. I forgot that packages on stable repo haven't been updated yet
July 14, 20233 yr Just downloaded Armbian_23.5.5_Orangepi5-plus_jammy_legacy_5.10.160.img.xz and installed it to an sdcard to boot up on my Opi5+ and monitored with serial console, but the system wouldn't boot because of a koops. this happened with every boot. Quote [ 10.945354] systemd[1]: Caught <SEGV>, core dump failed (child 373, code=killed, status=11/SEGV). [ 10.945416] systemd[1]: Freezing execution. [ 29.088950] BUG: spinlock bad magic on CPU#4, kworker/4:2/144 [ 29.089117] Internal error: Oops: 96000004 [#1] SMP [ 29.090063] Modules linked in: ip_tables ipv6 pgdrv panfrost gpu_sched [ 29.090689] CPU: 4 PID: 144 Comm: kworker/4:2 Not tainted 5.10.160-rk35xx #1 [ 29.091323] Hardware name: Orange Pi 5 Plus (DT) [ 29.091761] Workqueue: events hdmirx_delayed_work_hotplug [ 29.092265] pstate: 60c00089 (nZCv daIf +PAN +UAO -TCO BTYPE=--) [ 29.092817] pc : spin_bug+0x70/0xb4 [ 29.093149] lr : spin_bug+0x68/0xb4 [ 29.093472] sp : ffff80000ad03200 [ 29.093782] x29: ffff80000ad03200 x28: ffff0001057a53c0 [ 29.094271] x27: 0000000000000000 x26: ffff8000089b5e68 [ 29.094756] x25: 0000000000000000 x24: ffff0001057a5388 [ 29.095241] x23: ffff80000ad03480 x22: ffff8000094b634c [ 29.095725] x21: ffff800009829008 x20: 0000000200000000 [ 29.096211] x19: ffff0001011d2610 x18: 0000000000000000 [ 29.096697] x17: 0000000000000000 x16: 0000000000000000 [ 29.097182] x15: 000000000000000a x14: 0000000000015b76 [ 29.097668] x13: 0000000000000006 x12: ffffffffffffffff [ 29.098155] x11: 0000000000000010 x10: ffff80008ad02ed7 [ 29.098641] x9 : ffff8000080de864 x8 : ffff80000ad02ef8 [ 29.099126] x7 : 0000000000000000 x6 : ffff80000a8800e0 [ 29.099610] x5 : 00000000000affa8 x4 : 000000000000000d [ 29.100095] x3 : 0000000000000000 x2 : 0000000000000000 [ 29.100580] x1 : ffff000104da0f40 x0 : 0000000000000031 [ 29.101067] Call trace: [ 29.101304] spin_bug+0x70/0xb4 [ 29.101603] do_raw_spin_lock+0x40/0xdc [ 29.101959] _raw_spin_lock_irqsave+0x2c/0x40 [ 29.102361] prepare_to_wait+0x3c/0x88 [ 29.102717] rpm_resume+0x1bc/0x430 [ 29.103049] __spi_pump_messages+0x1ac/0x57c [ 29.103447] __spi_sync+0x178/0x1e4 [ 29.103773] spi_sync+0x38/0x5c [ 29.104067] spi_write_then_read+0x128/0x1ac [ 29.104469] rk806_spi_bus_read+0x60/0x90 [ 29.104848] _regmap_raw_read+0x108/0x1a8 [ 29.105224] _regmap_bus_read+0x4c/0x84 [ 29.105577] _regmap_read+0xbc/0x138 [ 29.105918] regmap_read+0x54/0x80 [ 29.106236] regmap_field_read+0x40/0x88 [ 29.106603] rk806_field_read+0x38/0x68 [ 29.106961] rk806_regulator_is_enabled_regmap+0x9c/0xb0 [ 29.107447] _regulator_is_enabled+0x3c/0x50 [ 29.107849] _regulator_do_set_voltage+0xd0/0x45c [ 29.108285] regulator_set_voltage_rdev+0x134/0x1fc [ 29.108732] regulator_do_balance_voltage+0x94/0x390 [ 29.109189] regulator_balance_voltage+0x7c/0x80 [ 29.109612] regulator_set_voltage_unlocked+0xcc/0xf0 [ 29.110071] regulator_set_voltage+0x58/0x9c [ 29.110476] rockchip_dmcfreq_set_volt+0x80/0xe4 [ 29.110901] rockchip_dmcfreq_opp_helper+0x1d4/0x408 [ 29.111362] dev_pm_opp_set_rate+0x38c/0x4e0 [ 29.111762] rockchip_dmcfreq_target+0x88/0xb4 [ 29.112177] devfreq_set_target+0x88/0x13c [ 29.112552] update_devfreq+0x88/0xc4 [ 29.112894] rockchip_dmcfreq_system_status_notifier+0x1b4/0x1d8 [ 29.113439] notifier_call_chain+0x74/0x94 [ 29.113815] blocking_notifier_call_chain+0x4c/0x78 [ 29.114264] rockchip_system_status_notifier_call_chain.isra.0+0x28/0x34 [ 29.114877] rockchip_set_system_status+0x68/0xc4 [ 29.115314] hdmirx_delayed_work_hotplug+0xf4/0x2dc [ 29.115761] process_one_work+0x1e0/0x298 [ 29.116134] process_scheduled_works+0x4c/0x50 [ 29.116544] worker_thread+0x1f4/0x278 [ 29.116899] kthread+0xf4/0x104 [ 29.117194] ret_from_fork+0x10/0x30 [ 29.117530] [ 29.117530] PC: 0xffff8000080d6958: Using the Orangepi5plus_1.0.6_ubuntu_jammy_server_linux5.10.110.img version, I'm able to boot successfully. I copied the boot files from the OPi5+ img onto my sdcard with Armbian, and made the requisite changes so that the boot environment was pointing to Opi kernel/initrd/dtb, and as expected, was able to boot into the official armbian environment, so i could validate what kernel was installed on the image i downloaded, and it was "linux-image-legacy-rk35xx": Quote $ dpkg -l | grep linux-image ii linux-image-legacy-rk35xx 23.08.0-trunk--5.10.160-S2c1d-Df1ec-P0000-C2d32Hfe66-HK01ba-Vc222-Be693 arm64 Armbian Linux legacy kernel image version "5.10.160" git revision "2c1dcd460b945317d5f0fb9f929b01f46f4e2ca9" codename "Dare mighty things" drivers hash "f1ec859bd80e169d" patches hash "0000000000000000" .config hash "2d32937fec29a52a" .config hook hash "fe661159ee64825e" variables hash "" framework bash hash "e693c7b4dae91f2e" So there's something broken on that build for Opi5+ - at least it's failing on my board. Happy to provide more info, run test builds, etc.
September 4, 20233 yr I upgraded to 23.8.1, and it appears that rk35xx is available in the stable branch. Is it safe to migrate? Welcome to Armbian 23.8.1 Bookworm with Linux 5.10.110-rockchip-rk3588 System load: 1% Up time: 8 min Memory usage: 7% of 15.35G IP: 192.168.1.2 CPU temp: 38°C Usage of /: 19% of 236G Tip of the day: Submit your desktop wallpaper creation! https://forum.armbian.com/topic/29433-armbian-desktop-wallpaper-contest/ Last login: Mon Sep 4 08:40:53 2023 from 192.168.1.30 rob@orangepi5:~$ apt-cache search rk35xx linux-dtb-edge-rk35xx - Armbian Linux DTB, version 6.1.11-rk35xx edge linux-dtb-legacy-rk35xx - Armbian Linux legacy DTBs in /boot/dtb-5.10.160-legacy-rk35xx linux-headers-edge-rk35xx - Linux kernel headers for 6.1.11-rk35xx on arm64 edge linux-headers-legacy-rk35xx - Armbian Linux legacy headers 5.10.160-legacy-rk35xx linux-image-edge-rk35xx - Linux kernel, armbian version 6.1.11-rk35xx edge linux-image-legacy-rk35xx - Armbian Linux legacy kernel image 5.10.160-legacy-rk35xx linux-source-6.1.11-edge-rk35xx - This package provides the source code for the Linux kernel 6.1.11
September 8, 20233 yr @Efe Çetin Thanks, I successfully migrated to rk35xx with the stable branch. Maybe you want to update the note in the first post in this thread?
October 8, 20233 yr It does boot up and graphical user interface works, but I now get segmentation fault with any video playback with ffplay or mpv (using ppa:liujianfeng1994 repo). So anyone switching kernels should be aware that there might be video playback issues.
April 24, 20242 yr Quote It does boot up and graphical user interface works, but I now get segmentation fault with any video playback with ffplay or mpv (using ppa:liujianfeng1994 repo). So anyone switching kernels should be aware that there might be video playback issues. Seems this issue has been fixed, I am able to use the new kernel now with video playback. I did not do anything different...just update/upgrade.
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.