I did some experimentation re: Nvidia video drivers and OpenGL. Here's what I did:
1. Created a live USB, booted it with persist_all, used MX Repo Manager to select my mirrors, ran sudo apt update, ran the MX Updater to install all available updates, then remastered and rebooted.
2. Installed the Nvidia driver from the test repo and rebooted. Still no OpenGL renderers per inxi -G. This shows that it's not an issue with my installed version of 19b3.
3. Installed the antiX 4.9 kernel then ran the Live Kernel Updater, remastered, installed the 4.9 kernel in the live USB, rebooted. Booting stopped at the udev portion. Alt+F1 showed a console login prompt. Logged in and deleted /etc/X11/xorg.conf and rebooted.
4. Ran /usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh as su as my wifi no longer worked, rebooted, logged in to my SSID, reinstalled the Nvidia driver from test repo, rebooted. Still no OpenGL renderer. This shows that it's not an issue with the kernel.
5. Reinstalled MX-19b3 from my live USB, this time also installing its grub on my MBR.
(BTW there's a new option in the MX-19 installer if you install to existing partitions and preserve /home. Later on it prompts you whether you want to reuse your personal home directory, save it, delete it, plus one other option that I can't remember. It's not at all clear what the difference is between reuse and save. Once in the past I selected reuse, thinking that meant to reuse the existing home directory of my user name, while still preserving its contents as I'd already told the installer to do. I'm pretty sure it didn't save the contents, it replaced them all with those in /etc/skel. This time I selected save, but it saved it as /home/jay.001. It appears to no longer leave the contents of your home directory alone as it does in MX-18. I could be mistaken though.)
6. MX-19's grub didn't pick up my encrypted MX-18 installation and only gave me the MX-19 boot options, even after running sudo update-grub and rebooting. I selected booting MX-19 with the 4.9 kernel with systemd from advanced options. Still no OpenGL renderer. This shows it has nothing to do with booting with Sys V or the shim in MX-19 Buster.
7. Booted my MX-18 personal snapshot USB, ran MX Boot Repair to reinstall the MX-18 grub, got the usual can't create a chroot environment error. Reinstalled MX-18 from my snapshot that I made a few weeks ago. MX-18's grub shows all of both 18 and 19's boot options in its (flat) grub menu plus memtest, so I'm back in business. (However I just have the nouveau video driver as I made the snapshot just prior to installing the Nvidia driver in MX-18 the first time. I may just leave it that way. I only installed Nvidia's driver to see if it would work or not.)
8. I just reburned the 19b3 iso to my USB and booted it:
Code: Select all
demo@mx1:~
$ inxi -G
Graphics: Device-1: NVIDIA GT216M [GeForce GT 230M] driver: nouveau v: kernel
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: NVA5 v: 3.3 Mesa 18.3.6
showing it's strictly an Nvidia driver issue, not something to do with OpenGL in general on this machine.
Conclusion: Something is wrong with the OpenGL packages for the Nvidia 340.170 legacy drivers, both the ones in stable and test. They get installed but they don't work or don't get loaded or something. The Nvidia driver itself works, but there's no OpenGL rendering so some apps don't work.
...going for sleep & wake-up once more solved it, though..
). Sure enough, first time I realized this, I manually checked, and there were over 200MB of updates I should have installed many days prior 