Active threads

No, same error. We prefer to see the replicateable changes instead of running a wild binary. Does it work for you on real Odroid-HC4 hardware?

@Morales MoralesThe older build where ethernet is working: https://github.com/sicXnull/armbian-build/releases/download/mxqpro/Armbian-unofficial_26.02.0-trunk_Mxqpro-h313_trixie_current_6.12.74_cinnamon_desktop.img.xz The semi-official one where it's not: https://armbian.com/boards/x96q

Oh, my GOD ! I used the Android14 OS image from FriendlyElec google drive, and every video format I tried worked perfectly with full hardware acceleration ! Using Kodi player, this NanoPi M5 it is even capable of playing H.265 Full-4K 60fps 10bit HDR, without frame drop ! So the hardware is perfectly functional for 4K movies. The problem is the software component that is present in other OSes besides Android. Guys, I don't understand... Can't we take the drivers that FriendlyElec used in the Android14 OS image and adapt them for Armbian ? It would be brilliant to have an OS as cool as Armbian with full video acceleration capabilities ! Since I have this board, I'll gladly help you with any tests needed to make this Armbian for NanoPi M5 functional ! Just give me some ideas on what I should do... I will be your NanoPi M5 beta-testeer.

Well I gave up on it. I can't figure out how to boot anything other than armbian on NVMe and I need to boot a USB for starters. I guess I'll have to use for armbian until a cheap board with UEFI arrives. Orange Pi 6 Plus is too expensive for me.

Hi, I think swapon is not visible because you are not root. It should already be there via required package "mount". Try tu "su -" then you will "see" the command.

Hey! i had similar issues with the ES8388 analog and HDMI output path alignment on my OPi5 Plus under recent edge/mainline kernels. Sometimes the card states look fine in ALSA/pavucontrol but the streams just don't bridge to the hardware mapping properly, or the default audio levels are hitting gain issues. To test if it’s just a software-side compression or file amplification issue before diving too deep into modifying the device tree (.dts), try running a quick format check with a known sample using explicit routing- aplay -D plughw:1,0 your_audio.wav If your test files are inherently too quiet or failing to hit the threshold cleanly, you can boost them up beforehand via tools like MP3Louder just to make sure you aren't fighting low baseline source levels on top of the kernel driver bugs. If it completely stays dead silent even with clean, forced audio files, then it's definitely the device tree overlay parameters (simple-audio-card) not toggling correctly on your specific build version. Which image build date and kernel version are you currently on?

The post is from nov 2022, and OP reported it worked 2 weeks later... But good advice non the less... xD

maybe first post the output of uname -a on the raspberrypi3B+

if nand-sata-install is not maintained is there a replacement

Here is the commit: https://github.com/Guation/radxa-cubie-a5e-armbian-build/commit/202f1bf3943e2a583e10405f54b206fae9991a98

@sivert The "edge" kernel 7.x is more or less the stock kernel from upstream. It's missing some specific K1 drivers developed by SpacemiT basically. I think, upstream devs may implement their own version, thus may need some time. I am not sure, if upstream has the necessary SoC register documentation or if they persue some reverse-engineering on this. I recommend sticking with "current". HTH // Sven-Ola

@0757myt: Thank you so much for your clarification. I am really sorry that some parts of the guide are written too briefly. Sometime I don't know how to explain all of this messy things to new users. @hmoob I looked at your board and it seems your board doesn't have a power IC. There are just some diodes and capacitors near the DC port. May be one of them get shorted or burned but they are not really important. If you are good at soldering, you can definitely find the points for + and - pin to power the board so we will have 1 more USB port. Home Assistant need docker supports. Make sure that you are using the latest image (v1.1): https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/tag/kernel-6.6-armbian-26-v1.1

Since you cannot trust this EMMC, @magixx256 Here is how to get log2ram up and running, plus a quick way to double-check your storage health. 1. Install log2ram Manually Run these commands to pull the official repository, install it, and get it running: # Download and extract the latest release curl -L https://github.com/azlux/log2ram/archive/master.tar.gz | tar zx # Move into the folder and run the installer cd log2ram-master sudo ./install.sh # Clean up the installer files cd .. && rm -rf log2ram-master Reboot to Activate It For log2ram to properly hijack the logging system and mount it into RAM, you need to reboot the machine: sudo reboot Verify It's Working Once the box boots back up, run your status command again: systemctl status log2ram You should see an active (exited) status (which is normal for this service, as it just runs a script at boot to create the RAM disk). You can also verify it's actively mounting by checking your system disks: df -h | grep log2ram You'll see a line showing /var/log mapped to log2ram with a size of about 40MB or 50MB. 2. A Quick Note on System Stability Since log2ram holds your logs in memory and only writes them to your eMMC/SD card once a day (or right before a clean shutdown), a sudden power pull means you lose the logs from that day.

Please note that ophub is not Armbian. They use the Armbian name without permission, do not contribute to Armbian development nor participate in these forums. Having said that, android TV boxes are a community supported effort under Armbian. It would be appreciated if you took the time to submit a PR to include your efforts into Armbian.

I have also tried to build a new image and I am now getting a new error related to 16kb size. I have previosly had success 26.2.0 trunk 151, which was able to boot and worked quite well, Excluding known issues such as HDMI support and Fan speed needing to be adjusted with a script. Issue is that this build is no longer available. I think until we get more demand from Retroid Community we might just be out of luck

Problem solved. I used following instructions : Install Hacs on Home Assistant - Step-by-Step [year] — LazyAdmin

I bought an NVMe SSD and it is being recognized.

Hello everydoby. I'm starting work with the same board. Do you have any new information about the images to this board?

@ulumid Ram Initialstation ist done by U-Boot with a suitibal rkbin binary located in the first sectors of mmc. This ist spezific for your Board. connect PC to serial debug console and Test If Android Boot Starts and switchover to mmc if it is pluged.

Java folder inside, please don't use it. Read before: https://github.com/DesktopECHO/T95-H616-Malware

I made this to work on sbc:s both with or without a boot partition: https://github.com/UnconnectedBedna/shrink-backup Uses rsync so it's way faster than a dd. Creates an img file at minimum size. Autoexpansion on restore available for Armbian. Also contains a systemd-nspawn utility if you want to make changes to the img file itself.

Please read the Armbian TV box FAQ and the installation instructions for amlogic TV boxes. https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

Please move to Allwinner https://forum.armbian.com/topic/56539-how-to-install-armbian-on-mx10-f3-tv-stick/ https://xdaforums.com/t/how-to-use-otg-in-twrp.3097688/

Title: [Working Image + Patch] Orange Pi 4A (T527) - Fast Ethernet Fixed on Mainline 7.0 Edge Hi everyone, Since the Orange Pi 4A (Allwinner T527) is currently an unmaintained community target on the bleeding-edge Mainline 7.0 Edge branch, the default images boot up completely blind with cannot attach to PHY (error: -ENODEV) errors. After a lot of debugging, I (with assistance from Gemini - who wrote this post) managed to successfully compile a full, functional Debian Trixie image where Ethernet works perfectly (capped at 100M) and the green status LED pulses a native heartbeat. The secret sauce is that the board uses a Motorcomm YT8531 transceiver, but the kernel falls back to a Generic PHY driver which fails to calibrate the high-frequency RGMII clock skews required for Gigabit speeds. Dropping the link frequency down to 100 Mbps Full Duplex bypasses the timing sensitivity completely, allowing NetworkManager to instantly pull a stable IPv4 DHCP lease! (Note: Mainline 7.0 does not yet have internal C drivers for the T527 audio codec or the SDIO mmc1 bus clocks, so internal audio and onboard Wi-Fi remain offline. Use a USB sound/Wi-Fi dongle if needed). I can't vouch whether HDMI is working or not as I was debugging it using a serial cable. 📦 Download the Image https://drive.google.com/drive/folders/1ieu3TBn2nSP0BaJvJMIhLeLM6kt-x8bX?usp=sharing 🛠️ The Device Tree Patch File I managed to diff the radxa-cubie-5e.dts file and patch it to get it to kind of work with the opi 4a. The patchfile is also in the google drive folder and supplied as an attach here. To include this in your own Armbian build environment, delete any old patches and save this file exactly as: build/userpatches/kernel/archive/sunxi-7.0/zzzz-working-opi4a.patch It wipes out the broken default configurations and replaces them with clean, compiling mainline mappings. You can then build the image using this: ./compile.sh build BOARD=orangepi-4a BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=trixie USERPATCHES_ALLOWED=yes SYSTEM_VERBOSE=yes FORCE_REBUILD=yes 📝 Step-by-Step Instructions to Lock Down the 100M Connection Because the Generic PHY driver cannot process 1Gbps packets correctly, the interface will sit in an unconfigured DOWN loop upon initial boot. Run these steps via your serial terminal loop to bring it online and automate it: Force the hardware down to 100M to clear the packet queue: sudo ethtool -s end0 speed 100 duplex full autoneg off Tell NetworkManager to explicitly negotiate the port: sudo nmcli device connect end0 Make the 100M setting permanent so it survives a reboot: sudo nmcli connection add type ethernet con-name eth-100m ifname end0 802-3-ethernet.auto-negotiate no 802-3-ethernet.speed 100 802-3-ethernet.duplex full ipv4.method auto ipv6.method disabled Automate the green status heartbeat LED: Open /etc/rc.local and add this line right above exit 0 echo heartbeat > /sys/class/leds/green:status/trigger Reboot, and you should have a 100% automated, maintenance-free, fully operational network target - with some tweaking will hopefully get you to the next stage as apt will be working. Hope this helps anyone else struggling to get this community board running on modern releases! zzzz-radxa-to-orangepi4a-fix.patch

Same situation here. The Orange Pi CM4 is not officially supported by Armbian and it doesn't look like it will be anytime soon. The Banana Pi CM4 image works best as a base (same SoC), but expect some missing features like NPU/video acceleration depending on the kernel. Official Orange Pi images are easier but come with all the usual vendor kernel issues.