Active threads

Sorry, appears to be working good. My bad wrong governor selected.

I run output/images/Armbian-unofficial_24.5.0-trunk_Onecloud_bookworm_current_6.6.21_minimal.burn.img on my onecloud board. It shutdown about every 40 minutes. How to solve this problem? Thanks! journalctl.log kern.log armbian-hardware-monitor.log

Hi again, Quick update for potential other readers, and some questions. I've now also got overlayroot setup to keep the internal flash mounted as readonly for normal operation. So as to not burn through the flash's endurance counters within a year on a device that's writing logs, status information, etc. to flash continuously. And also to protect it against issues when people just pull the plug while it's operational, potentially corrupting flash and making it unusable without physical recovery. Seems to be working great, but had to adjust the initramfs hook and script files (mount -o move instead of mount --move in script, and adding lines to copy_exec /bin/grep, /usr/bin/stat, and /bin/echo to the initramfs. Seems to be working just great including with pikvm. Two questions: My rk3318 android tv box "H96 Max v11" does have the two red/blue leds on the pcb, but no clock display. There are solder points on the pcb though. Would it be possible to use these pins for GPIO access (maybe even add an I2C RTC module), or would that not be possible within the limits of hardware/firmware? Any pointers on where to start looking, if at all possible? In pikvm config, following generic instructions, I was able to easily add the usb ethernet gadget and do routing/masquerading for the attached device. Yet, when I tried to configure usb mass storage gadget, the result was that the keyboard/mouse stopped responding in pikvm. From the pikvm documentation (unfolding the USB limitations section) it looks like there could be an issue with capabilities of the chip in relation to the number of endpoints needed. Yet, that page mentions mass storage would require 2 endpoints for each msd, and usb ethernet would require 3 endpoints per emulated device. So it's strange that ethernet does work but msd does not. Enabling only one at a time, of course. Is there any data on the number of endpoints available on the rk3318 chip? Or maybe someone knows how to make msd working? Or.. maybe it was intentionally disabled in srepac's kvmd-armbian because it's not working either way? The usb ethernet gadget was disabled in the config as well but works like a charm, so not sure why msd didn't work as expected. Or maybe msd is only supported for the usb3 port and not on the usb2 port that I'm now using for otg connection to the remote? Sorry, too many question marks here... Any pointers would be much appreciated!

@McTurbo OrangPi official images use the vendor kernel 5.10 with various custom patches and drivers. Armbian does not offer vendor kernel anymore because after a while they become old and unmaintained.

Do you see CPU stalls in kernel logs/dmesg? We have two reports with sunxi family boards and 6.6.16 kernel, reporting high CPU usage, unstable operation and kernel logs reveal CPU stalls every few minutes. I'll build and test with latest Linux 6.6, else with edge, in the hope it can be fixed forward instead of backwards. Nasty to debug (for me) since no process, cron job or anything else is obviously associated with those CPU stall events.

Here is my solution. I created a sdcard with u-boot firmware according to the instructions on this webpage: https://docs.u-boot.org/en/latest/board/starfive/visionfive2.html I noticed these instructions will use OpenSBI v1.4. The Starfive firmware is still using OpenSBI v1.2. Flip the boot selector switch on the board ==> to select boot from sdcard. Insert the sdcard created from that u-boot website. Boot the system. It will boot without starting any operating system. U-Boot 2024.07-rc1 (Apr 26 2024 - 10:32:34 +0300) OpenSBI v1.4 Swap the sdcard with the Armbian sdcard. Enter these commands: mmc list mmc dev 1 load mmc 1:1 ${fdt_addr_r} /boot/dtb/starfive/jh7110-visionfive-v2.dtb load mmc 1:1 ${kernel_addr_r} /boot/vmlinuz-5.15.0-edge-starfive2 load mmc 1:1 ${ramdisk_addr_r} /boot/initrd.img-5.15.0-edge-starfive2 setenv bootargs 'root=/dev/mmcblk1p1 rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0' setenv kernel_comp_addr_r 0x5a000000 setenv kernel_comp_size 0x04000000 booti $kernel_addr_r $ramdisk_addr_r:$filesize $fdt_addr_r This will boot Armbian and recognize the 8GB RAM. I also found there is a problem recognizing the UUID of the sdcard or nvme during operating system boot. For sdcard boot I needed to edit the /etc/fstab -- switch the UUID to the device name sdcard example: # cat /etc/fstab /dev/mmcblk1p1 / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 These instructions also worked with Ubuntu 24.04. I saw the same memory problem as with Armbian.

Probably no dtbo will be needed. Find the 5 pins in your orange pi, that would be contacted by the hat, and try to control them with the Python code here: https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/?do=findComment&comment=181191 if that lorahat software is open source, then change that source code to point to the correct pin addresses

Please, can you share your hostapd.conf (minus the ssid and keys of course) I am running into other problems, but I am glad that others are getting hostapd working 👍

After the usb4-1 lines, you should have seen cdc_acm something You can check that you have the acm driver with: zcat /proc/config.gz|grep ACM you should see config_usb_acm=m Have you tried: ls /dev/ttyUSB* ? When you see the ttyACM*, you should get the by-serial files appear automatically (devrules function)

any one help me to amlogic s805 latest ver plz.. plz......

Hi @Gunjan Gupta I am helping a client with an issue on their nanopi neo where armbianEnv.txt and other files are seen to be corrupted. The symptoms resemble the various complaints seen over the years on this forum. A system restart generally seems to be involved. I am speculating that they are removing power without a safe shutdown. You mentioned earlier in the discussion on Dec 2023: Do you recall which commit the changes to filesystem options were made so that we can code review? My client is using a build from May 2023. So I am wondering if they are missing some critical changes that would make the file system more reliable. Please let me know if you remember what filesystem options were changed and when they were made. A link into Git would be very helpful here. My customer is not ready to upgrade, but would be open to have me patch in upstream fixes. Thanks, Chris N.

@pocosparc Can You Manage some fixes for this H96 Max vendor DTB Kernel 6.1.43 to included on armbian build?

It's finally working now! And it probably was working before, but I didn't notice it, because for whatever reason the IP address of the Orange Pi changed when using the ssd. When I tried to ssh on the device, I couldn't get any connection, since I was using the IP to connect. When using the new IP of the device (I was checking the web interface of my router and it showed me an Orange Pi 5 with a new IP), it worked like a charm! Thanks for your input @royk & @igelkotten! Just to clarify @igelkotten: I didn't use dd in my last attempt at all. I created one single partition on the ssd and did what @royk suggested from the very beginning: Use armbian-install (which is btw also accessible through armbian-config) and then "4 Boot from MTD Flash - system on SATA, USB or NVMe". After that is completed, it asks you if you want to install/update the bootloader on MTD Flash, which I agreed. Then I didn't already reboot the device. Instead I took a look at the armbianEnv.txt and /etc/fstab to see if the UUID is correct. Everything looked fine, so I rebooted without the micro sd card and apparently the Orange Pi was working the whole time, but using a different IP. Anyway, it's working now and I'm happily using the ssd! Thanks again for the help!

@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.

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.

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.

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

I am using the default values (after various tests). # cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand Edit: I would love to use schedutil but low priority tasks take three times as long with it to complete compared to ondemand (!!) (I tested that with a complete file scan of my nextcloud installation). There was a lot discussion going on in armbian/build on github. Finally the Armbian default governor was set to schedutil again instead to ondemand. But schedutil parameters need to be fine-tuned such that EAS works correctly and from my own observations I can confirm that this is clearly not (yet) the case at least for the rk3399. Anyway - you can set min_speed to 600000 or 816000 for all cores (ondemand): it does not affect power consumption at all, but it renders your Helios64 more responsive. And disable armbian-hardware-optimize - it degrades performance.

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

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.

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

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!

I suggest looking over the overlays available; https://github.com/BPI-SINOVOIP/pi-linux/tree/pi-6.1-sunxi/arch/arm64/boot/dts/allwinner/overlay They may or maynot need to be edited as BSP VS MAINLINE usually isn't identical.

Hey Efe, Thank you for your help. Cannot believe that I downloaded the wrong Armbian image. With the Armbian_24.2.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz, I managed to boot into the setup CLI, although it is very "flashy". The monitor turns off and on again every 2 seconds. After setting up, it says "Starting desktop environment..", and goes black from there. The flashy CLI helped me figure out the reason. I am using ultra wide screen with 5120 x 1440 resolution. After changing to standard 2k resolution, I can boot into the desktop without any issue. Once I am in, I can change the resolution in settings to 5120 x 1440. I think the initial Linux configurations cannot understand weird aspect ratio. I tried 2k resolution with Joshua Riek image that I failed to boot before and it worked normally this time. Because Joshua Riek uses GUI first-boot screen, I went immediately to black screen instead of "flashy CLI".