All Activity

Tried building a trixie image with this tee and still locks at the same spot

Haha - yes, I did eventually `saveenv'... just being super-cautious, and not sure what was going to work, given all the Kernel Panics. Also, in case some other poor guy comes by later and looks for some examples... If i boot the stock kernel/OS from eMMC, it loads (most of the time) and runs fine. I've had a few kernel panics, but usually it loads. If i boot fresh to the eMMC, it also seems to do better. There are some statements around the web that indicate uBoot might be 'hiding' errors prior to the booti, which causes people (like me) to tear their hair out looking in the wrong place -- i.e., register data is already bad before control is even transferred to the kernel. I did pull down armbian build and build out the latest kernel - 6.18, to see if that might make a difference, but no luck. If anything it caused more issues. I WAS able to get all the way booted up into Armbian one time -- adding the pcie power config switches (I thought), and it was stable for a while -- until i tried to `apt update', at which point it locked up. Haven't been able to get all the way up again. My current guesses to look into are: 1. make sure i'm not, as you said, overwriting myself during booti 2. continue to look for kernel config / versions that have better luck with SATA + mvebu64/power config. I'm guessing since I can boot the pre-installed OS that my hardware is actually OK. If you could provide your relevant ext4load (or similar) that you're using for SATA load, i'd appreciate it. I do get these bad rx status issues, and the networking isn't really coming up on the stock. -- Base install: [ 11.352864] mvneta d0030000.ethernet eth0: bad rx status 0cc10000 (crc error), size=75 [ 13.352762] mvneta d0030000.ethernet eth0: bad rx status 0cc10000 (crc error), size=75 root@ccpe10c1a5:~# cat /proc/cmdline console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/mmcblk0p1 rw rootwait net.ifnames=0 biosdevname=0 root@ccpe10c1a5:~# uname -a Linux ccpe10c1a5 4.19.62-00036-gbc6a6e31fe72 #1 SMP PREEMPT Tue Jun 16 15:39:07 CST 2020 aarch64 aarch64 aarch64 GNU/Linux root@ccpe10c1a5:~# free -m total used free shared buff/cache available Mem: 993 59 793 2 140 867 Swap: 0 0 0 root@ccpe10c1a5:/media/disk0# dmesg | grep -i panic root@ccpe10c1a5:/media/disk0# w 18:17:28 up 19 min, 1 user, load average: 0.05, 0.03, 0.04

Ambian-imager requires a glibc 3 versions newer that this bookworm amd64 has, won't run at all. restricting dd to bs=512 gets only 2something megabytes a second, glacially slow. The more usual bs=4096 is 50x faster, niether of which reports any write errors. And its booted and configured. time about a month off. I run ntpsec on this machine so I'll follow the /etc/chrony/README and assign a source address by number. but ip a shows only an active ipv6 address while ip r returns nothing. hostname is bananapi-m5 which is unk on the local net. IOW its booted but network is only ipv6 & no route of either flavor is assigned. Is this exactly how it was spun to be? I've brought the card back to my reader, and will edit the /etc/hostname to match its ID for 192,168,71,2 in the /etc/hosts file I'll install. And reboot it. but the card won't mount despite the fact that it boots. from this bash xfc4 terminal: root@coyote:/etc# mount -t ext4 /dev/sdc1 /mnt/sdc1 mount: /mnt/sdc1: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. dmesg however has no additional info. only this: [1618874.568139] sd 37:0:0:0: [sdc] 249737216 512-byte logical blocks: (128 GB/119 GiB) [1618874.568944] sdc: detected capacity change from 0 to 249737216 [1618874.569933] sdc: sdc1 [1619402.494452] loop0: detected capacity change from 0 to 12943360 [1619402.494871] EXT4-fs (loop0): VFS: Can't find ext4 filesystem [1619458.923461] loop0: detected capacity change from 0 to 12943360 [1619458.923910] EXT4-fs (loop0): VFS: Can't find ext4 filesystem as I made two attempts to mount it. it loads and boots normally when installed in the bpi-m5. So other than the extra server line I just put in /etc/chrony/sources.d/ which doesn't work because no ipv4 net is even available AND the nearest ipv6 enabled anything is a minimum of 125 miles from me, its about as useful as the teats on a bore hog. Neither is the thought of editing on that tiny screen, the 40 or so lines of /etc/hosts that make up my /etc/hosts file. Doubly frustrating is the fact that the mouse speed is measurable fraction of C speed and totally disappears when inside the xfce4 terminal borders. But installed in the bpi-m5 it boots normally. back in my reader: root@coyote:/etc# e2fsck /dev/sdc e2fsck 1.47.0 (5-Feb-2023) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/sdc The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> Found a dos partition table in /dev/sdc ???????????? wtf??????????? And I get the same result for /dev/sdc1 obviously something is screwed. So I unpackedca new 200mb writeable sandisk u-sd & wrote the new image to it. fdisk then says its a dos partition table. Can a "dos" table be used at all on a 128gb card? I've heard not but don't know where the failure is. ipa shows only ipv6, ip r shows nothing. The only thing that could be used for net config is armbian.config which I think is NetworkManager . but that's by now known not to work. So whats left????? IOW what the hell is being used to configure network NOW with a 6.18 kernel ???? And how do I use the new tools if any, to set it up for a network address on 192.168.71.2, an ipv4 address THAT WORKS FOR EVERYTHING??????? Or do I go back to the soon to expire Armbian_25.5.1_Bananapim5_noble_current_6.12.28_xfce_desktop.img which I am using 2 more times here in front of klipper driven 3d printers. And which if asked to apt update, now want around 430 new files to do the update but failing in the make a new initrd stage. Start by putting a gpt partition table in the xz with a respin. And stop assuming that the whole planet has ipv6 connectivity, central WV is not the only ipv4 island on this planet so blessed.

Hello! How to download nightly build with 6.18 kernel? I've got 404 error when trying to download via link.

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.