All Activity

It is. Before I managed to rebuild u-boot with ZFS support, I had to boot off of EMMC. I shrunk first partition with kernel, initrd etc, and then made another one with actual FS. Temporary solution for me back then. But gave me time to rebuild everything and enable native ZFS boot. Since then, I use EMMC only as a ZFS volume (another one in the mirror is NVME drive). never used armbian-config though - I am old-schooler, so I had to build whole stack myself to get what I wanted.

I am using the same board, and I also experienced this. Sometimes USB is not re-enumerated. Also, if you're using USB-C, sometimes some wires requires you to flip the connector. Basically some makers are cheaping out on cables, and they work only when you flip it. Also, if you'll leave the drive connected and reboot, does it find it? Have you checked u-boot, does it see it? Be aware, that USB-C connector is finicky. I had to replace it (resolder with new, sturdier variant), and then make it concrete-hard to break by solidifying epoxy over and under it (keep connector connected in it, and put some oil on it before plugging it in, so that epoxy won't leak inside it.

Use armbian imager for flashing it, arduino flasher cli is not compatible

Hi @Logan thats probably the reason why your board does not boot from NVME.

@sven-ola there is no nvme device in the /dev

current_6.6.99_minimal (desktop build has the snd-usb-audio module)

@Vinicius Guastala Thank you for your feedback. Your patches have already been merged into my repository.

@KhanhDTP are you using esync of wine? NTsync is available on 6.18+ rk3588 kernels. I think that may give a performance improvement.

Of course, you can build an A7S image now as well. There's no display output yet.

There is a Readme.txt stating: opirv2.img is for Nextcloud install, while Armbian is none of that. You probably want the latter.

Hello I am trying to install armbian on this box (Bqeel U1 Max 4/128G but unable to boot multitool from SD. tried multiple cards and sw (rufus/etcher) does anyone know what could be the reason and how to solve it? I took pics and serial logs also of a successful factory boot. sdfail.txt boot DC.txt

Should I try opirv2-* image or Armbian-* one?

Hello @Eule - what was you solution? When I had to guess: remove SD card to trigger eMMC boot? @Logan There's a real large bunch of reasons, why you where not able to install. That screen shot probably does not show any hints. Copy and paste your terminal session where you hacked in installation commands to a text file. Then post it here as attachment, then I may be able to help. Best // Sven-Ola

@Sergioclr You don't need patches to edit the kernel config: config/kernel/linux-sunxi64-legacy.config sicxnull already has this patch, but with a different name: drv-pwm-sun50i-h616-enhance-pwm.patch drivers-pwm-Add-pwm-sunxi-enhance-driver-for-h616.patch To add Zero2W Ethernet settings to your DTS, you can create your own patch using git commands: Run ./compile.sh Press Ctrl+C in the middle of the kernel compilation. Navigate to the directory: cd cache/sources/linux-kernel-worktree/6.6*/ Use the following commands: sudo git status sudo git add . sudo git commit -m "dummypatch" sudo pico arch/arm64/boot/dts/allwinner/sun50i-h313-x96q-lpddr3.dts sudo git add . sudo git commit -m "Fix Ethernet" sudo git format-patch -1 1 for the first commit (0001-Fix-Ethernet.patch)... 2 for the first and second commit (0002-dummypatch.patch) ) The first "add" and "commit" cleans the kernel of previous patches, leaving you with a clean, patched kernel. The format-patch command will create a patch in the root directory of the kernel. Copy it to your patch directory. For original Armbian kernel patches, you must add them to series.armbian and series.conf.

I have just turned my machines on today and now does the PWM signal on node 3 work, but it is still behaving weird. It is running around 3000 RPM with a pwm1 value of 3, where node 1 need a pwm1 value around 70. The pwm1 was working for 2 hours after that full speed I am currently focusing on fix node 3 (Healthy) which are running the same kernel as node 1 (Healthy) . I checked the dtb files using a sha256sum and that matched on both machines. I did also validate the kernel checksum which also match.

I want to give it a try on MeCool KM6 Deluxe, just started researching.

Thank you for any information... when I have more time I will try with the help of AI... because I don't have enough knowledge myself 🙂 regards

Using our XR expertise, Collabora created a standalone XR experience for our 1% for the Planet partner, SOMAR, to showcase the direct impact of underwater noise pollution on marine life. View the full article

moved to staging

Activity: 1) 159-add-x96-q-lpddr3-v1.3-defconfig.patch has been tested both ways: with original parameters and with suggested (above) parameters; 2) The box boots but I am unable to set IP addresses, even in wlan0, via Armbian-config (errors reported); 3) So far the best result is from ~/build/patch/u-boot/u-boot-sunxi/board_x96q/arm64-sun50i-h313-add-x96q-lpddr3-defconfig.patch with the appropriate +CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y and secure-boot.patch. Armbian-config works as designed and IP addresses can be set. Ideas: describes a similar problem (eth0) Suggested action plan: https://github.com/armbian/build/pull/6617/files [Fix issue #6528 opi-zero2w, ethernet PHY not powered #6617] Problem: I don't know how to implement it and/or if that proposed corrections will tamper with ~/build/patch/u-boot/u-boot-sunxi/board_x96q/sunsi-add-h616-internal-eth-phy-support.patch As usual, suggestions will be welcome 🙂

thank you for official image but can't install to the nvme

You need to look into github changes then, everything is traceable, but certainly not an easy and quick thing to do.

@KhanhDTP, that's great news! Thank you very much for the testing!

What you prefer or think is best. An extra boot partition is more flexible as it is an extra 'boot-stage' sort of, and normal computers that use UEFI anyway need also a FAT formatted bootpartition besides 1 or more rootfs for (multiple) OS. So not a bad approach to have separate boot partition an if on SD-card, is removable, so is flexible in case of trouble and/or testing things.

For that dts file must be changelog somewhere explaining changes. I decompiled both dts files but it is hard for me to decode changes in short time.