All Activity

Hardware: OrangePI-5-Plus (rk3588), with "32 GB" of RAM Operating System: Debian Trixie (pure, except EFI boot and Armbian edge kernel) Root File System: Ext4 (encrypted) Desktop: KDE Plasma 6.3.6 (wayland, GDM3), KDE Frameworks version: 6.13.0, QT version: 6.8.2 EFI Source: https://github.com/edk2-porting/edk2-rk3588 The boot messages, after a few starts (spaced apart) of the low-memory-monitor.service, say there's a failure to start it. After booting is complete, here's a screenshot of the output of: systemctl status low-memory-monitor.service This error didn't show up until I installed a number of packages. I tracked down the offending package from the Trixie repository: Package: xfsprogs Version: 6.13.0-2+b1 Size: 4774 kB Once this package was removed, the error vanished, and a repeat of the above Status command reported low-memory-monitor-service as active and okay. I also found that, while the error occurred with the Armbian edge 6.16.4 kernel, it did NOT occur with the Debian 6.16.3 kernel. Kernel With The Error (kernel source: Armbian) --------------------- Package: linux-image-edge-rockchip64 (Armbian Linux edge kernel image 6.16.4-edge-rockchip64) Version: 25.8.1 Size: 282 MB Kernel Without The Error (kernel source: trixie-backports) ------------------------ Package: linux-image-6.16.3+deb13-arm64-unsigned (Linux 6.16 for 64-bit ARMv8 machines) Version: 6.16.3-1~bpo13+1 Size: 210 MB I also briefly tried regressing the Armbian edge kernel from 25.8.1 (6.16.4) to the previously available version of 25.5.2, which was 6.16.0-rc3 (I think). The error occurred with that kernel as well. An Effect of This Bug (Possibly) When this error was showing up, I was once using the internet (firefox) for a while, when after closing it, I discovered that my desktop background image had changed on its own. I could not change it back, no matter what I did. I could change it to something else, but whenever I changed it back, the altered image returned instead of what it should have been. But once I rebooted, the background was back to normal. While this one experience is not a conclusive, it is indicative of a possible memory leak.

@SuperKali I have the original NanoPC-T6 - purchased around 2 years ago. While it does negotiate HS400 mode, it's not stable - medium or heavy I/O activity like performing an apt upgrade or even booting will cause I/O errors to be logged by the kernel. I've just tried switching to 6.16.4-edge-rockchip64 via armbian-config. It took a few attempts to get it booted - it hung several times at "begin: running /scripts/init-bottom ... done". On the successful boot, I could see quite a few I/O errors during boot. Here's the kernel logs showing HS400 mode was negotiated along with the I/O errors: root@nanopct6:~# dmesg | grep mmc [ 1.776595] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ 1.875696] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.876758] mmcblk0: mmc0:0001 A3A444 230 GiB [ 1.880737] mmcblk0: p1 [ 1.881457] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ 1.883682] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ 1.885887] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0) [ 2.191107] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 2.191125] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 2.191132] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 2.191158] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 122,32 bit host data width,256 deep fifo [ 2.191894] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO [ 2.204956] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 4.370210] EXT4-fs (mmcblk0p1): mounted filesystem a4f48be8-f667-4cac-a9a7-61ce8f9035d1 ro with ordered data mode. Quota mode: none. [ 5.796770] I/O error, dev mmcblk0, sector 261857 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 5.819713] I/O error, dev mmcblk0, sector 261857 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 5.848297] I/O error, dev mmcblk0, sector 261857 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 7.379796] I/O error, dev mmcblk0, sector 221648 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 [ 7.538332] I/O error, dev mmcblk0, sector 183451920 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2 [ 7.727265] I/O error, dev mmcblk0, sector 182816073 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 [ 7.889544] I/O error, dev mmcblk0, sector 182816073 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 8.181746] I/O error, dev mmcblk0, sector 182816073 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 8.325932] I/O error, dev mmcblk0, sector 182816073 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 8.865460] I/O error, dev mmcblk0, sector 189262696 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2 [ 9.097362] EXT4-fs (mmcblk0p1): re-mounted a4f48be8-f667-4cac-a9a7-61ce8f9035d1 r/w. [ 11.883700] I/O error, dev mmcblk0, sector 189160184 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2 [ 13.327491] I/O error, dev mmcblk0, sector 189233040 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 13.534473] I/O error, dev mmcblk0, sector 189247499 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 14.342633] I/O error, dev mmcblk0, sector 214158 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 [ 16.773905] I/O error, dev mmcblk0, sector 189145145 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 [ 16.943465] I/O error, dev mmcblk0, sector 189142964 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 [ 16.946051] I/O error, dev mmcblk0, sector 189142966 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 [ 17.923621] I/O error, dev mmcblk0, sector 182816073 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 17.943695] I/O error, dev mmcblk0, sector 182816073 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Once booted it's pretty easy to trigger on-demand with a lightweight fio test: fio --filename=fio.bin --size=1GB --direct=1 --rw=randrw --bs=64k --ioengine=libaio --iodepth=1 --runtime=120 --numjobs=1 --time_based --group_reporting --name=rw --eta-newline=1 rw: (g=0): rw=randrw, bs=(R) 64.0KiB-64.0KiB, (W) 64.0KiB-64.0KiB, (T) 64.0KiB-64.0KiB, ioengine=libaio, iodepth=1 fio-3.36 Starting 1 process fio: io_u error on file fio.bin: Input/output error: read offset=705167360, buflen=65536 fio: pid=2237, err=5/file:io_u.c:1896, func=io_u error, error=Input/output error (with similar I/O errors logged in to the kernel logs at the same time). When running in HS200 mode using the DTB provided by @usual user, I can't trigger any I/O errors - no matter how hard I push it via fio. I then tried switching to the vendor kernel ("linux-image-vendor-rk35xx=25.8.1 v6.1.115"). That did result in a bunch of I/O errors being logged (including on the apt output), and when rebooting in to the new kernel there was no output whatsoever (I assume it got corrupted and couldn't boot). So instead, I booted back off the SD card and switched that to the same vendor kernel - which did work. And in better news, I was able to mount the MMC partition from there and run the same fio test without issue. fio --filename=/mnt/mmc/root/fio.bin --size=1GB --direct=1 --rw=randrw --bs=64k --ioengine=libaio --iodepth=1 --runtime=120 --numjobs=1 --time_based --group_reporting --name=rw --eta-newline=1 rw: (g=0): rw=randrw, bs=(R) 64.0KiB-64.0KiB, (W) 64.0KiB-64.0KiB, (T) 64.0KiB-64.0KiB, ioengine=libaio, iodepth=1 fio-3.36 Starting 1 process Jobs: 1 (f=1): [m(1)][2.5%][r=40.8MiB/s,w=42.6MiB/s][r=653,w=682 IOPS][eta 01m:57s] Jobs: 1 (f=1): [m(1)][4.2%][r=43.1MiB/s,w=42.8MiB/s][r=690,w=685 IOPS][eta 01m:55s] <snip - it continues like this> The kernel log output is slightly different on this vendor kernel. While it also negotiated in HS400 mode, there's a few extra things - e.g. CQHCI, a second Bus speed line etc. dmesg | grep mmc [ 8.561754] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply from device tree [ 8.561774] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply property in node /mmc@fe2e0000 failed [ 8.565806] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply from device tree [ 8.565834] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply property in node /mmc@fe2e0000 failed [ 8.566361] mmc0: CQHCI version 5.10 [ 8.597464] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ 8.729576] mmc0: Command Queue Engine enabled [ 8.729603] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 8.731147] mmcblk0: mmc0:0001 A3A444 230 GiB [ 8.739493] mmcblk0: p1 [ 8.740546] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ 8.742822] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ 8.744487] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (234:0) [ 8.946192] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state [ 8.946214] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state [ 8.946285] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 8.946331] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 8.946345] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 8.946397] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 154,32 bit host data width,256 deep fifo [ 8.946494] dwmmc_rockchip fe2c0000.mmc: Looking up vmmc-supply from device tree [ 8.946761] dwmmc_rockchip fe2c0000.mmc: Looking up vqmmc-supply from device tree [ 8.960553] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 9.063046] mmc_host mmc1: Bus speed (slot 0) = 198000000Hz (slot req 200000000Hz, actual 198000000HZ div = 0) [ 9.176670] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 257 [ 9.176684] mmc1: new ultra high speed SDR104 SDXC card at address aaaa [ 9.177135] mmcblk1: mmc1:aaaa SD256 238 GiB [ 9.180796] mmcblk1: p1 [ 10.118815] EXT4-fs (mmcblk1p1): mounted filesystem with writeback data mode. Quota mode: none. [ 11.268903] EXT4-fs (mmcblk1p1): re-mounted. Quota mode: none. [ 110.819476] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Quota mode: none. ------ @usual user Thank you for the information about how you compiled the DTB with the overlay built in. It's also good to hear that the board isn't too difficult to remove. I tried to apply a little bit of pressure around the M.2 slot and the board just fell out! Now I need to find where I put my UART adapter...

can we have HS200 be the default but an armbian-config option to enable HS400 via an overlay [with appropriate warnings/documentation]? fwiw I have a NanoPC-T6 with current/mainline kernel [running my HomeAssistant, so I'm loathe to mess with it] that I had to abandon using the eMMC due to IO errors. It's in the official case so can't do much inspection either.

ARM CPU running Linux 2GB RAM NPU for AI (maybe as little as CV) ARM MPU running Sketch (Arduino) https://store-usa.arduino.cc/products/uno-q Closed source

PR for these changes: https://github.com/armbian/build/pull/8734

@JohnTheCoolingFan what image are you using? I can reproduce the issue consistently with Armbian_25.8.1_Bigtreetech-cb1_bookworm_current_6.12.35_minimal.img . This is the Minimal / IOT image one can grab from https://www.armbian.com/bigtreetech-cb1/ . Interestingly enough, the Minimal / IOT image does not use NetworkManager, it's configured with systemd-networkd backend (or "renderer" as they call it) for netplan. Perhaps this is the key difference: I saw a comment on a topic below stating that MainsailOS has added CB1 Trixie image which is forced to NetworkManager and it's claimed to be stable.

Hi, welcome everyone. I’m using an H50 TV box that I was about to throw away because I thought I had completely bricked it. I disassembled it and found the pins to activate maskrom mode. I think this could be useful for everyone. I then installed the current image, and everything seems to work except for the HDMI output (blank screen). Do you have any suggestions? Thanks. Some data and photo below. In case you want to install please note that also multitool fails to activate the HDMI, so you will need SSH to config. SOC: RK3188 (Hopefully - I did not remove the heatsink) eMMC: Samsung KLMBG4GEAC-B001 32GB (64x4) eMCP: Samsung KMQN10006B 8 GB eMMC + 1 GB LPDDR3 RAM Wi-Fi IC 339S0209 2.4G/5G LAN working WIFI Working ---------------------------- root@rk3318-box:~# lscpu Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: ARM Model name: Cortex-A53 Model: 4 Thread(s) per core: 1 Core(s) per cluster: 4 Socket(s): - Cluster(s): 1 Stepping: r0p4 CPU(s) scaling MHz: 60% CPU max MHz: 1008.0000 CPU min MHz: 600.0000 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid Caches (sum of all): L1d: 128 KiB (4 instances) L1i: 128 KiB (4 instances) L2: 256 KiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-3 Vulnerabilities: Gather data sampling: Not affected Indirect target selection: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Reg file data sampling: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Not affected Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Not affected Srbds: Not affected Tsa: Not affected Tsx async abort: Not affected Vmscape: Not affected root@rk3318-box:~# free -l total used free shared buff/cache available Mem: 1504636 291372 1037440 46940 297848 1213264 Low: 1504636 467196 1037440 High: 0 0 0 Swap: 752316 0 752316 SOME TESTS ON THE HDMI ISSUE: hdmi_debug_20251008_230528.log hdmi_test_20251008_230948.log

That was just a simple one-liner (fdtoverlay -i rk3588-nanopc-t6.dtb -o rk3588-nanopc-t6.dtb rk3588-nanopc-t6-emmc.dtbo). In order to carry out the test in my environment, the typing task was a little more complex: It apparently depends on how the overlay was applied, because fundamentally it should also work when applied dynamically. However, the static application of an overlay has the disadvantage that in the case of an incompatibility, one is only confronted with an error message and does not experience a system that fails to start. It is not very difficult to get it out. It is held only by the slight adhesive strength of the thermal pad between the SoC and the casing when the bottom plate is removed. A cautious light steady pull releases it. The only difficulty is in gripping the board to make apply this pull. I screwed a bolt into one of the mounting PCB nuts and used it as a handle. With such a socket in one of the SMA antenna connection ports, the UART connection can be permanently routed to the outside without modifying the casing. I use it to route the fan connector outside. Without the possibility of providing meaningful serial console logs, you will probably be left on your own with it.

Sorry, I don't have this device. Try inserting a USB flash drive into the USB connector and installing the OS from the SD card on it. Try the available options. And choose focusing on your own real logic. Of particular interest and attention if you install the OS on eMMC. Then boot from the eMMC without an SD card connected. And then insert the card into the SD connector and run $HOME/bin/armbian-install. What do you see in the selection window?

Hello Nob0dy , If you use 25.11.0-trunk.129 after cold reboot you must make soft reboot then second Ethernet port work.

Anyone trying to compile mpv 0.3.9, is it possible to do it with Linux 6.15? With the libraries in Debian Trixie? (considering mpv 0.3.9 is from sept 2024, and Trixie came with mpv-0.4.0) https://github.com/mpv-player/mpv/releases

apt install f2fs-tools

Hello! Stock image from armbian.com; Armbian_25.8.1_Rockpi-s_trixie_current_6.12.41_minimal.img Here is the armbianmonitor's output: https://paste.armbian.com/ikodekuzel The error might be caused by the absence of the f2fs package in the image. root@rockpi-s:~# armbian-install Select filesystem type for eMMC /dev/mmcblk0 2 f2fs <OK> Formating /dev/mmcblk0 to f2fs ... please wait. Error: Filesystem tools for f2fs not installed, exiting root@rockpi-s:~# find / -type f -name f2fs* root@rockpi-s:~#

Ok, I only use this utility on Radxa products ATM, and AFAIK they can't boot from USB without a bootloader on the eMMC or SD card. If I had an image on a USB flash drive attached to the SBC, where would armbian-install expect to find it mounted? And then, would choice #1 or #3 use the SD card or the USB image? Also, should option #2 not show? I don't know how it would copy from the eMMC to the eMMC... The operation of the script works well, but the menu could be much clearer for the Radxa products.

see: /usr/bin/armbian-install The create_armbian function takes different arguments depending on the selection number. Everything looks right on this selection screen. But it seems to me that we see an excessive selection offer in the next selection step and this is misleading. But on other platforms where loading is possible only from a soldered chip, which is defined by the kernel as /dev/mtd, the selection screen will look logical. Try installing the OS on an eMMC or on an SSD connected to the device via a USB-SATA adapter using various options. Experiment. If you find illogical options, then feel free to write your opinion here.

That seems to work! Let me ask you this, though. Can you clarify what selection #2 means? Selection #1 will copy the eMMC image to the SD card. Selection #3 will copy the SD card to the eMMC (shouldn't the text read "Boot from eMMC - system on SD Card, SATA, USB or NVMe") What is selection #2 for?

thanks for getting in touch, looks like you're the first one with these 2gb boxes I think the memory trainer for 4gb and 2gb are the same, do stress and performance tests, if crash occurs you really need a new memory trainer for 2gb, you can find an example of memory trainer on this @mvpwar logs do not use third party images, not even mine, always get the official ones This is really an unknown, I bought 4 boxes of this model in 2022, since then there have been changes in the manufacturer's list of materials, the wifi driver is not configured for a reason, the reason is that the wifi has changed several times, you can install the 2022 driver or you can look for users @dfahren who have a different chip here, or even detect a new chip unknown to everyone sudo rmmod brcmfmac_wcc brcmfmac brcmutil modprobe brcmfmac About the TTL debug: (link) windows debug (link) (link) search by image with Ai tool on aliexpress this topic have images from sd-card holder For this question we need to ask @Jean-Francois Lessard he was in contact with this drivers for a while. (Link) this display will be enabled on kernel 6.18+ if you want to mess with experimental images follow this I only got involved in this because there were many interested users, I wasn't one of them

I am unable to reproduce this on BigTreeTech Pi (v1.2). Set wifi up using netplan via NetworkManager. Wifi connects after a reboot, same if I poweroff the device, disconnect power and then connect back up.

Is your monitor a standard 1080p resolution or something else? If you try a server build that doesn't load a graphical interface does it work? Have you tried something more standard like gnome instead of cinnamon?

Copy armbian-install to bin home directory Please replace line 839 as indicated here: Run the corrected version of the script. If everything works correctly for you, confirm it here. I will add a correction to the next pull request.

I also installed armbian Armbian_community_25.11.0-trunk.273_Aml-s9xx-box_noble_current_6.12.49_cinnamon_desktop.img.xz di s905x tv box, installed on SD memory card, installation went smoothly, creating username and password was completed, after that load desktop enviroment and dark. no hdmi signal, then i turn it off and on again it can start and load to the password entry screen, and after i enter the password and press enter button, it loads then goes dark no signal Again

➜ ~ dmesg| grep mmc [ 1.926019] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ 2.026282] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 2.031712] mmcblk0: mmc0:0001 A3A444 230 GiB [ 2.037074] mmcblk0: p1 [ 2.038122] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ 2.040301] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ 2.042564] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0) [ 2.150020] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 2.150727] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 2.155343] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 2.155854] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 98,32 bit host data width,256 deep fifo [ 2.156969] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO [ 2.169374] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.432912] mmc_host mmc1: Bus speed (slot 0) = 198000000Hz (slot req 200000000Hz, actual 198000000HZ div = 0) [ 2.714811] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 230 [ 2.717703] mmc1: new UHS-I speed SDR104 SDXC card at address 544c [ 2.719268] mmcblk1: mmc1:544c LX64G 58.9 GiB [ 2.721418] mmcblk1: p1 p2 [ 5.394333] EXT4-fs (mmcblk1p2): mounted filesystem 00560a2f-4a48-4f42-85db-f7197f411193 ro with ordered data mode. Quota mode: none. [ 8.122124] EXT4-fs (mmcblk1p2): re-mounted 00560a2f-4a48-4f42-85db-f7197f411193 r/w. Quota mode: none. ➜ ~ uname -a Linux t6.superkali.lan 6.14.4-edge-rockchip64 #1 SMP PREEMPT Fri Apr 25 08:51:21 UTC 2025 aarch64 GNU/Linux root@t6-2:~# dmesg | grep mmc [ 1.793233] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ 1.892860] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.893418] mmcblk0: mmc0:0001 A3A444 230 GiB [ 1.900752] mmcblk0: p1 [ 1.901187] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ 1.902094] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ 1.903152] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0) [ 2.015519] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 2.015588] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 2.015603] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 2.015721] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 98,32 bit host data width,256 deep fifo [ 2.016264] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO [ 2.029321] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.270630] mmc_host mmc1: Bus speed (slot 0) = 198000000Hz (slot req 200000000Hz, actual 198000000HZ div = 0) [ 2.473628] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 247 [ 2.477145] mmc1: new UHS-I speed SDR104 SDXC card at address 544c [ 2.478144] mmcblk1: mmc1:544c LX64G 58.9 GiB [ 2.483356] mmcblk1: p1 [ 3.176039] EXT4-fs (mmcblk1p1): mounted filesystem 3aa41aca-1f77-4222-b253-8d444c3dfca5 ro with writeback data mode. Quota mode: none. [ 8.484634] EXT4-fs (mmcblk1p1): re-mounted 3aa41aca-1f77-4222-b253-8d444c3dfca5 r/w. Quota mode: none. root@t6-2:~# uname -a Linux t6-2.superkali.lan 6.14.4-edge-rockchip64 #1 SMP PREEMPT Fri Apr 25 08:51:21 UTC 2025 aarch64 GNU/Linux root@nanopct6-lts:~# dmesg | grep mmc [ 4.386835] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state [ 4.386849] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state [ 4.386921] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 4.386972] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 4.386986] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 4.387034] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 157,32 bit host data width,256 deep fifo [ 4.387131] dwmmc_rockchip fe2c0000.mmc: Looking up vmmc-supply from device tree [ 4.387431] dwmmc_rockchip fe2c0000.mmc: Looking up vqmmc-supply from device tree [ 4.403026] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 4.495259] mmc0: Command Queue Engine enabled [ 4.495299] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 4.496710] mmcblk0: mmc0:0001 A3A561 57.6 GiB [ 4.505219] mmcblk0: p1 [ 4.505766] mmcblk0boot0: mmc0:0001 A3A561 4.00 MiB [ 4.506882] mmcblk0boot1: mmc0:0001 A3A561 4.00 MiB [ 4.507923] mmcblk0rpmb: mmc0:0001 A3A561 16.0 MiB, chardev (234:0) root@nanopct6-lts:~# uname -a Linux nanopct6-lts 6.1.84-vendor-rk35xx #1 SMP Wed Dec 18 05:56:40 UTC 2024 aarch64 GNU/Linux root@nanopct6-lts:~# The first two are the variants with 256GB of eMMC, therefore non-LTS, while the last one is the LTS variant with 64GB of eMMC. From my tests with both the edge version and the vendor kernel, both negotiate in HS400 without any problems: A test carried out by T6-2: /dev/mmcblk0p1: Timing cached reads: 7686 MB in 2.00 seconds = 3845.97 MB/sec Timing buffered disk reads: 854 MB in 3.00 seconds = 284.38 MB/sec I don't see your errors, so I think there might be something strange with your board. Can you try the edge kernel and tell me if you have the same problems, or the vendor kernel?

@KingJ Which version of the NanoPC T6 do you have? The LTS or non-LTS version? I currently have both, and I will check the eMMC on both.

Hey @amazingfate, I have an issue with the build-in IR receiver on my OPI5+: ##O#O## OS: Armbian 25.8.1 noble aarch64 ####### Host: Orange Pi 5 Plus ########### Kernel: 6.1.115-vendor-rk35xx ############# Uptime: 2 mins ############### Packages: 1934 (dpkg), 5 (snap) ################ Shell: bash 5.2.21 ################# Resolution: 3840x2160 ##################### DE: GNOME 46.0 ##################### WM: Mutter ################# WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: x-terminal-emul CPU: (8) @ 1.800GHz Memory: 2585MiB / 15957MiB After a reboot it works just fine, but once I suspend/resume it stops working. Logs look clear of errors. I have tried to troubleshoot with ChatGPT but goin' in circles and gave up. Lastly ended up with some speculations from it like: static int rockchip_pwm_remotectl_resume(struct device *dev) { struct remotectl_dev *rc_dev = dev_get_drvdata(dev); // Re-init or restart the device if (rc_dev && rc_dev->restart) rc_dev->restart(rc_dev); return 0; } static const struct dev_pm_ops rockchip_pwm_remotectl_pm_ops = { .resume = rockchip_pwm_remotectl_resume, }; static struct platform_driver rockchip_pwm_remotectl_driver = { .probe = rockchip_pwm_remotectl_probe, .driver = { .name = "rockchip_pwm_remotectl", .pm = &rockchip_pwm_remotectl_pm_ops, }, }; Do you think this is the problem, or if not can I share some details so you can try to find it?

hi guys, yesterdays announcement of Qualcomm Arduino UNO Q on some Dragonwing SoC ... but heard anybody about it already? how it can be open? some questions ... P.