Search the Community

My Banana Pi M2+ is running quite fine on noble but something is amiss with bluetooth. bluetoothctl never shows any devices even when scanning for them and there are plenty of devices within arm's length. I am hoping for your help in diagnosing and ultimately fixing the issue. Logs:

Dear Community, I'll build a Developer Team specially for Banana Pi Boards!" GPIO Libarys I started updating/modifing the old GPIO-Libarys, so they can be used on the latest builds! I want to build a Team, for GPIO-Libary Development, for porting these Libarys: WiringPi-Node WiringPi-PHP WiringPi-Perl WirinigPi-Ruby gpiozero rpi-gpio Updating and modifying these: RPi.GPIO BPI-WiringPi2-Python BPI-WiringPi2 At the end, all currently working GPIO Libarys are: luma.oled RPi.GPIO BPI-WiringPi BPI-WiringPi2 BPI-WiringPi2-Python Armbian Build System for Banana Pi I started building the build-system for full banana pi support! Anyone who would like to join the developer-team, just pn me, post in this thread, or contact me on github or discord!" I created a GIthub-Organisation for this project and a Discord Server. A Domain & VPS Server is commin Monday!" Goals: Support ONLY for Banana Pi Boards Board Determiner Script which exports Board-Infos, required by gpio-libs (usual located at: /var/lib/bananapi) APT-Mirror Archive Hosted by our project-teams vps-server! ( Mirror stores all latest gpio-libarys we specially build for using on latest builds and other packages we'll develope in future) Added APPGROUPS: Pentesting, TV-Box, Server-Side, Game Desk & Development Revised menu for selecting extensions and other additional items Revised config menu Adding additional build options A Web-Based Project-Server Hosted Build-System will be build and available on the project-page, where you can build images remotely, according to you settings made in the WebInterface, with live progress & build-log + downloading compressed own image-release. A publish option will be added to, where you can upload your builded image to any Cloud/Storage we provide. Revised device trees According to APPGROUPS and Enabled Extensions: I2C, SPI, UART are enabled in the gpio_develope extension, and all requirements for gpio-programming are pre-installed, the gpio libs are pre-installed too. If you have some Ideas, what we could add or which wishes we can make true, just reply in this post, or contact us. Github Organisation Discord greetz, hexzhen3x7

Hello, I am curious to hear how accurate the measurement of temperature is from the onboard sensors, particularly in my case for the Banana Pi M2+. While I do understand that the BPi M2+ suffered from poor choices for thermal management from the manufacturer both in hardware and software, I believe that thankfully Armbian has worked out the kinks on the software side, hasn't it? I am running the latest noble image, here's what I noticed. The temperature as shown by the sensors and armbianmonitor commands never really goes below 60° even on idle with ambient temperatures of around 25 to 30 degrees. My SBC already came with a small heatsink attached to the CPU. I found that value pretty high and inquired with an infrared thermometer but couldn't really find a spot on the board over 40°. Which makes me wonder if the reading is accurate and properly calibrated? My impression is that it is not. Furthermore, I noticed the board behaves quite well under load. For example, I stress-tested it with the yes command on all cores for about an hour or so and while the temperature went up to 95°, it appears the software was well-tweaked to only slightly throttle the CPU (verified with armbianmonitor -m) to not exceed this. I am not 100% sure about the thermometer readings, but I believe they were around 60° at the time, certainly nowhere near what sensors was showing. I have been testing the board for about a week now and I have to say that one time, the board did indeed shut down due to thermal overload. Interestingly, this wasn't even when the CPU was heavily loaded but there was a lot of IO wait. Temperature was high and it briefly shot up to 101° (ouch) which triggered an emergency shutdown to prevent thermal damage. Looked good to me, mostly. So, again, my question today is how trustworthy are the readings from the sensors, are they properly calibrated?

Hello, long time Banana Pi user here. I have a BPI-M2+ and recently decided to write Armbian_23.02.2_Bananapim2plus_bullseye_current_5.15.93_minimal.img to emmc. I am using cat6 over gigabit LAN and am seeing scp and rsync transfers to the device averaging 1.7mb/s. Transfering an 850mb file took unusually several minutes. It starts off at 40mb/s then quickly drops to under 2mb/s. Is this typical? I would think over LAN I would be seeing much faster speeds. Untarring this same 850mb archive also took unusually long. Could the emmc be damaged or on it's way out? How would I check? Please see armbianmonitor output. https://pastebin.com/RCaPzUEz

Hello everyone, I am an old-timer in Debian and Ubuntu and have uploaded and maintained packages there. I've come across an issue in a package that I use that affects 32-bit platforms such as armv7 but not 64-bit platforms. I've already analysed the problem and applied a fix, compiled the package locally and I'm happy. But I'd like to get the fix into armbian as well so others will not run into this fairly serious problem (for the package in question, it is essentially useless at the moment in noble). I looked through the various github repositories but was unable to see how to apply a patch to a userland package and have it published. Given that armbian systems seem to pull their packages from ports.ubuntu.com, is it that armbian does no patching of their own to packages but instead relies on Ubuntu and Debian to land their fixes? If that's the case, I've already started the process but I'd like to know if there is an armbian-specific way of fixing userland as well. Regards

https://paste.armbian.com/faquvejaxo works ok for my alternate 2G4 network. Scanning wifi does not show any 5G8 networks. From dmesg: bananapim2plus:brcm:% dmesg |grep -i brcm [ 7.495253] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 7.497405] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.bin failed with error -2 [ 7.497440] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.bin [ 7.871128] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt failed with error -2 [ 7.871159] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt [ 7.993563] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 7.995261] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 7.996183] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2016 11:30:56 version 7.45.77.h8.4 FWID 01-ee8a6268 [ 18.307085] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch not sure if or how to apply hints from here thank you for all your work

Hi, I could enable "spidev" support by armbian-config -> system -> hardware (enable spidev) . Everything worked fine. However, the original spidev module supports messages only up to 4096 bytes. I compiled a new version of custom spidev.ko with the 32,768 buffer size. Then, converted it to spidev.ko.xz ( xz -v spidev.ko) and replaced the original file under /lib/modules/5.15.85-sunxi/kernel/drivers/spi/spidev.ko.xz The new module works fine when I install it manually: insmod /lib/modules/5.15.85-sunxi/kernel/drivers/spi/spidev.ko.xz However, after the reboot the original 4096-byte version of "spidev" module is loaded magically. It is loaded even if I remove the /lib/modules/5.15.85-sunxi/kernel/drivers/spi/spidev.ko.xz file. I searched through the whole micro-SD partition and cound not find any copy of spidev.ko.xz or spidev.ko Would you please explaine the mystery ? Thanks in advance

Hello, could be possible to introduce the package with newest available GDB 13.2? The version 13.1 is rather unusable — it segfaults on regular basis.