Active threads

Thank you very much c0rnelius. After applying your fix SPDIF works on VONTAR X3 Amlogic S905X3.

Right so 1GB - display framebuffer allocation. Can you confirm HDMI works as it been a while since I built an system image with 6.1 kernel. I dont recall display issues, just problems relating to SPI at the time. Anyway kernel 6.1 is no longer supported, even as a legacy kernel. The earliest kernel you can now build with is 6.6. I am suprised that the mirrror archives I have looked at so far do not feature any 6.6 kernel builds for the Cubieboard. Thats not to say it would be impossible to compile with an older kernel but could prove more trouble than what it is worth. I am interest to see what if encounter any stability issues when booting an edge kernel. Interesting, that is the exact same RAM chips used on the pcDuino2 but the additional text enscribed is different. Just to be safe can you run memtester to see if it picks up an errors. For example: sudo memtester 64MB 2. Even without re-compiling the entire system, what we can do is replace the targeted board dts. This should be doable given you already have a serial link, but you will need to catch uboot early on to hault to boot process to get a uboot prompt. Then running setenv ftdfile sun4i-a10-topwise-a721.dts to see if the onboard display works. *update* - upon checking kernel sources the previously mentioned patches are no longer necessary as the changes appear to have been included in the latest sub revision of kernel 6.12.30 All the best Ryzer

Actually its the opposite so it must have been something else. Etcher is known to be broken for bigger images (desktops). There is some bug in the .xz decompression method used by Etcher. I am using only USB imager for at least a year and haven't run into any problems. At least not on this level.

moved

yes I can confirm

Thanks - I'm worried my main issue was with the overlay loading issue I mentioned. I did try 6.15 but prob need to retry with the hack with overlay-user. But man... it is SO incredibly simple to switch the kernels.

See for more details but without using the overlay-user folder - I was not able to get the pwm to work on a fresh download.

https://paste.armbian.com/cawuyeyice

Armbian 24.5 works normally, but this issue occurs in versions 24.8, 25.5 and 25.8 [ 0.872698] dwhdmi-rockchip ff940000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 0.872852] dwhdmi-rockchip ff940000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.361552] dwhdmi-rockchip ff940000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 2.361723] dwhdmi-rockchip ff940000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.361912] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) [ 2.363007] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff80008120fe60) [ 22.444508] hdmi-audio-codec hdmi-audio-codec.8.auto: Only one simultaneous stream supported! [ 22.444524] hdmi-audio-codec hdmi-audio-codec.8.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 0.871390] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffff80008120b5e8) [ 0.872604] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffff80008120b5e8) [ 2.360057] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffff80008120b5e8) [ 2.361397] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffff80008120b5e8) [ 2.363007] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff80008120fe60) [ 2.364674] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [ 2.510919] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device

I just did some new experiments, trying to get touch working in ili9488 LCD v2.1 Increasing or decreasing the SPI MHz in both the LCD and touch section of the DTS DONT WORK... I couldn't get touch working Next is to use a software defined SPI with spi-gpio (based on my experience in my ili9341 thread) does anybody know a Python soft spi program which can talk to ads7846/xpt2046?

And could you tell me how to add a patch to my .dtb or .dts file. I installed linux-headers but I don't know what to do next with the patch posted above by c0rnelius.

I was having some trouble with newer ili9488 LCD v2.1, and I didn't have ili9488 LCD v1.1, so I decided to experiment again with ili9341 LCD v1.2. I found that this DTS https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#findComment-204672 Doesn't work with the touch chip. By accident, I ran the ili9488 driver on this ili9341, and I saw garbled graphics... but the good news: touch was working. Something in the ili9488 DTS which doesn't work for the ili9488 LCD, works for ili9341. I found the difference was not in the ads7846 section, but in the spi speed for the ili9xxx part. I switched back to the ili9341 DTS (with adafruit driver), but changed the SPI speed from 24MHZ to 40MHz.... then the ili9341 DTS was working with graphics and touch again ALTHOUGH the graphics have some flashing pseudo-colors in some places. Maybe the 40MHZ is too much, but I re-gained touch in ili9341 LCD v1.1. I will keep doing experiments. Playing with the SPI Mhz didn't help with the ili9488

So I was able to reproduce the issue when trying to boot via NVMe after using armbian-config to switch from emmc. Using rkdeveloptool to flash the SPI with https://dl.radxa.com/rock5/sw/images/loader/rock-5b+/release/rock-5b+-spi-image-8ea7ee4-20240730.img (short guide in the spoiler) I was able to boot into the NVMe. Looking into fixing the broken SPI installation

Check here https://github.com/armbian/community/releases/tag/25.5.0-trunk.256 or on a mirror with archive https://docs.armbian.com/Mirrors/#current-mirrors for what you are looking for. We're aware that some links are broken for yet to be determined reason.

I think using the ubuntu keyserver is good as well but that this is a 'small' issue, it is easy to miss a small thing in a project this huge consider the number of boards, kernels, and distributions (including the different releases). if this little thing breaks, we can fix in our installed os using these methods.

moved

this soldering is visionally not very attractive 😛 , but at lest the result is what counts 👍

We don't deal with Android. Better check xda developers forums.

Description As per title How Has This Been Tested? [ ] hasn't Checklist: [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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description This is a draft/wip for adding https proxy caching. This is especially designed for machines hosting lots of github runners to reduce their bandwidth usage by sacrificing disk space. http caching has been merged already and only needed minor changes. Caching https however is way more complicated. Encryption needs to be broken and rewrapped and then obviously downloads will fail due to cert issues. Classic MITM. So a new certificate authority (CA) needs to be put in place to allow these "fake" certs. Why is this even necessary? Well one major part is downloads from upstream apt repositories. The other major part is downloading 3rd party repositories and artifacts from OCI/ORAS/whatever the correct name for that system is. They do not allow plain http downloads but redirect to https. So in order to cache these encryption must be broken on the fly. On custom runs this works already with the mentioned extension. However when the build framework is used within a GH Actions Runner environment it would need to detect this and enable the extension automatically. No clue how to do that or overall if it is worth diving even deeper into this topic. Therefore this RFC to collect feedback. Also lots of fail-safe checks are missing. Sometimes I had to mix run_host_command_logged and chroot_sdcard since pipes don't work using latter. Documentation summary for feature / change Yes, this would need documentation. How Has This Been Tested? [x] custom builds with ENABLE_EXTENSION [ ] Test B Checklist: [no idea] 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description as per title How Has This Been Tested? [x] build [ ] nope, no hw on hand right now Checklist: [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

Hi, Tried this Opi5-Plus with kernel-6.15.2-edge-rockchip64 but mpv doesn't seems to have vpu hardware acceleration Does this repository works on RK3588 - Orange Pi 5 Plus Debian Trixie with mainline kernel 6.15.2-edge-rockchip64?

I think @amazingfate made a custom Chromium package at some point that included optimizations for rk35xx but no clue about its status. Might be even included in mesa-vpu extension? Firefox probably won't work since that would need adjustments as well and I think messing with browsers is a pita already. topics merged as duplicates.

I don't know. I don't have this board nor is the Armbian team aware of its state since it is community supported. This looks like some upstream (Debian to say) uboot package which certainly does not support this board. IIRC u-boot versions for rk3588, depending on family are something like 2017.09 or 2024.01 (both vendor cases) and 2025.01 or .04 for current/edge.

Same problem here, but enabling the audio codec on armbian-config was not sucessfull on this version: v25.5.1 for Orange Pi Zero running Armbian Linux 6.12.30-current-sunxi Any solution?