All Activity

6.10 is, as the name implies, bleeding edge, so do not expect stuff to work. Mainline support for rk3588 is still in development. In theory though HDMI should work already, however might not have been tested on this device yet and there are caveats. Anyway if you prefer a working system, get an image with vendor 6.1.y kernel. Regarding the ssh stuff I think @Alessandro Lannocca did some work on SSH, either you grabbed an image where fixes were ongoing or you found another bug that needs attention.

Might be a known similar issue where when using armbian-install on OPi5 the contents of /boot is not copied to the nvme and therefore booting fails. However copying everything manually and adjusting the blkid it works just fine.

for some strange reason the content of armbianEnv.txt (rootdev) is not applied in my opi5, if anyone can help me. Thank !!!

Decoding time is ok if there is no frame drop.

For Armbian 24.04 I recommend you see the method used by the Botspot pi-apps application from github, I tested the script method and it worked very well Pi-Apps The script for Armbian 24.04 was the Steam install script, it includes BOX86 and BOX64 After install box Just install Wine normally Edit: plot twist: Steam don't work..... just box86 and box64

- Please help me. I'm stuck 100% here after booting on mxq pro4k. (Rk3228a) Unable new reboot from sd card on tv box. - I think armbiam jammy not support in board. - How to boot sd card or command to boot. https://silpakorn-my.sharepoint.com/:f:/g/personal/koosiriwanich_s_su_ac_th/EukZkSlhAyZKiP3mCGqwFR8BHyHl3i4euWPhGaXiqRvUEw?e=3GUsYW

The RED LED is set on DTS to be HeartBeat: This is the code @Vincenzoernst1 if you wanna change it: sudo apt update sudo apt install armbian-config sudo armbian-config Edit Device tree with armbian config. led_status: led-status { label = "led-status"; gpios = <&gpio0 RK_PD4 GPIO_ACTIVE_HIGH>; linux,default-trigger = "heartbeat"; pinctrl-names = "default"; pinctrl-0 = <&led_status_enable_h>; }; @Vincenzoernst1 I noticed that you care a lot about the look of the box I invite you to participate in the development of This project with @pocosparc The objective is here

P.S. Below is the initial output that I got on the serial port, before it asked me to reset the root password: $ sudo bt -b 1500000 No port specified, using ttyUSB0 (last registered). Use -l to list ports. Trying port ttyUSB0... Connected to ttyUSB0 at 1500000 bps. Escape character is 'Ctrl-]'. Use escape followed by '?' for help. DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0x1 CH0 RX Vref:28.3%, TX Vref:22.8%,21.8% CH1 RX Vref:26.3%, TX Vref:19.8%,19.8% CH2 RX Vref:26.7%, TX Vref:19.8%,19.8% CH3 RX Vref:27.5%, TX Vref:20.8%,20.8% change to F1: 528MHz change to F2: 1068MHz change to F3: 1560MHz change to F0: 2112MHz out U-Boot SPL board init U-Boot SPL 2017.09-g1b1171b7c71-220418 #fa (Apr 18 2024 - 11:12:44) unknown raw ID 0 0 0 unrecognized JEDEC id bytes: 00, 00, 00 Trying to boot from MMC2 No misc partition spl: partition error Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(a7d1d8d191...) + OK ## Checking u-boot 0x00a00000 ... sha256(235390ebc4...) + OK ## Checking fdt-1 0x00aa7e10 ... sha256(d25019e2ea...) + OK ## Checking atf-2 0x000f0000 ... sha256(aa71013e72...) + OK ## Checking atf-3 0xff100000 ... sha256(4b2065349b...) + OK Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000) Total: 368.979/520.85 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45 NOTICE: BL31: Built : 10:11:21, Dec 27 2023 INFO: spec: 0x13 INFO: code: 0x88 INFO: ext 32k is valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2024.07-rc4-armbian (Jun 17 2024 - 14:10:22 +0000) Model: Generic RK3588S/RK3588 DRAM: 8 GiB Core: 291 devices, 25 uclasses, devicetree: separate MMC: mmc@fe2c0000: 1, mmc@fe2e0000: 0 Loading Environment from nowhere... OK In: serial@feb50000 Out: serial@feb50000 Err: serial@feb50000 Model: Generic RK3588S/RK3588 Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': No EFI system partition No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables 0 efi_mgr ready (none) 0 <NULL> ** Booting bootflow '<NULL>' with efi_mgr Loading Boot0000 'mmc 1' failed Loading Boot0001 'mmc 0' failed EFI boot manager: Cannot load any image Boot failed (err=-14) Scanning bootdev 'mmc@fe2c0000.bootdev': 1 script ready mmc 1 mmc@fe2c0000.bootdev.part /boot/boot.scr ** Booting bootflow 'mmc@fe2c0000.bootdev.part_1' with script Boot script loaded from mmc 1:1 225 bytes read in 4 ms (54.7 KiB/s) 28236660 bytes read in 2365 ms (11.4 MiB/s) 32883200 bytes read in 2752 ms (11.4 MiB/s) 148215 bytes read in 22 ms (6.4 MiB/s) Working FDT set to 12000000 Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' ## Loading init Ramdisk from Legacy Image at 12180000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 28236596 Bytes = 26.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 12000000 Booting using the fdt blob at 0x12000000 Working FDT set to 12000000 Loading Ramdisk to eb3d9000, end ecec6b34 ... OK Loading Device Tree to 00000000eb34c000, end 00000000eb3d8fff ... OK Working FDT set to eb34c000 Starting kernel ... Loading, please wait... Starting systemd-udevd version 252.22-1~deb12u1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... [FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server. [FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server. [FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server. [FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server. [FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server. Armbian-unofficial 24.8.0-trunk Bookworm ttyS2 nanopi-r6c login:

Thanks for getting back to us. I ran the script. During the setup, I am pretty sure that I asked it for a window manager (xfce). Then I fired up the image, I get no output on the HDMI connected monitor. Then I connected it to the serial port and rebooted and this time it asked me to specify a root password, and a username and password. So it seems to have started up successfully. nanopi-r6c login: erik Password: _ _ ____ _ ____ __ ____ | \ | | _ \(_) | _ \ / /_ / ___| | \| | |_) | | | |_) | '_ \| | | |\ | __/| | | _ <| (_) | |___ |_| \_|_| |_| |_| \_\\___/ \____| Welcome to Armbian-unofficial 24.8.0-trunk Bookworm with bleeding edge Linux 6.10.0-rc4-edge-rockchip-rk3588 No end-user support: built from trunk System load: 17% Up time: 0 min Memory usage: 9% of 7.75G IP: 192.168.1.60 CPU temp: 34°C Usage of /: 5% of 116G RX today: 83.9 KiB Configured profile sync daemon with overlayfs. erik@nanopi-r6c:~$ But the window manager does not start, and still nothing on the monitor. Is this the expected behavior? Sorry if I'm being dumb, I have never used armbian before.

question: i see the red EMMC(? its not ethernet.) led blinking all the time. Iotop doesnt show any writes. Is it a write (access) led?

indeed this would be a very nice little server 💪

Okay, I get it. Can we just take these few patches from the 6.6 kernel and add them to the 6.1 kernel? It is better if they are in the form in which they already exist in 6.6. I mean, what have you already tested.

True, but the "random.c" on the 6.6 branch contains bunch of other changes not present in 6.1 (15 commits to be precise). I suppose the change "random: handle creditable entropy from atomic process context" woks well with these commits, but is broken without some of these changes. In fact, I kind-of confirmed that, per my comment below. Overall, this looks plausible. The change was originally done and tested on the mainline, with all other changes being present. Then it was cherry-picked into 6.6 and 6.1 branches, where it received more limited testing that did not catch the problem. I'm guessing the problem does not show up on x86 and shows up on armhf. It could be timing dependent, so only shows up under specific circumstances. I'm hoping there would be just a few commits (ideally just one) that could be cherry-picked into 6.1 branch to make it work.

Hello, After several days of debug I put the finger on a very strange issue using integrated Ethernet. I use my Rockpro64 mostly as a Samba and DNS server. In my network context I implement 2 vlans as vlan interfaces (eth0.10 and eth0.20). Each of these interfaces needs to use a specific mac address that differs from physical eth0 mac address (it is an important point). If I use only the physical mac my router is not be able to route correctly between vlans (probably an ivl/svl issue). Under this context I first noticed that when I bring down eth0.20 although using vlan 10 (so eth0.10) connectivity is lost. I then write a script to gather all needed information (ie. ip link/addr/route/rule/neigh, ping, arping, netstat, ...) ==> no peculiar problem I then add a background tcpdump and, guess what, the connectivity loss didn't occur anymore ! After thinking a bit, I made the assumption that the main difference is the use of promiscuous mode during tcpdump. ==> and "bingo" : setting 'promisc' flag on eth0 acts as a workaround. Also if I do not set a specific mac for vlan and use physical mac leads to no connectivity issue, despite the wrong routing. The key point seems that bringing down a vlan interface unregisters all macaddress from listening process instead only the needed, so the connectivity problem. I don't know if it's a hardware limitation, a driver bug or Armbian issue, but I am open to any fix or at least, any debug hint that helps to narrow down the root cause. Regards.

Hello: I am tyring to build the latest version of moonlight-qt (6.0.0). Up until now, I succeded by removing the disable-libdrm and disable-wayland to enable hardware acceleration and use H264, H265 and AV1 all of them through hardware acceleration. However, I get huge decoding times and they are even variable, ranging from 40ms to 300ms depending on what is going on in the streaming. The 4.3.1 version provided by @amazingfate works very good at 4ms decoding time but I would like to test the new AV1 encoder and features from the latest version. What steps should I follow to get it working correctly? Thank you in advance

Hello everyone: I own an Orange Pi 5B 16GB. Today I updated from Armbian 24.2.1 to 24.5.1 stable. This new release includes the 6.1 kernel. When I issue the apt upgrade command I correctly get updated to 24.5.1 version but I am still in kernel 5.10. So, in order to be at kernel 6.1, I use armbian-config. The problem is, after doing this and rebooting, the board no longer boots, I dont' get SSH, anything... Another thing that I updated besides armbian itself where sobre libraries like libv4l or libmpp from @amazingfate, before updating those 6.1 kernel switching worked. Any help in how can I debug (like reading UART port) or solve this? Thanks in advance

Thanks for the response, I will dig around some more. Screens in general seem to have a lot of Dificulties. I'd rather have mipi, but that rarely works.

Name topik: Orange Pi Zero 2W overlay I2C SPI help Write here

Yeah, I just realized that after the reinstall everything worked fine. Maybe I just messed up something before. Thank you for your help! Now I have another issue with SPI. Can I write here or should I open a new topic?

@Werner While I was doing something, they had already done it.

Description Add v3 patch of rkvdec2. Add a v4l2 patch to fit rkvdec2's 16x16 minnimal decoding size for chromium. Remove VDPU121 node because there is already a 4K H264 decoder. Gstreamer can't handle two. Add udev rule for chromium How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh kernel BOARD=rock-5b BRANCH=edge DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow [x] gst-launch-1.0 --no-fault filesrc location=/home/jfliu/Big_Buck_Bunny_2160_10s_H264_1s.mp4 ! parsebin ! v4l2slh264dec ! autovideosink [x] chromium can decode 4K h264 video. Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

https://github.com/armbian/build/pull/6771

BPI-F3 Introduction For this device, we can make an image using the Source Code: BananaPi_BPI-F3#_development Let's try to add support to the Armbian build system.