All Activity

I normally like building server images because they are small and fast to compile. An then I can add the wanted desktop by "sudo apt install gnome" or other desktop later. But, sometimes I wonder if the desktop images have more features, like hardware drivers, than a server image with an added desktop afterwards. Can this be the case? Or does server images contain the same drivers and hardware support as a image built with a destop included?

After building many images, often there are combinations of kernel, sbc card and linux base that will just give an error, like this one: Getting sources from Git [ kernel:6.1 rk-6.1-rkr5.1 ] fatal: detected dubious ownership in repository at '/home/steven/build/cache/git-bare/shallow-kernel-6.1' To add an exception for this directory, call: git config --global --add safe.directory /home/steven/build/cache/git-bare/shallow-kernel-6.1 [💥] Error 128 occurred in main shell [ at /home/steven/build/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged() --> lib/functions/logging/runners.sh:193 fetch_from_repo() --> lib/functions/general/git.sh:129 kernel_prepare_git() --> lib/functions/compilation/kernel-git.sh:20 do_with_hooks() --> lib/functions/general/extensions.sh:567 do_with_logging_unless_user_terminal() --> lib/functions/logging/section-logging.sh:97 compile_kernel() --> lib/functions/compilation/kernel.sh:35 artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:240 artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392 main_default_build_packages() --> lib/functions/main/build-packages.sh:102 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] Is there an easy fix for this, or does it mean that the combination of build options are not valid?

Since I'm not capable of writing any code, how much do i have to donate to get it added? :-)

I've attached the .xsession-errors log file content. As in regards to updating packages.... I always update my board every time I start it and I don't really pay attention to what it updates as I always update everything. After you mentioned about xsession errors, I noticed that in the bottom left corner there was a drop down list with the xsession (wayland and X11). I saw that by default Wayland is selected and when I selected X11 it just worked. xerror.log

moved

Probably because nobody implemented this yet. Feel free to do so and send a PR.

moved

Use edge or vendor for more features. current will stick to 6.12 LTS kernel which will receive fixes only.

Ok, maybe I made a mistake before. I tried with an no secure-boot .img file and it give a long list of DRAM params and I put it in the file below. But I don't know What I can do with it... I will appreciate your help. Thanks. DRAM_Transpeed_M98txt

I received my new LCD today. It is a 9486 but luckily it worked with my 9488 dts HOWEVER: The touch xpt2046/ads7846 is not sending any events…checking with evtest… same dts works with the ili9488 4.0” I already tried changing the GPIO polarity (level and clock transition) has anyone worked with any of the red 3.5 lcd ili9488 or 9486

Thanks again @Nick A, I already did it, the file I got, cant understood well, and there are very low information about dram, just 3 params dram {phandle = <0x7a>;}; vcc-dram = <0x04>; dram = "/dram"; dtb.0.dts

I don't think increasing the SPI clock can help Try adding "BGR=<1>;" under the rotation line... this works for the ili9341, but i dont know about the driver that you use.

Hi Dan, how did you go with this one. Any luck? I didn't know these chips supported sleep and hybernate modes.

hello, agesome! The same thing happened to me, test 20mhz (20000000), I suggest increasing above 32mhz and test. I'm using mine at 46mhz and it's normal, but it used to give an error, it wouldn't update the screen, it would freeze, now it's normal because I disabled “dma-names=””;” Try it and let me know.

I tried, unfortunately the other one I have here at home doesn't recognize when I use it. To try another one, I'll have to buy a new one... =(

I have uploaded an updated version here. Also, for thoses who want to use internal emmc (boot without sdcard), you can run this script: You can reinstall android using this, connecting DQ08's usb2 port (using a male-male usb cable) to the computer while pushing the button in the AV connector. Then, in the app (extracted to c:\), choose firmware / firmware.bin / restore / run.

Armbian_community_25.5.0-trunk.538_Orangepizero2w_bookworm_current_6.12.23_minimal.img When try to boot. It get stuck trying to boot from emmc. It does not have emmc. After several power restart sometimes it boots form microsd. also it ask for tags which has only one option "Solved". I had to tag this topic as solved in order to be able to submit it.

It could be a problem with the solder Buy a board from https://www.armbian.com/partners/

I have noticed that when building images using the same kernel but selecting Ubuntu or Debian base (Bookworm vs Jammy), some hardware doesn't work on one of the images. Since the kernel is identical, why is not the hardware support the same? Is there a different build script for the two bases? Different userspace drivers? Just wondering..

I was hit by this on a fresh install (after I had to replace my SSDs due to SMART errors). Can confirm that Armbian_community_25.5.0-trunk.538_Helios4_bookworm_current_6.6.90_minimal.img.xz now boots and works again. Thanks, @djurny for your great work!

hey so i have a rk3328 tv box with 1gb and 8gb flash , wanted to install linux on it for fun , but failed here is what i did. i couldnt boot from sd so followed (https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453) the file in the comment was unavailabe so i got the MiniLoaderAll.bin from here (http://112.124.9.243/dvdfiles/RK3328/tools/) everything with rkdeveloptool went okay , but after flashing the image on the emmc it still didnt want to boot , but now i could boot multitool from the sd card and flash the image from there. however still nothing , tried to burn the image directly on the sd card and boot form there but still doesnt boot , tried rkdeveloptool again , nothing , but now i cant even use rkdeveloptool , when i plug it to my laptop "lsusb" doesnt even show it . it still boots form the sd card with multitool and thats it . it only boots when the sd card has multitool. tried flashing it a few more times from multitool but still nothing. is it bricked? also sorry if the post is hard to read , my english is not good and im new to this stuff. help appreciated / i dont know how to get my device's dtb / the only dmesg i found was inside multitool message (3).txt

During the installation process of Armbian you set admin password, make a new user, set time zone and system langue, BUT not the keyboard layout... Any reason this is not part of the default armbian install process? Keyboard layout should be the first option to set during boot.

I just tested the latest, 2025 May, built image with default/recommended options and there are some missing features. Here is what I have tested: LAN yes WiFi yes BT yes USB3 *partly, some devices are not detected at all, some will take a few minutes before detected* GPU Mali-G610 (Panfrost) HDMI audio *no* Fan control yes temp. sensor htop *no* Temp. sensor Gnome *no* Other: some cursor graphic glitches Armbian-unofficial_25.05.0-trunk_Rock-5c_noble_current_6.12.28_gnome_desktop.img Any ideas on how to get more features supported?

I hope the topic is on the right place ? It should only be a hint ! Kernel 6.12.20 for the banana Pi M2 zero doesn't support USB. I fixed this by reinstalling kernel v6.6.75. Regards Bernd

@rafaeldavid Try a different sdcard.