All Activity

Yeah, I wasn't asking for diagnostics, I realise that this issue could be for a myriad of reasons, just I was sure (before) that it was hardware related, now I'm not so sure. FWIW, it has just happened again less than an hour after boot, so I'm going to pull the card and chroot in to analyse. (I'm a software developer, so am well aware of the 'it don't go, what's wrong?' approach to tech support 😉) Interestingly, I was still logged in on an ssh shell, and I realised there was an issue when it was telling me that `cat` was an unknown command (clearly not!). I logged out, and now got the dreaded "Connection reset by 192.168.1.44 port 22". I also ran a full badblocks pass (4 real passes) on the SD card prior to imaging just to 100% make sure the card is fine. My main concern is that it will not have flushed logs to disk after the issue, so I suspect I will find nothing. ____ Edit: It looks like Armbian has rsync on a schedule to hold logs in RAM and perhaps periodically copy back to HDD. so unfortunately I have no useful info here. Going to look into the Armbian docs and see if I can get it to log directly to disk whilst I test.

@torz77 Without logs and diagnostic information it's hard to tell what is going on because what you're saying is the equivalent of "it doesn't work" Nonetheless I had the same symptoms when my SDcard was dying (bad sectors here and there). The kernel and network layer was loaded in to memory OK, so pings would work, but ssh calls upon extra binaries and files from the SD card and I was getting I/O errors, hence would result in SSH dying which is the connection refused the client sees. I had to connect mine to a display for the duration of a diagnostic session but thankfully it was easily reproducible so the error glared out. A replacement SD card got me there.

I wonder if that is related to the issue I've been having. Not long after I posted my last message, I hit an issue where the Odroid would stop allowing me to SSH in (connection refused) but would still respond to pings. I tried with many different SD Cards (and USB Hard disks) and the issue would not go away. Could happen after a few hours or a week or so. In the end I just took the device out of service, as I assumed that it was just dying. My Odroid is headless, so can't connect to console to see any potential error messages. I can't remember how far I dug into logs, but I am sure I must have. I have now re-imaged it again, with latest Armbian Stable on Trixie, and will monitor it for further issues. I still suspect the device is dying, but your message has given me hope that it is not. I would be interested to know if anyone else is experiencing similar symptoms. v25.11 rolling for Odroid C1 running Armbian Linux 6.12.47-current-meson Packages: Debian stable (trixie) Support: DIY (custom image)

@Rodrigo Campos @kazekami_him I think @nitrolack and @afiftyp had the same Transpeed M98-8k board. It booted fine with my transpeed image. (other than wifi) They didn't have a board that had secure boot. Check if your board is the same. Maybe you could try my older images. It could be the newer u-boot and patches broke the ram detection for your board? Maybe your board is using a different ram?

Hi and Thank @jock That's what I thought. I used ledconf-3 because that's the configuration you made specifically for my MX10 box. I ran a memtest, which went smoothly. The system is working, and I was able to compile rockchip mpp without any problems. The system is running Bookworm. Would it be better to update to Trixie or revert to a previous version? What do you think? I think the problem comes either from rk3318-box.dtb or from the overlays. Thanks again. 🤜🤛

Hi @kazekami_him, Thanks for your information, but I have no idea in how to use this content for test it. Maybe @Nick A Could understand what this guy did and how to bring it to his port and help us to detect the correct ram amount.

@jock well thanks but I already figured that part out 😊 my problem right now is that i can't find a single distro that works with my box . almost every one (even multitool) goes to a black screen and freezes excatly after 60 seconds . the best thing i could find was a android rom that have the same problem but in excatly 30 minute after booting up ! i did this stupid thing that did not backed up my original rom before writing to internal emcp flash 🤦‍♂️ if i can find any version that doesn't have this problem , i know how to merge armbian rootfs with it ! thank you again !

Have you tried your python script with your Linux PC? If it happens again, you can tell that the problem is within the ESP32 program. I generally prefer having the most complex system (Armbian) poll the simplest device (ESP32), instead of the ESP32 interrupting the Armbian system. I found it more stable that way. Stay with wifi, and use the ESP32 serial port just for debugging. Program the ESP32 print an acknowledgement of data requests, and an alarm if it gets stuck in an unexpected state. I have also found ESP32 circuit or micro python very stable for serial port communications.

I do not have any other monitor available but I did order a UART to usb device, and I have identified with a multimeter the uart pads, which are next to the SD card slot. I will keep this feed updated!

Hello! You should really look to the board name in rk3318-config rather than relying to led-conf numbering; also your dmesg is showing a very bad error which is probably due to an unstable system rather than a bug

rk322x armbian images never used the offset of 8192 sectors, only the multitool has such offset to increase compatibility with stock images

@Hqnicolas would it be possible to have the driver @guenter pointed out in the base image?

I think the core problem is that headers were compiled with Ubuntu compiler / userspace and you try to use it on Debian. I used this on Ubuntu, which is the reason why it worked. We are aware of this problem - headers should be distro specific. Which adds complexity on our side ...

Feel free to pr any missing overlay here: https://github.com/armbian/linux-rockchip

moved to csc https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image tl;dr: You are using the wrong image. Get/build one for your board

It works, but I found that the i2c dtbo file I needed was not in the armbian repository, so I manually extracted it from the radxa official image.

Armbian 25.8.1 Noble Gnome (Kernel: 6.1.115) + libMali (https://github.com/ginkage/libmali-rockchip) + box64 3.7 (https://ryanfortner.github.io/box64-debs/) + wine-9.22-staging-tkg-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/9.22) + DXVK-Sarek v1.11.1 - Mali GPU Fix by Ayman-Zeyada (https://github.com/Ayman-Zeyada/DXVK-Sarek/releases/tag/v1.11.1-mali-fix) ~60fps@1080p HK: SilkSong

What? Sharing various gaming experiences with RK3588 (Orange Pi 5) on Armbian. Why? Because RK3588 is a capable gaming chipset, Armbian is a good OS; Vulkan on RK3588 is getting better over time (PanVk) How? Posting your gaming results here (preferably with setup and screenshots/videos) so people can learn more.

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.

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

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)

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

I have an Orangepi5 ultra RK5388. I have tried the following versions of Armbian13. It doesn't recognize my USBs so I don't have a keyboard. vendor: https://armbian.systemonachip.net/dl/orangepi5-plus/archive/Armbian_25.8.1_Orangepi5-plus_trixie_vendor_6.1.115_minimal.img.xz.sha This one won't start ,current: https://armbian.systemonachip.net/dl/orangepi5-plus/archive/Armbian_25.8.1_Orangepi5-plus_trixie_current_6.12.43_minimal.img.xz There is also no reference to Debian13 in any repository on the Orangepi website.

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?

@hexdump hey mate , do you know if new armbian image still uses an offset of 8192 sector ? i'm trying the workaround you proveded in first page for linux hanging excatly after 60 seconds , but it only worked with multitool.img . with new armbian images it doesn't even boot after applying the trick 🙁 thanks