All Activity

I see this on your dts: ethernet-phy@1 { compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22"; But I think should be: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x1>; And try to use the generic driver for ethernet.

I made a typing error: Please use the the correct emmc block instead the parition: Extract the DTB file with: dd if=/dev/mmcblk1 of=rk3528-<TV_BOX_NAME>.dtb skip=<START_ADDR> count=<SIZE> bs=1

So I rebuilt the image, applied a patch to integrate the tpm into the dts during the build and it works. I still need to figure out how to make overlays work with GRUB in case we need them. Thank you for your support

Since you're using UEFI, you can use Grub to boot. Grub has a Devcetree command. There's also a post here on how to integrate overlays:

Hello, Thank you for your answers. I decided to recompile the whole image with the correct configuration to be sure I did not mess up anything when updating my kernel (following this https://github.com/armbian/build/commit/54c896e0298a441338cd7d29f312ca590304f120 , using BRANCH=vendor RELEASE=noble) I was able to get the boot logs (see attached file). It seems since I'm using UEFI it completely bypasses the U-Boot applying the overlays ( i can see EFI stub: Using DTB from configuration table inside the logs but no Applying device tree overlay...) . I'll try to recompile the image while integrating my overlay directly into it to see if it works. boot.logs

You are likely hitting genuine bugs and/or the situation of missing packages. I do not use Cinnamon, so I cannot comment much. Try to see if there is anything relevant in the logs. Check ~/.xsession* files for hints, too. Maybe try a different DE first, set up it to be working and then work on your preferred choice after that. Have a look at APA which is trying to improve the experience of Armbian as an OS, maybe it can help you. Good luck, amigo!

@Igor, supposedly, these images do not boot. Maybe you have a chance to verify on your end.

http://debug.armbian.de

most likely a bunch of packages that shouldn't have been removed were removed alongside, the joys of GUI package management 1) don't be afraid of the command line 2) see if /var/log/dpkg.log gives any hints what is missing What desktop system were you using before? Try to get it back installed. PS: In your current situation, you can reach a log-in console and command line with Ctrl-Alt-F1 PPS: Reinstalling from scratch might be faster.

I’m currently using the Armbian build system to generate images for the Orange Pi 5 Plus. To use the PREEMPT_RT kernel, I set the BRANCH to current, and with the PREEMPT_RT configuration on the 6.12 kernel I was able to successfully build the image and boot it. However, in this kernel version there are no dtbo files for peripherals like can0, i2c, etc., so I’m unable to use those interfaces. If I set the BRANCH to vendor, I can use the 6.1 kernel, but in order to use a PREEMPT_RT kernel I need to apply the RT patch. The RT patch currently provided is not compatible with the current BRANCH, so kernel build and image creation fail. My question is: while using the 6.12 current kernel, is there any way to copy and use the dtb and dtbo files from the 6.1 vendor kernel?

OK you have a Maxio MAE0621 ethernet chip. @Hqnicolas do you have any suggestions about the best way forward for this? Can I fork armbian github and then try to create a PR to support MAE0621 (I haven't done this before)? Or try to make a dpkg for Maxio ethernet module install (difficult I think)? Or just persist with building a custom armbian image (not sure the patch still works with current LTS kernel)? Edit : The last patch I posted fails on 6.12.58 (drivers/net/ethernet/stmicro/stmmac/stmmac_main.c has changed) I'll try to fix it and post an updated patch.

@qwerty keyboard H313/H616/H618 are pretty much the same. A133 and A64 are different SOC’s. You don’t need the dts for the dram settings.

All the DRAM settings in the patch file are labeled for the H616, but I have the H313. Should I use the data from the H616 or H313 column from the DRAM setting extraction?

I can't seem to manage to extract the device tree because of garbage software stacks (Wtf is "gradle"? Doing everything in BrainF*ck as a joke would unironically be better) but I can atleast extract the DRAM settings! Just running sunxi-fw against the whole firmware image did the trick! @ 16: boot0: Allwinner boot0 size: 49152 bytes eGON checksum matches: 0xf6e7eb45 DRAM parameters: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1f12 0x1f12 PARA0 : - - 0x1 PARA1 : 0x1f12 0x30fb 0x30fb PARA2 : 0x1 0x8000000 0x8000000 MR0 : 0x30fb 0x1f14 0x1f14 MR1 : 0x8000000 0x4 0x4 MR2 : 0x1f14 0x20 0x20 MR3 : 0x4 0 0 TPR0 : 0x20 0xc0001002 0 TPR1 : 0 0x80000000 0 TPR2 : 0 0 0xc0001002 TPR3 : 0 0 0x80000000 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f1107 0x2f1107 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0001002 0xeddc7665 0xeddc7665 TPR13 : 0x80000000 0x6041 0x6041 DRAM parameters 1: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 2: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 3: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 4: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 5: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 6: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 7: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1f12 0x1f12 PARA0 : - - 0x1 PARA1 : 0x1f12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0001002 0 TPR2 : 0 0 0xc0001002 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f1107 0x2f1107 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0001002 0xeddc7665 0xeddc7665 TPR13 : 0 0x40 0x40

One interface is for STA (client mode / normal wireless) and one for AP (access point, where you connect to) or P2P (Wi-Fi Direct). Some firmware / drivers enables this by default. Usually it is in Makefile (just example https://github.com/armbian/rtl8723ds/blob/main/Makefile) but it could also be deep in the code. Don't know.

I don't have a "boot_a", just a regular "boot". Isn't that "_a"/"_b" thing just a redundancy thing on some android devices? Also do I HAVE to use this "gradlew" program? Because it just errors out with some mystery "25.0.1" error code. qwerty@cod-waw-grenade-spam:~/Documents/compiling/Android_boot_image_editor$ ./gradlew unpack ./bootload er.img WARNING: A restricted method in java.lang.System has been called WARNING: java.lang.System::load has been called by net.rubygrapefruit.platform.internal.NativeLibraryLoa der in an unnamed module (file:/home/qwerty/.gradle/wrapper/dists/gradle-8.14-bin/38aieal9i53h9rfe7vjup9 5b9/gradle-8.14/lib/native-platform-0.22-milestone-28.jar) WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module WARNING: Restricted methods will be blocked in a future release unless native access is enabled FAILURE: Build failed with an exception. * What went wrong: 25.0.1 * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. BUILD FAILED in 795ms Why is this damn thing fighting me tooth and nail? Man I hate when this happens. People mention how web browsers are bloated and slow. This is true, but people should also talk about command line utilities that are bloated and slow. (Why does it have to build stuff on first run?)

Thanks laibsch, A little bit better, but this is a partial solution. Start button still missing. to turn off computer I have enter shutdown on cmd. And "logout" what is the command to log out? I am looking for solution on cinnamon forum but nothing until now.

The first image that boots ok down the list of older images is Armbian_25.5.1_Nanopim4v2_bookworm_current_6.12.28_minimal.img.xz Could not get those images to boot: Armbian_25.5.1_Nanopim4v2_trixie_current_6.12.32_minimal.img.xz Armbian_25.5.1_Nanopim4v2_noble_current_6.12.28_minimal.img.xz Armbian_25.8.1_Nanopim4v2_bookworm_current_6.12.41_minimal.img.xz Anyway, I am happy using the one I found booting. Thanks

Oh I get it. Since you are using another distro with newer versions of everything, my effort to build ffmpeg and mpv in Debian Trixie LOOKS like a backport to you XD

Ah sweet! Thank you! Honestly a lot of my frustration came from not being able to find stuff, so these links are a massive help!

Now I did exactly this and after rebooting the Pi, I just get a black screen with a movable mouse cursor. Nothing more, it doesn’t matter how long I wait. What problem is this now?

With 6.12, no changes as far as I know

You can remove packages in Discover.

I have changed it to public。 https://drive.google.com/file/d/1vyQGR8kgzhCzmwuXhb8q5j707U9IXFob/view?usp=sharing And images of my board: https://drive.google.com/drive/folders/1mKd1T83COy1KDLsmb9PbNnlm5FhdrBbV?usp=sharing

For the source code, after a bit of searching, I found https://de3.mirror.archlinuxarm.org I don't know if this will help you. I also tried the MiniArch-20240715-6.17.1-board-a527.cubie_a5e-SD-Image.img image, but it doesn't work either.