ELIAST

All. After some more research I could dig further, but still no picture on the tft screen. It seemes, the same probelm already popped up elsewhere: https://github.com/notro/fbtft/issues/577 by using some ideas there, I could achieve the follwoing: [ 11.299717] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 11.305551] fb_hktft32 spi1.0: fbtft_property_value: bpp = 16 [ 11.305563] fb_hktft32 spi1.0: fbtft_property_value: debug = 0 [ 11.305574] fb_hktft32 spi1.0: fbtft_property_value: rotate = 270 [ 11.305584] fb_hktft32 spi1.0: fbtft_property_value: fps = 20 [ 4.988032] /soc/spi@12d30000/hktft_cs_ogst@0: Fixed dependency cycle(s) with /soc/spi@12d30000/hktft_cs_ogst@0/hktft_cs_ogst_pins [ 11.305404] SPI driver fb_hktft32 has no spi_device_id for odroid,hktft32 [ 11.855462] graphics fb0: fb_hktft32 frame buffer, 320x240, 150 KiB video memory, 4 KiB buffer memory, fps=20, spi1.0 at 40 MHz Which seemes the display is visible by the system now. fbset mode "320x240" geometry 320 240 320 240 16 timings 0 0 0 0 0 0 0 nonstd 1 rgba 5/11,6/5,5/0,0/0 endmode following this route: https://unix.stackexchange.com/questions/20458/how-to-use-dev-fb0-as-a-console-from-userspace-or-output-text-to-it To use the framebuffer as console you need the fbdev module. Ok, let's see this. config-6.6.113-current-odroidxu4 has reference saying ONFIG_FRAMEBUFFER_CONSOLE=y so the above referenced fbdev should already be here. The lcd scripts coming with cloudhell al trying to send text to /dev/tty1 as the output console. So I assume, I should have something similar: dmesg|grep tty [ 0.000000] Kernel command line: splash=verbose console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=4cac61c9-e109-4524-9fd2-c9859f87842c rootfstype=ext4 rootwait rw drm_kms_helper.edid_firmware=edid/1024x768.bin smsc95xx.macaddr=00:1e:06:61:7a:55 governor=ondemand hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=false vout=dvi usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u [ 0.002547] printk: console [tty1] enabled [ 2.122547] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 124, base_baud = 0) is a S3C6400/10 [ 2.123447] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 125, base_baud = 0) is a S3C6400/10 [ 2.123502] printk: console [ttySAC2] enabled [ 9.707531] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty. [ 9.716917] systemd[1]: Expecting device dev-ttySAC2.device - /dev/ttySAC2... ttySAC is the UART what I'm using at the moment. tty1 however is my main "screen", on the HDMI. So the question is, how should I able to tell the system to open an other tty console with fbdev for the LCD screen?

Hi. I recently installed an Armbian 25.8.1 noble to an ODROID XU4 with CLOUDSHELL2. All is wonderful, except one thing. I can't make the small TFT work. I enabled the cs2 option in boot.ini, but did not solve the issue. Then it turned out the module loader in modproebe.d lokks as follows: options fbtft_device name=hktft9340 busnum=1 rotate=270 speed=35000000 force32b=1 bgr=1 but actually there is no such module (only hktft32 or hktft35, or ili9340 - none of these worked): /lib/modules/6.6.113-current-odroidxu4/kernel/drivers/staging/fbtft# ls -1 fb_agm1264k-fl.ko fb_bd663474.ko fb_hktft32.ko fb_hktft35.ko fb_hx8340bn.ko fb_hx8347d.ko fb_hx8353d.ko fb_hx8357d.ko fb_ili9163.ko fb_ili9320.ko fb_ili9325.ko fb_ili9340.ko fb_ili9341.ko fb_ili9481.ko fb_ili9486.ko fb_pcd8544.ko fb_ra8875.ko fb_s6d02a1.ko fb_s6d1121.ko fb_ssd1289.ko fb_ssd1305.ko fb_ssd1306.ko fb_ssd1325.ko fb_ssd1331.ko fb_ssd1351.ko fb_st7735r.ko fb_st7789v.ko fbtft.ko fb_tinylcd.ko fb_tls8204.ko fb_uc1611.ko fb_uc1701.ko fb_upd161704.ko How should it be possible getting this hktft9340 module into the kernel? Thank you!