Sounds like Arch did not enable that option in their PKGBUILD yet.
Someone already made a PR for the ALARM package to include it:
Just not accepted yet.
1 Like
I have
└─[$] <> uname -r
5.10.0-rc7-1-MANJARO-ARM
└─[$] <> sudo pacman -Qs mesa
local/glu 9.0.1-2
Mesa OpenGL Utility library
local/mesa-demos 8.4.0-4
Mesa demos and tools incl. glxinfo + glxgears
local/mesa-git 21.0.0_devel.132478.f9ceab7b237-1
an open-source implementation of the OpenGL specification, git version
And i get:
└─[$] <> vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
1488 frames in 5.0 seconds = 297.571 FPS
1504 frames in 5.0 seconds = 300.737 FPS
1503 frames in 5.0 seconds = 300.549 FPS
1503 frames in 5.0 seconds = 300.463 FPS
?
What am I doing wrong? Any Ideas?
Do you have
gpu_mem=64
dtoverlay=vc4-kms-v3d-pi4
it would not start lightdm with
dtoverlay=vc4-kms-v3d-pi4
only with
dtoverlay=vc4-fkms-v3d
thats the point but i am stuck here, no idea why it wouldn’t
Do you have xf86-video-fbturbo or x86-video-turbo-git installed? If so… uninstall them.
no, i uninstalled that like told in a previous post
maybe this helps a little;
╰─➤ grep EE /var/log/Xorg.0.log.old
[ 19.319] Current Operating System: Linux raspi 5.10.0-rc7-1-MANJARO-ARM #1 SMP PREEMPT Mon Dec 7 21:25:58 CST 2020 aarch64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 19.328] (EE) Failed to load module “fbdev” (module does not exist, 0)
[ 19.328] (EE) open /dev/dri/card0: No such file or directory
[ 19.328] (EE) open /dev/dri/card0: No such file or directory
[ 19.328] (EE) No devices detected.
[ 19.328] (EE)
[ 19.328] (EE) no screens found(EE)
[ 19.328] (EE)
[ 19.328] (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
[ 19.329] (EE)
[ 19.333] (EE) Server terminated with error (1). Closing log file.
I see you installed the mesa-git, I am not sure I have tried that version (new ones each Sunday). I can try it in the a few minutes. If you do not need Vulkan support, the regular Mesa (non-git) works, you might try it.
And try running:
$ glxgears | grep -i render
You should see
V3D 4.2
I have seen this before, I do not recall just why this occurs. The regular fbdev should be available, then it switches to V3D.
nope, just empty
there is something really wrong here
Try installing mesa, rather than mesa-git
ok just a moment,
but after installing
extra/xf86-video-fbdev
vulkan-mesa-layers
at least i have GUI with;
dtoverlay=vc4-km4-v3d-pi4
enabled,
now wit mesa NOT git
same fps
still empty line in
└─[$] <> glxgears | grep -i render
sure some dependency is missing,
Any ideas?
I have not installed vulkan-mesa-layers.
There must be something for a renderer, even with xf86-video-fbdev. It shows up as renderer llvmpipe, which is the software renderer.
Ok, i will have a look into that,
thank you so far, i have really been stuck
I get the same here with my setup. I have always blamed it on my VIZIO Tv not getting detected right.
This is normal when fbturbo is not installed or disabled. It loads the module.
[ 7.973] (II) LoadModule: "fbdev"
[ 7.973] (WW) Warning, couldn't open module fbdev
[ 7.973] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 7.973] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 8.004] (II) modeset(0): using drv /dev/dri/card1
[ 8.005] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32with
yay -S xf86-video-fbdev
i got rid of that error and suddenly GUI started
missing is still the accelaration
glxgears | grep -i render
stays empty
you says
[ 8.004] (II) modeset(0): using drv /dev/dri/card1
grep modset /var/log/Xorg.0.log
staying empty here
[ 11.467] (II) modeset(0): [DRI2] Setup complete
[ 11.468] (II) modeset(0): [DRI2] DRI driver: vc4
[ 11.468] (II) modeset(0): [DRI2] VDPAU driver: vc4
also
[ 10.796] (WW) Warning, couldn't open module fbdev
[ 10.796] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 10.796] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 10.801] (II) modeset(0): using drv /dev/dri/card1
In theory they should co-exist with vc4 being favored but it does not always switch, so I uninstall it.
On a related note, starting with one of the earlier mesa-git versions, I found that a hdmi 2.0 cable or proper hdmi_mode and hdmi_group settings became required for video to work properly. Previously a hdmi 1.4 cable worked fine, and without settings on multiple monitors that use.
Edit: So you could be getting the driver loaded but the black screen is due to vsync, not the driver.
Well,
i will try a fresh install, just to make clear that i did not misconfigure something.
Will give a shout then.
Another cable is on the way …