All Activity

TLDR; The dtb contains a 75 mV bump for all fast cores as suggested by @prahal. You can find the opp-table-1 in this thread above (posted April 19). Use device tree compiler 'dtc' to apply your own changes. The dtb further contains a fix that enables hs400 speed on emmc also proposed by prahal. There is also a change for providing L2 cache information (this is all explained in this post) - and there is also a note that 6.6.29 is stable with those modifications. However, 6.6.29 and 6.6.30 bugs me with frequent transmit queue timeouts while using the 2.5G interface (NETDEV WATCHDOG: end1 (r8152): transmit queue 0 timed out 8584 ms). I could not find any combination of settings to get rid of this. Therefore I switched back to 6.6.8 - it works perfectly fine - absolutely no issues. I am using the following configuration: root@helios64:~# cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=600000 MAX_SPEED=1800000 GOVERNOR=ondemand root@helios64:~# cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. for cpufreqpolicy in 0 4 ; do echo 0 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/io_is_busy echo 25 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/up_threshold echo 10 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/sampling_down_factor echo 200000 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/sampling_rate done for i in $(awk -F":" "/xhci/ {print \$1}" < /proc/interrupts | sed 's/\ //g'); do echo 20 > /proc/irq/$i/smp_affinity done for i in $(awk -F":" "/ahci/ {print \$1}" < /proc/interrupts | sed 's/\ //g'); do echo 10 > /proc/irq/$i/smp_affinity done exit 0 root@helios64:~# systemctl disable armbian-hardware-monitor.service root@helios64:~# reboot If you are happy with 6.6.29 or 6.6.30 go ahead. For your convenience I attach the modified dtbs. rk3399-kobol-helios64.dtb-6.6.8-L2-hs400-opp rk3399-kobol-helios64.dtb-6.6.29-L2-hs400-opp rk3399-kobol-helios64.dtb-6.6.30-L2-hs400-opp

Looking to /boot/dtb-6.6.30-current-sunxi64/allwinner/overlay/ for h616 not exit dtbo sun50i-h616-w1-gpio.dtbo So for this reason not available in armbina-config in HARDWARE setup w1-gpio so we can not at current use 1-Wire sensor to define on which GPIO is connected 1-Wire sensor DS18B20 uses the 1-wire bus so it will be nice to have possibility use 1-Wire sensors with OZPI v3

@cad 435 No you aren't really missing anything. In the stable channel, kernel .debs generally only get pushed out every three months when a new stable release is put out (24.05 will be out the end of this month for example). If you want to get regular updates of kernels you need to switch to the nightly builds repository in armbian-config. Right now there is no in between.

This is hard to say as we are talking about non standard Linux kernel. If HA works, IMO you can safely ignore those problems or: New kernel is being developed for several years and it might already be working for this use case. You can try by switching to it (armbian-config -> system -> alternative kernels -> select EDGE 6.8.something), but I give you no warranty that it will work. You might need to start with a new image. If it works well, report back and we will generate images by using that kernel. I know many things in graphical areas are missing there, but for this uses case we don't need HDMI output anyway ...

Hi Igor, the image: "Armbian_24.2.2_Khadas-edge2_bookworm_vendor_6.1.43-homeassistant_minimal.oowow.img.xz" work and after few mins I have access as regular HA. There are few warnings: Unsupported system - AppArmor issues : System is unsupported because AppArmor is working incorrectly and add-ons are running in an unprotected and insecure way. Unsupported system - CGroup version: System is unsupported because the wrong version of Docker CGroup is in use. Is it something you can fix in the image and I'll wait or I can upgrade and it will be fixed ? You did a great job man! I'll try to fix it for now, again thank you ! Richard.

Is it possible to upgrade? I upgraded the system and the kernel via armbian-config, but now I'm on 6.7.4-edge-meson64... I have no idea how to get to newest "latest release" from within the running system tbh... Is it even possible? sudo apt-get dist-upgrade also did really nothing.... I feel like I'm missing some kind of big point here which just hangs before my face, but I don't see it...

Hi, On post below i report i have a stable helios64 with ebin-dev's file dtb for 6.6.29 with ondemand 408-1800mhz Whereis a post explain how dtb file change for understand how that work? You speak about end of cpufreq, armbian-hardware-optimize.service, irq smp_affinity, xhci and ahci... anyone have enough knowlege to explain this change ? It's specific for helios64 support or that will be include on futur armbian for every boards/versions ?

@Victor Pecherskiy Then it seems like a software problem, unfortunately I don't have a 32GB to test it with. And what if you copy the dtb from Joshua Riek's image to your Armbian installation? This is a difference I found but not sure if it's possible to be the cause: https://github.com/Joshua-Riek/linux-rockchip/commit/fdf8d484eccb0949664b78b16e0a275e75c52e0d

Description Devicetree is already in https://github.com/armbian/linux-rockchip so just a board config is enough How Has This Been Tested? [x] ./compile.sh BOARD=rock-5-itx BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow, flashed to emmc and boot 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

Its a bug. You need to make sure the wireless country code is set, even when its not being used.

Hi. I installed Armbian on a raspberry pi 5. Everything went smoothly, but straight-away, I see that dmesg is filled with this error: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 I'm noticing some inconsistencies on the network, and I'm not sure if this is behind it. I tried installing the firmware-brcm80211, but it didn't help -- in fact, I think it might have made it worse. I've looked all over, but I cannot see any useful information regarding this. It has no usb devices attached, not using and gpio pins or anything fancy. It is just a node on the network that is presenting information on a television screen in our shop. It looks like the driver is not a good match for the hardware (that's my guess, anyway). In the past, I've seen errors like this fixed with the firmware I mentioned above. No such luck this time. Any way I can fix this? Thanks.

Hi all, I decided today to give an Armbian build a whirl as a virtual machine (guest). In particular, Armbian_24.2.4_Uefi-x86_jammy_current_6.6.21_kde-neon_desktop.img. As is usual with installing a virtual machine, it comes up with a default video resolution of 1024x768; I can usually quickly get it full screen on my system as 1920x1080 by going to the System Settings : Hardware : Display and Monitor : etc. However, here there is no hardware subsection at all, and a search didn't turn up a setting to change the display. Any advice on where to find it? I installed the spice guest driver and related packages on the guest. Thanks!

I have the same thing i am only seeing the first 8 pins. i did the "sudo su -" to change to root then the "echo "BOARD=orangepi5b" | sudo tee /etc/orangepi-release" where you able to figure anything out

Which is kind of odd since both Armbian and Joshua's work are very close kernel-wise.

That board is no longer a valid armbian board. It is EOS status (end of support). So there is no Armbian support and no community support for that board.

@royk, have not tried yet, hope to try soon. Since Ubuntu by Joshua Riek seems to work well, it seems to be a software problem.

In this case, I would try it again but with a USB meter plugged into 1 of 4 Odroid USB ports. Then when it boots up watch for voltage drops, even if it was running fine with the other firmware or system. Mine board even powered via J8 pin sometimes was not able to initialize the USB controller which is quite strange behavior and I would more likely to expect it when powered via crappy micro USB con.

Hi all, Armbian is now working on Rock 3C. You can download a community build: https://github.com/armbian/community/

hello, there is no option to install in flash, Install/Update the bootloader on SPI Flash im using olimex a20 lime with emmc Armbian 23.8.1 Jammy with Linux 6.1.47-current-sunxi verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=6a1af220-c7aa-449a-b709-c3eb897ae28a rootfstype=ext4 overlays=mmc2 pwm spi-add-cs1 spi-jedec-nor spi-spidev param_spinor_spi_bus=0 #param_spinor_spi_cs=1 param_spidev_spi_bus=2 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u im using like that but it dont boot if i remove sd lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 7.3G 0 disk └─mmcblk0p1 179:1 0 7.2G 0 part /var/log.hdd / mmcblk1 179:8 0 14.6G 0 disk └─mmcblk1p1 179:9 0 14.4G 0 part /mnt mmcblk1boot0 179:16 0 4M 1 disk mmcblk1boot1 179:24 0 4M 1 disk zram0 254:0 0 229.8M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk

It happens also with the latest Linux 6.7.4-edge-meson64 kernel. This problem could be related to a power switch which could be optionally connected to the J4 pin?

I gave up on 6.6.29/30: in general they are stable but the 2.5G interface causes trouble again (NETDEV WATCHDOG: end1 (r8152): transmit queue 0 timed out 8584 ms) although the code for the r8152 driver did not change since the release of 6.6.8. Therefore I am back again on 6.6.8. It runs fine with the kernel defaults, irq smp_affinity set for ahci and xhci (see above) (armbian-hardware-optimize.service disabled) and it also benefits from the 75 mV opp increase (dtb attached). rk3399-kobol-helios64.dtb-6.6.8-L2-hs400-opp

@elysiuMAccording to a user from a russian forum, the published stock firmware does not match the device. Maybe someone will find a solution soon!? https://4pda.to/forum/index.php?showtopic=1088113#entry129825636

I'm looking for a flash for this box. 16/2 x88 pro-b-rk3318-d4-v1.2 16/2

New imgs are now available. 6.6.30-current-meson64 https://www.armbian.com/bananapicm4io/

@Victor Pecherskiy To rule out if it's a hardware or software problem have you tried an "original" image from orange pi?