failed to enable hardware cursor

[resolut]

Hi I'm using a non-Raspian distro and I'm seeing these errors in Xorg0.log:

Code: Select all

[   182.952] (II) FBTURBO(0): hardware: vc4drmfb (video memory: 4050kB)
[   183.001] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[   183.001] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
[   183.008] (EE) FBTURBO(0): FBIOPUTCMAP: Invalid argument
[   183.009] (II) FBTURBO(0): failed to enable hardware cursor

Could these be caused by (A) a missing kernel module (B) a wrongly configured X server or (C) anything else?
In config.txt I gave the GPU 256M, up from the standard 64M.

Without a properly working X server my GUI experience is bad: It's slow, the bpp appears reduced, and the mouse pointer flickers a lot.
Thanks.

[kerry_s]

do you get the same in regular raspberry os?

[resolut]

do you get the same in regular raspberry os?

I don't. X works fine in Raspian 32-bit.
But Raspberry OS has other bugs that disincline me to use it, specifically neither the kernel nor the GUI deals with encrypted drives well; it's tedious to reverse mouse scrolling direction; and firefox crashes a lot in the 64-bit beta.

[kerry_s]

so what are you using?

if your not using the recommended os, then problems should be expected. no other os is optimized for pi's.
also 256mb is to much, your starving you cpu's. it's 1024mb shared between cpu & gpu, cpu is more important.

[resolut]

so what are you using?
if your not using the recommended os, then problems should be expected. no other os is optimized for pi's.

Slackware for Raspberry pi 4. In many ways it works better but the X Windows part is messed up.

[kerry_s]

so what are you using?
if your not using the recommended os, then problems should be expected. no other os is optimized for pi's.

Slackware for Raspberry pi 4. In many ways it works better but the X Windows part is messed up.

you most likely have no hardware acceleration

[kerry_s]

i read through there docs, it seems most things are manually configured like arch.
the best thing to do is ask in there forums for the proper settings.

[6by9]

FBturbo is incompatible with using mesa and GL for composition.

Rasbian has a systemd script in /usr/lib/systemd/scripts/gldriver_test.sh that nukes /usr/share/X11/xorg.conf.d/99-fbturbo.conf should the KMS driver be detected.

[resolut]

FBturbo is incompatible with using mesa and GL for composition.

Rasbian has a systemd script in /usr/lib/systemd/scripts/gldriver_test.sh that nukes /usr/share/X11/xorg.conf.d/99-fbturbo.conf should the KMS driver be detected.

That's good. What is the current state of 2D and GPU acceleration on the Pi4b? The other distro is just using fbdev for 2D.
I though I heard a while back of a plan to get Vulkan working with the GPU.

[cleverca22]

FBturbo is incompatible with using mesa and GL for composition.

Rasbian has a systemd script in /usr/lib/systemd/scripts/gldriver_test.sh that nukes /usr/share/X11/xorg.conf.d/99-fbturbo.conf should the KMS driver be detected.

That's good. What is the current state of 2D and GPU acceleration on the Pi4b? The other distro is just using fbdev for 2D.
I though I heard a while back of a plan to get Vulkan working with the GPU.

rpi4 has an fkms layer, which is just a kernel-side wrapper that maps the new kms api to the old dispmanx api
v3d is still handled in linux like before i believe

which kms you use, has to be set in the config.txt, like:

Code: Select all

dtoverlay=vc4-fkms-v3d

(i think)

[6by9]

FBturbo is incompatible with using mesa and GL for composition.

Rasbian has a systemd script in /usr/lib/systemd/scripts/gldriver_test.sh that nukes /usr/share/X11/xorg.conf.d/99-fbturbo.conf should the KMS driver be detected.

That's good. What is the current state of 2D and GPU acceleration on the Pi4b? The other distro is just using fbdev for 2D.
I though I heard a while back of a plan to get Vulkan working with the GPU.

rpi4 has an fkms layer, which is just a kernel-side wrapper that maps the new kms api to the old dispmanx api
v3d is still handled in linux like before i believe

which kms you use, has to be set in the config.txt, like:

Code: Select all

dtoverlay=vc4-fkms-v3d

(i think)

(You're correct).
The full KMS implementation for Pi4 has just had v4 sent to the relevant mailing lists. It's now pretty functional, and I'm in the process of updating our 5.4 kernel branch to use it.
On 5.4 you have 3 choices
- "dtoverlay=vc4-fkms-v3d" - FKMS. ARM 3D with a faked KMS implementation using the firmware. This is the default on Pi4.
- "dtoverlay=vc4-kms-v3d" - (full) KMS. ARM control of everything. Currently not totally stable on Pi4 using our kernel branch as it is still using v1 of the patchset.
- no additional overlay - a simple framebuffer with no 3d acceleration.

Your log snippet shows "hardware: vc4drmfb (video memory: 4050kB)". vc4drmfb will be one of the KMS options with emulated frame buffer, hence the guidance not to use fbturbo.