All Activity

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.

I think what you want to ask is "Can I use u-boot to boot Guix system", and the answer to THAT is probably yes, but that has nothing to do with armbian. What eselarm wrote above is what you have to learn/do and understand. IE, you would need to build Guix system using u-boot, and this forum is not the correct place to ask that question. Maybe ask in the IRC chat here https://guix.gnu.org/en/help/ and see if you can find someone that is willing to help out. Or maybe on the reddit: https://www.reddit.com/r/GUIX/ L1tech forum is pretty popular, maybe ask there: https://forum.level1techs.com/c/software/linux/27

I was searching for WI-FI Drivers for my X96 Mini because I was using my device with Armbian ophub's build. The only-ethernet thing kinda annoyed me so dived in and found there's a fix. A guy named lukas-kuna found a fix for the WI-FI chip (HERE). So I tried the fix and It really worked. So I decided to create a driver myself for Future use and for my fellow users. I used the Driver on Armbian 26.08 Build by ophub and the kernel version is 6.18.37. I created a Github Repo so I could share how I did it and how you could do it too. I Used DKMS to Automate the installation process, theres other ways to do it too. Also the DKMS method ensures driver doesn't disappear when switching to New or Different kernel. Here's the GITHUB REPOSITORY : https://github.com/rayhanorigin/SV6051-SV6051P-WiFi-driver-for-Amlogic-S905W-X96-Mini-with-DKMS-support. I'm Leaving the Driver File here as well. GOOD LUCK! NOTE: I didn't try the driver on openwrt because I have no interest on that thing. You may try because ophub's kernels are compatible with his builds of openwrt as well.

I'm back. I have UART converter. My plan is to test the peripherals - I2C at this moment. Since the armbian-config does not allow to configure device tree overlays I figured it out how to do it manually. I edit the file: `/boot/extlinux/extlinux.conf` to add additional line: fdtoverlays /boot/dtb/spacemit/overlay/k1-i2c4.dtbo It seems that U-Boot is ok with this: [ 9.909] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 9.935] Retrieving file: /boot/dtb/spacemit/overlay/k1-i2c4.dtbo [ 9.964] Uncompressing Kernel Image [ 10.316] Moving Image from 0x10000000 to 0x200000, end=27c4000 [ 10.337] ## Loading init Ramdisk from Legacy Image at 21000000 ... [ 10.340] Image Name: uInitrd [ 10.343] Image Type: RISC-V Linux RAMDisk Image (gzip compressed) [ 10.349] Data Size: 21020117 Bytes = 20 MiB [ 10.354] Load Address: 00000000 [ 10.357] Entry Point: 00000000 Verifying Checksum ... OK [ 10.458] ## Flattened Device Tree blob at 31000000 [ 10.459] Booting using the fdt blob at 0x31000000 [ 10.565] Loading Ramdisk to 7c974000, end 7dd7fdd5 ... OK [ 10.584] Loading Device Tree to 000000007c952000, end 000000007c973fff ... OK Starting kernel ... And I'm able to see additional `i2c-4` device: $ sudo i2cdetect -l i2c-0 i2c spacemit-i2c-adapter I2C adapter i2c-1 i2c spacemit-i2c-adapter I2C adapter i2c-2 i2c spacemit-i2c-adapter I2C adapter i2c-4 i2c spacemit-i2c-adapter I2C adapter i2c-8 i2c spacemit-i2c-adapter I2C adapter I'll test some sensors now...

Armbian is I think the easiest way to get Linux running on many many SBC's, but it is already pre-installed. So just 1 OS 1 boot method. If you want more , it is all DIY. Same as if you buy a a Windows laptop and want Linux on it essentially. Or just a DIY build PC where you put Linux on. You will need to understand disks, partitions, BIOS settings etc. But as you say Armbian is a good start as it is Linux so all can be done. An Armbian image for the RK35xx based SBC also contains the proper U-Boot, it is just that that U-Boot uses boot.scr as primary boot method. So if you remove or rename that file, it tries other methods, like extlinux and also as you need, EFI. But it needs to find a partition of type 0xEF00 and just FAT formatted with /EFI/boot/bootaa64.efi on it (or maybe Ext4 also works, at least it does not for computers with UEFI BIOS, those can only read FAT). What you can do to test is to move/delete/rename boot.scr in the rootfs of the Armbian install on the SD-card and then have/put a Armbian UEFI for Aarch64 on NVME/SSD/USB-stick. Or just hide/delete all partitions on the SD-card, then it is essentially only a storage place for U-Boot, same as EEPROM/SPI-NOR-flash on SBC's that have such a chip. Of course you can also go straight to Guix installing yourself, from iso9660 tha tyou put on CD-ROM or USB-stick. But advice is to have a serial console cable connected as U-Boot normally does not initialize HDMI, so don't come here and report 'black screen it does not work'.

@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 a pure 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. I say 'pure u-boot' because I sometimes see these u-boot.img files floating around on the web and just assume these might be the thing that I'm looking for. I have no idea really.

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