All Activity

ok. I have 5 cubieboard 1. Not possible memory card for every one.

Nobody knows, nobody tried. Give it a shot. There is only one way to find out.

Great! I will start to tinker around with armbian.

You can always restore to android. Armbian is providing kernel boot.img and a rootfs image, which will not harm flashing other os.

a friendly ping to maintainer of this device @amazingfate 😀

Till Now i have those images but as you said its old. Is possible to upgarde ubuntu from those images to latest ubuntu version?

Is it possible to add in kernel?

My PBP died, so I can no longer test it myself. You can start by testing the PPSSPP aarch64 AppImage. https://github.com/hrydgard/ppsspp/releases A couple of years ago I had performance issues with the PPSSPP Flatpak on my Phytium D2000, so I built it on Ubuntu 22.04. I'm not sure if I followed the instructions for Qt, or for Linux. So you need to install the prerequisites and I guess it doesn't hurt to install the additional packages mentioned for Ubuntu. https://github.com/hrydgard/ppsspp/wiki/build-instructions#building-with-cmake-other-platforms-eg-linux

moved to tvboxes

Hi @BOFFBOY, have you managed to make it work? Having similar issue : tried with two different orange pi 5 , two different nvme SSDs, three different Power supplies up to 5V/5A and three armbian kernels: 5.10 | 6.1 and 6.18

You are telling me to forget the thing I suspect is the reason for the network not working correctly...? If it is "working perfectly", why does it not resolve addresses from the bpi? Why is your bpi setting 127.0.0.53 (witch would be incorrect even if you ran a dns server ON that device, it should then be 127.0.0.1 (or the device ip), potentially at port 53 but IIRC, port 53 IS dns requests and where it will go without defining it) as dns server and not 192.168.71.1? There you go, there is another culprit. If writing 4k in each iteration fails, but 512 works, 99,99% chance the reason is the sd card is starting to completely fail. Armbian imager would have told you verification failed when verifying the image after writing it, there is zero verification when using dd. There should be no issue writing 4096 bytes (4k) each iteration with dd on a functioning sd-card. Seems you are more interested in screaming and complaining than actually getting to the bottom of it all and set it up like a NORMAL network where NOTHING has to be done on the devices because the settings will be configured correctly with the dhcp lease. Btw, here is the dev documentation for armbian imager (and the source code ofc), took me 30 seconds to find... https://github.com/armbian/imager/blob/main/DEVELOPMENT.md Not sure what useful things you expect to find in there that is not mentioned in the help. It writes an image and does verification of that image (and you can download images), that's it. Good luck I guess, I have nothing further to add.

Hello armbian accomplices, I though I would share my little journey about getting this tablet rooted with magisk so that hopefully one day armbian could run on it. Steps: 1. on android become developer 2. enable oem bootloader unlocking in developer options 3. adb reboot bootloader 4. fastboot oem unlock 5. reboot, the os will be wiped 6. install Magisk apk from github releases 7. get Teclast T60 AI firmware from their site it contains Firmware.img 8. ./sunxi-fw extract -n "wty:init_boot.fex" -o stock_init_boot.img Firmware.img 9. transfer to device and patch with Magisk app 6. adb reboot bootloader 7. fastboot flash init_boot_a /path/to/magisk_patched_init_boot.img 8. fastboot flash init_boot_b /path/to/magisk_patched_init_boot.img 9. fastboot reboot Now do people know about what needs to be done to get xfce with armbian booted on this apparatus?? I think I need better AI agent for this than Deepseek as it is a bit sloppy as usual, Gemini Pro or Claude probably.

Okay I think you are right they are shifting the RAM GB numbers so 8 GB is actually 4 GB as the price suggests. Now now, what I ended up doing is I bought a Teclast T60 AI tablet(for 100 euro shipped in EU) with Allwinner A772 which is supported by armbian and comes with 6GB RAM. I do not know if I will be trying to boot armbian on it soon but I was able to root it with Magisk. It did went on quite a journey to get it rooted as I kind of soft bricked it at first. Deepseek was giving me little wrong information but we got there. I think I might need a more competent AI agent like Gemini pro to get display, touch, wifi, bluetooth etc. working with armbian. Perhaps I post about the rooting process elsewhere at some point. Here is some of the gear I have if people are interested: https://www.aliexpress.com/item/1005009330391341.html DUX DUCIS Foldable Bluetooth 5.0 Keyboard with Touchpad & Phone Holder For Phones Tablets PC iOS Android Windows Mac https://www.aliexpress.com/item/1005011827691576.html https://www.aliexpress.com/item/1005009419399930.html HGFRTEE 3840*2160 13.3inch 4K Portable Monitor All in all pretty pleased with it so far, not exactly Surface pro 5/7 which I also have and they all weight about 1000 grams but then on the other hand this tablet did not cost me hundreds of $ so I can be little less nervous about someone stealing it.

@jock Thank you, I will try.

After more than six successful years with Helios4, I have to say goodbye to this platform and the highly valued, helpful, and knowledgeable Armbian forum. With 32-bit, it’s no longer feasible to continue using it in the future. I have installed the 4 8TB hard drives from the NAS into an Odroid H4+ (Intel, 64-bit), installed OMV8, and on top of that, Nextcloud-AIO Hub 26 Winter and AdGuardHome. Thank you very much for your support over the past few years. btw. The Helios4 hardware (excluding the hard drives) is still available.

Hmm that doesn't look great. It looks like it is crashing at random places vs the same place every time. It makes you wonder if you have a true hardware problem (e.g. bad memory). Can you never make it to a login prompt? I would double check all your memory locations for the FDT, ramfs and kernel to make sure you aren't accidentally overlapping anywhere. And yes, I would avoid starting anything at 0. I actually found a kernel bug from doing that. You could also consider trying to load the kernel as an EFISTUB directly. I don't know if that's supported by armbian or not, but you could experiment. You do know you can save u-boot variables to the SPINOR storage so you don't have to type them in every time, right?

@mrdeathjr Mainline Linux support for the A733 is still in its early stages. I currently have a Armbian build using a collection of patches sourced from the kernel mailing lists. However, I’m getting a lot of errors and haven't managed to boot to a login prompt. https://oftc.catirclogs.org/linux-sunxi/2026-03-23 13:07 <indy> hi all, is there any a733 upstreaming effort? 13:29 <apritzel> indy: effort is underway: pinctrl is WIP (patches have been on the list), and the clock patches have recently been posted 13:30 <apritzel> RTC and AXP are on the list as well, that would conclude the basic necessities to get a DT merged that wouldn't break in the future 15:25 <indy> apritzel_, is it targeted for 7.0? 15:29 <apritzel> indy: no, that's way too late, v7.0 is due to be released in like three weeks already. It's even too late now for v7.1. 15:30 <apritzel> and it's the usual bottleneck: reviews ... I hope I find some time soon to look at the clock patches With @alexc hard work porting the v1.4.8 BSP driver to kernel 6.18, I was able to create a working Armbian build for the Radxa A7Z. https://github.com/NickAlilovic/build/tree/Radxa-mainline-WIP

In my personal opinion with lastest changes showed in kernel lore on a733 https://lore.kernel.org/linux-sunxi/?q=a733 kernel 7.1 give many things for a733

Hi.. I need de original firmware for android box Q17 Allwinner h313.. Someone can help me?

So I'm still doing s-thing wrong with dd. What is correct for this later spin? using 128GB cards.

your card imager needs a CLIBC_2_38, 3 versions newer than my bookworms 2-35, so I'm stuck at dd.

Because I know little to nothing about systemd, I have not touched it. If it is enabled, and IDK how to fix it if it was enabled in the .img. if so that is a bug & is a reason for a respin. Its finally done but probably won't mount as dmesg says it cannot find the ext4 file system. So another ugly thought crosses my curious mind, what is the DEFAULT file system, btrfs?

Please forget I ever mentioned dnsmasq, it exists only in the router where its working perfectly for 7 of the 8 machines here. w/o any man pages I haven't a clue how to run any of the systemd stuff so any config changes that need to be done after 1st boot in order to enable /etc/hosts for local lookups is equ to asking 10k monkeys to retype all of Shakespear's work w/o a single typo. We both know that aint gonna happen b4 the universe runs down in another 500 billion years, So, I am going to rewrite that img to a fresh 128G u-sd, change the /etc/hostname to amanda and rewrite the the /etc/hosts file with mine. Then you tell ME what to do via systemd to make a user "ping -c1 yahoo.com translate" to its dns address in <1.5 milliseconds. That rewrite will take at least an hour. maybe into 2 because the only wat to get a boot able image out of that respin is with dd if=/dev/zero bs=512 count=20 of=/dev/sdc to wipe the u-sd card. then dd if=Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img bs=512 of=/dev/sdc option bs=4096 is much much faster, only about 12 minutes to write but will NOT boot nor will it mount as /dev/sdc1 to /mnt/sdc1 So ATM its being written at bs=512, hoping it will work. That takes well over an hour. You have an image writer, "Armbian.Imager_1.2.5_amd64.AppImage" which has no manpage, a useless help screen and has never written a bootable .img file to any sd card since I dl'd it in jan 25. I haven't even bothered to try it as it this time as apparently burns up any u-sd card I've tempted it with so good but cantankerous old dd to the rescue. That, and 45 years a DM-II is slowly taking my eyesight because of macular-degeneration, not your problem of coarse, but mine at 91 yrs old. But saying dd is slow is an understatement, glacial is a better description. from the shell doing the writing: root@coyote:/home/gene/Downloads/armbian# dd if=Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img bs=512 of=/dev/sdc status=progress 6230856192 bytes (6.2 GB, 5.8 GiB) copied, 2939 s, 2.1 MB/s

I'd like to add my observations. The current version is 7.0.0-rc6-edge-sunxi64. The wireless interface is available, but if Ethernet is connected, it's impossible to connect to either interface via SSH. However, as soon as the Ethernet speed is set to 100, both interfaces become operational. Maybe this will help revive the hardware.

Does it? Does not look like 192.168.71.1 to me... And: That is not correct, that is the global scope, no ip can end with 0. Ehhh... What do you call dnsmasq on your router then?!? If you don't "maintain" that, yes, things like this can happen, especially since you have set the leases to never expire. I have no idea if this is the case, it's for YOU as sysadmin of your network to know. Nobody knows what you did after install. All that is known after all things written in this thread: You have a dhcp server you have a dns server (dnsmasq) you installed Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img (that comes with network manager according to documentation) It seems you have systemd-networkd enabled Unless you can prove the default config was with both systemd AND network manager, YOU have made changes that breaks the installation. Nobody can answer what you did, only you. The normal way if having a local dns server (even if it ONLY forwards request to outside dns server) is to configure the resolving for local domains in the dns server and not touch it at device level. For example a consumer grade router, it will set dns to router ip in the dhcp lease and when requests come in, resolve with asking your ISP dns servers. Hence, if looking up what dns server is used on the devices, they will NOT point to your ISP dns servers (or google or cloudflare etc), it will point to your router ip. Lets say you have a pihole on your network that acts as dns server, then you configure the router (dhcp server) to point to THAT ip for dns, hence, the dhcp lease will deliver THAT ip. And then you configure the pihole to resolve local ip:s and what outside dns servers to use. The DEVICES will ONLY see the local ip where the pihole lives in this situation. Resolving domains to local ip:s (/etc/hosts on your device) has nothing to do with your dns detection failing. This is all pretty basic networking... Edit For reference, this is what your /etc/resolve.conf should look like (or similar) if you configure your dhcp server to point at the ip where dnsmaq lives (same ip as the router itself) then propagate those settings via the dhcp lease. Then nothing has to be done on any device except for resolving local ip:s if you refuse to do that with dnsmasq. If you configure dnsmasq to do that, resolving will be done on the router instead of the devices and absolutely nothing has to be done on any device. With systemd: # Generated by resolvconf domain home nameserver 192.168.71.1 With network manager: # Generated by NetworkManager search home nameserver 192.168.71.1 If you don't want to reinstall again, make sure systemd network services are disabled and network manager is enabled and then reboot. But be mindfull you might need physical access if network completely fails at boot. IIRC relevant services are (I could be wrong here, you should read up on documentation) systemd_networkd.service, systemd_resolved.service & networkmanager.service I'm in the middle of moving, so I only have an arch desktop and laptop up and running at the moment, so I can not confirm on any armbian installation that I provide 100% accurate information.