10:06 <schurig> Hi ... I'm a bit struggling with using Etnaviv (from self-compiled kernel 5.6.12) on an i.MX6 with Xorg ... both in Debian Buster and Debian SID

10:06 <schurig> when I have no xorg.conf file, X won't even start (e.g. when started with "Xorg -keeptty vt1" or "xinit")

10:07 <schurig> when I have one, I need to add a

10:07 <schurig> Option "AccelMethod" "none"

10:07 <schurig> clause to make it start ... but my suspicion is that this is then just framebuffer ?!?!

10:16 <schurig> and without an xorg.file, I get "Require OpenGL version 2.1 or later." followed by "(EE) modeset(0): Failed to initialize glamor at ScreenInit() time."

10:16 <schurig> any idea on how to debug this further?

10:18 <lynxeye> schurig: don't use the generic modesetting driver and glamor on etnaviv

10:19 <lynxeye> use the xf86-video-armada driver to get proper 2D acceleration

10:21 <schurig> oh, I thouht that that one was outdated in favor of the xorg modesetting driver. Okay, I'll give it a try.

10:22 <lynxeye> schurig: modesetting is the way to go on most modern GPUs, which don't even have a 2D unit anymore. i.MX6 on the other hand has a full GPU just dedicated for 2D tasks, so you really want to use it for Xorg accel. And the only way to do so is using the armada driver.

10:25 <schurig> as Debian hasn't it, I need to compile it on my own .. which one should I use, the unstable branch from this: http://git.arm.linux.org.uk/cgit/xf86-video-armada.git/log/?h=unstable-devel

10:25 <schurig> master is really old, last commit 2014 ...

10:27 <austriancoder> schurig: unstable

13:03 <schurig> Jookia: you updated one does still need some headers from the attic/ of etna_viv ?

13:04 <Jookia> schurig: yes. the instructions should still work fine

13:06 <schurig> when I saw the non-X11 demo-app "kmscube" running I thought that this is what Wayland (and also modesetting for X11) will use ...

13:06 <schurig> so kmscube was more or less just a test for me that I got my device tree right?

13:08 <Jookia> i don't know

13:30 <CoLa-M> hi, I am trying to obtain the etnaviv GPU counters with glGetPerfMonitorGroupsAMD(&n, 0, NULL) but get no output value written into n, does anyone have an idea what I might do wrong?

13:44 <CoLa-M> oh, apparently I do not find the extension... /o\ from which Mesa version onwards should that be available? I am running with Mesa 18.1.9

14:17 <schurig> okay, I compiled it and I added then Section / Driver "armada" / EndSection thingy, and my Xorg now starts

14:17 <Jookia> schurig: congrats :)

14:17 <schurig> so far so good ...

14:18 <schurig> but when I start "glxinfo", I see two error messages:

14:18 <schurig> 1: libGL error: failed to authenticate magic 1

14:18 <schurig> 2: libGL error: failed to load driver: etnaviv

14:18 <schurig> I used strace, and it could at least open the file: openat(AT_FDCWD, "/usr/lib/arm-linux-gnueabihf/libdrm_etnaviv.so.1", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 4

14:21 <schurig> in case someone wants to have a look at the Xorg.0.log: https://pastebin.com/ZvRzp2bQ

14:32 <Marex> CoLa-M: you want to update mesa to 20.1.y or master, there are A LOT of fixes

14:33 <Marex> schurig: is there any particular reason for X11 ?

14:35 <CoLa-M> Marex: no hope to get the GL extension working for mesa 18.1? I am kind of stuck with an embedded device that das not want to have a new mesa for the next 1/2 year

14:38 <Marex> CoLa-M: there were fixes for race conditions and incorrect rendering, so you want that update

14:39 <schurig> Marex: why X11? Because Wayland support in Debian Buster sucks. There's not even sway ... and I don't want to compile all by myself. Would I have wanted that, then I would have used Yocto in the first place ...

14:40 <CoLa-M> thanks, will definitely look into updating it

14:44 <schurig> Marex: yesterday I made myself mesa .deb's compiled against Buster from mesa HEAD. I now installed them (libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0), but the error messages stay

14:48 <Marex> schurig: btw do you know Richard from OE ?

14:49 <Marex> schurig: btw I tested etnaviv on debian testing (which one is that now , that's not buster, is it ?) and mesa from experimental with WL and that worked quite well

14:50 <Marex> oh yes, buster is stable and I can imagine that would suck with WL

14:50 <Marex> although I'm not particularly sure using x11 is a big win

14:52 <schurig> Marex: I knew Richard Purdie once ... I'm one of the Bitbake/OE founders, together with Kergoth, MickeyL and Zecke. RP came a bit later. But I more or less stopped using OE years ago.

14:52 <Marex> schurig: can you pastebin the x11 log (/var/log/X*) ? maybe there is some hint

14:52 <Marex> I suspected as much ...

14:53 <schurig> I think in the git history of "bitbake" you find me still, but someone removed my name from copyright comment :-(

14:53 <schurig> Debian testing ... is nothing, really. It's just has a meaning directly when the next Debian Stable is meant. Outside of this small window, it should better not be used.

14:54 <schurig> but when there is no Stable in the works, then packages move from Sid to Testing based on "Days without grave bugs" (it's a bit more complicated). So you can wait for some perfectly valid package, or a security bug fix, until these days are over.

14:54 <schurig> whereas in both Stable and Sid you'll have the security fix right away. So I never use Testing.

14:55 <Marex> schurig: it might make sense to try sid then and see whether you have more luck with X11 there, and if so, find the diffeerence between that and stable

15:18 <schurig> I "apt update" & "apt upgrade" to Sid. Still get those two error messages. The various glx* programs (e.g. glxheads) still show that they use llvmpipe, just now based on llvm-10 instead of llvm-7

15:27 <lynxeye> schurig: etnaviv_dri.so is present in /usr/lib/dri ?

15:29 <Marex> lynxeye: seems like it's loaded according to the x11 log

15:30 <lynxeye> Marex: not talking about the Xorg driver, which seems to be loaded okay, but the GL driver

15:30 <schurig> yes, it's there. Strangely a lot of those files have the exact same length

15:31 <lynxeye> schurig: That's megadrivers, aka one big driver file with all HW support. All of them are just hardlinks IIRC

15:31 <schurig> https://pastebin.com/aCPz4JZR

15:32 <schurig> i guessed so ... so etnaviv_dri is part of such a megadriver

15:33 <schurig> and "ldd" on it shows that all needed libs are there as well