All Activity

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

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.

Both logs show initial timestamped text, then the same again non-timestamped. That is something fundamentally wrong. You can de-compile and compared DTB files but it might not reveal why it fails. Btrfs might by just un-related. I see in the NOK log a disabling of an LDO, might be on purpose but also because code is just corrupted somehow. I do not have this BPIM2U board, so no way to see if same would happen for me. Hope someone else can reproduce, else use older kernel that does not fail.

Ok. Thanks. dd copie the blob. It has SPI or a little memory, but as I understand it could be a problem, so it easier to use SD as boot-disk.

Update: After another apt dist-upgrade this day and repeating all steps, it works now :-) Hi, I can boot my RV2 via SD, but it doesn't boot from eMMC after copying it with armbian-install on the eMMC. What I did * Wrote the Armbian-RV2 image to an SD card * Bootet from it * Updated via apt dist-upgrade * Installed on the eMMC via armbian-install * Installed on MTD via armbian-install Any hints what I can do to make it boot from eMMC? Thank you

@humanus Did you build that yourself? I tried Nick's A7A and A7Z images, but they won't boot on the A7S.

logs with verbosity=7 BOOTLOG-NOK.TXT BOOTLOG-OK.TXT

I assume OPi02w has no on-board storage, so it only is the bootcode in ROM, and that reads U-Boot binary blob from fixed sector offset location on the SD-card. It does not even need a MBR-table or GPT and it is not in a partition, so you won't see it. Only if you use dd to read (or write/wipe) that data you will know. See how U-Boot needs to be written for your OPi02w, then you will understand. If the U-Boot is build to initialize the USB and HDD, you do not need /boot partition on the SD-card. But I do not know that. Not all USB-SATA chipset drivers are in U-Boot, so if not, you indeed need a boot partition on de SD-card where kernel initrd DTB are, those should understand USB-SATA chips and so see the rootfs on HDD.

The bootlog-OK.txt shows: [ 10.796728] Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read which is not good at all. I also think you think you still not have set verbosity=7 in armbianEnv.txt, else the both the OK and NOK logs would show more and that is needed as a start for further investigation.

After inspecting the differences between those 2 bootlogs, it looks like it hangs up for some reason when trying to check the root filesystem for errors.

Hey Installed Armbian (Ubuntu-noble) with XFCE desktop on an HDD(sda) from SD-card, so I need to have an SD-card in my orange pi zero 2w. I wonder if I can move /boot to an another smaller SD-card? Or do I also need an "mbr" or someting also there u-boot are? /Cheers

Bootlog with non-working and working dtb file. bootlog-OK.txt bootlog-NOK.txt