All Activity

Yes, the cpu temperature is about 40 °C.

lsusb should display USB devices.

Are you using proper cooling?

Plug in another usb-serial device, see what happens in that case

I tried another version: armbian_23.02.0-runk_Onecloud_jammy_edge_6.1.9_minimal.burn.img It shutdown about every 10 minutes. log uploaded here: https://paste.armbian.com/reseqowita armbian-hardware-monitor.log dmesg.0 kern.log 23.02.0-shutdown-every-10-minutes.txt

Do you see CPU stalls in kernel logs/dmesg? We have two reports with sunxi family boards and 6.6.16 kernel, reporting high CPU usage, unstable operation and kernel logs reveal CPU stalls every few minutes. I'll build and test with latest Linux 6.6, else with edge, in the hope it can be fixed forward instead of backwards. Nasty to debug (for me) since no process, cron job or anything else is obviously associated with those CPU stall events. EDIT: Indeed, a sunxi current build with latest Armbian and Linux 6.6.29 solves the high CPU load and stalls for one of the two users. Awaiting feedback from the 2nd one. Those two use NanoPi NEO and Radxa Zero, while I was not able to replicate the issue on NanoPi M1 (all same SoC) with 6.6.16 from Armbian repo. EDIT2: Jep, solved for the 2nd user as well. I would have linked package builds for download, but my post was flagged for review and removed when I edited the link inside. A simple kernel asset build with latest Armbian will do.

@martivo are you using beta or stable?

Yes. I have krescue. It still hasn't worked. I have a vim3 from a year ago that I have manjaro booting from sdcard. I'd like it to be armbian, but havent managed to get an armbian sdcard to boot in it. Its my only working vim3. I bought a Vim4 recently. But it was DOA. Now I'm travelling and have no recourse but to keep using manjaro which Kind-of sucks. I left the android only vim3 at home.

Here is the most recent thread on s805:

There are is no Armbian support for s805 based tv boxes (only s905 based boxes).

Post of NicoD

Hello, I'm new to this forum here. I don't know if it have solution to boot flashed USB (NOT SD-Card) contain Armbian OS from Recovery Mode on cheap Android TV Boxes (Set-top) ? Because I have this box with model `SB801` (Device name: Acnos SB801 [from Vietnam] ) doesn't have SD-Card slot but it has specs like Odroid C1 / MXQ / Mbox SB801. Little specs preview: + CPU: Amlogic S805 + RAM/ROM: 1GB/8GB + Running OS: Android 4.0 + USB Slot: 2 + Display connector: HDMI, [? Red,White,Yellow] + Network: Ethernet, Wi-Fi Thanks. **sorry for my bad English

@A J I'm not sure which image you have burned, but most images do not have a separate boot partition, they just have one ext4 partition that contains everything. Images that have a separate /boot partition do that either because of limitations of the u-boot version being used, or because they want to provide easier access to the /boot via a non linux platform (i.e. windows) for accessing the contents of that partition.

Hello there! I want to ask a question about burning images into SD cards. I followed the steps of OP, I tried to burn the image via DD and via balenaEtcher, and both of them didn't created a boot partition (balenaEtcher did warn me that the image does not contain a partition table). As far as I recall, those files like uEnv.txt, .dtb, etc must be placed in the boot partition, am I right? Did I do something wrong, or did I should somehow create those parts by myself? Thanks!

Sorry, appears to be working good. My bad wrong governor selected.

I run output/images/Armbian-unofficial_24.5.0-trunk_Onecloud_bookworm_current_6.6.21_minimal.burn.img on my onecloud board. It shutdown about every 40 minutes. How to solve this problem? Thanks! journalctl.log kern.log armbian-hardware-monitor.log

Libre Renegade overlays opp-1.4ghz and opp-1.5ghz load but not working in trixie edge (24.5.0-trunk.512). Both overlays do work in 24.2.1 bookworm.

Hi again, Quick update for potential other readers, and some questions. I've now also got overlayroot setup to keep the internal flash mounted as readonly for normal operation. So as to not burn through the flash's endurance counters within a year on a device that's writing logs, status information, etc. to flash continuously. And also to protect it against issues when people just pull the plug while it's operational, potentially corrupting flash and making it unusable without physical recovery. Seems to be working great, but had to adjust the initramfs hook and script files (mount -o move instead of mount --move in script, and adding lines to copy_exec /bin/grep, /usr/bin/stat, and /bin/echo to the initramfs. Seems to be working just great including with pikvm. Two questions: My rk3318 android tv box "H96 Max v11" does have the two red/blue leds on the pcb, but no clock display. There are solder points on the pcb though. Would it be possible to use these pins for GPIO access (maybe even add an I2C RTC module), or would that not be possible within the limits of hardware/firmware? Any pointers on where to start looking, if at all possible? In pikvm config, following generic instructions, I was able to easily add the usb ethernet gadget and do routing/masquerading for the attached device. Yet, when I tried to configure usb mass storage gadget, the result was that the keyboard/mouse stopped responding in pikvm. From the pikvm documentation (unfolding the USB limitations section) it looks like there could be an issue with capabilities of the chip in relation to the number of endpoints needed. Yet, that page mentions mass storage would require 2 endpoints for each msd, and usb ethernet would require 3 endpoints per emulated device. So it's strange that ethernet does work but msd does not. Enabling only one at a time, of course. Is there any data on the number of endpoints available on the rk3318 chip? Or maybe someone knows how to make msd working? Or.. maybe it was intentionally disabled in srepac's kvmd-armbian because it's not working either way? The usb ethernet gadget was disabled in the config as well but works like a charm, so not sure why msd didn't work as expected. Or maybe msd is only supported for the usb3 port and not on the usb2 port that I'm now using for otg connection to the remote? Sorry, too many question marks here... Any pointers would be much appreciated!

@McTurbo OrangPi official images use the vendor kernel 5.10 with various custom patches and drivers. Armbian does not offer vendor kernel anymore because after a while they become old and unmaintained.

Here is my solution. I created a sdcard with u-boot firmware according to the instructions on this webpage: https://docs.u-boot.org/en/latest/board/starfive/visionfive2.html I noticed these instructions will use OpenSBI v1.4. The Starfive firmware is still using OpenSBI v1.2. Flip the boot selector switch on the board ==> to select boot from sdcard. Insert the sdcard created from that u-boot website. Boot the system. It will boot without starting any operating system. U-Boot 2024.07-rc1 (Apr 26 2024 - 10:32:34 +0300) OpenSBI v1.4 Swap the sdcard with the Armbian sdcard. Enter these commands: mmc list mmc dev 1 load mmc 1:1 ${fdt_addr_r} /boot/dtb/starfive/jh7110-visionfive-v2.dtb load mmc 1:1 ${kernel_addr_r} /boot/vmlinuz-5.15.0-edge-starfive2 load mmc 1:1 ${ramdisk_addr_r} /boot/initrd.img-5.15.0-edge-starfive2 setenv bootargs 'root=/dev/mmcblk1p1 rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0' setenv kernel_comp_addr_r 0x5a000000 setenv kernel_comp_size 0x04000000 booti $kernel_addr_r $ramdisk_addr_r:$filesize $fdt_addr_r This will boot Armbian and recognize the 8GB RAM. I also found there is a problem recognizing the UUID of the sdcard or nvme during operating system boot. For sdcard boot I needed to edit the /etc/fstab -- switch the UUID to the device name sdcard example: # cat /etc/fstab /dev/mmcblk1p1 / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 These instructions also worked with Ubuntu 24.04. I saw the same memory problem as with Armbian.

I found that the official OrangePi images enable 4:4:4 output, but only with the Debian image. The Ubuntu image only has 4:2:2 output. I couldn't figure out how they did this as I couldn't see any difference in the driver config. So it seems they changed something in the code to get it working, possibly something similar to the patch you linked.

Probably no dtbo will be needed. Find the 5 pins in your orange pi, that would be contacted by the hat, and try to control them with the Python code here: https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/?do=findComment&comment=181191 if that lorahat software is open source, then change that source code to point to the correct pin addresses

Please, can you share your hostapd.conf (minus the ssid and keys of course) I am running into other problems, but I am glad that others are getting hostapd working 👍

After the usb4-1 lines, you should have seen cdc_acm something You can check that you have the acm driver with: zcat /proc/config.gz|grep ACM you should see config_usb_acm=m Have you tried: ls /dev/ttyUSB* ? When you see the ttyACM*, you should get the by-serial files appear automatically (devrules function)