All Activity

@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

Just a shot in the dark, does this build work better?

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.

$ swapon -bash: swapon: Unknown command I was about to create a swapfile and then the above command happened. Where can I find swapon?

I followed your link and tried your build, nice menu but same error: jedec_spi_nor flash@0: unrecognized JEDEC id bytes: 00, 00, 00 Failed to initialize SPI flash at 0:0 (error -2) This error is from U-Boot and Linux gives the same, my first post shows the error in Linux with debugging turned on and a reduced frequency (and vcc-supply) set in device tree source. It works with Hardkernel's firmware, thus is not a faulty hardware and nothing new.

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

I'd start by checking whether the issue showed up right after an apt upgrade or after updating OMV itself. I've had cases where reinstalling the OMV packages and checking the service logs made it much easier to pinpoint what actually broke. Posting the output of the relevant logs would also help others narrow it down instead of guessing.

As long as you do not provide proper serial console logs, no one can tell what is going on. I can't help you in this situation any further, and you have to find a solution for yourself.

ok, me too is not booting its first. is my hc4 flash chip newer? i think i tried all, mine is not initialized (petitboot said xt25f128b). you said just `run mmc-to-sf`, that is not a mainline v2026-04 standard set variable, brother. Thank you for your answer. I cannot access flash from mainline U-Boot nor Linux.

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

I was wondered homeassistant is running well on the orangepi pc2.(image armbian with pre-installed homeassistant). The raspberrypi3B+, also 64 bit, running raspbian, is very slow. For that reason I would make a test to replace raspbian by armbian. This way I can check if it is the hardware of the pi or raspbian image that make it slow.

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

Nope, my build is based on current mainline and even build on target (aarch64). I.e. no cross-compiling involved. Oh, by the way, in my build bootstd scans any attached storage for a valid bootflow and uses the first found one. The used hardware interface dosen't matter and even network is valid.

After a lot of attemps with kernel versions and so on without any result this is the simple solution: Buy an USB to analog adaptor for 6 euro's brand MOSWAG, that's all folks.

You're using Hardkernel's U-Boot. Yes, it's probably more importent to read from flash memory early, at boot. Using the manufactors bootloader is the only option until the chip or whatever is supported "mainline". If one doesn't care about flash, but doesn't want to depend on SD card to boot from e.g. SATA, an option is to run Hardkernel's Linux, once to write U-Boot to NOR flash . kexec seems to need CONFIG_PROC_KCORE, but Armbian as many others doesn't. Mainline U-Boot doesn't load Hardkernel's Linux. Perhaps just boot the spiupdate.img without spiboot.img and run. (sounds strange I know, but better than cross-cross-compile out-of-date) Any news on mainline (patched) support for SPI NOR flash on Odroid-HC4? Perhaps I miss just a simple thing?

That error with mkimage during nand-sata-install is fairly common on XU4 and usually harmless if the system boots fine afterwards. The tool is a bit outdated and often throws this warning even when U-Boot is written correctly. Since it’s working after reboot, I wouldn’t worry about it.

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.

The kernel 6.18 has the driver i2c-k1x, which is not present in 7.x. There is also i2c-k1, present in both releases. I'm using 6.18 with i2c-k1x, it seems that 10-bit addressing is not supported `i2cdetect -F 4` shows: 10-bit addressing no It seems that the bus is working with 400 kHz frequency, but I don't know why. I was reading driver source and for me if spacemit,i2c-fast-mode or //spacemit,i2c-high-mode is not present, then it shall be 100 kHz. I have no idea how to verify or change the baudrate. I have two sensors, first requires 100 kHz and it is not working, and the second is up to 400 kHz and it seems to be working (I can read some registers, but nothing special). Therefore I assume that bus is operating at 400 kHz.

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.