That compiled, but there are no entries in /sys/bus/pci*/devices.
I think I enabled all necessary drivers …
Mainline support for RockPi 4?
Dunno mate I was looking at this
https://github.com/torvalds/linux/compare/master...ayufan-rock64:master and doing a compare to the master.
I wasn’t really sure about this @145
vcc_phy: vcc-phy-regulator {
compatible = "regulator-fixed";
regulator-name = "vcc_phy";
regulator-always-on;
regulator-boot-on;
};
I will let you compare as not even sure if ayufan has pcie implemented mainline maybe not its was just a hunch he might of.
He is the guy to get in touch with his knowledge is like awesome and I am not worthy.
PS with your compiling if you have a m.2 sata ssd drive and you ever fancy enabling CONFIG_SATA_AHCI in the working 4.4 kernel
Then seeing if you have a sata ssd drive recognised would at least rule that one out.
It will never be recognised without that in the config but even when enabled we may only find out why it was removed or omission .
The LiFePo4wered hat works, or at least it would work if I’d see it on i2c, which I don’t.
Probably a speed issue – the LiFePo4 requires 100kbit, not 400. Worse, it doesn’t do clock stretching because the Pi doesn’t support that anyway. Changing the obious value in the DTS didn’t affect the result. Sigh.
CONFIG_SATA_AHCI is on in my kernel, didn’t change anything unfortunately.
I wrote to ayufan, no reply yet, will keep everybody posted. Let’s hope we’ll get a functional board in 5.3 …
Yeah must of done a typo when I did a find or some mistake.
The whole sata ssd on pice not working is confusing me. But actually my bugbear was cost and seemed to of found one https://www.mymemory.co.uk/integral-120gb-m-2-2280-pcie-nvme-ssd-drive.html so its even less of a pressing need than I thought.
5.2 is released and there is a whole slew of patches in 5.3-rc1 and mesa-19.1.2 is released tomoz that should have much better panfrost support.
Now that kernel 5.2 is released (to the manjaro arm repos at least). Any idea on how to get gpu acceleration working in x11?
I have just been trying and dunno as since Mesa 19.1.1 I had to compile the Master 19.1.2
Which worked but Manjaro have released 5.2 & 19.1.2 as it came out yesterday and it seems like a reversion or what I was compiling missed the deadline.
I am just going to compile mesa & drm one more time and the Master (latest) again.
https://panfrost.freedesktop.org/building-panfrost-mesa.html
PS you have to remove fbturbo driver to force panfrost
If you sudo pacman -Ss fbturbo
That will search for the package as I can never remember its full name
sudo pacman -R fbturbo whatever
reboot and the KMS driver should be loaded
pacman -S bc python-pip flex bison base-devel ncurses cmake xorg-util-macros
pip install scikit-build mako meson ninja
1 Like
Yeah master works but also did drm.
Quick run down as the above is for a debian/ubuntu or something
sudo pacman -S bc python-pip flex bison base-devel ncurses cmake xorg-util-macros
sudo pip install scikit-build mako meson ninja
git clone https://gitlab.freedesktop.org/mesa/drm.git --depth=1
cd drm
./autogen.sh
./configure --prefix=/usr
make -j6
sudo make install
cd ..
git clone https://gitlab.freedesktop.org/mesa/mesa.git --depth=1
cd mesa
mkdir build
meson -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false -Dplatforms=x11,drm,surfaceless -Dprefix=/usr build/
ninja -C build/
sudo ninja -C build/ install
As long as you removed the fbturbo package reboot and there you go
[rock@rockpi4 ~]$ glmark2
=======================================================
glmark2 2014.03
=======================================================
OpenGL Information
GL_VENDOR: panfrost
GL_RENDERER: panfrost
GL_VERSION: 2.1 Mesa 19.1.2 (git-fe1f7b538b)
=======================================================
[build] use-vbo=false: FPS: 164 FrameTime: 6.098 ms
[build] use-vbo=true: FPS: 382 FrameTime: 2.618 ms
[texture] texture-filter=nearest: FPS: 394 FrameTime: 2.538 ms
[texture] texture-filter=linear: FPS: 394 FrameTime: 2.538 ms
[texture] texture-filter=mipmap: FPS: 391 FrameTime: 2.558 ms
[shading] shading=gouraud: FPS: 328 FrameTime: 3.049 ms
[shading] shading=blinn-phong-inf: FPS: 328 FrameTime: 3.049 ms
[shading] shading=phong: FPS: 296 FrameTime: 3.378 ms
[shading] shading=cel: FPS: 239 FrameTime: 4.184 ms
[bump] bump-render=high-poly: FPS: 196 FrameTime: 5.102 ms
[bump] bump-render=normals: FPS: 414 FrameTime: 2.415 ms
[bump] bump-render=height: FPS: 402 FrameTime: 2.488 ms
libpng warning: iCCP: known incorrect sRGB profile
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 381 FrameTime: 2.625 ms
libpng warning: iCCP: known incorrect sRGB profile
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 186 FrameTime: 5.376 ms
[pulsar] light=false:quads=5:texture=false: FPS: 415 FrameTime: 2.410 ms
libpng warning: iCCP: known incorrect sRGB profile
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4:glmark2: ../src/util/ralloc.c:91: get_header: Assertion `info->canary == CANARY' failed.
Aborted (core dumped)
Dunno if that is me compiling glmark2 from aur wrong or panfrost.
rock@rockpi4 glmark2]$ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
5384 frames in 5.0 seconds = 1076.761 FPS
5361 frames in 5.0 seconds = 1072.048 FPS
5554 frames in 5.0 seconds = 1110.738 FPS
5602 frames in 5.0 seconds = 1120.345 FPS
5608 frames in 5.0 seconds = 1121.375 FPS
5634 frames in 5.0 seconds = 1126.753 FPS
5653 frames in 5.0 seconds = 1130.372 FPS
5640 frames in 5.0 seconds = 1127.873 FPS
5700 frames in 5.0 seconds = 1139.857 FPS
5600 frames in 5.0 seconds = 1119.792 FPS
2 Likes
libdrm in the manjaro arm repo seemed to be the latest code. Mesa 19.1 on the other hand was developed on a separate branch than master for over a month now according to the gitlab repo.
I’ll try building latest mesa from AUR first with “pamac build mesa-git”.
BTW I have been having wifi issues the whole night, after some package downgrading I believe the latest kernel linux-aarch64 (5.2.0-1) is the culprit. I have switched back to linux-aarch64-rc (5.2.0-rc7-4) for the moment.
It maybe you on the manjaro forum tony? I think we are at the bleeding edge but the devs are really quick to respond.
I don’t use wifi really, but will try.
Yep that was me, too bad wifi is also bugged on rc7, albeit lasting a little longer (2 hours) before stopped functioning.
The good news is I got panfrost working, like you said, all it takes is to install the latest mesa (built from git for now, 19.2 from repo after August) and remove the xf86-video-fbturbo-odroid-c2-git package.
Here is my log from glmark2-es2, this is the x11-glesv2 flavor I built from git. Off screen framerates were all messed up, but on screen tests seemed to be running okay, until it crashed at the shadow test (unfinished feature in panfrost maybe?).
[rock@Manjaro ~]$ glmark2-es2
=======================================================
glmark2 2017.07
=======================================================
OpenGL Information
GL_VENDOR: panfrost
GL_RENDERER: panfrost
GL_VERSION: OpenGL ES 2.0 Mesa 19.2.0-devel (git-39e7fbf24a)
=======================================================
[build] use-vbo=false: FPS: 179 FrameTime: 5.587 ms
[build] use-vbo=true: FPS: 383 FrameTime: 2.611 ms
[texture] texture-filter=nearest: FPS: 399 FrameTime: 2.506 ms
[texture] texture-filter=linear: FPS: 385 FrameTime: 2.597 ms
[texture] texture-filter=mipmap: FPS: 404 FrameTime: 2.475 ms
[shading] shading=gouraud: FPS: 334 FrameTime: 2.994 ms
[shading] shading=blinn-phong-inf: FPS: 334 FrameTime: 2.994 ms
[shading] shading=phong: FPS: 299 FrameTime: 3.344 ms
[shading] shading=cel: FPS: 285 FrameTime: 3.509 ms
[bump] bump-render=high-poly: FPS: 225 FrameTime: 4.444 ms
[bump] bump-render=normals: FPS: 415 FrameTime: 2.410 ms
[bump] bump-render=height: FPS: 362 FrameTime: 2.762 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 311 FrameTime: 3.215 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 160 FrameTime: 6.250 ms
[pulsar] light=false:quads=5:texture=false: FPS: 475 FrameTime: 2.105 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 40 FrameTime: 25.000 ms
[desktop] effect=shadow:windows=4: FPS: 291 FrameTime: 3.436 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 123 FrameTime: 8.130 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 124 FrameTime: 8.065 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 184 FrameTime: 5.435 ms
[ideas] speed=duration: FPS: 40 FrameTime: 25.000 ms
[jellyfish] <default>: FPS: 227 FrameTime: 4.405 ms
[terrain] <default>: FPS: 0 FrameTime: inf ms
[shadow] <default>:glmark2-es2: ../src/gallium/drivers/panfrost/pan_blend_cso.c:211: panfrost_get_blend_for_context: Assertion `fb->nr_cbufs > rti' failed.
Aborted (core dumped)I was the same and dunno if its panfrost but prob.
This is a Pi 3 for ref can not find pi 4
=======================================================
glmark2 2014.03
=======================================================
OpenGL Information
GL_VENDOR: Broadcom
GL_RENDERER: Gallium 0.4 on VC4
GL_VERSION: 2.1 Mesa 11.1.0
=======================================================
[build] use-vbo=false: FPS: 78 FrameTime: 12.821 ms
[build] use-vbo=true: FPS: 119 FrameTime: 8.403 ms
[texture] texture-filter=nearest: FPS: 128 FrameTime: 7.812 ms
[texture] texture-filter=linear: FPS: 127 FrameTime: 7.874 ms
[texture] texture-filter=mipmap: FPS: 119 FrameTime: 8.403 ms
[shading] shading=gouraud: FPS: 105 FrameTime: 9.524 ms
[shading] shading=blinn-phong-inf: FPS: 104 FrameTime: 9.615 ms
[shading] shading=phong: FPS: 97 FrameTime: 10.309 ms
[shading] shading=cel: FPS: 97 FrameTime: 10.309 ms
[bump] bump-render=high-poly: FPS: 68 FrameTime: 14.706 ms
[bump] bump-render=normals: FPS: 129 FrameTime: 7.752 ms
[bump] bump-render=height: FPS: 126 FrameTime: 7.937 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 77 FrameTime: 12.987 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 49 FrameTime: 20.408 ms
[pulsar] light=false:quads=5:texture=false: FPS: 94 FrameTime: 10.638 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 30 FrameTime: 33.333 ms
[desktop] effect=shadow:windows=4: FPS: 54 FrameTime: 18.519 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 44 FrameTime: 22.727 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 42 FrameTime: 23.810 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 53 FrameTime: 18.868 ms
[ideas] speed=duration: FPS: 79 FrameTime: 12.658 ms
[jellyfish] <default>: FPS: 63 FrameTime: 15.873 ms
[terrain] <default>: FPS: 5 FrameTime: 200.000 ms
[shadow] <default>: FPS: 46 FrameTime: 21.739 ms
[refract] <default>: FPS: 8 FrameTime: 125.000 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 136 FrameTime: 7.353 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 98 FrameTime: 10.204 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 134 FrameTime: 7.463 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 125 FrameTime: 8.000 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 92 FrameTime: 10.870 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5:Segmentation fault
I must of made a mess of things somewhere as originally I was running the above 2014 ver from Aur
Direct from github I had probs compiling and prob over complicated things.
My Pi4 which is strange as the results are not that bad but wow it feels in use much slower.
pi@raspberrypi:~ $ glmark2-es2
=======================================================
glmark2 2017.07
=======================================================
OpenGL Information
GL_VENDOR: Broadcom
GL_RENDERER: V3D 4.2
GL_VERSION: OpenGL ES 3.0 Mesa 19.1.0-devel
=======================================================
[build] use-vbo=false: FPS: 201 FrameTime: 4.975 ms
[build] use-vbo=true: FPS: 198 FrameTime: 5.051 ms
[texture] texture-filter=nearest: FPS: 184 FrameTime: 5.435 ms
[texture] texture-filter=linear: FPS: 185 FrameTime: 5.405 ms
[texture] texture-filter=mipmap: FPS: 186 FrameTime: 5.376 ms
[shading] shading=gouraud: FPS: 193 FrameTime: 5.181 ms
[shading] shading=blinn-phong-inf: FPS: 185 FrameTime: 5.405 ms
[shading] shading=phong: FPS: 168 FrameTime: 5.952 ms
[shading] shading=cel: FPS: 163 FrameTime: 6.135 ms
[bump] bump-render=high-poly: FPS: 166 FrameTime: 6.024 ms
[bump] bump-render=normals: FPS: 186 FrameTime: 5.376 ms
[bump] bump-render=height: FPS: 180 FrameTime: 5.556 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 140 FrameTime: 7.143 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 97 FrameTime: 10.309 ms
[pulsar] light=false:quads=5:texture=false: FPS: 183 FrameTime: 5.464 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 62 FrameTime: 16.129 ms
[desktop] effect=shadow:windows=4: FPS: 141 FrameTime: 7.092 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 141 FrameTime: 7.092 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 138 FrameTime: 7.246 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 157 FrameTime: 6.369 ms
[ideas] speed=duration: FPS: 262 FrameTime: 3.817 ms
[jellyfish] <default>: FPS: 137 FrameTime: 7.299 ms
[terrain] <default>: FPS: 20 FrameTime: 50.000 ms
[shadow] <default>: FPS: 112 FrameTime: 8.929 ms
[refract] <default>: FPS: 40 FrameTime: 25.000 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 205 FrameTime: 4.878 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 174 FrameTime: 5.747 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 196 FrameTime: 5.102 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 187 FrameTime: 5.348 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 167 FrameTime: 5.988 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 185 FrameTime: 5.405 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 177 FrameTime: 5.650 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 129 FrameTime: 7.752 ms
=======================================================
glmark2 Score: 158
=======================================================
Then again its about 200% for the rk3399 and my new build drops to 30%
I have been googling the Mesa teams latest panfrost efforts that seems to have a lot of focus with wayland.
So rebuilt mesa -b master and went through and even optional dependencies installed them apart from dlopen as not sure what or which package.
[rock@rockpi4 mesa]$ meson -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false -Dprefix=/usr build/
The Meson build system
Version: 0.51.1
Source dir: /home/rock/mesa
Build dir: /home/rock/mesa/build
Build type: native build
Program python found: YES (/usr/bin/python)
Project name: mesa
Project version: 19.2.0-devel
C compiler for the build machine: cc (gcc 8.3.0 "cc (GCC) 8.3.0")
C++ compiler for the build machine: c++ (gcc 8.3.0 "c++ (GCC) 8.3.0")
C compiler for the host machine: cc (gcc 8.3.0 "cc (GCC) 8.3.0")
C++ compiler for the host machine: c++ (gcc 8.3.0 "c++ (GCC) 8.3.0")
Build machine cpu family: aarch64
Build machine cpu: aarch64
Program pkg-config found: YES (/usr/bin/pkg-config)
WARNING: Project targetting '>= 0.45' but tried to use feature introduced in '0.46.0': Python Module
Program python3 found: YES (/usr/bin/python3)
Checking for function "bswap32" : YES
Checking for function "bswap64" : YES
Checking for function "clz" : YES
Checking for function "clzll" : YES
Checking for function "ctz" : YES
Checking for function "expect" : YES
Checking for function "ffs" : YES
Checking for function "ffsll" : YES
Checking for function "popcount" : YES
Checking for function "popcountll" : YES
Checking for function "unreachable" : YES
Checking if "__attribute__((const))" compiles: YES
Checking if "__attribute__((flatten))" compiles: YES
Checking if "__attribute__((malloc))" compiles: YES
Checking if "__attribute__((pure))" compiles: YES
Checking if "__attribute__((unused))" compiles: YES
Checking if "__attribute__((warn_unused_result))" compiles: YES
Checking if "__attribute__((weak))" compiles: YES
Checking if "__attribute__((format(...)))" compiles: YES
Checking if "__attribute__((packed))" compiles: YES
Checking if "__attribute__((returns_nonnull))" compiles: YES
Checking if "__attribute__((visibility(...)))" compiles: YES
Checking if "__attribute__((alias(...)))" compiles: YES
Checking if "__attribute__((__noreturn__))" compiles: YES
Checking if "__uint128_t" compiles: YES
Compiler for C supports arguments -Werror=implicit-function-declaration: YES
Compiler for C supports arguments -Werror=missing-prototypes: YES
Compiler for C supports arguments -Werror=return-type: YES
Compiler for C supports arguments -Werror=incompatible-pointer-types: YES
Compiler for C supports arguments -Werror=format: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -fno-math-errno: YES
Compiler for C supports arguments -fno-trapping-math: YES
Compiler for C supports arguments -Qunused-arguments: NO
Compiler for C supports arguments -Wmissing-field-initializers: YES
Compiler for C supports arguments -Wformat-truncation: YES
Compiler for C supports arguments -fvisibility=hidden: YES
Compiler for C++ supports arguments -Werror=return-type: YES
Compiler for C++ supports arguments -Werror=format: YES
Compiler for C++ supports arguments -Wformat-security: YES
Compiler for C++ supports arguments -fno-math-errno: YES
Compiler for C++ supports arguments -fno-trapping-math: YES
Compiler for C++ supports arguments -Qunused-arguments: NO
Compiler for C++ supports arguments -Wnon-virtual-dtor: YES
Compiler for C++ supports arguments -Wmissing-field-initializers: YES
Compiler for C++ supports arguments -Wformat-truncation: YES
Compiler for C supports arguments -Woverride-init: YES
Compiler for C supports arguments -Winitializer-overrides: NO
Compiler for C++ supports arguments -fvisibility=hidden: YES
Compiler for C supports arguments -Werror=pointer-arith: YES
Compiler for C++ supports arguments -Werror=pointer-arith: YES
Compiler for C supports arguments -Werror=vla: YES
Compiler for C++ supports arguments -Werror=vla: YES
Checking if "GCC atomic builtins" compiles: YES
Checking if "GCC atomic builtins required -latomic" links: YES
Checking if "GCC 64bit atomics" with dependency not-found links: YES
Header <sys/sysmacros.h> has symbol "major" : YES
Checking if "xlocale.h" compiles: NO
Checking if "sys/sysctl.h" compiles: YES
Checking if "linux/futex.h" compiles: YES
Checking if "endian.h" compiles: YES
Checking if "dlfcn.h" compiles: YES
Checking if "execinfo.h" compiles: YES
Checking if "sys/shm.h" compiles: YES
Checking for function "strtof" : YES
Checking for function "mkostemp" : YES
Checking for function "posix_memalign" : YES
Checking for function "timespec_get" : YES
Checking for function "memfd_create" : YES
Checking if "strtod has locale support" links: YES
Checking if "Bsymbolic" links: YES
Checking if "gc-sections" links: YES
Checking if "version-script" links: YES
Checking if "dynamic-list" links: YES
Checking for function "dlopen" : NO
Library dl found: YES
Checking for function "dladdr" with dependency -ldl: YES
Checking for function "dl_iterate_phdr" : YES
Checking for function "clock_gettime" : YES
Found pkg-config: /usr/bin/pkg-config (1.6.1)
Run-time dependency zlib found: YES 1.2.11
Run-time dependency threads found: YES
Checking for function "pthread_setaffinity_np" with dependency threads: YES
Run-time dependency expat found: YES 2.2.7
Library m found: YES
Run-time dependency libdrm found: YES 2.4.99
llvm-config found: YES (/usr/bin/llvm-config) 8.0.0
Run-time dependency LLVM (modules: bitwriter, engine, mcdisassembler, mcjit) found: YES 8.0.0
Run-time dependency valgrind found: YES 3.14.0
Program bison found: YES (/usr/bin/bison)
Program flex found: YES (/usr/bin/flex)
Found pkg-config: /usr/bin/pkg-config (1.6.1)
Build-time dependency wayland-scanner found: YES 1.17.0
Program /usr/bin/wayland-scanner found: YES (/usr/bin/wayland-scanner)
Run-time dependency wayland-protocols found: YES 1.17
Run-time dependency wayland-client found: YES 1.17.0
Run-time dependency wayland-server found: YES 1.17.0
Run-time dependency wayland-egl-backend found: YES 3
Run-time dependency x11 found: YES 1.6.8
Run-time dependency xext found: YES 1.3.4
Run-time dependency xdamage found: YES 1.1.5
Run-time dependency xfixes found: YES 5.0.3
Run-time dependency xcb-glx found: YES 1.13.1
Run-time dependency xcb found: YES 1.13.1
Run-time dependency x11-xcb found: YES 1.6.8
Run-time dependency xcb-dri2 found: YES 1.13.1
Run-time dependency xcb-dri3 found: YES 1.13.1
Run-time dependency xcb-present found: YES 1.13.1
Run-time dependency xcb-sync found: YES 1.13.1
Run-time dependency xshmfence found: YES 1.3
Run-time dependency glproto found: YES 1.4.17
Run-time dependency dri2proto found: YES 2.8
Run-time dependency xxf86vm found: YES 1.1.4
Run-time dependency xcb-xfixes found: YES 1.13.1
Run-time dependency xcb-randr found: YES 1.13.1
Run-time dependency xrandr found: YES 1.5.2
Library sensors found: YES
Program nm found: YES (/usr/bin/nm)
Program symbols-check.py found: YES (/usr/bin/env python /home/rock/mesa/bin/symbols-check.py)
DEPRECATION: build_always is deprecated. Combine build_by_default and build_always_stale instead.
Checking for function "mincore" : YES
WARNING: Project targetting '>= 0.45' but tried to use feature introduced in '0.50.0': Python module path method
Program /usr/bin/python3 found: YES (/usr/bin/python3)
Message: Configuration summary:
prefix: /usr
libdir: lib
includedir: include
OpenGL: yes (ES1: yes ES2: yes)
OSMesa: no
DRI platform: drm
DRI drivers: no
DRI driver dir: /usr/lib/dri
GLX: DRI-based
EGL: yes
EGL drivers: builtin:egl_dri2 builtin:egl_dri3
GBM: yes
EGL/Vulkan/VL platforms: x11 wayland drm surfaceless
Vulkan drivers: no
llvm: yes
llvm-version: 8.0.0
Gallium drivers: panfrost kmsro
Gallium st: mesa
HUD lmsensors: yes
Shared-glapi: yes
[rock@rockpi4 ~]$ cat glmark2-es2-wayland
=======================================================
glmark2 2017.07
=======================================================
OpenGL Information
GL_VENDOR: panfrost
GL_RENDERER: panfrost
GL_VERSION: OpenGL ES 2.0 Mesa 19.2.0-devel (git-3043908ccb)
=======================================================
[build] use-vbo=false: FPS: 178 FrameTime: 5.618 ms
[build] use-vbo=true: FPS: 317 FrameTime: 3.155 ms
[texture] texture-filter=nearest: FPS: 394 FrameTime: 2.538 ms
[texture] texture-filter=linear: FPS: 386 FrameTime: 2.591 ms
[texture] texture-filter=mipmap: FPS: 400 FrameTime: 2.500 ms
[shading] shading=gouraud: FPS: 238 FrameTime: 4.202 ms
[shading] shading=blinn-phong-inf: FPS: 220 FrameTime: 4.545 ms
[shading] shading=phong: FPS: 163 FrameTime: 6.135 ms
[shading] shading=cel: FPS: 142 FrameTime: 7.042 ms
[bump] bump-render=high-poly: FPS: 177 FrameTime: 5.650 ms
[bump] bump-render=normals: FPS: 327 FrameTime: 3.058 ms
[bump] bump-render=height: FPS: 274 FrameTime: 3.650 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 135 FrameTime: 7.407 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 154 FrameTime: 6.494 ms
[pulsar] light=false:quads=5:texture=false: FPS: 374 FrameTime: 2.674 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 33 FrameTime: 30.303 ms
[desktop] effect=shadow:windows=4: FPS: 153 FrameTime: 6.536 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 112 FrameTime: 8.929 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 114 FrameTime: 8.772 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 138 FrameTime: 7.246 ms
[ideas] speed=duration: FPS: 35 FrameTime: 28.571 ms
[jellyfish] <default>: FPS: 86 FrameTime: 11.628 ms
[terrain] <default>: FPS: 10 FrameTime: 100.000 ms
[shadow] <default>: Set up failed
[refract] <default>: Set up failed
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 342 FrameTime: 2.924 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 161 FrameTime: 6.211 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 342 FrameTime: 2.924 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 219 FrameTime: 4.566 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 163 FrameTime: 6.135 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 228 FrameTime: 4.386 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 232 FrameTime: 4.310 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 129 FrameTime: 7.752 ms
=======================================================
glmark2 Score: 205
=======================================================
@tonyunreal dunno about wifi as connected and been running for a couple of hours, couple of reboots.
No problem here? So far anyway.
It might be the panfrost crashes as whatever happens its seems then to effect shutdown at least.
I did notice this though
[.[0;32m OK .[0m] Reached target .[0;1;39mHost and Network Name Lookups.[0m.
[ 168.455433] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 168.456432] usbcore: registered new interface driver brcmfmac
[ 168.576683] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 168.577534] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 168.578984] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84
You might be clashing with other channels and have a limited set of alternatives hence why I am OK and you are not?
@tonyunreal Nah been trying to break it and have.
Heavy throughput does it pretty quick, ssh it doesn’t really fail.
Watching a youtube video maybe 5 mins 1080p
Jul 09 14:58:21 rockpi4 kernel: OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port
Jul 09 14:58:21 rockpi4 kernel: dwc3 fe900000.dwc3: Failed to get clk 'ref': -2
Jul 09 14:58:23 rockpi4 kernel: rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
Jul 11 06:59:52 rockpi4 kernel: ieee80211 phy0: brcmf_escan_timeout: timer expired
Jul 11 07:02:12 rockpi4 kernel: ieee80211 phy0: brcmf_escan_timeout: timer expired
Jul 11 07:10:12 rockpi4 bluetoothd[722]: Failed to set mode: Failed (0x03)
Jul 11 07:16:56 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:16:59 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:16:59 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:01 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:04 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:04 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:07 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:09 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:09 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:12 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:14 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:14 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:17 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:19 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:19 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:22 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:24 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:24 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:27 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:30 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:30 rockpi4 kernel: ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Jul 11 07:17:32 rockpi4 kernel: ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jul 11 07:17:32 rockpi4 systemd-resolved[677]: Failed to send hostname reply: Invalid argument
Jul 11 07:17:32 rockpi4 systemd-resolved[677]: Failed to send hostname reply: Invalid argument
It might be
wifi-coexistence
The BCM43* series chips are notorious for problems when both wifi and bluetooth are used at the same time. This coexistence issue comes in varying degrees of severity but for most users makes using the Pi in bluetooth A2DP mode while also using wifi impossible. Bluetooth buffer underruns are caused by sharing the UART device, resulting in skipping, popping, hissing, and generally unusable audio. For some users, this also effects peripherals such as mice and keyboards. A firmware fix was found for both the Pi3 and Pi ZeroW, discussion of this fix can be found in this github issue.
To deploy the fix to the current firmware in Arch add the following lines:
btc_mode=1
btc_params8=0x4e20
btc_params1=0x7530
to the end of these firmware config files:
/usr/lib/firmware/updates/brcm/brcmfmac43430-sdio.txt
/usr/lib/firmware/updates/brcm/brcmfmac43455-sdio.txt
This fix can be found in this git commit. The fix is experimental and is not yet deployed to the upstream package
1 Like
glmark doesn’t crash halfway on x11 anymore, though it did seem to skip some tests (shadow & refract).
[rock@Manjaro mesa]$ glmark2-es2
=======================================================
glmark2 2017.07
=======================================================
OpenGL Information
GL_VENDOR: panfrost
GL_RENDERER: panfrost
GL_VERSION: OpenGL ES 2.0 Mesa 19.2.0-devel (git-8c5692b696)
=======================================================
[build] use-vbo=false: FPS: 250 FrameTime: 4.000 ms
[build] use-vbo=true: FPS: 410 FrameTime: 2.439 ms
[texture] texture-filter=nearest: FPS: 431 FrameTime: 2.320 ms
[texture] texture-filter=linear: FPS: 371 FrameTime: 2.695 ms
[texture] texture-filter=mipmap: FPS: 442 FrameTime: 2.262 ms
[shading] shading=gouraud: FPS: 351 FrameTime: 2.849 ms
[shading] shading=blinn-phong-inf: FPS: 351 FrameTime: 2.849 ms
[shading] shading=phong: FPS: 317 FrameTime: 3.155 ms
[shading] shading=cel: FPS: 301 FrameTime: 3.322 ms
[bump] bump-render=high-poly: FPS: 229 FrameTime: 4.367 ms
[bump] bump-render=normals: FPS: 450 FrameTime: 2.222 ms
[bump] bump-render=height: FPS: 427 FrameTime: 2.342 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 338 FrameTime: 2.959 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 169 FrameTime: 5.917 ms
[pulsar] light=false:quads=5:texture=false: FPS: 463 FrameTime: 2.160 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 37 FrameTime: 27.027 ms
[desktop] effect=shadow:windows=4: FPS: 287 FrameTime: 3.484 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 121 FrameTime: 8.264 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 127 FrameTime: 7.874 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 256 FrameTime: 3.906 ms
[ideas] speed=duration: FPS: 41 FrameTime: 24.390 ms
[jellyfish] <default>: FPS: 239 FrameTime: 4.184 ms
[terrain] <default>: FPS: 12 FrameTime: 83.333 ms
Error: DepthRenderTarget::setup: glCheckFramebufferStatus failed (0x8cdd)
Error: Failed to set up the render target for the depth pass
[shadow] <default>: Set up failed
Error: DistanceRenderTarget::setup: glCheckFramebufferStatus failed (0x8cdd)
Error: Failed to set up the render target for the depth pass
[refract] <default>: Set up failed
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 376 FrameTime: 2.660 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 359 FrameTime: 2.786 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 463 FrameTime: 2.160 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 393 FrameTime: 2.545 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 358 FrameTime: 2.793 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 401 FrameTime: 2.494 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 403 FrameTime: 2.481 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 117 FrameTime: 8.547 ms
=======================================================
glmark2 Score: 299
=======================================================
1 Like
Big increase on the wayland glmark2 but its really strange as wayland does actually feel really snappy and fast.
But with 19.2.0+ its looking really really good for panfrost as the devs have said they have done zero optimisation as of yet and quite a bit could be done but there focus is purely completing the various working api’s.
The bluetooth and wifi is the broadcom that is on the raspberry
https://archlinuxarm.org/platforms/armv6/raspberry-pi
Bluetooth
firmware
To be able to talk to the bluetooth chip, you must install the services, firmware, and UDEV rules. The pi-bluetooth package from the AUR is available to do this.
wifi-coexistence
The BCM43* series chips are notorious for problems when both wifi and bluetooth are used at the same time. This coexistence issue comes in varying degrees of severity but for most users makes using the Pi in bluetooth A2DP mode while also using wifi impossible. Bluetooth buffer underruns are caused by sharing the UART device, resulting in skipping, popping, hissing, and generally unusable audio. For some users, this also effects peripherals such as mice and keyboards. A firmware fix was found for both the Pi3 and Pi ZeroW, discussion of this fix can be found in this github issue.
To deploy the fix to the current firmware in Arch add the following lines:
btc_mode=1 btc_params8=0x4e20 btc_params1=0x7530to the end of these firmware config files:
/usr/lib/firmware/updates/brcm/brcmfmac43430-sdio.txt
/usr/lib/firmware/updates/brcm/brcmfmac43455-sdio.txtThis fix can be found in this git commit. The fix is experimental and is not yet deployed to the upstream package
The firmware is prob correct but prob in need of some parameter tinkering
1 Like
Posted this as an update to the earlier report from @Antram .
Currently on the mainline 5.2 kernel, we have the support of:
video out: 1080p 60hz or lower resolutions only
gpu acceleration: [mesa 19.2 required] most tests in glmark2-es2 passing with decent framerates, fluid x11 & wayland desktop experience (with minor hiccups)
video decoding: 1080p h264 plays fine with mpv, no 4k or hevc support (software decoders only?)
audio out: [manjaro patched] hdmi audio only (no es8316 analog audio)
wifi & bt: [manjaro patched, ap6256-firmware package required] working, with heavy regressions (see posts above)
ethernet: working (though I only measured up to 200Mbps)
usb 2.0: working
usb 3.0: only the bottom port works (the upper port is wrongly flagged as otg in kernel 5.2, see posts above for custom kernel fix)
emmc: working
nvme ssd: not working
1 Like
Yeah I keep wondering why no one from radxa is pushing any pcie dts to mainline uboot & kernel.
There isn’t anything even though Pine have.
So it aint defo going to work.
I think actually video might be 2k 1440p as pretty sure I have played back 2k but 4k not a chance.
But 1080p is good.
Again that is mesa and vpau? something like that doh! my memory
Totally forgot about the usb3.0 otg keep plugging my mouse in it and then momentary angst as done it again dunno what it is when something doesn’t work that makes it more likely you will pick it.
In 5.2 the manjaro guys tried to patch hdmi audio and wifi the actual mainline stuff is 5.3 and fingers crossed as its already been there for some time that when linux next becomes 5.3-rc1 then it will be up and running.
But pcie I see as hugely important as so many have chosen the nvme ssd option and see nothing and its will be down to patches on mainline unless something is pushed fairly quickly to mainline.
PS check https://1drv.ms/u/s!AocmAh35i26QiUjEeJEX4zboMH1X wayland gnome as its surprised me as I am running via sd card but with some quick storage I am thinking this is the first sbc that runs gnome that is tolerable.
I will remember to trim and do more disk cleaning before I create a disk image next time as its pretty big with bloat but just try it in terms of use.
Still has all the horrid boot errors that cause delay but once up and running its a surprise.
Added the info about video decoding to my post above.
As for the desktop experience, I don’t know about Gnome 3 (can’t stand it for a while), but the current Manjaro lxqt is way more fluid than the Debian/Ubuntu images Radxa provided. I spent two days with the Debian Strech image, while everything works including proper support for 4k / QHD video out, the desktop applications is too unresponsive and the Internet browsers are way worse.
Yeah if you look in mesa/blob/master/meson_options.txt
It could purely be the build options and hardware accel could be there just dunno if or what has been done.
Ps this is the best option
option(
‘I-love-half-baked-turnips’,
type : ‘boolean’,
value : false,
description : ‘Allow work-in-progress freedreno vulkan driver to be enabled’,
)
Desktop wise I am the same also didn’t like KDE but seems like they have all become fluid and capable of lower hardware.
Suggestion was just to give a test drive as Gnome3 on a sbc!!! preposterous 
Quite interesting not a fan but think it works well.
I am dying to get pcie and just see what it feels like under the hood.