All Activity

Today I manage to Start Kernel Rockchip Legacy 5.10 ubuntu-24.04-beta-preinstalled-desktop-arm64-orangepi-3b.img.xz The system starts but after reboot it crashes. This is the error LOG on BOOT After some time: rk3566-rk817-tablet-k108.dtb rk3566-rk817-tablet-k108(decompiled).dts rk3566-rk817-tablet-k108.dts

@Markus Braun edit: I have an orange pi 5 plus! I have mine booting without any SD card. I sadly don't recall whatever guide I followed but I am pretty sure I had to toogle nvme booting somwhere in armbian-config or some command that updated the bootloader on the opi5+ This is my /boot/armbianEnv.txt verbosity=1 bootlogo=true overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=4578f871-5c8a-406a-87bd-be8562b1f8bf rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u my /etc/fstab look like this UID=4578f871-5c8a-406a-87bd-be8562b1f8bf / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 UUID=dce8fefd-ace9-468e-8695-55071f59094f /boot ext4 defaults,commit=600,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 [... nfs and other irrelevant junk] Did you change your fstab before running dd so it reflects the UUID of the the nvmes /boot disk? or change it to /dev/nvme... blabla ? I will be getting a new opi5+ in a week or two with an nvme so I will need to revisit these steps anyway. Let me know if I can check something on my side.

@Gullik I would assume we can get some ideas on progress with rk3588 from this link(even if it isn't specific for opi5/opi5+): https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md It seems HDMI audio is not even being worked on but it might also come 'natual' with the GPU stuff/other hdmi stuff(I dont know) Maybe it works with the libmali stuff I don't know. But I find it pretty wonky as it is with the legacy kernel that is supposed to work with it.

I removed the line "overlays=ssd-sata", but it still doesn't boot. I didn't think that I had to buy any additional equipment just to be able to use my ssd on the Orange Pi 5.

@Markus Braun In armbianEnv.txt remove the line "overlays=ssd-sata" A ftdi adapter doesn't cost the world and it saves you from a lot of hassle.

note that various armbian os images are linked on github https://github.com/armbian/os https://github.com/armbian/os/releases are you able to download images from there? you probably have to copy that say into a usb thumb/flash drive bring that home and you can try flashing that using dd from your raspberry pi I think there are also torrents link as alternative on the boards web pages, but I'm not too sure if you are able to download torrents say on a public terminal.

I don't have a ftdi adapter. How exactly do I disable the sata overlay? The files in /boot on my nvme are: armbianEnv.txt boot.bmp boot.scr dtb initrd.img-5.10.160-rockchip-rk3588 uInitrd armbian_first_run.txt.template boot.cmd config-5.10.160-rockchip-rk3588 Image System.map-5.10.160-rockchip-rk3588 The armbianEnv.txt on the nvme says: verbosity=1 bootlogo=false overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588s-orangepi-5.dtb rootdev=UUID=e389976d-765a-4392-97c0-fdc69e5fb045 rootfstype=ext4 overlays=ssd-sata usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u My /etc/fstab on the nvme says: # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=e389976d-765a-4392-97c0-fdc69e5fb045 / ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 lsblk -f gives me: NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 0 100% /snap/certbot/3641 loop1 squashfs 4.0 0 100% /snap/core/16578 loop2 squashfs 4.0 0 100% /snap/certbot/3698 loop3 squashfs 4.0 0 100% /snap/core/16931 loop4 squashfs 4.0 0 100% /snap/core20/2186 loop5 squashfs 4.0 0 100% /snap/core20/2267 loop6 squashfs 4.0 0 100% /snap/hello-world/29 mtdblock0 mmcblk1 ├─mmcblk1p1 vfat FAT16 armbi_boot F086-14E9 153M 40% /boot └─mmcblk1p2 ext4 1.0 armbi_root 384d3db4-7e83-40fe-933e-22e63200cb80 12.4G 55% /var/log.hdd / zram0 [SWAP] zram1 35.6M 17% /var/log nvme0n1 └─nvme0n1p1 ext4 1.0 e389976d-765a-4392-97c0-fdc69e5fb045 I'm a little desperate here, but thanks for your support @royk! Any other ideas? I cannot be the only one with this problem, can I? My ssd is 2 TBs, maybe this is too much? Do you have any other ideas?

Le potato won't boot from SSD. Followed the steps from 1) James Chamber's SSD Boot Guide also 2) Using Libre Flash Tool. Always getting errors: Not sure what is happening but would anyone know how this can be resolved? Using Armbian Home Assistant Supervised image from here.

@Markus Braun It might be a good idea to check the serial console to see what's going wrong, keep in mind that you need a ftdi adapter that can handle a high baudrate. Things you could check: Did you disable the sata overlay? Did you check if all the files are in the /boot folder of the nvme? Checked if the correct UUID is in /boot/armbianENV.txt and /etc/fstab Removed the SD-card at the first boot from NVME?

AFAIK, to get fully working 4:4:4 modes, there is the need to import some "experimental" patches that are floating in the rockchip kernel mailing list. The patches have been tested a lot by libreelec users on various rockchip platform (32 bit rockchip device like rk322x and rk3288 already have them merge in), but have been judged "too complicated to maintain" for rockchip64 repository. You can see the last attempt here and the previous attempt here, useful to get the points of the discussion.

rkvdec does not technically "override" hantro h.264: hantro and rkvdec are two totally different devices and both are exposed by v4l2 framework to userspace. It's up to the user application to choose the preferred device. Ffmpeg, which is perhaps the most common user application around, has no way to choose the v4l2 device for h.264. The workaround to force ffmpeg to use rkvdec (yes, because it is more performant) was to avoid declaring hantro as capable of h.264, sto the only left h.264 decoder is rkvdec. edit: and yes, rkvdec is in the kernel staging directory, plus armbian has a patch to enable h.265 decoding too

After your image is recorded on the SD card with the dd command, during the first startup, the root partition will be stretched over all free space and you will need to configure the user, language preferences, system clock.... This process proceeds without an emergency if the device is connected to the Internet and requires access to the Linux console, for example "minicom" via UART. If the device does not have a real-time hardware clock, this will cause problems with subsequent system starts. The system service will send a request to the time server at startup and wait indefinitely for a response. This is what you need to pay attention to first.

I wiped the SSD again, this time I created only one big ext4 partition. After that I used armbian-install "4 Boot from MTD Flash - system on SATA, USB or NVMe" and "7 Install/Update the bootloader on MTD Flash". I restarted the Orange Pi 5, but it booted from the micro sd card again. When trying to boot the system without the micro sd card (only the ssd present), it won't boot up at all. Is there anything I'm missing? The folders and files are all on the ssd. Everything seems fine. Do I have to edit the armbianEnv.txt on the ssd?

I am using the default values (after various tests). # cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand

How can i flash to internal memory . it's better Sd card

I want to try the 6.6.29 version, wich governor do you recommend? Which value in cpufrequtils? Thanks.

okok, i do one pass with my setting and if not crash, i try GOVERNOR=ondemand after, my pattern test during 36-40hours, keep in touch after this time if i not crash/freeze before

Hi with kernel version 6.7.4 nvme is not shown at all. Not sure which kernel I was before update but system setup to boot from emmc and system on nvme does not boot. Booting from SD card with 6.1.50, all's well but doing apt update && apt upgrade and nvme disappears.

I am using the ondemand governor. # cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand

Hi, okok, i test with my pattern test My brother have Helios64 also, he use it with many Docker Container and freeze everyday with default settings, same stabilty problem, he pass to 1200 1200 performance this day and test this setting for moment... if work better to my side with your file, my brother test your file on his helios Your file is on my helios, 400-1800 schedutil echo check > /sys/block/md0/md/sync_action -> running btrfs check --check-data-csum --readonly --progress /dev/disk/by-uuid/XXXXXXXXXXXXX -> running Freeze Crash... Not Freeze Crash... Keep in touch

you just need to take it from android. This is the method: https://forum.armbian.com/topic/24091-efforts-to-develop-firmware-for-h96-max-v56-rk3566-4g32g/page/2/#comment-153809

Hello! I have Orange Pi Zero 3 I got Armbian image from this link - https://github.com/armbian/community/releases/download/24.5.0-trunk.474/Armbian_community_24.5.0-trunk.474_Orangepizero3_bookworm_current_6.6.28_minimal.img.xz Of course I've made apt update and apt upgrade And now I'm tying to install zigbee2mqtt using this guide - https://www.zigbee2mqtt.io/guide/installation/01_linux.html So, I can't list USB devices root@orangepizero3:~# ls -l /dev/ttyACM0 ls: cannot access '/dev/ttyACM0': No such file or directory root@orangepizero3:~# ls -l /dev/serial/by-id ls: cannot access '/dev/serial/by-id': No such file or directory I have tryed some tips I've found but no result, only I can see my device in this- root@orangepizero3:~# dmesg -w . . . [ 1958.349181] usb 4-1: new full-speed USB device number 2 using ohci-platform [ 1958.585233] usb 4-1: New USB device found, idVendor=1a86, idProduct=55d4, bcdDevice= 4.42 [ 1958.585266] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1958.585286] usb 4-1: Product: SONOFF Zigbee 3.0 USB Dongle Plus V2 . . . So, do someone have idea how to fix it and get /dev/serial/by-id**** usb addres for config need? Thanks)

hey guys! nice to meet y'all the reason that brought me here is Zero 2W and tv-out issue any recommendations how can I adapt these patches to h618? or maybe someone is already working on that? or maybe there are other options how to turn on tv-out for Zero 2W? I've tried different distros with 6.1 & 6.6 kernels and no luck with tv ;( many thanks in advance!