-
Upcoming Events
-
-
Volunteering positions
-
Part time technical support
Position: Technical supportNumber of places: 12Applicants: 12
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Activity Stream
-
2
trixie apt warning: "Policy will reject signature within a year"
We already did that. I think the problem is that our keys are not packed (yet) but added at build time. When a person upgrades from Bookworm to Trixie, this will show up, while on new Trixie images this shouldn't manifest. @zital debian Is this the case? https://github.com/armbian/configng/commit/5d866b9b105bfd46cb341c21c70ba76e32e1fea2 We are signing with old and new key (which is aligned with current standards) since then. -
0
ESP-WROOM-32 Module: Crashing under Python Script on Armbian
Hi everyone, I recently got an ESP-WROOM-32 Development Board to use as a companion board for my Armbian SBC setup. My goal is to have the ESP32 collect sensor data and send it to the Armbian host over serial or WiFi. It works okay at first, but after a while running a Python script, the ESP32 crashes or stops sending data. Setup Details: Armbian running on a Banana Pi (or similar SBC) ESP-WROOM-32 connected over serial (USB-to-TTL) and also configured via WiFi Python script (on the Armbian side) reads from the serial port / receives via a simple socket over WiFi Power supply is stable; using 3.3 V TTL logic on ESP and stable USB power Now here are my issues: Script runs fine for some minutes (5–10), then suddenly no data from ESP3. ESP32 sometimes reboots (observed via onboard LED), sometimes appears alive but unresponsive. Logs show no obvious error messages; serial just quiet or times out I've tried lowering the serial baud rate. Added delays / sleeps in code to reduce data flood. Ensured the USB-power to ESP32 is stable / using good cable. Tried Py serial and different socket listener scripts Could USB-TTL or serial USB drivers under Armbian be causing issues (overheating, buffer overflows)? Would switching fully to WiFi (TCP/UDP) instead of serial help stability? Any tools or logging tips on Armbian to catch the crash (kernel logs, serial trace, etc.)? Thanks in advance for any advice. Jordan -
5
How Do You Build With The Latest (Relatively) Stable Edge Kernel, Not The Ultra-Latest Bleeding Edge Kernel?
I don't see it as the very latest bleeding edge kernel version. I see it as a newish Linux, which already has the armbian patches updated for. Some CPUs end up with newer or older Linux versions, due to varying levels of development success. For example, sunxi's armbian edge is 6.15.4 today, but the linux trunk is up to 6.17-rc6 ... (not available in Armbian) -
7
HDMI doesn't work for rk3568 on some displays
I tried it on 6.16.7, and the log started working: [ 4.838111] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device Error again after initialization: [ 5.118148] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 5.637839] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes -
0
Zero 3w Gadget mode
Has anyone ever gotten the Radxa Zero 3w working in gadget mode? I bought a Zero 3w about a week ago and have been beating this horse most of the time. I can't get the device to connect via USB. A or C. When I try to connect (radxa.local) it will always go through wifi. If I have wlan0 disabled or even my internet off it just will NOT connect. It clearly is using wifi to connect even if I use the hostname. Maybe this is something simple but I and another engineer I work with have been scratching our heads about it. The obligatory AI search was an endless loop of everything we had already tried. Anybody have any advice?
-
-
Member Statistics