04-08-2024, 12:44 AM
@funkster
This is a bummer.
Checking the InterWeb™, I see this (9 year old) language regarding the fbturbo driver https://github.com/mati75/xserver-xorg-video-fbturbo
I added the italics for emphasis. Purely speculating, I wonder if "drop in replacement" means you could reverse course and use the standard fbdev driver. Someone more intimately familiar with the arcana of the X Window System might comment.
In any case, with the Bookworm edition of Raspberry Pi OS we'll see the Wayland protocol become the default so who knows what will work then (supposedly X will still be available in the Debian/RaspiOS repos but who knows how many years that will last).
Regards,
Kent
Code:
[ 46.528] (II) LoadModule: "fbturbo"
[ 46.531] (WW) Warning, couldn't open module fbturbo
[ 46.531] (EE) Failed to load module "fbturbo" (module does not exist, 0)
[ 46.531] (EE) No drivers available.
[ 46.531] (EE)
Fatal server error:
[ 46.531] (EE) no screens found(EE)This is a bummer.
Checking the InterWeb™, I see this (9 year old) language regarding the fbturbo driver https://github.com/mati75/xserver-xorg-video-fbturbo
Quote:xf86-video-fbturbo - video driver, primarily optimized for the devices powered
by the Allwinner SoC (A10, A13, A20). It can use some of the 2D/3D hardware
acceleration features.
And because this driver is based on xf86-video-fbdev (with none of the
original features stripped), it actually supports all the same hardware
as xf86-video-fbdev. Essentially, xf86-video-fbturbo can be just used as
a drop-in replacement and run on practically any Linux system. There will
be no real difference on x86, but any ARM based system should see better
performance thanks to some additional optimizations (the elimination of
ShadowFB layer, ARM NEON/VFP code for dealing with uncached framebuffer
reads, automatic backing store management for faster window moves).
I added the italics for emphasis. Purely speculating, I wonder if "drop in replacement" means you could reverse course and use the standard fbdev driver. Someone more intimately familiar with the arcana of the X Window System might comment.
In any case, with the Bookworm edition of Raspberry Pi OS we'll see the Wayland protocol become the default so who knows what will work then (supposedly X will still be available in the Debian/RaspiOS repos but who knows how many years that will last).
Regards,
Kent
