**** BEGIN LOGGING AT Tue Apr 26 02:59:56 2022 Apr 26 05:59:43 hmmmm Apr 26 06:48:41 whether Beaglebone supports Python and matlab codes for audio signal processing? Apr 26 20:22:30 Hey all, I've been struggling to get the SGX/PVR drivers running with LXQT installed. Anytime libgbm.so.2 shows up in my /usr/lib/, lightdm doesn't start correctly. If I remove it, pvr fails to load. Thoughts? Apr 26 20:25:54 the sgx drivers are incompatible with x11 Apr 26 20:26:58 they're also a pain to get working in general, but you're not going to get them working with lightdm at all Apr 26 20:27:56 Oh.. Ok. Then to clarify my understanding, is the LXQT image of debian stretch hardware accelerated? We've been trying to run some gui apps ad I feel like we are not able to use the GPU Apr 26 20:28:11 no, since the gpu does not support x11 Apr 26 20:28:17 (or rather, the gpu drivers) Apr 26 20:28:18 Oh.. Ok. Then to clarify my understanding, is the LXQT image of debian stretch hardware accelerated? We've been trying to run some gui apps and I feel like we are not able to use the GPU Apr 26 20:28:31 (sorry for the double post) Apr 26 20:28:32 also, debian stretch is extremely ancient Apr 26 20:28:38 and obsolete/unmaintained Apr 26 20:29:50 I agree that its pretty dated, however, the recommended image from "latest images" is OMAP3/DM3730 Debian 9.5 2018-10-07 4GB SD LXQT Apr 26 20:30:07 ohh, for the old beagleboard Apr 26 20:30:34 TI_AM335x_BeagleBone_Black Apr 26 20:30:50 beaglebone black isn't omap3 Apr 26 20:31:04 the beaglebone black uses an AM3358 Apr 26 20:31:41 oh, right, i meant Debian 9.9 2019-08-03 4GB SD LXQT Apr 26 20:31:41 the latest recommended image for which is the AM3358 Debian 10.3 2020-04-06 4GB SD IoT Apr 26 20:32:01 (or generally its eMMC flasher equivalent, AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher ) Apr 26 20:32:18 note that the IoT image doesn't include a GUI, since almost nobody uses one on a beaglebone Apr 26 20:32:29 I was having issues getting any sort of graphics working on the buster images, maybe I missed something Apr 26 20:33:09 the AM335x is targeted at industrial applications and has very limited graphics capabilities, mostly intended just for simple touchscreen interfaces Apr 26 20:34:13 which is exactly what my company uses them for. I'm trying to get them away from the old unmaintained qt-over-vnc touch interface that they hacked together for debian 7 Apr 26 20:34:32 qt5 can run directly on the framebuffer, without x11 Apr 26 20:35:08 with gpu (eglfs backend) or without (linuxfb backend) Apr 26 20:35:44 is https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston compatible with the buster images? Apr 26 20:36:01 I felt i had problems trying to get a framebuffer/kmscube running Apr 26 20:36:57 I know there are people who have things working, but I don't know if they've been kind enough to do any sort of write-up Apr 26 20:37:37 that wiki page looks outdated to me Apr 26 20:38:26 it's really about all I've found on how to get sgx/pvr running correctly, but again, I'm not sure Apr 26 20:38:47 and it gets close, but it feels like something is missing Apr 26 20:39:10 rcn-ee: I forgot, are the sgx userspace libs packaged nowadays? Apr 26 20:39:51 I know the kernel drivers are Apr 26 20:42:59 RMoll: sorry, I haven't done anything with graphics on the bbb for many many years, so I don't really have any uptodate guidance Apr 26 20:43:24 I know the gpu can be made to work Apr 26 20:43:37 All good, the insights you've provided about the gpu drivers already answered many of my questions Apr 26 20:43:42 but it may also be worth evaluating qt5 with the linuxfb backend Apr 26 20:44:23 in general, if kmscube runs, then gpu accel is working? Apr 26 20:44:58 iirc, back when I did, the linuxfb backend (without gpu) actually resulted in faster execution than the eglfs backend (with gpu). we ended up using eglfs anyway because the linuxfb backend back then didn't support double-buffering hence caused noticable flickering, but I think that's been fixed nowadays Apr 26 20:45:58 (iirc qt5's "linuxfb" backend these days actually supports using dri/kms instead of the legacy fbdev kernel interface) Apr 26 20:47:24 unless you actually *need* opengl es/es2, e.g. for 3d rendering, then you'll obviously want to get the gpu working Apr 26 20:48:32 we wanted to see if we could get .NET 5+ to run targetting the framebuffer or drm, from https://github.com/AvaloniaUI/Avalonia. Might be too uch to ask from the bbg it sounds like Apr 26 20:49:22 I do have it able to run outputting directly to the FB, but we were unsure about input performance since X server tends to take care of mouse inputs Apr 26 20:50:48 not sure what you mean, obviously inputs will be faster / more efficient *without* an extra middle-man like x11 Apr 26 20:52:17 We couldn't test touch inputs because once we lose access to X, we can't seem to provide human input to the application Apr 26 20:53:05 sounds like some kind of configuration issue, or a permissions issue... make sure the user running the application (presumably the "debian" user") is a member of the "input" group Apr 26 20:53:28 which can be fixed by doing "sudo adduser debian input" and then logging out and back in Apr 26 20:53:57 good idea, i'll check Apr 26 20:56:49 ls **** ENDING LOGGING AT Wed Apr 27 02:59:56 2022