01:51 <junari> Hi. I have a g57 device, but it doesn't have the display output implemented on it yet. Because of this, the kernel disables the gpu related regulator. How can I verify that the gpu is working?

02:45 <CounterPillow> If a necessary regulator for the GPU is getting turned off by a missing video output driver then the device tree is wrong and not declaring the dependency correctly. Either way, if the GPU shows up in /sys/class/drm as a `render` directory then at least the driver probed and initialised correctly.

02:58 <junari> Looks like I was wrong, I can't find any messages about disabling the gpu controller right now. In /sys/class/drm there are card0 and renderD128 that refer to gpu

03:00 <CounterPillow> does `eglinfo | grep -i panfrost` show anything?

03:02 <junari> Yes, "OpenGL core/compatibility/ES profile renderer: Mali-G57 (Panfrost)"

03:07 <CounterPillow> kk, so the driver is both loaded and evidently userspace is fine talking to it. I'm not sure what's the currently accepted way of getting a picture out of the Linux graphics stack without a video output (I think OSMesa is no longer a thing?), but that would be the next step. Maybe you could `weston --renderer=gl --backend=vnc` and then VNC into it or something?

03:09 <CounterPillow> maybe you could also `weston --renderer=gl --backend=headless` and then use `waypipe` to do it over ssh.

03:15 <junari> weston --renderer=gl --backend=vnc - failed with "fatal: failed to create compositor backend"

03:25 <CounterPillow> read the line above that error message

03:27 <junari> full output here https://gist.github.com/iuncuim/cfb638cd3777027b290e4be3ed536d6f

03:29 <CounterPillow> >[03:25:49.448] The VNC backend requires a key and a certificate for TLS security (--vnc-tls-cert/--vnc-tls-key)

03:29 <junari> With the headless option, I can see in nvtop that the gpu is in use. That's good

03:38 <junari> okay, there is option --disable-transport-layer-security to disable tls

03:44 <junari> I connected using vnc, thanks for the tip. But glmark2 still cannot initialize canvas

03:48 <junari> But glmark2-wayland works!

04:09 <olivial> junari: likely glmark2 doesn't work because weston doesn't enable xwayland by default. You can start it with '--xwayland' or stick 'xwayland=true` in the config to enable it

04:12 <junari> olivial: yes, it works, thank you

07:42 <linkmauve> junari, CounterPillow, you don’t need to run Weston on the board to use waypipe to display on your local computer, just use `waypipe ssh` and run any Wayland client over there.

09:33 <junari> linkmauve: Could you please explain what commands I should enter? On the pc side it should be waypipe ssh xyz@ip glmark2 (for example), and on the device side?

09:35 <linkmauve> Exactly, and on the device side nothing, it will just work.

09:35 <linkmauve> You just need to also have waypipe installed there.