piCore15.0 Beta

[Juanito]

I tried updating xorg-server as this provides the modesetting driver, but no luck.

If I load graphics-KERNEL, but delete the modesetting driver, x starts using the llvmpipe software acceleration.

One thing I notice is that when graphics-KERNEL is loaded at the console prompt, the screen blanks and doesn't come back without turning it off/on - this doesn't happen with piCore64-15.x (v3d) and didn't happen with piCore-14.x (vc4).

So far no amount of googling turns up anything.

[yvs]

Hello, I have pi3b+ under hands that used to test gtk4 3d app, it works. For TC15 with v4 overlay `inxi -b` output there looks like

System:
  Host: box Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
  Desktop: FLWM v: N/A Distro: piCore 15.0
Machine:
  Type: ARM System: Raspberry Pi 3 Model B Plus Rev 1.3 details: BCM2835
    rev: a020d3 serial: xxx
CPU:
  Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 600 min/max: 600/1400
Graphics:
  Device-1: bcm2835-vc4 driver: vc4_drm v: N/A
  Device-2: bcm2835-hdmi driver: N/A
  Display: server: X.org driver: X: loaded: fbdev failed: modesetting
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    resolution: 800x480
  API: OpenGL v: 4.5 vendor: mesa v: 23.1.4 renderer: llvmpipe (LLVM 15.0.7
    128 bits)
Network:
  Device-1: bcm2835-mmc driver: mmc_bcm2835
  Device-2: driver: lan78xx type: USB
Drives:
  Local Storage: total: 14.84 GiB used: 3.67 GiB (24.8%)
Info:
  Memory: total: N/A available: 920.9 MiB used: 184.3 MiB (20.0%)
  Processes: 112 Uptime: 18m Shell: ash (busybox) inxi: 3.3.35

screen (LCD) doesn't blank and GTK apps with GL 4.5 CoreProfile work not so fast but acceptable taking into account hardware.

If there's need some info for comparing, let it know.

[yvs]

and with modesetting

System:
  Host: box Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
  Desktop: FLWM v: N/A Distro: piCore 15.0
Machine:
  Type: ARM System: Raspberry Pi 3 Model B Plus Rev 1.3 details: BCM2835
    rev: a020d3 serial: xxx
CPU:
  Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 700 min/max: 600/1400
Graphics:
  Device-1: bcm2835-vc4 driver: vc4_drm v: N/A
  Device-2: bcm2835-hdmi driver: N/A
  Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
    dri: vc4
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    resolution: 800x480~60Hz
  API: OpenGL v: 2.1 vendor: broadcom mesa v: 23.1.4 renderer: VC4 V3D 2.1
Network:
  Device-1: bcm2835-mmc driver: mmc_bcm2835
  Device-2: driver: lan78xx type: USB
Drives:
  Local Storage: total: 14.84 GiB used: 4.32 GiB (29.1%)
Info:
  Memory: total: N/A available: 920.9 MiB used: 148.6 MiB (16.1%)
  Processes: 117 Uptime: 3m Shell: ash (busybox) inxi: 3.3.35

[Juanito]

I can get 3d acceleration with wayland:

Code: [Select]

inxi -b
System:
  Host: boxrpi3c Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
  Desktop: Weston v: 8.0.0 Distro: piCore 15.0
Machine:
  Type: ARM System: Raspberry Pi 3 Model B Rev 1.2 details: BCM2835
    rev: a02082 serial: 00000000c521e83a
CPU:
  Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 600 min/max: 600/1200
Graphics:
  Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A
  Device-2: bcm2835-vc4 driver: vc4_drm v: N/A
  Display: wayland server: X.org compositor: Weston v: 8.0.0 driver: X:
    loaded: fbdev failed: modesetting gpu: vc4_hdmi,vc4_drm
    resolution: 1920x1080
  API: OpenGL Message: No GL data available.
Network:
  Device-1: bcm2835-mmc driver: mmc_bcm2835
  Device-2: driver: smsc95xx type: USB
Drives:
  Local Storage: total: 59.48 GiB used: 407.4 MiB (0.7%)
Info:
  Memory: total: N/A available: 920.9 MiB used: 227.6 MiB (24.7%)
  Processes: 113 Uptime: 1h 24m Shell: ash (busybox) inxi: 3.3.35

..but not X (inxi via ssh):

Code: [Select]

inxi -b
System:
  Host: boxrpi3c Kernel: 6.6.34-piCore-v7 arch: armv7l bits: 32
  Console: pty pts/0 Distro: piCore 15.0
Machine:
  Type: ARM System: Raspberry Pi 3 Model B Rev 1.2 details: BCM2835
    rev: a02082 serial: 00000000c521e83a
CPU:
  Info: quad core ARMv7 v7l [MCP] speed (MHz): avg: 600 min/max: 600/1200
Graphics:
  Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A
  Device-2: bcm2835-vc4 driver: vc4_drm v: N/A
  Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
    dri: vc4 gpu: vc4_hdmi,vc4_drm tty: 80x40
  API: OpenGL Message: GL data unavailable in console. Try -G --display
Network:
  Device-1: bcm2835-mmc driver: mmc_bcm2835
  Device-2: driver: smsc95xx type: USB
Drives:
  Local Storage: total: 59.48 GiB used: 407.7 MiB (0.7%)
Info:
  Memory: total: N/A available: 920.9 MiB used: 220.5 MiB (23.9%)
  Processes: 110 Uptime: 1h 52m Init: BusyBox Shell: ash (busybox)
    inxi: 3.3.35


[Paul_123]

Perhaps look at the script mention in the RaspiOS package

https://forums.raspberrypi.com/viewtopic.php?p=2176793&hilit=Vc4+blank+screen+Xorg#p2176793

[Juanito]

Thanks for the suggestion.

There are a couple of scripts, which produce:

Code: [Select]

Section "OutputClass"
  Identifier "vc4"
  MatchDriver "vc4"
  Driver "modesetting"
  Option "PrimaryGPU" "true"
EndSection..but the xorg log says "Option "PrimaryGPU" is not used"

and one that says "Glamor should not run on platforms prior to Pi 4":

Code: [Select]

Section "Device"
Identifier "kms"
Driver "modesetting"
Option "AccelMethod" "msdri3"
Option "UseGammaLUT" "off"
EndSection..but as per the xorg log, glamor is not disabled by it.

If I delete libglamoregl.so, it doesn't help

[yvs]

I can get 3d acceleration with wayland:

Code: [Select]

inxi -b
...
  Display: wayland server: X.org compositor: Weston v: 8.0.0 driver: X:
    loaded: fbdev failed: modesetting gpu: vc4_hdmi,vc4_drm
    resolution: 1920x1080
  API: OpenGL Message: No GL data available.


with wayland it's strange that inxi (it uses glxinfo) cannot detect GL version

Code: [Select]

..but not X (inxi via ssh): [code]inxi -b
  Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
    dri: vc4 gpu: vc4_hdmi,vc4_drm tty: 80x40


not sure, can it be connected with `disable_fw_kms_setup`? In my case with v4+LCD+Xorg there's

Code: [Select]

display_auto_detect=1
dtoverlay=vc4-fkms-v3d
disable_fw_kms_setup=1
in config.txt and I've not touched Xorg.conf at all

[Juanito]

dtoverlay=vc4-fkms-v3d is depreciated, what happens if you use dtoverlay=vc4-kms-v3d?

[yvs]

> dtoverlay=vc4-fkms-v3d is depreciated, what happens if you use dtoverlay=vc4-kms-v3d?
>
  I've not known that, it has been always working there, so I've not thought to change it.
  wiil test a bit further with vc4-kms-v3d and let it know...

p.s. meantime just for test checked it out with hdmi monitor, with hdmi it also works

Code: [Select]

Graphics:
  Device-1: bcm2835-vc4 driver: vc4_drm v: N/A
  Device-2: bcm2835-hdmi driver: N/A
  Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
    dri: vc4
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    resolution: 1920x1200~60Hz
  API: OpenGL v: 2.1 vendor: broadcom mesa v: 23.1.4 renderer: VC4 V3D 2.1
part of Xorg.log related to graphics

Code: [Select]

[    19.828] (II) xfree86: Adding drm device (/dev/dri/card0)
[    19.828] (II) Platform probe for /sys/devices/platform/soc/soc:gpu/drm/card0
[    19.833] (**) OutputClass "vc4" setting /dev/dri/card0 as PrimaryGPU
[    19.833] (II) LoadModule: "glx"
[    19.834] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[    19.856] (II) Module glx: vendor="X.Org Foundation"
[    19.856]    compiled for 1.21.1.8, module version = 1.0.0
[    19.856]    ABI class: X.Org Server Extension, version 10.0
[    19.857] (II) Applying OutputClass "vc4" to /dev/dri/card0
[    19.857]    loading driver: modesetting
[    19.857] (==) Matched modesetting as autoconfigured driver 0
[    19.857] (==) Matched fbdev as autoconfigured driver 1
[    19.857] (==) Assigned the driver to the xf86ConfigLayout
[    19.857] (II) LoadModule: "modesetting"
[    19.857] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[    19.866] (II) Module modesetting: vendor="X.Org Foundation"
[    19.866]    compiled for 1.21.1.8, module version = 1.21.1
[    19.866]    Module class: X.Org Video Driver
[    19.866]    ABI class: X.Org Video Driver, version 25.2
[    19.866] (II) LoadModule: "fbdev"
[    19.867] (II) Loading /usr/local/lib/xorg/modules/drivers/fbdev_drv.so
[    19.869] (II) Module fbdev: vendor="X.Org Foundation"
[    19.869]    compiled for 1.21.1.8, module version = 0.5.0
[    19.869]    Module class: X.Org Video Driver
[    19.869]    ABI class: X.Org Video Driver, version 25.2
[    19.869] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    19.869] (II) FBDEV: driver for framebuffer: fbdev
[    19.869] (--) using VT number 2

[    19.916] (II) modeset(0): using drv /dev/dri/card0
[    19.916] (WW) Falling back to old probe method for fbdev
[    19.916] (II) Loading sub module "fbdevhw"
[    19.916] (II) LoadModule: "fbdevhw"
[    19.917] (II) Loading /usr/local/lib/xorg/modules/libfbdevhw.so
[    19.919] (II) Module fbdevhw: vendor="X.Org Foundation"
[    19.919]    compiled for 1.21.1.8, module version = 0.0.2
[    19.919]    ABI class: X.Org Video Driver, version 25.2
[    19.919] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    19.920] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    19.921] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    19.921] (II) Applying OutputClass "vc4" options to /dev/dri/card0
[    19.921] (==) modeset(0): RGB weight 888
[    19.921] (==) modeset(0): Default visual is TrueColor
[    19.921] (II) Loading sub module "glamoregl"
[    19.921] (II) LoadModule: "glamoregl"
[    19.921] (II) Loading /usr/local/lib/xorg/modules/libglamoregl.so
[    19.986] (II) Module glamoregl: vendor="X.Org Foundation"
[    19.986]    compiled for 1.21.1.8, module version = 1.0.1
[    19.986]    ABI class: X.Org ANSI C Emulation, version 0.4
[    22.288] (II) modeset(0): glamor X acceleration enabled on VC4 V3D 2.1
[    22.288] (II) modeset(0): glamor initialized
[    22.288] (==) modeset(0): VariableRefresh: disabled
[    22.288] (==) modeset(0): AsyncFlipSecondaries: disabled
[    22.290] (II) modeset(0): Output HDMI-1 has no monitor section
[    22.293] (II) modeset(0): EDID for output HDMI-1
....
[    22.295] (II) modeset(0): Output HDMI-1 connected
[    22.295] (II) modeset(0): Using exact sizes for initial modes
[    22.295] (II) modeset(0): Output HDMI-1 using initial mode 1920x1200 +0+0
[    22.295] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    22.295] (==) modeset(0): DPI set to (96, 96)
[    22.295] (II) Loading sub module "fb"
[    22.295] (II) LoadModule: "fb"
[    22.295] (II) Module "fb" already built-in
[    22.295] (II) UnloadModule: "fbdev"
[    22.295] (II) Unloading fbdev
[    22.296] (II) UnloadSubModule: "fbdevhw"
[    22.296] (II) Unloading fbdevhw
[    22.711] (==) modeset(0): Backing store enabled
[    22.711] (==) modeset(0): Silken mouse enabled
[    22.802] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    22.802] (==) modeset(0): DPMS enabled
[    22.802] (WW) modeset(0): Option "PrimaryGPU" is not used
[    22.803] (II) modeset(0): [DRI2] Setup complete
[    22.803] (II) modeset(0): [DRI2]   DRI driver: vc4
[    22.803] (II) modeset(0): [DRI2]   VDPAU driver: vc4
...


[yvs]

> dtoverlay=vc4-fkms-v3d is depreciated, what happens if you use dtoverlay=vc4-kms-v3d?
>
  with vc4-kms-v3d it doesn't work in my case, looking at Xorg.log there's difference with fkms:

Code: [Select]

--- fkms
+++ kms

-(II) xfree86: Adding drm device (/dev/dri/card0)
-(II) Platform probe for /sys/devices/platform/soc/soc:gpu/drm/card0
-(**) OutputClass "vc4" setting /dev/dri/card0 as PrimaryGPU
+(II) no primary bus or device found
...
despite that I can see /dev/dri/card1 there, no idea why it comes in card1 slot with kms, maybe some kindof race condition (I've not digged into it)

[yvs]

I can get 3d acceleration with wayland:

Code: [Select]

inxi -b
...
  Display: wayland server: X.org compositor: Weston v: 8.0.0 driver: X:
    loaded: fbdev failed: modesetting gpu: vc4_hdmi,vc4_drm
    resolution: 1920x1080
  API: OpenGL Message: No GL data available.


with wayland it's strange that inxi (it uses glxinfo) cannot detect GL version

It's the most interesting thing on rpi3, there's no xwayland there? If it's a pure wayland compositor, could you please share that binding API(OpenGL ES version and not llvm renderer) less than 3.0 or later?

[Juanito]

Correct - that's weston running without xwayland - it seems faster than x/flwm too

glxinfo doesn't work on wayland/weston.

Here's all I can find from "XDG_RUNTIME_DIR=/run/user/1001 weston-launch -- --log=/home/tc/weston_log":

Code: [Select]

weston 8.0.0
...
[09:02:07.602] Loading module '/usr/local/lib/libweston-8/drm-backend.so'
[09:02:07.606] initializing drm backend
[09:02:07.608] using /dev/dri/card0
[09:02:07.608] DRM: supports universal planes
[09:02:07.608] DRM: supports atomic modesetting
[09:02:07.608] DRM: supports picture aspect ratio
...
EGL version: 1.4
[09:02:07.722] EGL vendor: Mesa Project
[09:02:07.722] EGL client APIs: OpenGL OpenGL_ES
...
[09:02:07.726] GL version: OpenGL ES 2.0 Mesa 24.1.4
[09:02:07.726] GLSL version: OpenGL ES GLSL ES 1.0.16
[09:02:07.726] GL vendor: Broadcom
[09:02:07.726] GL renderer: VC4 V3D 2.1
...
[09:02:07.878] DRM: head 'HDMI-A-1' found, connector 32 is connected, EDID make 'DEL', model 'DELL U2720Q', serial 'JT61X13'
...

[yvs]

Correct - that's weston running without xwayland - it seems faster than x/flwm too

Code: [Select]

[09:02:07.722] EGL client APIs: OpenGL OpenGL_ES
[09:02:07.726] GL version: OpenGL ES 2.0 Mesa 24.1.4
[09:02:07.726] GL vendor: Broadcom


Wow, it works without glx and opengles<3.0 is attached to egl(wayland)

glxinfo doesn't work on wayland/weston.

I've looked into inxi-3.3.35 script, it calls all things that possible (glxinfo, eglinfo, clinfo,...) to collect and parse API info.
If there's mesa was built on the way, supposedly there's eglinfo there and can be used for inxi pretty print.

[Juanito]

xorg-server patched and Xorg-3d adjusted so that RPi3 xorg-2d and xorg-3d work with vc4-kms-v3d

[yvs]

xorg-server patched and Xorg-3d adjusted so that RPi3 xorg-2d and xorg-3d work with vc4-kms-v3d

it looks like software rendering and visually slower comparing to v4-fkms

with v4-kms line in config

Code: [Select]

tc-kms% inxi -Ga
Graphics:
  Device-1: bcm2835-hdmi driver: vc4_hdmi v: N/A bus-ID: N/A
    chip-ID: brcm:3f902000 class-ID: hdmi
  Device-2: bcm2835-vc4 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:soc
    class-ID: gpu
  Display: server: X.org driver: X: loaded: fbdev unloaded: modesetting
    gpu: vc4_hdmi,vc4_drm display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
  API: OpenGL v: 4.5 vendor: mesa v: 24.1.4 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: llvmpipe (LLVM 15.0.7 128 bits)
    device-ID: ffffffff:ffffffff memory: 898.4 MiB unified: yes

with v4-fkms

Code: [Select]

tc-fkms% inxi -Ga
Graphics:
  Device-1: bcm2835-vc4 driver: vc4_drm v: N/A bus-ID: N/A chip-ID: brcm:soc
    class-ID: gpu
  Device-2: bcm2835-hdmi driver: N/A bus-ID: N/A chip-ID: brcm:soc
    class-ID: hdmi
  Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev
    dri: vc4
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
  Monitor-1: DSI-1 size-res: N/A modes: FIXED_MODE
  API: OpenGL v: 2.1 vendor: broadcom mesa v: 24.1.4 glx-v: 1.4 es-v: 2.0
    direct-render: yes renderer: VC4 V3D 2.1 device-ID: 14e4:ffffffff
    memory: 898.4 MiB unified: yes


p.s. and gtk4 related:
it has started complain on vulkan after tcz updates

Code: [Select]

error while loading shared libraries: libvulkan.so.1: cannot open shared object file: No such file or directory

with loaded libvulkan (and v4-kms): it cannot use dri2 via egl->vulkan

Code: [Select]

% gtk4-widget-factory
libcups.so.2: cannot open shared object file: No such file or directory
Failed to load module: /usr/local/lib/gtk-4.0/4.0.0/printbackends/libprintbackend-cups.so
libgstplayer-1.0.so.0: cannot open shared object file: No such file or directory
Failed to load module: /usr/local/lib/gtk-4.0/4.0.0/media/libmedia-gstreamer.so
libEGL warning: DRI2: failed to authenticate
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
libEGL warning: egl: failed to create dri2 screen