All Activity

Just compiled and flashed a Cinnamon desktop image. Boots fine Video over HDMI working. Audio over HDMI working. The video experience is not that much satisfying. There seems to be no graphic acceleration, yet. WebGL aquarium runs at 5 FPS with 500 fishes, 15 FPS with 100 fishes. Youtube videos are relatively laggy and you'll experience high CPU load. All the GPIO hardware stuff has not been tested, yet. No clue how to do it... Now I'd like to have some more people on board to support me by adding graphic acceleration and how to merge the M1S support now into the Armbian repo. Greetings.

I've got a REV 1.1. Try flashing the binary. I got the timing from the opi zero2 Make sure you flash it to the correct node, be it mmcblk1, sdb, etc. sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblkX conv=fsync bs=1024 seek=8 u-boot-sunxi-with-spl.bin

M.2 NVMe slot is also WORKING. At least the SSD gets detected with "cat /proc/partitions". It is not listed under "df -h" but I think this is because it is not mounted yet...

Okay. Thank you!

Since you have now confirmed the HDMI functionality, the time has come for me to retire further support. I am only interested in generic support; for Armbian-specific issues, you'll have to wait for others who are interested.

Okay, one step further: HDMI output is WORKING! initially I had the M1S connected to the Aux input of my AV receiver. There seems to be a problem with display detection (EDID, available modes) and so the M1S does not know which display mode to set. I then connected the M1S directly to an HDMI input of the TV and nothing changed. Rebooted and ... Surprise! Video output works, EDID information and available modes are available (wasn't when connected to AV receiver). So how can I tell Armbian to force a specific display mode even when no screen information is available?

To be honest I currently don't know. I booted my first from SD card. That worked as described above. After that, I've shut down the M1S, set the M1S to UMS mode and cloned the SD card to the internal eMMC. Booted as described. But please tell me how to perform that test and I can give your kernel build a try . Greetings

Version `25.8.2` of kernel, dtb and/or header package on Armbian Ubuntu Noble break `zfs-dkms` (I'm pretty sure kernel module `zfs` was not built with success) I had to run: ```sh sudo apt install linux-image-current-meson64=25.8.1 linux-headers-current-meson64=25.8.1 linux-dtb-current-meson64=25.8.1 && sudo dpkg-reconfigure zfs-dkms ``` I couldn't look in to the problem, because I was busy doing something else when I was just upgrading every package on the system. I had to prioritize quickly fixing it before another user arrives so I just reverted the suspicious packages (the three I mentioned in the title) I can't look into the problem now either because the computer is not being used by me alone..

From what I’ve found, the K2B has three revisions; mine is REV 2.2 (it’s printed right on the PCB). Looks like they swapped the RAM from DDR4L to DDR3—mine has DDR3 chips on board—so that might be why it’s acting up. Kickpi’s site barely loads from China; I really dislike that company, the documentation is almost non-existent. I found some here: https://github.com/tan-zhihao1/kickpi-book/tree/master/h618/en Still, I want to crack the problem. With the current sale the 2 GB + 0 GB version is only 78 CNY (about 11 USD), which is hard to pass up. Thanks for getting back to me. K2B.zip

Hello, I`ll try to hook up display to OpangePi PC, But have no output. My English is not native so i`ll try to write in simlpe way. image Armbian_23.8.1_Orangepipc_jammy_current_6.1.47_minimal.img.xz my dts: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&spi0>; __overlay__ { status = "okay"; // cs-gpios = <&pio 0 9 0>,<&pio 0 8 0>; /* PA9=CS0 for LCD, PA8=CS1 for touch */ display: display@0 { compatible = "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; spi-max-frequency = <20000000>; txbuflen = <65536>; rotate = <270>; bgr = <0>; fps = <30>; buswidth = <8>; regwidth = <16>; height = <480>; width = <320>; reset-gpios = <&pio 0 2 1>; /* PA20 */ dc-gpios = <&pio 0 71 0>; /* PA10 */ debug = <0>; init = <0x10000b0 0x00 // Interface Mode Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x10000C0 0x0D 0x0D // Power Control 1 0x10000C1 0x43 // Power Control 2 0x10000C5 0x00 0x48 0x80 // VCOM Control 1 0x10000C7 0x00 // VCOM Control 2 0x1000036 0x28 // Memory Access Control (Rotacao) 0x100003A 0x55 // Pixel Format Set (16bit) 0x10000B1 0xB0 0x11 // Frame Rate Control 0x10000F0 0x01 // Enable Extended Comand Set 0x10000F6 0x00 0x01 0x32 // SPI ilInterface Control 0x1000026 0x01 // Gamma Set 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 // Positive Gamma Correction 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F // Negative Gamma Correction 0x10000B6 0x02 0x02 0x3B // Display Function Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x1000029>; // Display ON }; // xpt2046: xpt2046@1 { // compatible = "ti,ads7846"; // reg = <1>; // spi-max-frequency = <2000000>; // interrupts = <0 7 2>; /* high-to-low edge triggered */ // interrupt-parent = <&pio>; // pendown-gpio = <&pio 0 7 0>; // ti,keep-vref-on = <1>; // ti,x-min = /bits/ 16 <200>; // ti,x-max = /bits/ 16 <3900>; // ti,y-min = /bits/ 16 <200>; // ti,y-max = /bits/ 16 <3900>; // ti,x-plate-ohms = /bits/ 16 <60>; // ti,pressure-max = /bits/ 16 <255>; // ti,swap-xy = <1>; // }; }; }; }; when board boots, display switch from white to black. Without console output. gpio readall - looks good. all pins present. when I try Armbian_25.8.1_Orangepione_noble_current_6.12.43.img.xz board boots. add overlay to it, by armbian-add-overlays remove HDMI cable. (Really good first-config over ssh, why not to add this to other boards, like mine?) reboot Display works(Ony if HDMI is unpluged), with output of boot Armbian. I`ll think this something wrong with output on spi LCD over OrangePi PC Armbian build, or sometning like that way.... Any advise?

Hello, has anyone managed to get this camera to work on zero 3?

Hmmm. Never mind, maybe. I see that Armbian has it included here, but for some reason it was not installed automatically. https://github.com/armbian/build/tree/main/packages/bsp/odroid

Sorry for the late feedback. I was waiting for a new kernel update (6.12.54-bcm2711) to confirm it was all right. Just as what @Werner said, in the `/etc/initramfs/post-update.d/z50-raspi-firmware` contains snippets of the code that prints out the error. And it's indeed no actual harm. Also, without setting on-hold of the `raspi-firmware`, kernel updates works just fine. We are good. Thank you all!

Hi! I dont know if anyone else mentioned this here but here is my issue: My RK3229 boots into armbian fine but after like 60sec the screen turns black and both blue LED stays on. Is there a fix for this?

If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc. In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11 https://github.com/robertojguerra/opiz3-labwc-setup I am open to read any improvements, or show me how I could make deb packages. In the near future, I will make a step-by-step video tutorial in Youtube.

Just out of curiosity, are you able to run your device with firmware loaded from microSD? I. e. firmware area on eMMC cleared. If so, you can try my kernel build and see how it works for you.

For video acceleration, you need to stick with Bookworm.

I don't think you understand how Armbian works. This board is community supported. It does not and hasn't been an Armbian supported board. Given the hundreds of boards out there Armbian only has the resources to officially support a handful. The rest end up being supported by the user community like this board. Thus support is only as good as the community volunteers who have the board and wish to volunteer their time to support it. Armbian provides the tools and infrastruction to make supporting boards easier, but the work still needs to be done by someone for community supported boards like this.

Booting from internal eMMC also works. Regarding HDMI: I've made another build where I pulled the DTS definitions for the M1S from the Linux mainline repository directly during compilation (thanks ChatGPT!). But that also did not help. The system "works" as before, just no HDMI...

Can I still find the image somewhere? I would like to run Armbian on my Jetson Nano 2 GB, but Armbian_community_25.11.0-trunk.367_Jetson-nano_trixie_current_6.12.54_minimal.img and older images won't boot. I have tried images repeatedly over the past six weeks, but none of them will boot. It would be a shame if the Jetson Nano 2 GB ended up as electronic waste.

If it isn't the PSU or SD than I'm not sure. The only REV available in the STATES "which is where I am" is the 2GB. The u-boot patch set is identical to the BPI-M4-Zero "minus the dts and defconfig of course". All my testing has been done with the unit I have available to me. It works with the Armbian, KIckpi and my own personal builds. As an aside the Kickpi web site is down for me STATE side. Not sure what that means? Doesn't look good though. Anyway, I'm out of ideas. Sorry.

I dd the armbian.img > emmc. and remove my sd card still the same output

I learned today that the cpudriver is the default which caps all cores at 480000 and refuses to respond to govenor or maxes or mins. Currently digging through the armbian build system to get the rockchip kernel source info to manually compile the rockchip_cpufreq.ko and I did see that the patchfiles (irrelevant for cpufreq) contained this: - "MAINTAINERS" # constant churn, drop them. sorry. - "Documentation/devicetree/bindings/arm/rockchip.yaml" # constant churn, conflicts on every bump, drop it. sorry. Given the fact that the build system says it's dropped and the forums say it's dropped I only expect support for the 5b to worsen over time. For anyone reading this, It's best to start looking for replacements for armbian for this board. The 5b has been tossed overboard by armbian, and there will be more breaking changes for it like the emmc that noone from the armbian team will care to fix or investigate. For anyone else going down this rabbithole, allow me to save you some time vendor) BOOTDIR='u-boot-rockchip64' declare -g KERNEL_MAJOR_MINOR="6.1" # Major and minor versions of this kernel. declare -g -i KERNEL_GIT_CACHE_TTL=120 # 2 minutes; this is a high-traffic repo KERNELSOURCE='https://github.com/armbian/linux-rockchip.git' KERNELBRANCH='branch:rk-6.1-rkr5.1' KERNELPATCHDIR='rk35xx-vendor-6.1'

Yep enabled the module and it's working now, Just sent a PR. Thank you.

Using mainline, which this img does, I have only had issues when the PSU isn't up to snuff. A 5V 2A should be enough, I use a 5V 3A usually. My only other suggestion would be; dd off the u-boot and OS from the eMMC and see if that helps.