I think people who package #Mesa should disable #llvmpipe by default.
I don't think there's any situation where it's useful to the typical end-user, and many where it's problematic.
@topher if you like #SGI #IRIX, then maybe @bunsenlabs / #BunsenLabs woth it's #OpenBox desktop is right up your alley?
@EpicPawt I can recommend to take a look at #TinyCore and #BunsenLabs if you like some #smol #desktop #distro...
TinyCore is a #BusyBox / #Linux and @bunsenlabs is a nifty #Debian derivate which runs even on a #GMA500 / #Poulsbo / #IntelAtom Z-series system like the #VaioP11Z just fine despite using #llvmpipe for rendering...
@krutonium I can recommend @bunsenlabs / #BunsenLabsLinux which runs smooth in my #Vaio #P11Z with the shitty #GMA500 in #llvmpipe.
Those are the options with a fancy #GUI.
@weirdfish @oldperl es gibt nen #fallback...
#SofwareRenderer [wie bei #Windows] per llvmpipe...
Okay, korrekterweise ist der #FOSS-Treiber #nouveau zu benennen, aber wenn ihr nen Schuldigen sucht, dann müsst ihr #nvidia's Kundendienst konsequent abnerven bis diese einen brauchbaren Treiber als #FLOSS releasen...
I'm wondering if anybody can help me with this fiddly problem. I've been playing Death Stranding (which I got free through the Epic store a while back) using the Heroic Games Launcher. It was working perfectly, but suddenly I'm getting this error message when I try to launch it. I haven't intentionally changed any settings (though have been moving items in my Steam library between internal hard drives). Any thoughts? #HeroicGamesLauncher #Epic #Proton #Linux #DeathStranding #error #llvmpipe
@sleepybisexual @Raspberry_Pi well, #Termux does offer you some packages, tho I'm not shure if it does anything beyond #llvmpipe aka #performance will be trash and battery runtime abysmal...
@marcan @AsahiLinux Yeah, I know ~why~ they did it and from their perspective that's all fine - basically like the @Raspberry_Pi having no #EFI and simply a bootcode EEPROM...
It just makes programming stuff quite annoying cuz there isn't some basic #llvmpipe-style fallback but one propably has to fully initialize the attached display and it's parameters - whereas for the MacBooks that's not needed due to the panel configuration being static.
Next time you suffer from #ImpostorSyndrome remember that this ancient geek, super developer and extreme techie just debugged an #Ubuntu system for more than an hour to figure out why it wasn't possible to expand the desktop across monitors after the installation of #NVidia drivers.
... only to finally figure out that the cause for the #llvmpipe being the active driver and causing all of the issues was ...
... that I had installed the #headless version of the drivers.
Okay.. I think I got the new API for #opencl's WorkGroupInfo figured out as it works quite nicely with #radeonsi now. Just missing implementations for #nouveau, #llvmpipe and #panfrost (and maybe the #iris one could be improved a little?)
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19855