[SOLVED] Local UI display with 3.5 inch TFT

[Langohr]

Hi UpsiUps,

thanks for the quick reply and you pointed me into the right direction. After searching and trying around for several hours I'm pretty sure that xserver is the clue.
With raspian-jessie I was able to run the TFT display as it should. But with moOde I'm receiving this error log from xinit:

[ 88.036] (==) Assigned the driver to the xf86ConfigLayout
[ 88.036] (II) LoadModule: "modesetting"
[ 88.036] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 88.037] (II) Module modesetting: vendor="X.Org Foundation"
[ 88.037] compiled for 1.19.2, module version = 1.19.2
[ 88.037] Module class: X.Org Video Driver
[ 88.037] ABI class: X.Org Video Driver, version 23.0
[ 88.037] (II) LoadModule: "fbturbo"
[ 88.037] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ 88.037] (II) Module fbturbo: vendor="X.Org Foundation"
[ 88.037] compiled for 1.19.2, module version = 0.5.1
[ 88.037] Module class: X.Org Video Driver
[ 88.037] ABI class: X.Org Video Driver, version 23.0
[ 88.037] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 88.038] (II) FBTURBO: driver for framebuffer: fbturbo
[ 88.041] (WW) Falling back to old probe method for modesetting
[ 88.041] (EE) open /dev/dri/card0: No such file or directory
[ 88.041] (WW) Falling back to old probe method for fbturbo
[ 88.041] (II) Loading sub module "fbdevhw"
[ 88.041] (II) LoadModule: "fbdevhw"
[ 88.041] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 88.042] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 88.042] compiled for 1.19.2, module version = 0.0.2
[ 88.042] ABI class: X.Org Video Driver, version 23.0
[ 88.042] (II) FBTURBO(0): using /dev/fb0
[ 88.042] (II) FBTURBO(1): using /dev/fb1
[ 88.042] (II) FBTURBO(2): using /dev/fb0
[ 88.042] (II) FBTURBO(3): using /dev/fb1
[ 88.042] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 88.042] (EE) Screen 0 deleted because of no matching config section.
[ 88.042] (II) UnloadModule: "fbturbo"
[ 88.042] (II) UnloadSubModule: "fbdevhw"
[ 88.042] (EE) Screen 0 deleted because of no matching config section.
[ 88.042] (II) UnloadModule: "fbturbo"
[ 88.042] (II) UnloadSubModule: "fbdevhw"
[ 88.042] (EE) Screen 0 deleted because of no matching config section.
[ 88.042] (II) UnloadModule: "fbturbo"
[ 88.042] (II) UnloadSubModule: "fbdevhw"
[ 88.042] (EE) Screen 0 deleted because of no matching config section.
[ 88.042] (II) UnloadModule: "fbturbo"
[ 88.042] (II) UnloadSubModule: "fbdevhw"
[ 88.042] (EE) Device(s) detected, but none match those in the config file.
[ 88.042] (EE)
Fatal server error:
[ 88.042] (EE) no screens found(EE)
[ 88.043] (EE)


I have found the missing file 99-fbturbo.conf after installing all missing fbturbo drivers and changing from fb0 to fb1, but the xserver can not find any display and stops with fatal error.
I have also followed this fantastic instructions without success:
https://rataks.com/blog/raspberry-pi-tou...omium.html

-> Looks like I'm lost and need further help, please!

BTW: Yes, the cmdline is single line (I can see boot process on the 3.5" TFT). And yes I have edited 99-calibration.conf but I believe this is for touch and I will not use the touch.

Many thanks for your help


P.S. I found this for testing: "cat /dev/urandom > /dev/fb1" and it did what it should: my 3.5" display shows random pattern now but also on ssh I see error message:
cat: write error: No space left on device
Perhaps this could help