Active threads

I understand, but would I be able to do it officially?

Also Check your PSU if the problem is intermittent.

In one post here I saw a "please buy hardware we recommend" quote, and I appreciate that, but I wasn't able to find a recommended boards list - is there even one? Or should I just use the standard/platinum support filtering on the main page? Anyway, I could also use some help / recommendation for a general purpose SBC as I ... didn't by one for years. I'm looking for a more recent SBC to run a small, low power server (think pihole, homeassistant, zigbee, etc). I don't have specific requirements, but I'd like the board to have some kind of "long term support" and I'd also like to choose something that the armbian team would recommend, maybe from a manufacturer that supports armbian directly, or at least provides good documentation. Headless install, may use GPIO, at least 3 USB ports, built-in ethernet + wifi + BT (not sure if there's an SBC that would support zigbee natively?). And also, avoid using an SD card. Ability to use eMMC or SSD would be important. Where I'm coming from: I still run two first-gen Raspberry Pis as webcams + dataloggers (the 26 pin GPIO ones with 256 and 512 MB RAM respectively) and I used OrangePi One and Lite as two surprisingly stable servers for years (one a small postfix mailserver + datalogger, the other even running 4 docker containers). I like using low-level hardware to its limits🙂 I have recently upgraded to an already outdated OrangePi PC+ that I found in the drawer - at least it has 1 GB of RAM and I was starting running into limits with the 512 MB ones. So yeah - I don't need the top of the range SBC but something ... reasonably priced (think ~40 €) that will run well for years to come. I heard good stuff about the Radxa boards with Rockchip SoCs but I have no experience as I haven't bought new SBCs in ... years. Thanks in advance 🙂

In this final article of a three-part series, I look at locking with C++ and Matt Godbolt's notion of CADR. View the full article

Hi, I got new H96 Max M9S and would like to ask some questions before flashing armbian on the device. 1. In this thread reset button is mentioned and I cannot find one on the case and neither on the board. Is there o photo of it or is it another name for maskrom switch? 2. I intend to flash from Linux, is the following method correct: - put device in maskrom mode - connect it to a computer by a USB A-A cable (to USB 2.0 port) - on a computer: rkdeveloptool ld (to list recognized devices) - on a computer: rkdeveloptool db RK3576_MiniLoaderAll.bin - on a computer: rkdeveloptool wl 0 h96_max_m9s_rk3576_20240930_1033.img - restart H96 Max M9S I also have a question regarding building Armbian image: which dtb file should I use to put in directory build/packages/blobs/h96-m9/ (is it H96-RK3576-BOX.dtb)? Best Regards and keep up the good work.

Having trouble with my klipper accelerometer every time the dtb is upgraded during a update/upgrade. I made this patch to fix the spi@5011000 { ...} section: 831c831 < status = "disabled"; --- > status = "okay"; 834a835,840 > spidev@0 { > compatible = "armbian,spi-dev"; > reg = <0x00>; > spi-max-frequency = <0xf4240>; > }; > And then dtc -I dtb -O dts -o sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb patch -b sun50i-h6-orangepi-3-lts.dtso opi3lts-dtb.patch dtc -I dts -O dtb -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb sun50i-h6-orangepi-3-lts.dts Not sure if this is a sane and safe way to do it, but it works for me at least. Hope it can find it's way in a sane form into a future release. Maybe it's better to do it in an overlay, rather than directly? opi3lts-dtb.patch

Hi, Not an expert here, but some educated guesses would be related to either timing, blocksizes towards the devices. Anything that might change or increase the amount of ATA commands towards the disks would be my bet to look at. You could experiment with enabling/disabling NCQ, reducing read-ahead, increasing chunksizes in case you use [software] RAID, increasing caching by tweaking vm options. Perhaps even the IO schedulers, there might have been some new IO schedulers introduced on the new kernel that show different behavior compared to the older kernel, etc. Groetjes,

Hi, If you want to know which kernel is used for your build, just run: ./compile.sh inventory-boards This will take some time. Open the resulting .csv file, which will contain all combinations possible. Groetjes,

Thanks for the detailed description! Very useful post, especially for those who are just starting to tinker with Armbian on TV boxes. I had a similar situation with another S905X3 box - neither Wi-Fi nor Bluetooth worked, and there was trouble with HDMI audio. Special thanks for the advice on disabling unattended-upgrades and systemd-networkd-wait-online, I just encountered problems with long loading, now I understand where the legs are growing from. Regarding USB audio - an excellent solution, I didn't even know that it was so easy to bypass the lack of built-in sound. I will try with a similar adapter. If you have a chance, tell me later whether you managed to set up Wi-Fi via a USB adapter or in another way. And I wonder if you tried other window environments besides XFCE? LXQt, for example? In any case - a great guide, thanks for your work!

Description Currently, PocketBeagle 2 edge images cannot build (without patch 1) and fails to boot (without patch 3). The patch one just defines the missing variable for OPTEE. Patch 3 specifies root using path instead of UUID. For some reason, UUID does not work with PocketBeagle 2 U-boot. How Has This Been Tested? Tested on PocketBeagle 2 rev A0 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description The idea is to introduce the possibility to cache downloads from GH runners to lower downstream bandwidth used and increase overall speed. Especially on machines with lots of runner this could save quite some bandwidth while sacrificing disk space. http caching has been tested and seem to work nicely. https caching is a lot more tricky and may be introduced later. This PR has two parts: set apt repository to http instead of https where possible. Packages are signed anyways. Pass various proxy environment variables to docker so it respects those. Doesn't make sense not to pass them since when using PREFER_DOCKER=no and any of these variables are set beforehand they just work. So this more or less just harmonizes overall behavior. There is still an issue on line 4838 caused by https://github.com/armbian/build/blob/c0da65087aad628ba0714f23d8d29800f152d97c/lib/functions/rootfs/apt-install.sh#L67 due to absence of apt proxy setting there. Not sure why this is not added here? How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] build random image: https://paste.armbian.de/xopitiguyo , look for 10.100.0.87 to see where it is used [x] built the same random image but having all proxy env variables unset beforehand: builds just fine as well: https://paste.armbian.de/ozidivugor Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. This PR adds the RT kernel config file for TI devices. If RT_KERNEL=yes is passed as an argument to ./compile.sh, a PREEMPT_RT image is built. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. Tested this on SK-AM62B. Test 1: boot test: the board successfully booted Test 2: uname -a test: PREEMPT_RT string was present in the output, thus suggesting that its indeed an RT image Test 3: zcat /proc/config.gz | grep -i RT: Further confirmed that the PREEMPT_RT config is enabled in the running image Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] My changes generate no new warnings cc: @glneo @Grippy98 @nmenon @sadik-smd View the full article

direct boot from nvme isn't possible. Boot loader (u-boot to say) must be present on SPI, eMMC or microSD.

try: sudo gpg --keyserver keyserver.ubuntu.com --recv-keys 93D6889F9F0E78D5 sudo gpg --export 93D6889F9F0E78D5 | sudo tee /etc/apt/trusted.gpg.d/armbian-configng.gpg > /dev/null

sudo armbian-config

Put a multi meter on the PSU you are using to power the pi a flakey PSU can cause strange intermittent issues same for router.

Related issue: https://github.com/armbian/build/issues/8261 Currently resolved for the beta repository. Now it's possible to switch to beta, update base-files and switch back to `apt.armbian.com`. Fixing for stable marked as "todo".

Ok that is a promising start at least. Are the 'BUG: bad page state messages' every boot or occasionally? The route cause will probably be difficult to find, possibly a deep route kernel or hardware issue. I tend to find that sometimes I will get the bad page state messages and then on another occassion get no kind of faults. You shouldnt need to enter any credientials on first boot, that only applies to setup over network connection. Once you have been able to login and if wireless works then you can install memtester to see if that picks up an errors. not a problem, looking forward to hearing your progress Ryzer

Hi pcduino2user, Nice to see a fellow Pcduino user, I guess not many people interested in over a decade old hardware at this point. I try my best, I am by no means an expert, most of my current changes are just corrections to the device tree. Anyway, there appear to breaking changes in kernel 6.12 which breaks hdmi output. The intial patches for adding the hdmi display nodes are in my pcduino2-and-3-improvements branch however they are for much older kernel versions so need to be re-created, something I plan to do within the coming week. Additional the display driver needs a minor tweak. I currently have a userpatch derived from: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20241130-hdmi-mode-valid-v5-10-742644ec3b1f@linaro.org/ Thanks Ryzer

@usual user But the filesystem was never currupt and the issue was only with the boot partition which is not a journaling filesystem. The Odruids is also known to work reliably without UPS.

Description Update odroidxu4-current kernel to 6.6.93. How Has This Been Tested? [x] Reboot of my Odroid HC1 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

But my "overlays" have something very important provided by armbian - Panfrost GPU support. Is there really no way to make them work together?

Hi @Faheem, are you do it armbian install and working in this board? I use rk3228 boxes and want know more about this H313 boards, i see a mx10 with this chip in aliexpress, but before to buy, i should want sure it working linux! The H313, is it too problematic so or not? Thanks!

Question. Are there any owners of this R57 model?

Description The current script can overwrite drivers which are set as built-in in the board-specific config. This is not desirable. Add a check to ensure we do not convert built-in stuff into modules. First encountered it when pocketbeagle 2 kernels was enabling EXT4 as module instead of being built-in, which makes the current rootfs (using ext4) fail to run. How Has This Been Tested? Tested on PocketBeagle 2 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article