SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
you are kind to explain in detail what we wait for Mesa-22.1.x ?
IF there's an issue, please be kind to say it publicly - there may be people able to eventually help.
I for one, I've built and used with great success and since long time the Mesa-22.x.y which ships the Gallium only drivers.
This is my mesa.SlackBuild for version mesa-22.x.y :
Code:
#!/bin/bash
# Copyright 2006, 2007, 2008, 2009, 2010, 2011, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021 Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
cd $(dirname $0) ; CWD=$(pwd)
PKGNAM=mesa
VERSION=${VERSION:-$(echo $PKGNAM-[0-9]*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
DEMOVERS=${DEMOVERS:-8.4.0}
BUILD=${BUILD:-1}
BUILD_DEMOS=${BUILD_DEMOS:-YES}
NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}
# Be sure this list is up-to-date:
GALLIUM_DRIVERS="nouveau,r300,r600,svga,radeonsi,swrast,virgl,iris,crocus,zink"
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) export ARCH=i586 ;;
arm*) export ARCH=arm ;;
*) export ARCH=$( uname -m ) ;;
esac
fi
# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
echo "$PKGNAM-$VERSION-$ARCH-$BUILD.txz"
exit 0
fi
## COMMENTED OUT as swr seems to be broken with llvm13:
## Build swr for the following architectures (not for i?x6, as this will cause
## an Illegal Instruction startup failure on many otherwise supported CPUs):
#for swr_arch in x86_64 ; do
# if [ "$ARCH" = "x86_64" ]; then
# GALLIUM_DRIVERS="$GALLIUM_DRIVERS,swr"
# fi
#done
TMP=${TMP:-/tmp}
PKG=$TMP/package-mesa
if [ "$ARCH" = "i586" ]; then
SLKCFLAGS="-O2 -march=i586 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
LIBDIRSUFFIX="64"
else
SLKCFLAGS="-O2"
LIBDIRSUFFIX=""
fi
rm -rf $PKG
mkdir -p $TMP $PKG
cd $TMP
rm -rf ${PKGNAM}-${VERSION}
tar xvf $CWD/${PKGNAM}-${VERSION}.tar.?z || exit 1
cd ${PKGNAM}-$VERSION || exit 1
# Let's kill the warning about operating on a dangling symlink:
rm -f src/gallium/state_trackers/d3d1x/w32api
# Make sure ownerships and permissions are sane:
chown -R root:root .
find . \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
-exec chmod 755 {} \+ -o \
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
-exec chmod 644 {} \+
# Apply patches from git (and maybe elsewhere):
# Patches obtained by:
# git checkout origin/17.2
# git format-patch 93c2beafc0a7fa2f210b006d22aba61caa71f773 # 17.2.6 release
if /bin/ls $CWD/patches/*.patch 1> /dev/null 2> /dev/null ; then
for patch in $CWD/patches/*.patch ; do
patch -p1 --verbose < $patch || exit 1 ;
done
fi
# Revert these patches from git (and maybe elsewhere):
if /bin/ls $CWD/patches-revert/*.patch 1> /dev/null 2> /dev/null ; then
for patch in $CWD/patches-revert/*.patch ; do
patch -p1 -R --verbose < $patch || exit 1 ;
done
fi
# Configure, build, and install:
export CFLAGS="$SLKCFLAGS"
export CXXFLAGS="$SLKCFLAGS"
mkdir meson-build
cd meson-build
meson setup \
--prefix=/usr \
--libdir=lib${LIBDIRSUFFIX} \
--libexecdir=/usr/libexec \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--includedir=/usr/include \
--datadir=/usr/share \
--mandir=/usr/man \
--sysconfdir=/etc \
--localstatedir=/var \
--buildtype=release \
-Dplatforms=x11,wayland \
-Dgallium-opencl=icd \
-Dgallium-nine=true \
-Dosmesa=true \
-Dgallium-drivers=$GALLIUM_DRIVERS \
-Dvulkan-drivers=amd,intel,swrast \
-Dvulkan-layers=device-select,intel-nullhw,overlay \
-Dglvnd=true \
-Dllvm=enabled \
-Dshared-llvm=enabled \
-Dshared-glapi=enabled \
-Degl=enabled \
-Dgles1=enabled \
-Dgles2=enabled \
-Dopengl=true \
-Dglx=dri \
.. || exit 1
"${NINJA:=ninja}" $NUMJOBS || exit 1
DESTDIR=$PKG $NINJA install || exit 1
cd ..
# Install /etc/drirc as a .new file:
if [ -r $PKG/etc/drirc ]; then
mv $PKG/etc/drirc $PKG/etc/drirc.new
fi
# Add a default provider for glvnd when the vendor cannot be determined:
( cd $PKG/usr/lib${LIBDIRSUFFIX}
if [ ! -r libGLX_system.so.0 ]; then
ln -sf libGLX_mesa.so.0 libGLX_system.so.0
fi
)
if [ "$BUILD_DEMOS" = "YES" ]; then
# Now build/install a small subset of the demos:
export CWD SLKCFLAGS NUMJOBS PKG
( cd $TMP
rm -rf mesa-demos-$DEMOVERS
tar xvf $CWD/mesa-demos-$DEMOVERS.tar.?z* || exit 1
cd mesa-demos-$DEMOVERS
chown -R root:root .
find . \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
-exec chmod 755 {} \+ -o \
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
-exec chmod 644 {} \+
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--build=$ARCH-slackware-linux || exit 1
make $NUMJOBS || exit 1
# Install all the demos (including the pointless ones) at first, in a
# temporary location:
make install DESTDIR=$PKG/cruft || exit 1
# Install gears and glinfo, as well as a few other demos:
mkdir -p $PKG/usr/bin
for demo in eglinfo gears glinfo glthreads glxcontexts glxdemo glxgears \
glxgears_fbconfig glxheads glxinfo glxpbdemo glxpixmap ; do
mv --verbose $PKG/cruft/usr/bin/$demo $PKG/usr/bin
done
# Remove cruft:
rm -rf $PKG/cruft
) || exit 1
fi
# Strip binaries:
find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find $PKG/usr/man -type f -exec gzip -9 {} \+
for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
# Compress info files, if any:
if [ -d $PKG/usr/info ]; then
rm -f $PKG/usr/info/dir
gzip -9 $PKG/usr/info/*
fi
mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION/html
cp -a \
docs/COPYING* docs/relnotes/${VERSION}.html docs/README* docs/GL* \
$PKG/usr/doc/$PKGNAM-$VERSION
cp -a docs/*.html $PKG/usr/doc/$PKGNAM-$VERSION/html
rm -f $PKG/usr/doc/$PKGNAM-$VERSION/html/relnotes*.html
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
zcat $CWD/doinst.sh.gz > $PKG/install/doinst.sh
cd $PKG
/sbin/makepkg -l y -c n $TMP/${PKGNAM}-$VERSION-$ARCH-$BUILD.txz
I've even built Mesa 22.1.1 on Slackware 15.0 as seen in the attached screenshot - and it works fine.
From my experience, the Intel Crocus taken over to Intel i965 and do a fine job for everything starting with Intel GM45 and yet not supported by Iris.
I've even built an Mesa Amber package, testing it with great attention, having the advantage of having hardware which uses Intel i965 alternatively - like is Intel GM45, Sandy Bridge and Ivy Bridge graphics.
And there is my mesa-amber.Slackbuild using mesa-21.3.8 :
Code:
#!/bin/bash
# Copyright 2006, 2007, 2008, 2009, 2010, 2011, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021 Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
cd $(dirname $0) ; CWD=$(pwd)
PKGNAM=mesa
VERSION=${VERSION:-$(echo $PKGNAM-[0-9]*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
DEMOVERS=${DEMOVERS:-8.4.0}
BUILD=${BUILD:-1}
BUILD_DEMOS=${BUILD_DEMOS:-YES}
NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}
# Be sure this list is up-to-date:
DRI_DRIVERS="i915,i965,r100,r200,nouveau"
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) export ARCH=i586 ;;
arm*) export ARCH=arm ;;
*) export ARCH=$( uname -m ) ;;
esac
fi
# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
echo "$PKGNAM-$VERSION-$ARCH-$BUILD.txz"
exit 0
fi
## COMMENTED OUT as swr seems to be broken with llvm13:
## Build swr for the following architectures (not for i?x6, as this will cause
## an Illegal Instruction startup failure on many otherwise supported CPUs):
#for swr_arch in x86_64 ; do
# if [ "$ARCH" = "x86_64" ]; then
# GALLIUM_DRIVERS="$GALLIUM_DRIVERS,swr"
# fi
#done
TMP=${TMP:-/tmp}
PKG=$TMP/package-mesa-amber
if [ "$ARCH" = "i586" ]; then
SLKCFLAGS="-O2 -march=i586 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
LIBDIRSUFFIX="64"
else
SLKCFLAGS="-O2"
LIBDIRSUFFIX=""
fi
rm -rf $PKG
mkdir -p $TMP $PKG
cd $TMP
rm -rf ${PKGNAM}-${VERSION}
tar xvf $CWD/${PKGNAM}-${VERSION}.tar.?z || exit 1
cd ${PKGNAM}-$VERSION || exit 1
# Let's kill the warning about operating on a dangling symlink:
rm -f src/gallium/state_trackers/d3d1x/w32api
# Make sure ownerships and permissions are sane:
chown -R root:root .
find . \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
-exec chmod 755 {} \+ -o \
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
-exec chmod 644 {} \+
# Apply patches from git (and maybe elsewhere):
# Patches obtained by:
# git checkout origin/17.2
# git format-patch 93c2beafc0a7fa2f210b006d22aba61caa71f773 # 17.2.6 release
if /bin/ls $CWD/patches/*.patch 1> /dev/null 2> /dev/null ; then
for patch in $CWD/patches/*.patch ; do
patch -p1 --verbose < $patch || exit 1 ;
done
fi
# Revert these patches from git (and maybe elsewhere):
if /bin/ls $CWD/patches-revert/*.patch 1> /dev/null 2> /dev/null ; then
for patch in $CWD/patches-revert/*.patch ; do
patch -p1 -R --verbose < $patch || exit 1 ;
done
fi
# Configure, build, and install:
export CFLAGS="$SLKCFLAGS"
export CXXFLAGS="$SLKCFLAGS"
mkdir meson-build
cd meson-build
meson setup \
--prefix=/usr \
--libdir=lib${LIBDIRSUFFIX} \
--libexecdir=/usr/libexec \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--includedir=/usr/include \
--datadir=/usr/share \
--mandir=/usr/man \
--sysconfdir=/etc \
--localstatedir=/var \
--buildtype=release \
-Dplatforms=x11,wayland \
-Damber=true \
-Ddri-drivers=$DRI_DRIVERS \
-Dgallium-drivers=swrast \
-Dosmesa=true \
-Dglvnd=true \
-Dllvm=enabled \
-Dshared-llvm=enabled \
-Dshared-glapi=enabled \
-Degl=enabled \
-Dgles1=enabled \
-Dgles2=enabled \
-Dopengl=true \
-Dglx=dri \
.. || exit 1
"${NINJA:=ninja}" $NUMJOBS || exit 1
DESTDIR=$PKG $NINJA install || exit 1
cd ..
# Install /etc/drirc as a .new file:
if [ -r $PKG/etc/drirc ]; then
mv $PKG/etc/drirc $PKG/etc/drirc.new
fi
# Add a default provider for glvnd when the vendor cannot be determined:
( cd $PKG/usr/lib${LIBDIRSUFFIX}
if [ ! -r libGLX_system.so.0 ]; then
ln -sf libGLX_amber.so.0 libGLX_system.so.0
fi
)
if [ "$BUILD_DEMOS" = "YES" ]; then
# Now build/install a small subset of the demos:
export CWD SLKCFLAGS NUMJOBS PKG
( cd $TMP
rm -rf mesa-demos-$DEMOVERS
tar xvf $CWD/mesa-demos-$DEMOVERS.tar.?z* || exit 1
cd mesa-demos-$DEMOVERS
chown -R root:root .
find . \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
-exec chmod 755 {} \+ -o \
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
-exec chmod 644 {} \+
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--build=$ARCH-slackware-linux || exit 1
make $NUMJOBS || exit 1
# Install all the demos (including the pointless ones) at first, in a
# temporary location:
make install DESTDIR=$PKG/cruft || exit 1
# Install gears and glinfo, as well as a few other demos:
mkdir -p $PKG/usr/bin
for demo in eglinfo gears glinfo glthreads glxcontexts glxdemo glxgears \
glxgears_fbconfig glxheads glxinfo glxpbdemo glxpixmap ; do
mv --verbose $PKG/cruft/usr/bin/$demo $PKG/usr/bin
done
# Remove cruft:
rm -rf $PKG/cruft
) || exit 1
fi
# Strip binaries:
find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find $PKG/usr/man -type f -exec gzip -9 {} \+
for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
# Compress info files, if any:
if [ -d $PKG/usr/info ]; then
rm -f $PKG/usr/info/dir
gzip -9 $PKG/usr/info/*
fi
mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION/html
cp -a \
docs/COPYING* docs/relnotes/${VERSION}.html docs/README* docs/GL* \
$PKG/usr/doc/$PKGNAM-$VERSION
cp -a docs/*.html $PKG/usr/doc/$PKGNAM-$VERSION/html
rm -f $PKG/usr/doc/$PKGNAM-$VERSION/html/relnotes*.html
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
zcat $CWD/doinst.sh.gz > $PKG/install/doinst.sh
cd $PKG
/sbin/makepkg -l y -c n $TMP/${PKGNAM}-amber-$VERSION-$ARCH-$BUILD.txz
Honestly, we will need this alternate Mesa Amber package containing only the legacy non-Gallium drivers, ONLY IF we still want to support the really old graphics, like ATI R100 and R200 or Intel GMA 3150 - which at best are rocking an OpenGL 1.4.
IF we ship also the alternate Mesa Amber package, then I seen that it conflicts with the main Mesa package. So it's quite clear that eventually it should be shipped as an alternate package on /extra .
I for one, I talk with both Mesa packages in the hand - I've seen how behaves the Mesa 22.x.y and I've seen how behaves the Mesa Amber.
With all respect due, what the heck we wait when the solution is obvious?
PS. Those who uses the Ivy Bridge graphics under i965 knows that Mesa 21.x.y advertise only OpenGL 3.0, while Crocus from Mesa 22.x.y goes up to OpenGL 4.2, as shown in the screenshot.
Last edited by LuckyCyborg; 06-05-2022 at 11:24 AM.
Probably he removed or adjusted the reverting patches. Likely is their removal, otherwise probably he had been presented the modified patches.
But I think that the place of an eventual legacy Mesa package is within /pasture not /extra .
Yes, I have been removed those patches.
However, I believe that the place of an eventual Mesa Amber package is /extra because it's still maintained in LTS mode (for the legacy non-Gallium drivers only!!! ) and it's an alternative for the legacy hardware.
As creepy as it looks, seems like we need 2 different Mesa package to cover the entire graphics stack.
Still, the Mesa 22.x.y covers anything at least barely modern and capable at least of OpenGL 2.0 .
So, the "affected" users are those who still rocking Pentium III and similar hardware. Yet, they will get a software OpenGL driver like llvmpipe, until they replace their Mesa with the correct Mesa Amber variant.
Last edited by LuckyCyborg; 06-06-2022 at 04:23 AM.
I believe that the place of an eventual Mesa Amber package is /extra because it's still maintained in LTS mode (for the legacy non-Gallium drivers only!!! ) and it's an alternative for the legacy hardware.
IMO, this has no place in Slackware then, not even in pasture. There's also SlackBuilds.org which would be a good place for legacy stuff.
I mean, who still runs a computer with a Pentium III and wants to run the latest Slackware on it? Don't torture that geriatric hardware!
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 451
Rep:
Quote:
Originally Posted by Windu
IMO, this has no place in Slackware then, not even in pasture. There's also SlackBuilds.org which would be a good place for legacy stuff.
I mean, who still runs a computer with a Pentium III and wants to run the latest Slackware on it? Don't torture that geriatric hardware!
It will run (at least on a VM), but not very happily. A few packages don't work; pretty much anything Rust-based is out (most notably Firefox), along with a few other odds and ends.
IMO, this has no place in Slackware then, not even in pasture. There's also SlackBuilds.org which would be a good place for legacy stuff.
I mean, who still runs a computer with a Pentium III and wants to run the latest Slackware on it? Don't torture that geriatric hardware!
Well, in fact this Mesa Amber will be needed for computers with up to Intel Core 2 Duo and Core 2 Quad on socket 775, because some Intel chipsets for socket 775 still shipped openGL 1.4 embedded graphics like GMA 3150.
Ho wait ...year 2525 slackware stucks on mesa 21.3000.3000
??
We need go to front.
Good question!
Well, from what I known, the Mesa Amber (then the legacy drivers from 21.3.x, BUT not the Gallium ones too) will be supported in LTS mode until 2026.
Not a really impressive EOL date, considering over 5 years of today development cycles of Slackware...
I for one, I believe that IF we are lucky, we will get Slackware 15.1 around AD 2027, when the Mesa Amber will be already dead and buried. Since long time - and with it, will end the support for legacy hardware over non-Gallium drivers.
Like our friend @Windu said, maybe makes no sense to mess with Mesa Amber...
Last edited by LuckyCyborg; 06-06-2022 at 09:33 AM.
Well, in fact this Mesa Amber will be needed for computers with up to Intel Core 2 Duo and Core 2 Quad on socket 775, because some Intel chipsets for socket 775 still shipped openGL 1.4 embedded graphics like GMA 3150.
That's why I think that Mesa Amber will be still needed in Slackware.
Those computers with relative powerful CPUs and forced to use the OpenGL 1.4 graphics included in motherboard, are probably better deserved by LLVMpipe - anyway today even the GMA 3150 is a crap.
Happened to have an HP dc7800p USDT, and from what I seen, the Plasma5 fallback to software rendering when the openGL support is lower than 2.0 , so it uses the soft or LLVM pipe anyway.
However, the computers forced to use discrete graphics supporting only OpenGL 1.4 are much older.
Last edited by LuckyCyborg; 06-06-2022 at 10:16 AM.
alsa-lib-1.2.7 package, not work here, (1.2.6.1, work), with (Juniper HDMI Audio Radeon HD5700 Serie)
tested here, work fine.
Testing the new Slint installer it took me several hours to understand that using alsa-lib-1.2.7 is what prevented it to speak in a Qemu VM, although I have no issue using it on bare metal. Downgrading it to 1.2.6.1 solved this issue (not sure it be the same, though).
Last edited by Didier Spaier; 06-09-2022 at 07:48 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.