fixed my problem with maskmod had to hold the RST button with the usb cable connected for 10sec [counted and tried for few times] to be able to enter it again! the other problem only the desktop version works!! tried the minimal img Armbian_community_24.8.0-trunk.6_Rk322x-box_bookworm_current_6.6.31_minimal.img.xz with no vail only desktop ver works Armbian_community_24.8.0-trunk.6_Rk322x-box_jammy_current_6.6.31_xfce_desktop.img.xz

Hello, AFAIK you have two options: - broken board/DDR memories - bad command rate timing The former problem cannot be solved unless you are capable of fixing the board at industrial level, but most probably your problem is the latter. Usually most boards/ddr memories work with 2T (2 clock cycles) command rate, which is more compatible because more "relaxed". For some reasons I don't know, some DDRs want 1T Command Rate. You can edit the multitool.img file with an hex editor and change the byte at position 0xABFC. You should find it to be 0x01 (2T CR), and you should turn it to 0x00 (1T CR): then write again the multitool on sdcard and try again via maskrom The multitool is also capable to switch from 1T to 2T and viceversa when the loader is installed in the eMMC, so if you burn armbian on eMMC, don't forget to use the Command Rate multitool menu option to select the right CR option!

All Armbian images require the user to have an internet connection. Before the first start, your device must be connected to the router using a cable and the router must distribute IP addresses via DHCP. Almost all devices do not have a watch with a battery. Therefore, after the kernel boot stage, the OS service tries to configure the system clock by sending a request to the NTP server. If there is no response, then the system waits for it and kind of stops. The user sees a blank screen. This line says that the system turned out to be in the past. [ 6.026051] systemd[1]: System time before build time, advancing clock. At the same time, it cannot properly process the file system that is in the future. Possible solutions to the problem: 1) Purchase a watch with a battery and connect it to the 40 pin connector. Add a dtbo overlay file for this type of watch. Set the system clock to the current time. 2) Connect the device to a local network in which there is another device with a watch with a battery. Configure and run an NTP server on this device. On a device without a watch, specify the NTP address on the local network.

Description Ubuntu noble ships qbootctl with a bug which makes qbootctl service can't start: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057918. I fixed it in my ppa liujianfeng1994/qcom-mainline. I use a silly dd method to create rootfs. It's better to use losetup to load the built image and copy rootfs from the mounted loop device. Note: ubuntu noble also ships mkbootimg with bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050300, which will make this extension not working. So it's better not using noble as build environment. Debian's fix is still not packaged: https://salsa.debian.org/android-tools-team/android-platform-tools/-/commit/d26c3b5ac89efd92eb96ad029cd06400c1c9f015 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh BOARD=xiaomi-elish BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DEB_COMPRESS=xz DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=noble Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description The general improvements for RK3588 on 6.9 and 6.10 weren't as many as we've hoped, but still this is what was mainlined: USB3 DRD support, including PHY usbdp HDMI PHY GPU We already had most of those features patched in via patches, but this gives us the chance to finally be able to remove those and stay closer to mainline. -> PR summary: (+5,895 - 28,098) ~= 22,000 lines less 👍 (meaning less hassles in the future, less maintenance needed) In addition to that, I have also updated our patch to support RK3588 thermal sensors and management, enabling and improving the use of cooling fans. This patch also includes updates for CpuFreq and OPP. We had an old patch that patched in the HDMI Controller driver, but this patch does not build on 6.10. Fortunately, I was able to include a new, improved version for this driver, which is as recent as 1st of June. Since out "general-add-overlay-compilation-support.patch" became obsolete in Linux 6.9 (see AR-2352) , @paolosabatino developed an improved way on adding overlays as first seen in https://github.com/armbian/build/pull/6690. I have adapted this patch for 6.10, which also paves the way for other kernel bumps to 6.10 in the future. In addition to that, there are some fixes included for Orange Pi 5 and Khadas Edge 2 patches, which were failing on 6.10. Please see the commit messages for details. How Has This Been Tested? [x] Compile success: ./compile.sh BOARD=nanopc-cm3588-nas BRANCH=edge RELEASE=trixie EXPERT=yes KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no [ ] HDMI is untested [ ] More general testing is needed Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article