Active threads

Klipper Load Cell Documentation The kx711 is specifically referenced near the bottom of the documentation. It needs slow speeds and I believe has been incorporated into recent Klipper releases. I posted the file output on graphics, framebuffer and drm to @Torte github link. Also found an informative YouTube video on adding a Klipper Touch Screen, over serial, and configuring it. I'm adverse to tossing electronics into landfills - motivation to invest some time into a build for the Sovol boards and tolerate the mksclient propriatary blob. If the touch screen proves to be a show stopper,

In the meantime, I fixed internal audio for "edge" (was: missing headphone GPIO). And also investigated around the esos.elf RTOS firmware. There's a license for that, which I added to my tree. The license basically says: use but do not infect with GPL: https://gitee.com/spacemit-buildroot/buildroot-ext/blob/k1-bl-v2.2.y/board/spacemit/k1/target_overlay/lib/firmware/LICENSE.spacemit_esos. Continuing on kthread issue. LG // Sven-Ola

What happens if your start armbian-resize-filesystem.service manually? IE "sudo systemctl start armbian-resize-filesystem.service" and then check the log for the service?

You can create an extension including something like unset armbian_kernel_config__force_pa_va_48_bits_on_arm64

Nevermind, got the answer from here.

If you can get the unit in the proper state by shorting, you can flash an android img or custom one using this tool; https://github.com/natinusala/linux-amlogic-toolkit Other repos that you may find useful: https://github.com/mluis/aml-flash-tool https://github.com/Stane1983/aml-linux-usb-burn

@Dangrain There is a paragraph Partecipation and debugging with the suggested operations to let other people help you in a proper way and perhaps improve support for your board in the mainline armbian codebase. You may want to go your own way, but then helping will be much harder.

I would like to say thank you very much to @sicxnull for the latest images of X96Q V5.1. They work really well and allow me to install HA as well as use it like a PC. You really did a great job!

Interested myself in the 3W in general, and if I can find them anywhere. They have the proper chip for a zero form factor board to use with the Radxa 5C and 5A, and several other boards. So I've looked, but they seem to have been outdated by the better zero form factor boards... which also seem to have a specific chip type, and aren't really compatable with the other chips if you're trying to give yourself some headroom to run clusters or offload some processes. I don't know too much about too many things yet, but I know that I need to stick with 1 chip, like a GPU arcitecture, and I can't find the 3W anywhere for any type of reasonable price. I think I found a few for like $300, but the dream of using this stuff at the top end of what it can be used for is looking grim as I am having troubles finding some of these parts for this more developed chip style. I'm sure in due time, it will all be replaced by the new Radxa zero form factor, along with the Pi form factor which will probably gravitate to this new more powerful model. The Zero board has twice the specs aprox. as the old 3W, which means likley the next Radxa board is comming out swinging to start with 32GB of RAM, and then it'll be updated with 64GB. As they seem to do that... Start half mast, then bring out a new twice as powerful model. Hoping to get my first arm project going, and I wish I knew more about ARM in general before I started focusing on 1 chip style. Radxa is cool, and they are buff as can be, but as ARM evolves, the specificity of board type to the different things you have to do is a big big pain in the ass that makes this whole adventure more painful then it should be... Eventually I'm sure it'll all come together into a standard.... But by then, you can't be a pioneer in the tiny computer parts projects. Hope this thread evolves some. I know just seeing a title on 3W caught my eye, and it's on the top of the list. I'll be getting more involved with all of this in the days to come. If you can message me, feel free. I am pretty Armtarted, and would love any information I can get.

Hello, I had a similar problem - unbootable Rock64 after kernel upgrade from 6.6.x to 6.12.x (error: Wrong Ramdisk Image Format). You can look in this thread djurny found a solution, that works for me. Maybe it will help.

Hi Chris, when I tried to install the headers on my pcduino3nano, there were two options: linux-headers-armmp (or equivalent for your board) and kernel-headers. This secong package name was incomplete, but apt suggested a list of possible matches for my system. Give that a try. Cheers, Gaetano.

I would use systemd. Depending on what application you are talking about, a simple or oneshot service should do the trick. Read the first two examples in the manual: https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Examples Assuming you mean an application started by the system and not your user, select the version that fits your situation, create/edit the file /etc/systemd/system/name_your_service.service with the contents needed, for example: [Unit] Description=Service to start "application" [Service] Type=simple ExecStart=/path/to/application [Install] WantedBy=multi-user.target Then enable the service and reboot. sudo systemctl enable name_your_service.service sudo reboot now You can use "systemctl status name_your_service.service" to see status, or "journalctl -u name_your_service.service" to see logs. You should obv change the name of the service from name_your_service to something fitting. If you want the application to run even earlier at boot, you can change multi-user.target to basic.target instead, but be mindful that if you do that and the application requires for example network to be available, you then also need to add "After=network-online.target". Instead, it's usually better to use "Before" and "After" variables and stay on multi-user.target. Please see manual in link above and https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html for more advanced usage.

Related answer: https://forum.armbian.com/topic/57601-missing-headers-for-618-kernel/#findComment-232075

I'll start on congratulating you for all you have accomplished. Now to your questions. I've never experienced a case where installing to emmc took away the ability to boot from the SD card, nor have I ever heard that reported by other users in the forums. So that one is a mystery. To debug that you would need to find your uart connection on the board and hook up a usb-uart adapter to monitor the uboot process. I would also recommend you try putting your image on a usb thumb drive and see if that works for a workaround. For autologin, you should just be able to follow any standard guidelines for doing that with a google search of 'xfce4 auto login' and you will likely need to edit some config file somewhere to enable this. Exactly what may depend on are you running Ubuntu or Debian userland with the Armbian kernel.

Oh, I do not have a nanopi r3s, and I do not plan to buy it. The image is for the radxa zero 3w, but as I provided the source of building it, you can customize it to build with nanopi, too. The reason I mentioned nanopi r3s is because it has a dedicated case for it. I ended up using raspberry pi zero case for it, with some custom modifications, which is also nice. Raspberry Pi 1/2/3, zero/zero w/zero w2 won't work, because they only have 1 USB controller. The trick here is to have at least 2 USB controllers: 1 in host mode to connect to the UAC2.0 speakers, and 1 in gadget mode as a UAC1.0 USB device. Raspberry Pi 4/5 should work, but you need to make sure the power supply is strong enough, which is a big issue here, because with the official image, you can only connect the USB C port for power and as a USB gadget port, yet PS5 probably won't support that much power for RPi 4/5, so you ended up needing a USB power and data splitter for that, and connect the data port to PS5, then a separate power supply for the power port (simliar things happened in PiKVM).

I am working on a new version of the Luckfox Core3566 Board and Patches, as well as adding the Orange PI CM4 board to Armbian. Both rely on the Rockchip RK3566. Luckfox Core3566 Starting with the Core3566: The current board is just the vendor u-boot and kernel. It lacks PCIe support, but surely it is helpful to be as near to manufacturer configuration in their patches. My board config on the other side is not supporting the vendor specific patches, but based on a clean u-boot v2025.10 and runs nicely with current and edge kernels and also runs smoothly with nvme storage. The luckfox-core3566 config is currently maintainerless, but maybe users would like to have this vendor kernel version. My question: 1) Would the Armbian rather like to replace the vendor board config with a more future proof board config like mine or 2) Keep both board versions ( like rename config/boards/luckfox-core3566.csc to config/boards/luckfox-core3566_vendor.csc ) and let my variant replace the config/boards/luckfox-core3566.csc as default? 3)rd option would be combine both configs, but I had struggle to do so, as my version is using a different u-boot, using a simplified partition setup etc. Orange Pi cm4 I created a new board configuration to let Orange PI CM4 to work with Armbian as well. It is pretty similar to the bigtreetech cb2, but it's ethernet wiring and pcie powering device config differs from latter. Is it okay to create a MR directly in Github or does it need alignment with Moderators first? Cheers, Daniel PS: Nice to have time to work on embedded arm systems again. I did work on the sunxi based cubieboard and cubietruck back in the days, but job, family and basically life pulled me away from it for such a long time.

Feel free to reach out and become a partner: https://www.armbian.com/partners/

LMAO! So... What exactly is your question? Did you try "the mouse & keyboard" and they did not work? I would say you will get basic functionality on almost any usb mouse or keyboard on linux. wifi on the other hand can be a hit or miss. A quick search on "USB Logitech Unifier Nano dongle" gave me this: https://forums.linuxmint.com/viewtopic.php?t=373365 so it seems you might want to use solaar to configure the stuff. As for the Inovato Quadra4K, it looks like it is an allwinner H6 processor so I suspect it should work using armbian....

@Bones558 I think the LED is always on by default and doesn't blink. You can try kernel 5.15, I'm using Armbian-unofficial_25.11.0-trunk_Radxa-cubie-a7z_jammy_legacy_5.15.147.img Since I don't have any TTL modules or display adapters, I directly followed the instructions at https://docs.armbian.com/User-Guide_Autoconfig/ to set up the wireless network. After powering it on and waiting for a while, I could directly access SSH. Hope this helps.

Hi, I'm a long time Armbian user and overall extremely happy. It my default Linux distro everywhere! Thanks to everyone who is developing or contributing to it! Every time I pickup a new board and deploy Armbian I have to edit the `armbianEnv.txt` file and change verbosity to 7. The same question repeats in my head. Why is it not the default? Systemd and startup messages spam up like crazy and they have nothing interesting to offer. I do care what hardware did the kernel detect or was a protocol correctly negotiated etc. I personally would have it in reverse, verbose kernel, quiet systemd. But thats just me. Could we at least have parity, if systemd verbose then make kernel verbose too, if kernel quiet then systemd quiet too. I'm trying to understand what was the rationale for having quiet kernel and verbose systemd? Thanks!!

https://docs.armbian.com/Developer-Guide_Build-Switches/ Check for ARTIFACT_IGNORE_CACHE diy packages are locally cached. automated packages from the CI are stored online in ghcr. not only this, also the status of build framework internals (like stuff in https://github.com/armbian/build/tree/main/lib/functions) since they also can alter a package. "development" should be sufficient.

Build from branch v20250306. error! [ Failed to fetch SHA1 of 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git' 'tag' 'v6.12.11' - make sure it's correct ] How to remove the error?

Does anyone here may have recommendations of standard sdcard or flashdrive that supports for installation on amlogic s905x devices? eg: sdcard only sdhc types or it will work with sdxc or any kind of limitations capacities for certain SBC ? . thank you in advance for your most kind replies. best regards

Hi Lessard can you please check this error (X88 PRO-B-RK3318-D4-V1.6)? root@GREEN:~/tm16xx-display# make module make EXTRA_CFLAGS="-DCONFIG_TM16XX -DCONFIG_TM16XX_KEYPAD -DCONFIG_TM16XX_I2C -DCONFIG_TM16XX_SPI -include /root/tm16xx-display/drivers/auxdisplay/tm16xx_compat.h -I/root/tm16xx-display/include/" -C /lib/modules/6.18.6-current-rockchip64/build M=/root/tm16xx-display/drivers/auxdisplay CONFIG_TM16XX=m CONFIG_TM16XX_KEYPAD=y CONFIG_TM16XX_I2C=m CONFIG_TM16XX_SPI=m CONFIG_LINEDISP=m modules make[1]: Entering directory '/usr/src/linux-headers-6.18.6-current-rockchip64' make[2]: Entering directory '/root/tm16xx-display/drivers/auxdisplay' CC [M] line-display.o CC [M] tm16xx_core.o CC [M] tm16xx_keypad.o tm16xx_keypad.c:81:6: error: redefinition of ‘tm16xx_set_key’ 81 | void tm16xx_set_key(const struct tm16xx_display *display, const int row, | ^~~~~~~~~~~~~~ In file included from tm16xx_keypad.c:18: tm16xx.h:189:20: note: previous definition of ‘tm16xx_set_key’ with type ‘void(const struct tm16xx_display *, const int, const int, const bool)’ {aka ‘void(const struct tm16xx_display *, const int, const int, const _Bool)’} 189 | static inline void tm16xx_set_key(const struct tm16xx_display *display, | ^~~~~~~~~~~~~~ tm16xx_keypad.c:135:5: error: redefinition of ‘tm16xx_keypad_probe’ 135 | int tm16xx_keypad_probe(struct tm16xx_display *display) | ^~~~~~~~~~~~~~~~~~~ tm16xx.h:184:19: note: previous definition of ‘tm16xx_keypad_probe’ with type ‘int(struct tm16xx_display *)’ 184 | static inline int tm16xx_keypad_probe(struct tm16xx_display *display) | ^~~~~~~~~~~~~~~~~~~ make[4]: *** [/usr/src/linux-headers-6.18.6-current-rockchip64/scripts/Makefile.build:290: tm16xx_keypad.o] Error 1 make[3]: *** [/usr/src/linux-headers-6.18.6-current-rockchip64/Makefile:2010: .] Error 2 make[2]: *** [/usr/src/linux-headers-6.18.6-current-rockchip64/Makefile:248: __sub-make] Error 2 make[2]: Leaving directory '/root/tm16xx-display/drivers/auxdisplay' make[1]: *** [Makefile:248: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.18.6-current-rockchip64' make: *** [Makefile:50: module] Error 2 Thank you

Yes. Please wait. I was busy with other personal projects, so I haven't been doing armbian stuff for a few weeks.