All Activity

The more SW components you try to let work together in your own systems, the higher the risk something will break as no one else has the same setup. Also if that SW is commercial (and closed-source) things will get worse. Final killer might be external storage like OneDrive, it is not even related to SW actually, just is fundamentally out of your control. If POTUS wants, internet plug is pulled and no access to your data, that, in the mean time can be used for al sorts of purposes you won't benefit from yourself on the longer term. I keep a Windows10 VM around, I had one (upgraded from free Windows Internal test license AFAIR) in VirtualBox, but wanted to move to libvirt/QEMU/KVM as that also works nice for ARM64 and it turned out that the USB extension not always worked (and needed manual install). Also as you noticed, VirtualBox is not in Debian. It was/is? in Opensuse, but with custom kernel module (that is what VMware and VirtualBox need). Now can be based on KVM, but not their defaults and complex as you need to setup/compile? yourself. Windows10 sees another computer when going from VirtualBox to libvirt/QEMU/KVM (with virt-manager as GUI) so I had to buy a new digital license for 20 Euros. I read in september MS will stop delivering updates (unpaid). That day would come of course, so I have a multi-year plan to get rid of Windows (and Google). Windows is almost done. I also have only 1 Intel box running (N100, runs Opensuse Tumbleweed but came pre-installed with Windows11), rest is ARM (or RISC-V or Atmel or Xtensa). Google is more difficult to get rid of, but slowly progressing.

Hi, can anyone help me with this TV box? I need to unlock it, but I don't know where to short the cable because the PC won't connect. Rk3228a, zq01-v1.51

Hi and thanks for the reply I have the device running official armbian at my location (already brought it back) and so I'm trying to figure out a way to "simulate" high latency. Any ideas? Otherwise we'll have to wait a few months so I can place it at it's intended location again. As you can imagine, this is something that's taken a LONG time. Many many months and progress is slow.

For those we cannot and will not help. This is a fork which uses the name Armbian without permission and does not contribute to the core development process. Ask at their place for help. For the leftover: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -u would be a good start.

So I have made some progress. A linux kernel for this device (based on the Berlin chipset family) exists at https://github.com/MarvellEmbeddedProcessors. I',m not sure how this piece adds towards creating a functional armbian install tho.

Hey fellas I have FOUR different armbian devices (one official armbian, three running ophub's armbian) which all seem to struggle with network throughput at high latency connections. It is not a cpu issue and this doesn't occur on x86 debian. Here's the odd thing. If I connect an ethernet usb dongle, like rtl8152b I get the full throughput even at high latency. What??? So it's a nic issue? I thought maybe the onboard ethernet isn't well supported by the kernel so I got a nanopi neo4 with onboard realtek gigabit running official armbian 6.12.3x ... AND it's slow too. Any onboard nic with armbian is slow in my tests. With slow I mean that a single connection gets 5-10Mbit. With a dongle I can get up to 100Mbit on a SINGLE connection from the same device. Why is a usb realtek dongle better supported than onboard realtek gigabit? I don't get it. Does anybody have an idea I could try? What's really difficult is that the problem only shows up at high latency. If I set up a new device at home (low latency) I get full throughput, but when it's in another country 200-300ms latency it just slows down to 5-10Mbit. The workaround with a dongle was just a fluke accident that I happen to notice. I truly believe armbian has a bright future but right now I'm tempted to go back to x86 for my needs and I'd rather not because arm SHOULD be better than x86 for IoT (my use case). Thanks for helping me figure it out. Love your work!

Actually in that post it was about downloading the boot_a partition. Then extracting the dts.. you can skip the dts extraction part for now. We need your boot_a partition. also that’s not the android dts you posted. It has some info but not all of it.

Oh, so it is the devicetree of Linux we want. My bad. Here it is: devicetree.txt FYI I was able to use binwalk -e on the boot partition dump, nice to see there is another way. Thanks for all the help

This post should help extracting your boot.img from android. That’s if your box is already rooted.

/sunxi-fw info -v fulldisk.img @ 0: mbr: DOS MBR protective MBR, GPT used GPT version 00010000 usable disk size: 7419 MB number of partition entries: 17 @ 16: toc0: signed boot image 2 items size: 98304 bytes @ 321: toc0: signed boot image 2 items size: 98304 bytes @26812: fit: U-Boot FIT image fit:__overlay__: "<no description>" fit:__overlay__: "<no description>" fit:fragment@2: "<no description>" So I never dumped just boot0 (and no firmware update available), but I have full emmc dump named fulldisk.img. I would assume it is the toc0? Trying to extract does not work , however: (maybe because there are two?) /sunxi-fw extract -v -n toc0 -o uboot0 /home/Tr/fulldisk.img unknown image file extracting the mbr works fine though.

Wait, that was the Linux kernel, not uboot. I'll get that

I did notice in the log: INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539

uboot-config-dump.txt Here it is

Will do

AXP1530 is the same as AXP313a. Take a look at the link I posted above. You could use this tool to extract your dram settings from an android update or boot0.bin. https://github.com/apritzel/sunxi-fw sunxi-fw info -v boot0.bin

hi, I am moving to mounted virtual drives but now solving OneDrive client, reading all the possible issues as its critical thing OneDrive folder is hidden/missing as its with reparsepoints from win11, so I will solve this there, but interesting is discussion about how unrealiable is ubuntu in relation to updates of even CURL ... heavily used by OneDrive client, author is complaining a lot, pushing Fedora or at least Debian instead of ubuntu because of backports - interesting as Debian has "label" of hairy distro, but it has these backports better updated than ubuntu ?? snap is criticized too - its all new to me, these compound bags and differences between them - apart from that, somewhere is also warfare against systemd, but thats over my head too )) ... saw some video about it, must rewatch ... this is interesting ... https://github.com/abraunegg/onedrive/discussions/3148 here the curl saga ... https://github.com/abraunegg/onedrive/blob/master/docs/usage.md#compatibility-with-curl I will do all whats needded, sure, only leaving it here for others too P.

Hello! Asus Tinkerboard is still perfectly supported by Armbian. Best setup is the current LTS kernel 6.12, you can take an image from the official download page: https://www.armbian.com/tinkerboard/ enjoy!

Thanks c0rnelius, this works.

HOST /dts-v1/; /plugin/; / { fragment@0 { target = <&usbotg>; __overlay__ { dr_mode = "host"; }; }; }; OTG /dts-v1/; /plugin/; / { fragment@0 { target = <&usbotg>; __overlay__ { dr_mode = "otg"; }; }; }; By default it is set to peripheral.

Thank you for the information I have completed the build dependencies step, for mesa 25.2, in Debian Trixie. However, when I build it, my orange pi zero 3 with 1 GB or RAM, it runs out of memory... even when I make a swap file of 2GB. I keep rebooting the opiz3, and continue the compilation job. Is this normal? In the raspberry forum, they told me that my LCD driver panel-mipi-dbi.ko doesn't work with X11... so I give up on this, and continue my development with labwc/wayland (easily installed in Trixie)

Device tree it is. I will follow up if i have any success. Thanks !

I set the dram speed to 648, no difference. Gotta be the axp or another option.

Maybe the mirror isn't good at this time. You can work around by choosing any mirror from this list and add it to your armbian source list: https://docs.armbian.com/Mirrors/

Ah, I misunderstood. I thought does not appear at all anymore but the question was about manual call. Has been answered properly already.

If there is no overlay available you may need to write one by yourself. I'd start by modifying the device tree itself and set the port in question to host and see if this actually works. I think armbian-config comes with a device tree editor. Make sure to make a backup beforehand.