Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. Radxa staff actually does not answer the original question w.r.t. Allwinner A733 HW virtualization, it is just that kernel config has it. But I see from releases 'bullseye', that does not look good at all. In theory, that means 5.10 kernel, and oldoldstable libvirtd/KVM/QEMU etc. As this SoC is bigLITTLE, (Cortex-A76 Cortex-A55), starting a qemu-system-aarch64 process will pick some of those cores randomly, assuming you have more than 1 vCore (smp option > 1) . Kernel older than 6.8 or so does not support moving between an A76 and an A55. That is the same for Rockchips (RK3588). It took me quite a while before I discovered that this is known behavior. So on for example on vendor rk35xx 6.1.115, I pin vCPUs, can be done in virt-manager GUI xml config or cmdline via taskset. As easy test, use -smp 1, then it should work. mainline kernel CPU numbers are such that simplest/lowest CPU's get lowest number. That might be the other way around on 6.1 or older downstream/vendor/BSP kernels. On an RK3588, a 2-core VM with 2x A76 and 512MiB is done by: taskset --cpu-list 6-7 qemu-system-aarch64 -M virt -cpu host -enable-kvm -m 512 -smp 2 \ -bios u-boot.bin \ -drive if=none,file=armbian.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -netdev bridge,id=hn1 -device virtio-net,netdev=hn1 \ -nographic Same should work on A733
  3. Today
  4. Hi all, I am unable to login to OMV on my Helios64. A bit of sleuthing indicates that this is because the / fs is at 100% capacity. At first, I figured I'll just transfer the system install from the 8GB SD Card I started with to the 16GB internal eMMC. Turns out past unfnknblvbl already did that, and now I need to go the other way. The documentation on the old Kobol site isn't entirely accurate about how to do this. My SDCard is /dev/mmcblk1 and even though it's formatted ext4, it simply doesn't show in armbian-config. In fact, the only device that shows in the Install menu is /dev/md127, which is the RAID array itself. I'd rather not be booting from that for obvious reasons. Assuming that I'm a bit of a Linux noob (I know just enough to be dangerous), is anyone able to tell me what am I doing wrong? Thanks! ๐Ÿ˜ƒ
  5. I've been using my Helios64 nonstop since i got it in 2020 (and the Helios 4 since 2018). It's been great the whole time; does exactly what I want it to do, and now I've made it my sole Plex server to save power. My only problem is that the internal eMMC is now 100% full (thanks to Plex), and I can't work out how to move the install back to the SDCard (Linux noob...), which is my I'm here. I'm sad these guys had to shut down. This could have been a magnificent project
  6. Hello, Here is a config file that works with linux-6.6.119 config-6.6.119 And a tarball here : https://drive.google.com/file/d/14EHPMT01-geYNflC2lqXNue4ZH25z-lA/view?usp=drive_link with a fresh built kernel. Two small patches are needed : one to activate the wifi/bluetooth card (in dtb file), another to add a delay in mwifiex_sdio.c What works : wifi, eth0 and eth1 cards I can't activate the bluetooth card with btmrvl_sdio (need to be investigate) If someone else can test this (@rolli_44 , @umiddelb ? ). Next : propose a patch to integrate this board in armbian ?
  7. log says: No space left on device So you need to look at that, remove unneeded stuff etc. Also check the output of df Maybe something else is wrong
  8. OrangePi in general is bad support, as also is stated on the image download page. For just driving a relay, so a pin change between high and low, you first need to select which pin from the GPIO header you want to use. You can see what are probably generic GPIO by default from picture here: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-2W.html In the latest image, I see there is no real support for OrangePi02W, only H5 and A64, not the actual H618 (it seems to use H616, so also that might lead to issues). You can look in file maybe, if you want other then defaults: /boot/dtb/allwinner/overlay/README.sun50i-H5-overlays I have older 32-bit Allwinner things, H3 for example. Analog and SPDIF audio works great there, that is why I bought those mainly. Also GPIO6 I use for driving a switch (via extra resistors and some MOSFET/TRIAC). I did some C-code and got working temp sensor and switch, see lgio code https://abyz.me.uk/lg/download.html But currently for years already in bash script: init: test -f /sys/class/gpio/gpio6/value && echo 6 > /sys/class/gpio/unexport echo 6 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio6/direction chown root:gpio /sys/class/gpio/gpio6/value chmod g+w /sys/class/gpio/gpio6/value on: gpioset gpiochip0 6=1 off: gpioset gpiochip0 6=0 This still works since Armbian Buster, now kernel 6.12. Not tested yet with 6.18
  9. Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.14-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.14) + DXVK-stripped v1.6.1 ~60fps@720p Noted: . The DX9 version of the game is black-screen. . The DX10 version works. However, it will crash immediately after the tutorial stage because the PanVk driver still lacks the "Geometry Shaders" feature. Devil May Cry 4 (DX10)
  10. As I said above, there is no usb otg functionality. If you want shell as ordinary user - install any app which allows access to shell (I'm using "Admin hands" in local shell mode) on your tv box. In this mode 'su' refuses to escalate privileges. If you want root access, you should connect using uart (see my messages above). You will get access to u-boot and android console. There you can execute 'su' and it will give you root privileges.
  11. This started happening fairly recently. If my Docker containers are left running for a period of time, this message will start appearing over and over in journalctl: dockerd[1491]: time="2025-12-27T20:55:44.808894213-05:00" level=error msg="Error writing log message" driver=json-file error="error writing log entry: write /var/lib/docker/containers/97e823567c56600b69888e6abf63189c6f586afbf6bcf06fca820eaf4ef46f7d/97e823567c56600b69888e6abf63189c6f586afbf6bcf06fca820eaf4ef46f7d-json.log: no space left on device" message= After a while, these two messages will start repeating (these were taken from a different instance of this happening, so the PID is different): rsyslogd[599]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2504.0 try https://www.rsyslog.com/e/2027 ] rsyslogd[599]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2504.0 try https://www.rsyslog.com/e/2027 ] Looking at btop when this is happening shows that the rsyslog and dockerd processes are using up most of the CPU, along with fail2ban for some reason. The full command for dockerd is: /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock Here are all my docker packages: docker-buildx-plugin/trixie,now 0.30.1-1~debian.13~trixie arm64 [installed] docker-ce-cli/trixie,now 5:29.1.3-1~debian.13~trixie arm64 [installed] docker-ce/trixie,now 5:29.1.3-1~debian.13~trixie arm64 [installed] docker-compose-plugin/trixie,now 5.0.0-1~debian.13~trixie arm64 [installed]
  12. Yesterday
  13. I would check out the boards with Platinum Support. Go to the vendor sites to see if they include or sell a fan for their board. Look for something with a Rockchip RK3576, plenty of RAM, and EMMC or UFS. RK3588 usually needs a fan.
  14. I built the latest Nobel build and ended up with Armbian-unofficial_26.02.0-trunk_Nanopiduo_noble_current_6.12.63.img. Even at idle it runs 70C. If you try to do upgrades it will do thermal shutdown. The temp reporting is real because it's hot enough to burn your finger if you hold the heat sink long enough. I used a PS2 usb fan (I call it the ghetto cooler 5000) long enough to downgrade kernel to 6.1.x. Now it idles around 50C. I know there's been heating issues with H3 (Duo uses H2+). I compared DTBs, voltages and cannot find the smoking gun. I played around controlling the voltages, etc. Anyways, I'm OK with 6.1.x kernel since this board was out in 2017. I still have a few I want to use for projects. I guess as long as I can use a current Ubuntu distro I'm OK. OK, unpacked one of my old breadboard projects on focal Linux nanopiduo 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l armv7l armv7l GNU/Linux. CPU idles cool, so I do a: sudo cat /sys/class/regulator/regulator.5/microvolts 1100000 It looks like 6.x kernel/nobel is using 1.3v. There it is. 1.1V. That confirms the mismatch perfectly. Your old Focal breadboard is running at 1.1V, while the modern Noble board is forcing 1.3V. On these chips, that 0.2V difference is massive because power (and heat) scales with the square of the voltage. Moving from 1.1V to 1.3V increases heat output by about 40%, which is why one board is a stable 50ยฐC and the other is a 96ยฐC furnace. So more hacking to do. I'll see if I can do a build hack.
  15. Hello everybody, My Box is a oxtagon shaped t95z plus 2 mb 16 mb chipset: processor arm cortex -a53 mali T820 GPU AP6255 wifi ac + bluetooth 4.2 sandisk SDINAD1F4-16G 16G emmc 16G rom lanson L5TC4G63CFR x2 dram 2GB I try to install armbian_community_26_2 _0-trunk.100 aml-s9xx-box_noble_current_6.12.63_cinnamon_dektop.img.xz I use meson-gxm-vega-s96.dtb And u-boot-s905x-s912.dtb copy and rename as u-boot.ext It boots to ash then it stops No asking for password and user I have no clue what to do next I have entered armbian-config but this returns a error Any tips?
  16. I reread it, but the information is not publicly available. Contact them directly? I haven't tried. Maybe they can help. Thanks for your time. I'll write back later; maybe someone will be interested.
  17. That would be a good start indeed.
  18. Yes, I am aware of this limitation.
  19. @eselarm Thank you very much for the details. I am currently working with the NanoPi R6S minimal image, with kernel 6.1 based on your feedback. I started out with the rolling release version, but that cannot run Jellyfin (because it is Forky). So I going back to the Trixie version and test this now. I will report back here whether the Jellyfin server works well with the transcoding of 4K movies (like the vendor FriendlyElec distribution does) and whether 4K movie playing can be smooth on it.
  20. Last week
  21. Board that would fit though, the H4 PLUS from hardkernel, limited to 4 sata instead of 5. 120x120, but only 2 screws would fit I believe...
  22. Update, this is also working .... extraargs=reboot=watchdog UPDATE: It stopped working after 3 successful reboots...
  23. Ok update.. I used a USB Ethernet to update and now the local phy is showing as end0 and it works. I'm kind of doubting my story now. I know the initial login could not connect to the Ethernet. After I installed on the local emmc and upgraded via apt upgrade things work now. I think this is a non-issue.
  24. Some of the Board manufacturers SDK's broke due to a deleted repository; looks like someone's having a rough end to the year.
  25. There is at least no primary GPT, all zeros from 0x200-0x20000 Fixed with: # gdisk Armbian_community_26.2.0-trunk.130_Radxa-cubie-a5e_trixie_edge_6.18.2_minimal.img GPT fdisk (gdisk) version 1.0.10 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y OK; writing new GUID partition table (GPT) to Armbian_community_26.2.0-trunk.130_Radxa-cubie-a5e_trixie_edge_6.18.2_minimal.img. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully.
  26. Interesting question. The dxf says the part in question is labeled ED1 besides CP18 and CP14. I found both CP18 and 14 in the schematics but ED1 not. Either mislabeled or I didn't catch it. https://x.na4.eu/KOTu3/quzevoji80.jpg OrangePi-Schematic of ZERO3.pdf
  27. @Nick A, @MeJune Luckly. On this thread: https://forum.manjaro.org/t/allwinner-h728-a523-a527-t527-initial-support-thread/173654/2 He working for a year to make the linux working stable on this box. This mean kernel, dtb, ... can be replace on armbian build. I super need new image for web-service hosting purpose. Hope all function working.
  28. Easiest approach is the customize-image.sh script in userpatches/. https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script
  1. Load more activity
ร—
ร—
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines