<icecream95>
jschwart: Some more up-to-date distributions already include Mesa with Panfrost enabled, but if you build from source you don't have to wait months for bug fixes
<icecream95>
jschwart: For the tinkerboard Armbian Bionic has an old kernel. Armbian Buster has a newer kernel which can at least run Panfrost (though there are a few bugs which were fixed in 5.4)
<icecream95>
jschwart: On the armbian page it looks like the Bionic server image has a 5.3 kernel, so you should be able to install that kernel as a package on your current Armbian install
<icecream95>
jschwart: Installing linux-image-current-rockchip and linux-dtb-current-rockchip *should* be enough to switch to the 5.3 kernel, but I can't guarantee it will work
<jschwart>
icecream95: so it's just moving to this 5.3 kernel and then building my own mesa?
<jschwart>
the last time I was playing with kernels some didn't boot and I had to chroot to armbian (from tinkeros) to switch to different kernels until I got one that was booting again :)
<icecream95>
You might also have to add /usr/local/lib to the top of /etc/ld.so.conf and run `sudo ldconfig` to let the system find the Mesa you compiled
davidlt has joined #panfrost
<jschwart>
icecream95: yeah I have used mesa versions installed in my homedir before with the right environment variables to load them instead of the system one
<jschwart>
I wouldn't mind that for panfrost either
<jschwart>
I was just thinking it might require more than just a kernel and compile mesa
stikonas has joined #panfrost
<icecream95>
You can add --prefix=/home/some/place to the meson .. line to install Mesa somewhere else
<icecream95>
LD_LIBRARY_PATH works fine, but if you've moved the install from where you originally put it, you'll also need LIBGL_DRIVERS_PATH=/path/to/mesa/lib/dri
<icecream95>
Here's a tip: To make the build a few minutes faster and make the installed files smaller, pass --buildtype=release to meson (it builds with debug symbols by default)
<icecream95>
Release builds don't have all the assertions of debug builds, so release builds don't fail as nicely.
<icecream95>
For example, with current Mesa master, if shader compilation fails, rather than exiting, it just goes round and round trying to compile the shader...
abordado has joined #panfrost
<jschwart>
thanks I'll try that and just use debug builds for reporting issues then
<jschwart>
this only will do 3D right? no video acceleration
davidlt has quit [Remote host closed the connection]
davidlt has joined #panfrost
<HdkR>
jschwart: Mali Utgard/Midgard/Bifrost/Valhall is a 3D accelerator only
<icecream95>
> We are attempting to uprev rk3288 from 3.14 to 4.19
<icecream95>
So, rk3288 VPU patches that actually work might soon (hopefully) appear for recent-ish kernels, so there is hope for one day having video acceleration on RK3288
<jschwart>
ah that's nice :)
<jschwart>
thanks a lot both for the info, also on pointing out to that I was mixing up the 3D and VPU parts :)
icecream95 has quit [Quit: leaving]
_whitelogger has joined #panfrost
<jschwart>
"Linux tinkerboard 5.3.11-rockchip #19.11.3 SMP PREEMPT Tue Nov 19 00:44:53 CET 2019 armv7l armv7l armv7l GNU/Linux"
<jschwart>
that went well :)
<jschwart>
seems mesa needs a newer meson than what's in Ubuntu 18.04
<jschwart>
just grabbing the deb from a newer ubuntu version seems to work fine
rhyskidd has quit [Ping timeout: 240 seconds]
<jschwart>
build finished, but glxinfo is not working yet:
<jschwart>
MESA-LOADER: failed to open swrast (search paths /home/julius/.lib/mesa/lib/arm-linux-gnueabihf/dri)
<urjaman>
that sounds like you're trying to run stuff from Xorg while xorg is not running glamor
<urjaman>
(also, it sounds like the mesa you built was built without swrast, which while it isnt needed to test panfrost, could still be helpful if you want to actually use said mesa as a daily driver...)
megi has joined #panfrost
<jschwart>
nah I don't need mesa as my daily driver
<jschwart>
this mesa*
<jschwart>
but do I need to run X with glamor against the same mesa version?
<urjaman>
yes
<jschwart>
then it seems my idea of installing in my homedir doesn't make much sense
<jschwart>
or can I run a second X.org instance as a regular user?
<urjaman>
or it doesnt need to be exactly same mesa version, but it does need to be a mesa with panfrost running glamor
<jschwart>
now I have the usual version of Ubuntu 18.04/Armbian
<jschwart>
I guess I'll have to do a systemwide installation
<urjaman>
you can install eg. to /usr/local, add that to your ld.so.conf (or ld.so.conf.d/ as a seperate file) and run ldconfig after the mesa install
<urjaman>
(or /usr/mesa or whatever you like :P)
davidlt has joined #panfrost
<jschwart>
will X.org automatically pick up that glamor should work then?
<urjaman>
i actually dont know if the patches to make glamor work again went into master already, but in theory yes
<urjaman>
if you have the panfrost kernel module loaded, Xorg using the modesetting driver (and doesnt have accel disabled), it should enable glamor
<jschwart>
it seems panfrost got loaded
<urjaman>
using the modesetting driver == not using fbturbo or something like that (modesetting is the default that comes with Xorg, atleast these days)
<jschwart>
it's using the modesetting driver already
<jschwart>
just not glamor I guess
<jschwart>
yeah it says glamor initialization failed
<jschwart>
seems the ld.so.conf changes aren't needed when using /usr/local, it works now :)
<jschwart>
glxinfo shows it's using panfrost that is
<jschwart>
but glxgears just shows a black window
<jschwart>
ah the whole display is frozen
<jschwart>
the seconds stopped ticking as well
<jschwart>
I can move the mouse cursor, but nothing else is still updating
<jschwart>
yeah things like xrandr and glxinfo also hang (via ssh with DISPLAY=:0)
davidlt has quit [Remote host closed the connection]
davidlt has joined #panfrost
abordado has quit [Read error: Connection reset by peer]
abordado has joined #panfrost
<jschwart>
so when I run glxgears, its window shows up and then the X.org display freezes apart from the mouse cursor
<jschwart>
killing the Xorg process with -9 restarts X.org and then I get a proper display again
megi has quit [Ping timeout: 240 seconds]
<jschwart>
it seems anything I launch causes the display to freeze, also xfce4-terminal
<jschwart>
let me know if there's anything I could provide to resolve this, should I recompile with debug (not release)?
abordado has quit [Ping timeout: 250 seconds]
karolherbst has quit [Ping timeout: 276 seconds]
yann|work has quit [Ping timeout: 240 seconds]
yann|work has joined #panfrost
karolherbst has joined #panfrost
davidlt has quit [Ping timeout: 250 seconds]
yann|work has quit [Ping timeout: 268 seconds]
sravn has quit [Quit: WeeChat 2.6]
sravn has joined #panfrost
yann|work has joined #panfrost
megi has joined #panfrost
icecream95 has joined #panfrost
<icecream95>
jschwart: Does the drm-glesv2 flavor of glmark2 work?