All Activity

I'm sorry but, lmao, this is entertaining to read. The sd card is OBVIOUSLY corrupt, it even TELLS YOU THAT in what you posted. But you think what I am seeing should tell me it fubar. That fact that this configuration works perfectly for 6 or 7 other machines in this house long string of cat5 or cat6 cable seems to be blowing right on by. This can't be true for all 4 u-sd cards I''ve tried. The last 2 were brand new, even faster rated cards, but all are 128gig sandisk's 1: the image itself has a dos table, which doesn't work above 32gigs acc what I have read and this prevents mounting the written images for installation in a card reader, but the used partition is ext4, so it boots ok but takes a long time because the net failure blocks the boot for many minutes 2: so I back up to a 25_05 image, and at one time had it booting the 6_18 kernal, but still no net which is the original problem. ATM I am wasting my time on a 25_05 build image which is running just fine on another bpi-m5 driving a 3d printer about 10x faster than OOTB. So I'd suggest you pass this one off to someone who knows how to make a 50 line /etc/hosts file work without a dhcp because I'm doing it on 2 other wintel boxes, an rpi4b running bookworm and 3 bpi-m5's running noble on 3d printers. The best I can do is post a pix of the 'netplan status --all" screen and somebody tell me whats wrong instead of berating me for not running a dhcp server properly.

I'm sorry but, lmao, this is entertaining to read. The sd card is OBVIOUSLY corrupt, it even TELLS YOU THAT in what you posted. It's probably a good idea to go back to the basics and learn linux properly if you don't know what a msdos (MBR) partition table is. https://unix.stackexchange.com/questions/289389/what-are-the-differences-between-the-various-partition-tables As for how to NORMALLY SETUP A NETWORK, you can read my earlier responses, no host files on the devices, no hardcoded ip, just a correctly configured dhcp server that delivers the CORRECT IP:s to all devices. Then the dns server on the network (dnsmaq in this case) resolves desired domains to local ip:s. That way, there is NO NEED to do ANY CONFIG on the devices, it is all done on the entire network.

@Nick A Thank you, can you publish a server image for the Radxa A7Z with kernel 6.18?

If an pre-made image is not there, just DIY. https://docs.armbian.com/Developer-Guide_Build-Preparation/

I see. Well I can confirm my bootloader is very stable. I have been running it on two devices for a couple years now without any issues. It cannot hurt to flash it again (to rule out random bitflips), but if you are getting sporadic crashing no matter the kernel/OS it does start to indicate a hardware issue. I have a laptop that crashes sporadically but it isn't so bad that I cannot use it. I've run memtest on it countless times without issue, tried replacing RAM, etc. some devices really are just cursed for whatever reason unfortunately. In case it is helpful, you can find the config for the kernel I run on my devices here: https://github.com/bschnei/linux-a3700

Moreso the timing of the boot sequence and device enablement. The fact that i got the Debian-on-SATA to load ONE TIME strikes me as very odd. The fact that i get kernel panics on the stock eMMC now and then, also strikes me as very odd. I've tried using the different uboot clock-timing builds for DDR offered by armbian ( ), but they all show the same thing... so i don't think it's the cpu/ddr timings.. i think its the bootup timings, or power configs or something introduced around pcie/sata since 4.x. But clearly i'm shooting into the wind at this point.

> Timing issue might occur in DDR mode I get every boot so that should indeed be ignored. What do you mean by timing issue? I could build you a bootloader clocked at 800Mhz instead of 1.2Ghz if that is what you are referring to?

Correct -- GTI ships it with Ubuntu. Installing either of the Armbian supported models (Debian Trixie or Ubuntu Noble) on the SATA causes bootup issues. The stock Ubuntu/eMMC boots up fine -- MOST of the time. i do get kernel panics sometimes even then. -- On the stock install via eMMC: root@ccpe10c1a5:~# w 04:41:40 up 8:24, 1 user, load average: 0.00, 0.00, 0.00 root@ccpe10c1a5:~# lsb_release -d Description: Ubuntu 18.04 LTS 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:~# cat /proc/cmdline console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/mmcblk0p1 rw rootwait net.ifnames=0 biosdevname=0 On the stock install, I was able to run a memtester test, 10 cycles, no errors. The only thing i got was these xenon-sdhi errors every now and then during the test (below); not sure if it was relevant or not. Although i have seen this when booting, before locking up: [ 3.650635] xenon-sdhci d00d8000.mmc: Timing issue might occur in DDR mode So i'm thinking the hardware is actually OK. It's got to be more a timing issue, or an overlap issue. I restructured the booti components, so there should be no overlaps, though... leaving me with a boot timing issue. Since the stock Ubuntu install fails via kernel panic at times, that's what I'm leaning towards. I guess it could still be configuration in the device tree... i'm not familiar with how to tune those, so looks like I'm going to have to keep digging. I'll have to look closer at what you're doing in ebu-bootloader... maybe it'll work around my issues somehow. Thanks again for all the engagement! -- E.g., Loop 10/10: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : setting 5[20847.635300] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 91[20966.319305] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 108[20989.955374] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 160[21061.452841] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us ok Checkerboard : ok Bit Spread : ok Bit Flip : setting 199[21753.608246] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 256[21832.440524] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us ok Walking Ones : ok Walking Zeroes : ok 8-bit Writes : ok 16-bit Writes : ok Done. -- espressobin-ultra> grep sdhci Errors.txt Block Sequential : setting 44[ 1160.445415] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 104[ 1243.071074] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Bit Flip : setting 207[ 2022.270265] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 493[ 2419.709372] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 51[ 5613.205850] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 86[ 7831.212692] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 114[ 7869.815417] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 139[ 7904.632847] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Bit Flip : setting 252[ 8698.620476] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Bit Flip : setting 345[11019.588593] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 128[12258.573632] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Bit Flip : tesetting 328[13172.479247] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Walking Zeroes : setting 121[13773.551198] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 94[14421.542088] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 241[14624.491234] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Solid Bits : setting 33[16456.854416] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 7[16509.517668] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 216[16797.761210] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Walking Ones : setting 44[17908.735026] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Walking Zeroes : setting 14[18044.789017] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 154[18905.444761] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us [18905.451549] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 228[19007.479627] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us [19007.486828] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Bit Flip : setting 14[19347.751784] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 164[19556.154518] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Block Sequential : setting 5[20847.635300] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 91[20966.319305] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 108[20989.955374] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 160[21061.452841] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us Bit Flip : setting 199[21753.608246] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us setting 256[21832.440524] xenon-sdhci d00d8000.sdhci: eMMC PHY init cannot complete after 1 us

I'm not sure I follow. You have the factory OS (debian IIRC) on EMMC still and it is stable?? But Armbian on M2 does not boot and/or is unstable? My setup has U-Boot loading systemd-boot via UEFI which then loads kernel. I also use Standard Boot so my entire bootcmd is simpy "bootflow scan -b". No complicated scripting. No loading things and calculating memory addresses. Moving away from all of that mess is really the primary motivation for building the firmware for this device in the first place. It is really nice--the only time I ever have to interact with u-boot is when I need to flash the firmware.

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 system will be wiped clean 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 10. adb reboot bootloader 11. fastboot flash init_boot_a /path/to/magisk_patched_init_boot.img 12. fastboot flash init_boot_b /path/to/magisk_patched_init_boot.img 13. 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 2.5+ or some Claude probably. I ended up battling with this for a few days.