All Activity

@bedna Yeah, that's exactly what I was asking. I found out how to install armbian on the NVMe, which is simply to run armbian install and it does it automatically for you. I don't see why that would be impossible if one can boot Armbian with Armbian. Is the '/boot' section that much geared to a distro? I thought that was just the linux kernel part. I also get the feeling that I would probably not need Armbian at all, but u-boot installed on the SD card, but that installing Armbian was at least a good start to see if everything was working and what the guix system ARM iso file is an iso9660 filesystem meant for a USB device, meaning that that I would need u-boot installed on the SD card to first boot the USB device run the guix system installer and then have u-boot boot the NVMe device.

From what I've seen, that particular tool is not as well maintained as some others. If it's a major uboot failure, it won't boot. If it's working, I think that's your answer.

It may be possible. But due to limited resources, forum support is limited to using Armbian as-is. Everything else goes in Off Topic. If you're truly interested, you could attempt to take the Armbian bootloader, kernel, and device tree, and drop that into a Guix install. But at that point, you are very much on your own.

@FrancasioHi, could you direct me to the link for that image? Thanks.

Guation. Would you be willing to share the patches (or Git commits) used to build the 1 GB Cubie A5E images? I'd like to incorporate them into the current Armbian build framework instead of using a prebuilt image.

i used nand-sata-install to move root from sd to ssd. at the end just after "Finalizing file sync ... Please wait" i got "Error while creating U-Boot loader image with mkimage" at the bottom of the screen. i rebooted and all seems to be working as planned. is this error anything to worry about?

raspbian is old 32-bit ARMv6, or maybe you use wrong naming. I see orangepi pc2 is also 1GB RAM and 4x Cortex-A53. So that is the same as RPi3B+. Armbian should be 64-bit on the orangepi pc2 and if that runs fine for you with HA, then it should also run fine the same way on RPi3B+. Armbian has no 32-bit support for raspberries, so maybe have a look if there is a ready-made image. The root filesystem on the orangepi pc2 you have currently should run almost unmodified on a RPi3B+. The issue is that raspberries boot filesystem is proprietary, but if you know or get to know how it works, you could get it to run.

That might be due to little RAM. I did a test install about a year ago on a raspi 3b+ with 1GB RAM, and it became extremely slow after a short while. htop showed, that the system was completely busy with swapfile access. Even a shutdown took some hours. Homeassistant might claim, that 1GB can suffice, but IMO that's more a proof-of-concept than a workable solution. As soon as you add some integrations, the free memory becomes quickly too low.

Maybe I am misunderstanding your question but: Armbian is one operating system, and Guix system is another operating system, so no. It's the equivalent of asking "can I install debian but boot NixOS from debian on another storage device". Unless it's a virtual machine you are talking about, you might be able to run a Guix system as a virtual machine in armian, but I don't think that is what you are asking. If you want to run Guix system, you need to boot Guix system. If it's just the package manager Guix you are talking about, then afaik also no (if you are talking about the guile scheme), for that to work you need to run Guix system, just like you need to use NixOS to run nix package manager. But I could be incorrect.

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

Is it possible to run armbian with pre-installed homeassistant on a raspberrypi 3B+ ? The reason of my question is, I have running homeassistant on a orangepi pc2 which work very well. On the raspberrypi 3B+ running unter raspbian, homeassistant is very slow.

I like Guix system. I really like it on my desktop, so now I want to use Guix system as the OS for my Orange Pi 5 Pro as well. The problem is, the Arm distro for Guix System is only available for Generic EFI and I didn't have the money to buy a Orange Pi 6 Plus. But I figure, why not install Armbian on SD card and have it boot Guix System on the SSD? Is that possible and if so, how would I achieve that? So far I've been able to 'dd' the guix system install ISO onto the SSD. It seems to have an iso9660 filesystem.

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.

Hi! I've been using the latest build on my H96Max TV Box (H313, 2GB LPDDR3) for a while and it works just fine. Recently tho, I've noticed that a more up to date community build for the X96Q DDR3 TV-Box popped up on the main boards page on armbian.com. So I got curious and tried booting that one, and it boots, but the built in ethernet port doesn't work there for some reason? I checked in the config file, and the kernel does seem to have the right drivers built in (dwmac-sun8i ig?). What should I try to get ethernet working on the more recent community builds? Thanks in advance!

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

Moved to the correct forum

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

The issue is not resolved yet. I need help getting the system to boot.