Active threads

Certainly worth a look. It is also probably worth comparing the Armbian commit from when I last had it working until now, but it will need to be when I have a bit more time, and me remembering just when I first started seeing these issues.

Hi pcduino2user, glad you are finding it useful. Maybe CMA Buffer size needs to be lowered during the kernel, which actually appears to get ignore anyway once the board has fully booted and replaced with 96mb based on the reserve memory node within the A10 DTSI. This is definitely needed if trying to run a desktop although I wouldn't recommend running a desktop on the Pcduino2. There are still some minor issues that I would like to address in future but I don't have as much time as I used to. For example the pcduino2 is actually booting from the Pcduino1 DTS although this problem is more cosmetic than functional. Both the Pcduino1 and Pcduino2 share the same uboot defconfig file but the Pcduino2 has a USB2 VBUS pin defined within its DTS and physically connected on the PCB. This is normally pulled high by a resistor so does not cause any problems with USB power being enabled. The build framework allows us to configure the kernel but there must be a way to customize uboot more dynamically as well? Now certain Armbian board configuration files appear to contain configuration data for adjusting the dram speed as can be found in the cubieboard.csc so I wonder if a similar setup in the pcduino2 configuration file to override the default device tree property to use sun4i-a10-pcduino2.dts instead of sun4i-pcduino.dts. Given the closeness of hardware it does not seem worth creating a separate defconfig file. Ryzer

Hi @Nick A, the armbian in afiftyp board just see 2GB to, at least it was this way in 2024 when he sent me his boot log. My board is very similar to afiftyp board, except of a number near the QC sticker, that looks like a version number. afiftyp number is 2336 and the mine is 2333. The amout of memory chips is identical to (8 chips), but tha labels is a litle different, but I cant found the label meaning. I use your image since very old one, so I don't think it is about u-boot update, but I could try an older one. About Secure Boot, A patch that you give me solved it and it isn't a problem any more (thanks again for it). @afiftyp, if I'm wrong and you already solve your rom amount in armbian, please let us know and if you could, explain us what you did to solve it, thanks.

Something like git clone https://github.com/armbian/build.git -b main cd build git remote add -f imx8mp-build https://github.com/OLIMEX/imx8mp-build.git git remote update git fetch origin git fetch imx8mp-build git checkout main git rebase imx8mp-build/bookworm # fix conflict vi VERSION git add VERSION git rebase --continue # fix conflict vi .github/dependabot.yml git add .github/dependabot.yml git rebase --continue git log

Following is the output of "mount|grep ro" root@rock-5-itx:~# mount|grep ro proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) /dev/sda2 on / type ext4 (ro,relatime) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19056) ramfs on /run/credentials/systemd-resolved.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) ramfs on /run/credentials/systemd-networkd.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) ramfs on /run/credentials/systemd-journald.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) ramfs on /run/credentials/getty@tty1.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) ramfs on /run/credentials/serial-getty@ttyFIQ0.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) Following is the output of "lsblk" root@rock-5-itx:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.5G 0 disk ├─sda1 8:1 1 256M 0 part /boot/efi ├─sda2 8:2 1 7.2G 0 part / └─sda3 8:3 1 8M 0 part sdb 8:16 0 465.8G 0 disk ├─sdb1 8:17 0 1M 0 part ├─sdb2 8:18 0 512M 0 part ├─sdb3 8:19 0 16G 0 part └─sdb4 8:20 0 449.3G 0 part mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 29.1G 0 disk mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk zram0 253:0 0 11.6G 0 disk [SWAP] zram1 253:1 0 50M 0 disk zram2 253:2 0 0B 0 disk nvme0n1 259:0 0 1.9T 0 disk ├─nvme0n1p1 259:1 0 1G 0 part └─nvme0n1p2 259:2 0 1.9T 0 part

I uploaded an updated version of the package bundle, with MPV and a few other updates that I found laying around: https://mega.nz/file/ZmwDBL6b#pGgXVRnoC0jU6dwFJebBcLDXyTNqdkmw3qvsOLz5qUI

@Dann https://dl.armbian.com/rock-5b-plus/Noble_vendor_gnome verifies fine for me. Try https://netcup-03.armbian.com/dl/rock-5b-plus/archive/Armbian_25.5.1_Rock-5b-plus_noble_vendor_6.1.115_gnome_desktop.img.xz and https://netcup-03.armbian.com/dl/rock-5b-plus/archive/Armbian_25.5.1_Rock-5b-plus_noble_vendor_6.1.115_gnome_desktop.img.xz.sha

AFBC support has been merged to PanVK and will be available in the Mesa 25.3 release! This new enablement reduces memory bandwidth and boosts performance. View the full article

@remolaan "...Hey i have a SDMC DV8040 stb ,SoC-Amlogic S805X,CPU-Quad-core 1.2 GHz,GPU-ARM Mali-450,RAM-1GB,Storage-8GB it currently runs custom made android 9..." Please @remolaan, could you send me a working download link for the custom Android 9 system you made?

You can add APA to your system and as one of the benefits get a managed GPG key so you should not run into this issue again in the future.

Armbian 25.8.1 Noble XFCE (mainline Kernel: 6.16.6-edge-rockchip64) + PanVk - mesa 23.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.7 (https://ryanfortner.github.io/box64-debs/) + wine-10.15-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.15) + DXVK-stripped v2.7.1 ~60fps@720p Hades

Hello @Ian Coelho, have you ever got any solution? I got the same issue

As long as you keep the discussion about this at their place... ophub is (ab)using the name Armbian without permission and they do not contribute to the core development process. Rather they trick users into thinking they get support here and therefore (ab)using our resources.

zero2w != zero2 moved

Hi and Thank @jock That's what I thought. I used ledconf-3 because that's the configuration you made specifically for my MX10 box. I ran a memtest, which went smoothly. The system is working, and I was able to compile rockchip mpp without any problems. The system is running Bookworm. Would it be better to update to Trixie or revert to a previous version? What do you think? I think the problem comes either from rk3318-box.dtb or from the overlays. Thanks again. 🤜🤛

@jock well thanks but I already figured that part out 😊 my problem right now is that i can't find a single distro that works with my box . almost every one (even multitool) goes to a black screen and freezes excatly after 60 seconds . the best thing i could find was a android rom that have the same problem but in excatly 30 minute after booting up ! i did this stupid thing that did not backed up my original rom before writing to internal emcp flash 🤦‍♂️ if i can find any version that doesn't have this problem , i know how to merge armbian rootfs with it ! thank you again !

Have you tried your python script with your Linux PC? If it happens again, you can tell that the problem is within the ESP32 program. I generally prefer having the most complex system (Armbian) poll the simplest device (ESP32), instead of the ESP32 interrupting the Armbian system. I found it more stable that way. Stay with wifi, and use the ESP32 serial port just for debugging. Program the ESP32 print an acknowledgement of data requests, and an alarm if it gets stuck in an unexpected state. I have also found ESP32 circuit or micro python very stable for serial port communications.

@Hqnicolas would it be possible to have the driver @guenter pointed out in the base image?

I think the core problem is that headers were compiled with Ubuntu compiler / userspace and you try to use it on Debian. I used this on Ubuntu, which is the reason why it worked. We are aware of this problem - headers should be distro specific. Which adds complexity on our side ...

Feel free to pr any missing overlay here: https://github.com/armbian/linux-rockchip

moved to csc https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image tl;dr: You are using the wrong image. Get/build one for your board

I don't see it as the very latest bleeding edge kernel version. I see it as a newish Linux, which already has the armbian patches updated for. Some CPUs end up with newer or older Linux versions, due to varying levels of development success. For example, sunxi's armbian edge is 6.15.4 today, but the linux trunk is up to 6.17-rc6 ... (not available in Armbian)

I tried it on 6.16.7, and the log started working: [ 4.838111] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device Error again after initialization: [ 5.118148] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 5.637839] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes

Has anyone ever gotten the Radxa Zero 3w working in gadget mode? I bought a Zero 3w about a week ago and have been beating this horse most of the time. I can't get the device to connect via USB. A or C. When I try to connect (radxa.local) it will always go through wifi. If I have wlan0 disabled or even my internet off it just will NOT connect. It clearly is using wifi to connect even if I use the hostname. Maybe this is something simple but I and another engineer I work with have been scratching our heads about it. The obligatory AI search was an endless loop of everything we had already tried. Anybody have any advice?

I was considering rebuilding the initrd image for orange pi 5 as I think there was an issue in what was put on the image file. But now I have an a system settup with 6.1.115 - I should be good.