All Activity

It appears there would have been no problem with the Logitech Unifying Dongle that uses Bluetooth. I ended up buying a Logitech Keyboard/Mouse combination that is practically identical except uses WiFi protocol rather than Bluetooth as per the suggestion of the vendor of the HamClock Quadra4K. PeeSHaw.... Prices have come down I guess... I found it at the local Wally World for $19.95 on sale... Crazy! I was asking because I had an older Logitech Bluetooth mouse and dongle and was thinking I would just use them and get the keyboard... Thank you for the help!

It works, I'm soooo happy with this. Big thank you!!!

Not excited AT ALL about Allwinner, but there are few (actually none that I've found?) choices for low-priced, "higher performance" SBCs with WiFi 6, BT 5.4, USB3, GB Ethernet, PoE and a small size and factory case. I'll take anything rockchip in a heartbeat I much prefer their chips. My go-to has been the RockPI-S, but it's low performance CPU, WiFi 4, BT 4, 100M Ethernet, USB2, and getting pretty old. AFAIK, there's nothing out there that checks all the boxes, sadly.

@NicoD I download and extract the Wine-Proton prebuilt binaries, then let Box64 do the rest. This is the script I used (You might want to change the directories)

There was a commit 4 days ago on that repo metioned above: https://github.com/joilg/x88pro/commit/a6630814a98b39ec39dc22108c01e35f5d456395 Anyone noticed? Anyone tried it? Any change?

This is putting some sort of warning flag for myself. 'pretty sure', 'chatGPT', a Rockchip board v.s. Allwinner board.

OK, so it actually was cold in FL for a couple weeks and I did a power hack. I ported Java UIO to Java UIO 2. Java UIO (HawtJNI) This was the "Old School" high-performance approach. It relied on a custom C wrapper and JNI to bridge the gap. How it works: You have to write a C helper file, compile it into a shared library (.so) for on ARM architecture (armv7l, aarch64), and bundle it in your JAR. The Overhead: Every call from Java to C has a "JNI transition cost." To minimize this, you used moveJavaToNative to bulk-transfer buffers, which added complexity to the Java code. Java UIO 2 (FFM / Project Panama) The "Modern" approach. It treats native memory and functions as first-class citizens in Java. I now cross compile on x86_64 for arm32 and arm64. How it works: Java uses Linker and SymbolLookup to find functions in u8g2 or libc directly. No custom C wrapper is strictly required unless you want to simplify complex macros. The Overhead: Transitions are heavily optimized by the JVM (often inlined). By using MemorySegment, you can point Java directly at the UIO hardware registers or the U8g2 tile buffer. The Armbian Advantage: It is "Write Once, Run Anywhere" for native code. As long as the system library (like libSDL2.so) exists on the Armbian filesystem, the same JAR will work on an Orange Pi 5, a Pine64, or even a Raspberry Pi without re-compiling C code.

It is possible but I think it is currently broken / unfinished / does not work (properly) yet.

I seem to remember at one point thinking that U-Boot could be installed into the SPI on the a5e and then I could choose the boot order. Is that possible or did I just dream it? If it is, how do I install U-Boot into the SPI? Is there one specifically for the a5e?

does any has vpu supported image for radxa cubie a7z

Could you please explain how to install wine-proton? I've been out of it for a while and don't remember a thing. I'll add it to armbian-gaming when I can make it work. And make a video about the process.

Actually not as I am human - I need time and focus to be able to understand what the code does. Same as everyone else. BASH is list of commands and if you are average tech person you can interpret those command, one after another to understand what is going on. AI can help. You can, but you can not expect that I will answer them. Perhaps someone else will, perhaps nobody. I show you how you can understand it without destroying my brain - I need to look into the code to answer questions ... Its Friday evening here and I already answered at maximum effort.

Just tested trunk 244, (Armbian_community_26.2.0-trunk.244_Radxa-cubie-a5e_trixie_edge_6.18.5_minimal.img.xz) and it doesn't have this reboot issue. However, trunk 244 doesn't support the PCIe, USB3 or WiFi/BT so something must have changed when those devices started to be supported recently. I take that back, it does still have the rebooting issue. I'll keep digging.

OK, so the URL I posted is not correct. If those devices are there, your only option is to use dd with correct offsets on SPI/MTD or eMMC ( or SD-card) to write a U-Boot binary. An lsblk should show those devices, else maybe the armbian-install tool is likely correct with its error message.

Radxa images comes with proprietary vendor kernel v5.15, which we won't integrate for this hardware - Armbian is only made with mainline derived v6.18.y / v6.19.y kernel, which is far from completion. Those SW stacks are fundamentally different. We can produce a Bullseye image, but with a kernel 6.18.y only ... which means identical hardware support as on Armbian Trixie. In general https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working

Lol. Maybe for YOU!! 😉 So I can post my questions about it here, then? Appreciate the help.

The e25 that I have has SD, eMMC and NVME storage options. It has an MTD/SPI as well. Pretty sure it's similar to the Cubie a5e where you can set the boot order in the SPI, however I just chatGPT'd the shit out of that one to get it sorted. I'd prefer to do it the "approved/armbian" way... Again, I assume having U-Boot in the SPI is the appropriate way to do things so I can boot from any of these devices (and perhaps even external USB?). I'd like to understand how to do that if someone knows?

Its BASH, so its easy to interpret: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/bin/armbian-install perhaps by AI: https://chat.z.ai/s/084a9535-9fd8-4078-ab9c-ad85254689cf Refactoring draft: https://github.com/armbian/configng/pull/384 Plan is to write this script from scratch ... but dunno when. This should work in all cases. I hope those tips helps.

see: https://radxa.com/products/network-computer/e25#techspec Only SD-card for this device, hence boot order is something fixed, just hardware. On software level it depends on how U-Boot it configured and compiled and on higher level, what partitions are found, can also be USB-stick, and what is on those partitions. Can be Armbian standard boot.scr or own extlinux or even EFI if you want. So minimum is SD-card with U-Boot on it, else nothing will happen unless maskROM is entered, see Radxa docs.

Awesome. Let me try that. Had to reinstall my SBC cause I done a stupid thing, removed my boot partition. Wanted to format another sd-card of the same size and didn't look well enough. Installing wine and all the others now, will try with all you've mentioned. Big thank you, I'm in the hospital with little to do, and I miss Farming Simulator to make the time pass quickly. Thank you for the great work.

I assume I should be using the MTD/SPI for u-boot on this device? If so, how do I update it and choose the boot order? armbian-install complains "No SPI image found." if I select "Install/Update the bootloader on MTD Flash"

I'm having trouble understanding armbian-install, is this a good place to discuss? Basically, I'd like to understand the menu options better. Probably because it's a generic tool for all devices, the selections aren't clear (to me at least), depending on what device I'm working with. For the most part, all I ever need to do is to copy the working SD image to the eMMC or NVME. Any armbian-install gurus lurking?

Thank you. Basic functionality, few non critical bugs = release ready. Moving to main download location. Imager will have them after they are moved to primary download location. Test images are not there. We don't provide that. We will only provide images with mainline derived kernel which is hard to compare - its a very different SW stack - with Radxa vendor kernel. Basic (!) functions for headless usage are already working. The rest in next 6-12-> month.

This would be amazing. I don't suppose anything came of this? I'm not sure if armbian-install is still actively maintained, but I'm not having any luck using it with several boards I have now.

Ty. Trixie Current and Vendor both boot properly, thank you! (The one difference is that Vendor keeps the LED ring on, Current starts with it on and then goes to green flashing like the other builds) EDIT - with the Vendor build, the USB-A port doesn't recognize any devices. I'll stick with current. Trixie (minimal) isn't available in Armbian Imager, btw, just bookworm and forky. I don't suppose there's a vendor version of trixie for the Radxa Cubie a5e? Current build has a power issue that the Radxa build doesn't.