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.
Over 120 individual programs plus dozens of programmer libraries and feature plugins
are released simultaneously as part of KDE Gear.
Today they all get new bugfix source releases with updated translations, including:
- dolphin: Don't recurse into symlinks when counting directory contents
- kdeconnect: Fix ssh authentication using pubkey on recent openssh versions
- libkdegames: Fix finding knewstuff themes
There is an improved patch for building (and shipping) both the classic i195 and Gallium's i915g drivers on latest Mesa from -current.
Code:
diff -urN mesa.orig/mesa-amber.build mesa/mesa-amber.build
--- mesa.orig/mesa-amber.build 2022-08-09 00:46:48.013005690 +0300
+++ mesa/mesa-amber.build 2023-02-04 09:49:21.213445329 +0200
@@ -84,6 +84,12 @@
rsync -lprvt $PKG/cruft/usr/lib${LIBDIRSUFFIX}/dri/ $PKG/usr/lib${LIBDIRSUFFIX}/dri/
rm -rf $PKG/cruft
+# Setup the classic i915 driver:
+( cd $PKG/usr/lib${LIBDIRSUFFIX}/dri
+ mv i915_dri.so i915_dri.so-classic
+ ln -sf i915_dri.so-classic i915_dri.so
+)
+
rm -rf $PKG/usr/doc/$PKGNAM-$AMBERVERS
mkdir -p $PKG/usr/doc/$PKGNAM-amber-$AMBERVERS
cp -a \
diff -urN mesa.orig/mesa.SlackBuild mesa/mesa.SlackBuild
--- mesa.orig/mesa.SlackBuild 2022-12-07 20:37:26.799032342 +0200
+++ mesa/mesa.SlackBuild 2023-02-04 09:52:19.133221025 +0200
@@ -34,7 +34,7 @@
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"
+GALLIUM_DRIVERS="nouveau,r300,r600,svga,radeonsi,swrast,virgl,iris,crocus,i915,zink"
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
@@ -165,7 +165,19 @@
)
if [ "$BUILD_AMBER" = "YES" ]; then
+ # Rename the Gallium i915 driver:
+ ( cd $PKG/usr/lib${LIBDIRSUFFIX}/dri
+ mv i915_dri.so i915_dri.so-gallium
+ )
+
. $CWD/mesa-amber.build
+
+ if [ ! -r $PKG/usr/lib${LIBDIRSUFFIX}/dri/i915_dri.so ]; then
+ # Don't keep renamed the Gallium i915 driver when the classic driver wasn't built:
+ ( cd $PKG/usr/lib${LIBDIRSUFFIX}/dri
+ mv i915_dri.so-gallium i915_dri.so
+ )
+ fi
fi
if [ "$BUILD_DEMOS" = "YES" ]; then
Mainly, it's about a better build logic, considering that on the current mesa.SlackBuild the (additional) Mesa Amber support is, well... optional.
As I already said, I believe that shipping both i195 drivers on Mesa is important, because the classic one is already legacy and the Gallium one is still maintained, with no signs that it will retired in the foreseeable future. Additionally, according with my experience, this i915g works better and with better performance with Plasma5 (even it presents worse artifacts) and on the XFCE sessions its behavior is excellent.
Last edited by LuckyCyborg; 02-04-2023 at 03:07 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.