All Activity

HI, I dont believe it is necessary to recreate the Topwise A721 dts as it should already be included in the kernel sources used. What most likely needs to be done as a minimum is config file so that the Armbian build system recognizes the board and knows how to handle it. Admittedly I have never added a board so I can only speculate. A problem you may face is that the internal LCD may no longer work with the latest kernels. best of luck Ryzer

oh right, then maybe there is a few things you can help me with in future as I still getting to grips with my esp32. Don't worry it look difficult at first but gets easier. Now I believe I know what the problem, on the overlays line modify it to i2c0-pi and i2c1-pi. This appears to be a common problem with armbian-config overlay functional. My own A10 and A20 systems also has this problem as well.

maybe add manually in the file /boot/armbianEnv.txt the entry: overlays=i2c0 i2c1 i2c2

thank you for your help

I've added trough the armbian-config the current, but no joy. Tried a few from ChatGPT - no joy as well. I am not into this, since it's my first ( so far only ESP32 ), and honestly I had no idea that this requires this much stuff just to run a basic feature😐 Any help is greatly accepted. This is the /boot/armbianEnv.txt : verbosity=1 bootlogo=true console=both disp_mode=1920x1080p60 rootdev=UUID=f5d36c6f-cd6a-4f3b-a0a8-b0e85ac089e5 rootfstype=ext4 overlay_prefix=sun50i-h616 overlays=sun50i-h616-i2c0-pi sun50i-h616-i2c1-pi usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

@jwillb00 I can’t think of anything else. I’ll try to compile another image when I have time.

That solves it thank you very much for your time! If I want to change between boards like Rockpro64, Raspberry Pi4, etc. is there anything that needs to be considered as far as "reset" to a fresh state. For the guide I am writing I would like to make sure there is no lingering configuration that could cause problems when switching between builds for different boards.

Hi! I have an old Allwinner A10 based tablet that runs on Android. I want to install some other OS on it. I tried the instructions on linux-sunxi.org and created a page for the tablet: https://linux-sunxi.org/Softwinners_crane I extracted the FEX file from an image I got from the manufacturers a long time ago: http://github.com/linux-sunxi/sunxi-boards/pull/72/files The linux-sunxi mailing list pointed out that my tablet is similar to Topwise A721, so I used that dts file to compile u-boot and the kernel, and tried to boot it through an SD card. Trying to boot that, u-boot starts, and then gets stuck at "Starting kernel..." Then I found this: After following this and building armbian, I realised that there is no script.bin to replace anymore (I'm guessing because now we use device trees?), so unable to boot this as well. What should I do to make this work with armbian? My guess is that I need to create a new dts or correct the Topwise A721 dts (https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/allwinner/sun4i-a10-topwise-a721.dts) and then try again. The only problem is that I have no experience with device trees. Would really appreciate help on getting this to work, thanks! :)

Hi Yordan, Are you sure you have correctly enabled the i2c overlay on your board? what is the output of cat /boot/armbianEnv.txt? If something is showing up even with nothing apparently connected they your are likely targeting a different bus. It is possible what you are seeing is the address of the internal pmic although this normal shows up as UU. Best of luck Ryzer

All things being equal....... steve@fedora43:~$ uname -a Linux fedora43 6.16.0-0.rc0.250528gfeacb1774bd5.5.fc43.aarch64 #1 SMP PREEMPT_DYNAMIC Wed May 28 19:45:02 UTC 2025 aarch64 GNU/Linux kernel-6.16.0-0.rc0.250529g90b83efa6701.6.fc43. created by jforbes 6 hours ago for Fedora 43 .

Hello. I wonder if this issue is connected to my issue - to show something on i2c, while there is nothing, and not be able to communicate on it ?

@Nick Aseems like that still didn't work. is there anything you do for your builds that is not on the github page? I'll look into it some more tomorrow.

Hello. I'm trying to communicate with i2c ( i've connected ADS1115 on it if this maters ), but even without anything connected on it - it shows 0x30 on it, and I am not sure how to make it works. Please help ! 😐

Beta repository. - should be on servers where we push on directly and this error can't occur (unless something broke down) - is the same quality as other Linux distributions (there is no other distro that would maintain those custom devices) - currently assembly is broken as some patches are failing and thus (beta) repo is not getting any updates until its fixed https://github.com/armbian/os/actions/runs/15337468717/job/43160986093

But still possible You can also switch manually to a fixed mirror from the list here: https://docs.armbian.com/Mirrors/

Since you are on current you cannot expect a major bump until the next LTS kernel is released. current will receive security fixes only. If you want something more recent you need to switch to edge kernels which follow non-LTS mainline kernel releases.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

I've got a ROCK 5B+ with two NVMe drives installed, and for reasons I've not been able to track down, I'm noticing that the `-edge` releases (Kernel 6.14.6) are not able to display more than one of the NVMe drives at once. I've checked various physical configurations (i.e., slot one, slot two, both slots), and only one slot is presented (i.e., output from `lspci` or `lsblk`) – but it doesn't seem to matter whether its slot one or two. If I use a `-vendor` images (6.1.115), I see both devices and can use them without problems. I'd love to be able to provide more information or help debug, but I'm not quite sure where to start here! Cheers Andrew

I noticed the clock speeds not dropping below 1000Mhz also when using the current kernel 6.12 Hopefully 6.14 will address these and let the cores clock down further when it's released to OPi5+ through an apt update.

You seem to take offense at anything that is not rah rah armbian. I can assure you that no offense was intended. Btw, I'm well aware of autonation but the guy that does most of their mainline compiling is a guy named J Forbes and I believe there is another guy who's name I can't remember off the top of my head. The main reason for my previous post was to find out if anyone has analog sound on the opi5+ when running mainline/uefi but apparently that slip right by you. Perhaps you should read my post again!