Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4484

Troubleshooting • Cannot run in framebuffer mode, works in Bullseye but not bookworm Raspi3

$
0
0
Hi

I'm trying to get startx running specifically on my TFT screen (MHS35) but encountering the below error regarding framebuffers.
This was working absolutely fine on my Raspberry pi 3 bullseye setup , but on Bookworm I'm getting the below error
Now this works fine with bookworm using a 2GB Raspi4.
I suspect this may not work with a 1GB Raspi4 as that wont have wayland running
I have disabled wayland on the Raspi4 using raspi-config which works anyway.

Hope someone can help
Using Lite OS version in both bullseye and bookworm

Everything is standard, all I have installed is Xorg

Code:

sudo apt-get -y install xorg 
I'm running xserver using startx with the below command

Code:

/usr/bin/startx /home/pi/<script to chromium>.sh -- :1 -layout TFT
I have a 99-fbdev.conf file in /usr/share/X11/xorg.conf.d/ that references my TFT (with some extra bits)

Code:

# FBTFT xorg config file#disable touch on hdmiSection "InputClass"    Identifier  "Touchscreen catchall"    #MatchIsTouchscreen "on"    MatchDevicePath     "/dev/fb0"    Option      "Ignore" "on"EndSectionSection "ServerLayout"    Identifier "TFT"    Option "BlankTime" "10"    Screen 0 "ScreenTFT"EndSectionSection "ServerLayout"    Identifier "HDMI"    Option "BlankTime" "10"    Screen 0 "ScreenHDMI"EndSectionSection "ServerLayout"    Identifier "HDMITFT"    Option "BlankTime" "10"    Screen 0 "ScreenHDMI"    Screen 1 "ScreenTFT" RightOf "ScreenHDMI"#    Screen 1 "ScreenTFT" LeftOf "ScreenHDMI"#    Screen 1 "ScreenTFT" Above "ScreenHDMI"#    Screen 1 "ScreenTFT" Below "ScreenHDMI"#    Screen 1 "ScreenTFT" Relative "ScreenHDMI" x y#    Screen 1 "ScreenTFT" Absolute x yEndSectionSection "Screen"    Identifier "ScreenHDMI"    Monitor "MonitorHDMI"    Device "DeviceHDMI"EndsectionSection "Screen"    Identifier "ScreenTFT"    Monitor "MonitorTFT"    Device "DeviceTFT"EndsectionSection "Monitor"    Identifier "MonitorHDMI"EndsectionSection "Monitor"    Identifier "MonitorTFT"EndsectionSection "Device"    Identifier "DeviceHDMI"    Driver "fbdev"    Option "fbdev" "/dev/fb0"    Option "SwapbuffersWait" "true"EndSectionSection "Device"    Identifier "DeviceTFT"    Driver "fbdev"    Option "fbdev" "/dev/fb1"EndSection



So the problem seems to be with the 1Gb Raspi3

Code:

/usr/bin/startx /home/pi/<script to chromium>.sh -- :1 -layout TFT(==) Log file: "/var/log/Xorg.1.log", Time: Mon Sep  2 04:36:01 2024(==) Using config directory: "/etc/X11/xorg.conf.d"(==) Using system config directory "/usr/share/X11/xorg.conf.d"(EE)Fatal server error:(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices(EE)(EE)Please consult the The X.Org Foundation support         at http://wiki.x.org for help.(EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.(EE)(EE) Server terminated with error (1). Closing log file.xinit: giving upxinit: unable to connect to X server: Connection refusedxinit: server errorCouldn't get a file descriptor referring to the console.

Statistics: Posted by MaryShah — Mon Sep 02, 2024 3:44 pm — Replies 0 — Views 49



Viewing all articles
Browse latest Browse all 4484

Trending Articles