All Activity

@Nick A 👍

@laibsch It seems that if you set the pixel clock or refresh rate too high that you can shorten its lifespan. But when you use extreme values and the display doesn't have any protection in rare cases you can even damage it. A bigger chance is driver instability or a distorted display.

Device: Orange-Pi-5-Plus Armbian-KDE-Neon After update this morning, KDE-Neon no longer boot up successfully to Plasma Desktop. Error "plasmashell" crash handle pop-up. Able to get into tty session by "ctrl+alt+F3" but not able to boot up successfully to KDE Plasma Desktop after the update/upgrade this morning.

Maybe upstream regression. KDE is using upstream testing branch.

@Nick A could you help me get the dram settings??? My box don't have root access, on aida64, it says my box has root, but the tv info (https://play.google.com/store/apps/details?id=com.saksham.developer.tvinfo&hl=en&pli=1) says it is not rooted?

pinging maintainer @Efe Çetin

@Nick A To be honest i don't really think about debug my box, but i sure will do more research after getting all settings done.

close investigation it seems to use grub, not bootp, card written does not show any activity of green led even after 10 minutes from powerup. Do you have some of the magic twanger needed to boot a pi? Thank you, gene1934

@royk What is the risk of doing that? Can you do actual hardware damage this way or would it be a case of reflashing in the worst case?

adding COMPRESS_OUTPUTIMAGE to your call will compress your image. $ ./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie COMPRESS_OUTPUTIMAGE=xz [...] $ ls -lh output/images/*.xz -rw-rw-r-- 1 user root 342M Aug 15 01:03 output/images/Armbian-unofficial_25.11.0-trunk_Rockpi-s_trixie_current_6.12.41_minimal.img.xz

There is no overlay for that, but at your own risk you can edit the current overlay with some help of AI. But it will need the exact data of the data sheet. Just upload the data sheet, overlay and relevant dts/dtsi files (some of the includes and includes of the includes of rk3588/rk3588s) and ask to make an overlay for this display for Armbian.

Compiling your own image may sound dauting but is actually fairly easy. Help is also available, just ask. https://docs.armbian.com/Developer-Guide_Building-with-Docker/ https://evilolaf.github.io/docupreview/Developer-Guide_Build-Preparation/ https://www.youtube.com/watch?v=kQcEFsXEJEE

Orange Pi 5 user here, got a new NVMe and decided to try the KDE Neon image for a first time, as it's reported that it's been tested and works: And it does -- until you do an apt update and reboot. Upon reboot, the graphical client and cursor appear but keeps popping up a bunch of error reporting windows, because KWin has crashed Just curious if anyone else wants to try it and confirm because you might want to remove that blurb Gnome image works great though, I've been running it full-time as a desktop with excellent stability and long long uptime

I wonder if the ENOENT at around line 493 of your log has anything to do with this. Maybe @schwar3kat has a comment?

Bookworm is going to remain as an armbian-build option, right?

The uncompressed minimal image is about 1.5GB. How large is your trixie based image after you compress it with xz ?

Hi, trying to get a bit deeper into Armbian, I tried to create my own minimal Trixie-based image for the RockPI-S. I'm using a Ubuntu Noble VM and I managed to run a successfull build following the quick start guide. However, creating an image using ./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie leads to an image with a size around 1.5GB. Compared to the downloadable minimal images, which have 200MB-300MB, this is quite large. Does anyone has any hints on how to proceed in order to self-build images comparable to the ones offered for download? Cheers,

@mdidis do non secure boot images show any output. The one posted is an android uboot output.

It seems to me that Gnome is installed by tasksel because you didnt deselect it. I mean that gnome is selected by default.

I tried this patch https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/blob/main/patches/1.5GB_OPZ3_fix.patch , ported to your u-boot (hardcoded 1.5gb), same result. Will try warpme or that sicxnull build, still wondering if I am on a red herring, I'll keep poking around and testing stuff. I'll post as I find things that work/don't work, hopefully this will help someone else too. And no worries, I'm sure your busy. You've helped a lot and helped me get a foundation. Thank you 💯 Log for notes:

Hello, I'm trying to connect a MIPI DSI display. Currently, backlight is working, but not the display in Armbian (Armbian 25.5.1 Noble Gnome). DTS is loaded and corresponding kernel module panel-simple-dsi is loaded as well. Same DTS works on the official Radxa 5c image (rock-5c_bookworm_kde_b2) (kernel 6.1.43-15) Has anyone faced a similar issue? armbianmonitor -u : https://paste.armbian.com/ocoperohak.yaml Thanks!

Do you perhaps know how we could integrate this into Armbian? I don't know much about Gnome internals - came this far: https://github.com/armbian/build/blob/main/config/desktop/common/environments/gnome/debian/postinst

I was thinking the same. Must soldering the TTY cosolle so can getting the Uboot messages. The eMMC is the flash dead and have one Armbian on the SD-Card for jump starting the USB-SSD but the device used is only the USB-SDD i the demesg and it shall writing other devices if not booting one the USB-SSD and its the right one then HA is current and on the SD-Card is not updated. Shall i rewriting the bootloader on the USB-SSD but it shall being updated for some mouths ago ?

Hi, yes, I agree, but I am only a user of Armbian and I do not have such skills to do this solution you suggest I can check the available Community Releases of Armbian and check how it works. Community editions, which are issued for testing and updated on average every week?