Search the Community

Hello, I have a Radxa Rock 4se with an RK3399 Rockchip on board. On my host system I run virtualbox with Ubuntu 22.04. I have build succesfully an armbian configuration for the Rock 4se with an edge kernel(6.6.xx) and it runs perfectly on my board, which also has an Raspbbery Pi camera v2 with the IMX219 which also runs okay. However know I would like to make some adjustments to the imx219.c driver, I know that in the cache directory the linux kernel is available. Can I adjust the imx219.c driver in the cache/sources/linux-kernel-worktree/6.6__rockchip64__arm64 and recompile only the kernel, without that the kernel completly is recompiled only difference so it will generate a new imx219.ko file. Kind regards

I changed this in the dt and got more than double the speeds from my Samsung U3 SD card: However I have no idea what the process of getting this into the kernel source looks like. --- rk3399-rock-pi-4b.dts 2023-10-04 15:36:05.031221270 +0200 +++ rk3399-rock-pi-4b-mod.dts 2023-10-04 00:34:15.773888431 +0200 @@ -342,6 +342,7 @@ disable-wp; pinctrl-names = "default"; pinctrl-0 = <0x26 0x27 0x28 0x29>; + sd-uhs-sdr104; phandle = <0xce>; };

I plan to upgrade my NVMe memory. I currently boot off it - I set this up using the Armbian installer. Before doing the upgrade I'd like to know that I can boot off my SD card, should anything go wrong with the upgrade. But I'm unsure how to disable the NVMe boot sequence (which I think is SPI flash --> eMMC/mmcboot --> NVMe). If I insert my Armbian SD card, the system doesn't start. I've tried shorting pins 23/25 to disable the SPI flash but this has no effect. I am assuming that I can complete the upgrade by amending armbianEnv.txt to make the 'rootdev=UUID' line point to the new NVMe's UID? Is there a known solution to my query?

Опубликовано: только что · Hidden - This content must be approved before it can be edited. HOT NEWS!!! With Armbian Armbian 23.02.2 Jammy with Linux 5.15.93-rockchip64 on (rockpi-4b plus v.1.72) Add (do it elso on all booting fevices = MMC, NVME, MPD, SD) the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot If you shorted 23-25 pins in 1.) then: disconnect them after the ROCK Pi 4 fully boot's enable spi-nor by executing (as root): echo spi1.0 > /sys/bus/spi/drivers/spi-nor/bind verify that the SPI mtd interface is enabled by running ls /dev/mtdblock0 if the last command does not list any file then something went wrong between 3.) and 5.) Run sudo nand-sata-install choose option: "Boot from SPI or MPD - system on SATA, USB or NVMe" choose NVMe partition, eg. /dev/nvme0n1p1 accept erasing of the choosen partition with "Yes" choose fs type (tested with ext4) wait a few minutes for rootfs transfer to chosen partition choose writing SPI bootloader with "Yes" confirm that you want to flash it with "Yes" wait ~60 seconds for writing choose Exit IN /boot/armbianEnv.txt choose your needing booting UUID, use command: sudo blkid it look like this: /dev/nvme0n1p1: UUID="ca927a6a-b2f0-4184-ab0f-5719e34172db" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="19354531-01" /dev/mmcblk1p1: LABEL="armbi_root" UUID="cfd67d21-5d00-4032-823e-b68830ca3543" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="22fbd54f-01" /dev/zram0: UUID="de7c0efa-e9cc-11ed-885d-c3fae5811b14" TYPE="swap" /dev/zram1: LABEL="log2ram" UUID="906b40da-e43c-4971-bff5-e9e402eada77" BLOCK_SIZE="4096" TYPE="ext4" in /boot/armbianEnv.txt look like it: sudo nano /boot/armbianEnv.txt verbosity=1 bootlogo=true overlay_prefix=rockchip fdtfile=rockchip/rk3399-rock-pi-4b.dtb rootdev=UUID=ca927a6a-b2f0-4184-ab0f-5719e34172db rootfstype=ext4 overlays=spi-jedec-nor param_spinor_spi_bus=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Reboot Enjoy Armbian booting with SPI / NVMe sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash without pci2.0 in /boot/armbianEnv.txt verbosity=1 Category Test Result HDParm Disk Read 609.77 MB/s HDParm Cached Disk Read 726.72 MB/s DD Disk Write 232 MB/s FIO 4k random read 54613 IOPS (218453 KB/s) FIO 4k random write 16151 IOPS (64605 KB/s) IOZone 4k read 132479 KB/s IOZone 4k write 79127 KB/s IOZone 4k random read 54327 KB/s IOZone 4k random write 89006 KB/s Score: 19365 and with pci2.0 in sudo nano /boot/armbianEnv.txt verbosity=1 bootlogo=true overlay_prefix=rockchip fdtfile=rockchip/rk3399-rock-pi-4b.dtb rootdev=UUID=ca927a6a-b2f0-4184-ab0f-5719e34172db rootfstype=ext4 overlays=pcie-gen2 spi-jedec-nor param_spinor_spi_bus=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Category Test Result HDParm Disk Read 579.83 MB/s HDParm Cached Disk Read 695.44 MB/s DD Disk Write 225 MB/s FIO 4k random read 57206 IOPS (228826 KB/s) FIO 4k random write 18720 IOPS (74881 KB/s) IOZone 4k read 131620 KB/s IOZone 4k write 79301 KB/s IOZone 4k random read 65461 KB/s IOZone 4k random write 117974 KB/s Score: 22989 All it tested on Brand:Samsung M.2 NVMe 980 Pro Board: Radxa ROCK Pi 4B plus v.1.72 hardware Device: Samsung SSD 980 PRO 1TB Class:SSD (M.2 NVMe) Изменено только что пользователем Cyrill PS. Создано с использованием материала от пользователя Igor, на этом же сайте и танцев с бубнами с материали RADXA. За что и благодарю, чем могу, сообщество и его верных пользователей.... на базе данного решения настроен NAS на базе urbackup server/client 2.5.31 - но это отдельная песня...

I have a Nebra hotspot with a Rockpi 4 plus v1.73 card. I can't find the Armbian image file to install Crankk mining. I only have 4A, 4B, 4C, and 4C+ img but no 4 plus. Help me! Is there a solution?

Hi, i just received my Rock 4 Se and a 32GB eMMC module today, and i'm currently not sure if the Image is incompatible, or if my storage modules are broken. I tried emmc standalone and SD for boot with nvme (from an dell notebook) for rootfs When i use the emmc, the filesystem goes into read only as soon as i do some apt upgrade. On reboot i often end up in initramfs nd have to fsck. I could gether some dmesg output: After this trace i get a lot of I/O Errors: Im not sure if this is an os or an emmc module issue. Any guess whats going wrong here? after that i coppied the current image ( Armbian_22.11.1_Rockpi-4b_bullseye_current_5.15.80.img.xz) onto a micro SD card, addedthe nvme drive, bootet that and made an armbian-install to migrate the rootfs to the nvme. After a reboot, i could actually start to instlall software. But after a while i still had some freeze of the whole system, so i had to power the board off and turn it on again. Sadly i do not have any more output from this situation. i'm also going to try a version with older kernel, will reportlater if that worked

I try to boot Armbian build for Rock Pi Model B but the screen stays black. The Armbian Download Page says for Model SE use Model B builds. Is there a configuration that i can change to make it work. I hope somebody can help me.

I have a Rock4 SE Board (or Rock Pi 4 SE) and I'm using the Armbian_23.02.2_Rockpi-4b_bullseye_current_5.15.93 Debian version. (Linux rockpi-4b 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 GNU/Linux) I am trying to set up the correct Device Tree Overlay configuration for my intended application. If I use Armbian-config as a tool to demonstrate the issue here. It starts by listing I2C7 and then I2C8. If I go to the Rock4 SE schematic and search for I2C8, it is not even setup as I2C: Then where is I2C6, for example. It's supposed to be there. If I then look further through the list, it is using RK3318 files (according to Internet search, they are from same 3300 family of chips but the 3318 has 4 x ARM Cortex-A53 @ 1.5 GHz cores). So are these correct. I'm rather confused by these. Could anyone explain. Thanks Colin PS. If I enable spi-spidev and then set the spi parameter to 0 it references SPI0, which is linked to the Ethernet port. I don't believe this is correct behaviour. The reason for this is that when setting it to 0, I cannot SSH into my board. When I set it to 1, I can. However when setting to 1, it shows the following (/dev/spidev1.0) when running ls /dev/spidev*

Hello, did somebody already have success connecting a Raspberry Pi 7 inch display to the current Armbian build? I already tried to add this overlay via armbian-add-overlay, but this did not work. What am I missing? Thank you for your help!

Hello, I have been looking for the solution to give access to the GPIO from the PI user for several weeks, does anyone have the solution? For information, I use a RockPI 4B+ under Armbian 22.11.4. Thank you in advance for your help. Regards Laurent