@Igor - Can you have a look at this please. I have retrieved the devicetree's for the radxa Debian release on which the fan works and my Armbian Ubuntu build using dtc -I fs /sys/firmware/devicetree/base uname -a lsb_release -a https://github.com/AaronNGray/radxa-rock-5b-plus The 'pwm-fan' nodes are the same.

@BipBip1981, can you please share again your feedback on fancontrol running on Trixie ? The site can't display the image.

He works as ili9341 and as ili9486. I use it now as ili9486. I`ll go further to make it work as native device. DRM frambuffer its something what needs to be kernel recompiled... as i know? And if i want to use it natively, i must edit or recompile u-boot.... DRM support for ILI9486 display panels modulename: ili9486.ko configname: CONFIG_TINYDRM_ILI9486 Linux Kernel Configuration └─>Device Drivers └─>Graphics support └─>Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) └─>SPI support └─>DRM support for ILI9486 display panels In linux kernel since version 4.14.326 (release Date: 2023-09-23) DRM driver for the following Ilitek ILI9486 panels: * PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5") * RPILCD 3.5" 320x480 TFT (Waveshare 3.5") If M is selected the module will be called ili9486. I will use it for KlipperScreen 😆 But as i se how hard is working that orangePi PC,i`ll doubt if i need this... Any way i`ll try )) Yes. But HDMI not connected. On OrangePiOne image its switching. If HDMI is connected its use it with no output to SPI. But if no HDMI present its use SPI as basic overlay On the same board. Because OPiOne had only 1 usb, OPiPC work only 1 usb ))) if whey work all 3, i`ll didnt open up a topic 😑 ili9486.dts

In that case, dont try my solution: it is for the red ili9341. If you search ili9486 threads in this forum, that same blue LCD is ili9486... so you were wrong in calling it ili9341 in the first place If you have time, find another solution to get you a DRM frambuffer (instead of a classic FB). Then you can enjoy smoother animations and video. Regarding displaying boot messages to the LCD, instead of HDMI. I don't know, but it may be because your HDMI is /dev/fb0 and the LCD is /dev/fb1 Will you use X11?

I`ll think its china lcd, it`s been presented many ears ago by someone to me. Thanks to your sugestions. I read it before topic up. As U can read, it working now, with touch The last question is how to output to it when system boots... Something like auto switch from HDMI to SPI LCD. Or just SPI LCD output after U-Boot loading. rc.local with con2fbmap 1 1 in it is not an good thing. Any Advice?