All Activity

I opened PR #9590 with the really minimal change that's needed to get my desired behavior back.

@Nick Acutecom.log log2.txt Here's how it looks right now, booting from an SD card on which I flashed the mainline U-Boot to boot the image.

I'm still working on getting the kernel compiled, but in the meantime I may have found where the option disappeared, back when 6.18 was still edge. https://github.com/armbian/build/commit/2a38243de9ff01e079b6ec0c930c00f892e163aa#diff-003c7426ff865cb4e5d2d17e324129fe9de266da1f83a11e290670929e55036dR10-L675

OK I think I have learned something. My fstab entry doesn't contain an entry like x-gvfs-show which i believe makes the disk appear in the UI (desktop icon and in Thunar?? I found this by comparing Gnome Disks settings for the SATA drive, which according to disks is mounted at mnt/data. Good. So next task is to install and configure SMB to share the root drive on the network ideally without the necessity of entering a password. So path should be /mnt/data?? and do I require Valid Users entry? Finally do I need smbpasswd.. Note users accessing will be from Windows 11 pcs and mobile phones (iOS) path = /mnt/data available = yes valid users = kealy read only = no browsable = yes public = yes writable = yes

Hello @lewa_j! Thanks for the explanation. As long as https://docs.mesa3d.org/drivers/powervr.html lists BXE-2-32 as unsupported we stick to the blobs. Of course, you are free to check this for youself, see compiling "getting started" above. HTH // Sven-Ola

Sorry for what should be help on a basic operation but I'm having real problems trying to share a SATA attached hard drive via SMB. My aim is to try and share the root of the whole 1Tb drive but I have two problems. 1) Getting the drive to mount at startup. (I thought internal and SATA drives did by default but this seems not to be the case 2) Creating a share with guest permissions. I understand that I should edit the fstb file using the UUID of the disk. I obtained the UUID but there are two listed. One for the whole disk and one for the partition. (Note The hard drive was formatted exFat in windows before being attached as whatever i did i couldn't write to it, something to do with having root permissions. I even tried taking ownership but without success) here is the blkid command output /dev/sda1: LABEL="data" UUID="74E3-01BF" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="6c2b2d10-01" /dev/mmcblk0p1: LABEL="armbi_root" UUID="69fa8a60-c365-456c-8d0a-7889eb4a3713" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c0cf2841-01" /dev/zram1: LABEL="log2ram" UUID="7269c460-6283-4374-bcba-be885c806c25" BLOCK_SIZE="4096" TYPE="ext4" /dev/zram0: UUID="7a1deaea-e26c-45f2-9a73-ac43c6bf301e" TYPE="swap" here is my fstb file UUID=69fa8a60-c365-456c-8d0a-7889eb4a3713 / ext4 defaults,,commit=120,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=74E3-01BF /mnt/data exfat defaults 0 2 I used the disk UUID rather than the partition however the disk is no longer visible when armbian starts. previously it was visible but unmounted. there is an entry in the /mnt/ folder called data. I was also unsure if I should enter the filetype exfat in the fstb entry as all other example show ext4 before defaults. Please can someone put me right and suggest the correct entry in the smb.conf file. I believe it should be something like this :- path = /media/kealy/data available = yes valid users = kealy read only = no browsable = yes public = yes writable = yes However as there is an entry in the /mnt/ folder should path be /mnt/kealy/data instead? Finally where should the user password go in the smb.conf or is public= yes is this necessary. The device will only be used in a family household to upload their photos from their phones.

Diagnosing System Issues and Getting Support with ArmbianmonitorArmbian is a lightweight operating system based on Debian/Ubuntu, highly optimized for single-board computers (SBCs) like the Raspberry Pi, Orange Pi, and many others. When facing system problems on an SBC running Armbian, the built-in utility armbianmonitor is an essential diagnostic tool. It quickly gathers crucial system data, making troubleshooting faster and more accurate for both the user and the community providing support. Key Diagnostic FunctionsThe primary use of armbianmonitor is to generate real-time performance and system configuration reports. By running the command without any arguments, you get a menu of options, but the most vital functions for diagnosis are: System Status (armbianmonitor -m): This provides a live monitoring dashboard. It displays key metrics like CPU frequency, load average, temperature, memory usage, and disk I/O. By watching this output while a problem (like a system freeze or slowdown) occurs, you can often pinpoint the bottleneck—for instance, a sudden spike in CPU temperature indicating a cooling problem, or sustained high memory usage pointing to a resource leak.System Information (armbianmonitor -u or -d): This is the most crucial function for seeking online support. It gathers a comprehensive, anonymized report including details about the kernel version, device model, installed packages, boot logs, and hardware configuration. This data is essential because the performance and stability of SBCs are often highly dependent on the specific kernel and hardware drivers used for that model.Getting Support OnlineWhen seeking help on platforms like the Armbian forum or GitHub, simply describing the symptoms is rarely enough. The person helping you needs to know the exact state of your system. By running armbianmonitor -u, the utility uploads the detailed diagnostic report to a public pastebin service (like https://www.google.com/search?q=paste.armbian.com) and provides a unique, short URL. You can then include this URL directly in your support request. This allows community members to instantly access the exact configuration, eliminating back-and-forth questions about device type, OS version, and log file locations. This standardized method is the fastest way to receive targeted, effective assistance and ensures your issue is diagnosed accurately. View the full article

Nice! I actually did something similar. In my case I ended up using an old PWM fan I had lying around, powering it through the 12V pin input. Then I used ground on pin 6 and the PWM signal from GPIO pin 11. I wrote a bash script and set it up as a service that controls the fan speed based on five temperature levels. Right now I’m running it on FriendlyElec CM3588 NAS with Armbian Linux 6.1.115-vendor-rk35xx (v26.2 rolling). The repo is in Spanish for now, but I’m planning to translate it to English soon: https://github.com/jgomezriesgobancario/cm3588-fan-controller **edited** Fix typos

@sven-ola CONFIG_POWERVR_ROGUE is for proprietary blob userspace drivers. CONFIG_DRM_POWERVR is new mainlined kerner driver (drivers/gpu/drm/imagination) for use with opensource mesa driver (main/src/imagination)

https://forums.kali.org/ There is an arm64 section.

Feel free to use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=nanopineoplus2notsurehowitsnameis BRANCH=current kernel-config and then build a kernel packages with the adjustments. Once installed and tested, you can PR to these kernel config here: https://github.com/armbian/build/tree/main/config/kernel

I suggest to ask directly at kali forums/chat/whatever they provide. We offer Armbian images with Kali tools pre-installed. However about their usage we cannot help

Does this forum support Kali in Raspberry Pi? Raspberry Pi Forums do not.

Thank Igor that explains it. I'll look at your suggestion or just go back to an SMB share

Hi! Yesterday I upgraded my NanoPi Neo Plus2, during that the kernel version went from 6.12.74 (package version 26.2.0-trunk.478) to 6.18.19 (package version 26.2.0-trunk.626). This morning I noticed, that this kernel is missing the dm-snapshot.ko module. I searched the forum if anyone else is having this problem, but it appears I am the only one using this feature. I use snapshots to create consistent backups of the system. Is there a reason why it was removed and more importantly is there a way to get it back without having to compile the kernel myself? Greetings PS: I should note, that I want the module back in newer kernel versions in the future. For now I downgraded to some older version that I was able to find a package for and got it working through that.

The same issue has occurred again. I had to take this measure again today to fix the zfs module. I had to revert the kernel, headers and dtb back to 25.11.2 from 26.2.1 of linux(meson64:arm64)

Hello. I installed Armbian 26.2.1 Minimal Debian 13 (Trixie), but the Wi-Fi still doesn't work. It doesn't connect to the AP during initial setup. After reconfiguring via armbian-config, it works until the first reboot.

moved to staging

Currently just hangs after the Loading kernel message, will provide a log with increased verbosity tomorrow

@boggy do you have a boot log from armbian?

@Nick A Hi, thank you for the quick response! So far the attempts to boot the transpeed image would hang during boot most of the time, but I did manage to get a working shell once, albeit still without any networking. The WiFi chip is BCM4334, the physical print on the chip wasn't too helpful, but in either case it's the exact same model as shown on the pictures on this article https://linux-sunxi.org/T95 (4/32 version). I can't currently test HDMI but it is attempting to load Plymouth despite the config specifying otherwise. I attached a boot log of the stock Android image, if it helps at all. Thank you so much for helping out, I really appreciate it! androidbtlog.txt

They don't provide images for armhf anymore. Last build was 3 years ago: https://hub.docker.com/r/owncloud/server/tags?page=1&ordering=last_updated&name=v7 We made a notice that its compatible for amd64 and arm64: https://docs.armbian.com/User-Guide_Armbian-Software/Media/#owncloud but our installer doesn't filter that out yet. Official Docker way, it won't work. Try something else, perhaps

@boggy Try my Transpeed 8K618T image. It includes the most critical DTS settings for this hardware. All your Dram settings in the dts have dram_type = <0x03> or DDR3. dram_para1 { device_type = "dram_para1"; dram_clk = <0x258>; dram_type = <0x03>; cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ sdmmc@04020000 { compatible = "allwinner,sunxi-mmc-v4p1x"; device_type = "sdc0"; . . . cd-gpios = <0x53 0x08 0x10 0x06 0x01 0x03 0xffffffff>; can you find the wifi chip on your board?

I am resurrecting a Banana Pi M1 that i've had in the cupboard since new. I've downloaded and installed Armbian 26.2.1 build date 03.02.26 rev 5abb97453. I want to use the SOC as a photo repository for a family member so they can use PhotoSync app to transfer their photos as a home NAS. I have attached a 1Tb 2.5" hard drive and was goin to set up and SMB share but notice in Armbian Config a software package for OwnCloud which looks perfect as it can be accessed via a web browser. I have tried installing OwnCloud from Armbian Config and it installs docker but then fails downloading the Owncloud package. The error is: Unable to find image 'owncloud/server:latest' locally docker: Error response from daemon: manifest for owncloud/server:latestnot found: manifest unknown:manifest unknown I've tried running Docker pull and it appears to have downloaded something but the file is only around 4kb. Ive also tried downloading an image from OwnCloudeu server but it cant find a ARMv7 image. I'm wondering if having a hard drive attached means the daemon is looking for the image on the local drive??? could someone please point me in the right direction to installing Owncloud Also I assume the standard install, docker runs a container in the Armbian file system. Obviously I want the storage to be on the 1Tb hard drive. can you choose a storage location in the Owncloud setup? many thanks

@Nick A I have one of those T95 H616 AXP313a tv boxes. I have successfully compiled a mainline U-Boot image and it boots fine, all with UART input/output, but none of the images from your github repo work. I only managed to boot MiniArch images up to 6.19 kernel but I couldn't get HDMI, Ethernet, WiFi or Bluetooth to work at all. Got any idea what could be missing? I can help in debugging if you'd like. I attached the extracted and decompiled DTS from the stock Android 10 firmware of the device. Thank you extracted.dts