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)