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.
that mean your 32 bit vulkan driver is broken, same problem as i have.
i don't think having the same version will solve the problem. i have same version of mesa 23.3.1 and the 32 bit vulkan driver is still broken.
Hmmm, I do have another SSD with an install of slackware updated sometimes in September, so I do have all the required packages.
Shall I just go copy/paste?
I just updated my laptop (Intel GPU) to the latest Slackware64-current with multilib as offered by Alien Bob. I run "/usr/bin/32/vkcube" and I get a spinning cube in a separate window. No errors or warnings regarding Vulkan.
Hmmm, I do have another SSD with an install of slackware updated sometimes in September, so I do have all the required packages.
Shall I just go copy/paste?
just downgrade to llvm 16 and mesa 23.1.8 and i think your problems with steam will be solved. Al least in my case with llvm 16 and mesa 23.1.8 i dont have any problems with the Vulkan 32 bit driver.
just downgrade to llvm 16 and mesa 23.1.8 and i think your problems with steam will be solved. Al least in my case with llvm 16 and mesa 23.1.8 i dont have any problems with the Vulkan 32 bit driver.
Yeah gonna get the files and try this - more could be broken than just the gaming here.
Let's hope they fix this asap.
On that note - perhaps u can help me out here.
So I have had a HP laptop (AMD) which burned out - the SSD is still intact.
Bought another laptop and was like - switch the SSD and you're up and running again, but it didn't work like that.
So now if I want to start up from the SSD, I need to launch from Slackware install USB and choose start from SSD from there.
I was using Grub2 as bootloader.
The new Laptop is a Zephyrus G14 2022, secure and fast boot off in BIOS, separate home partition.
What shall I do to be able to start up from my old slackware SSD without using the USB?
I really do not want to reinstall - my work data are up there.
Code:
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 616447 614400 300M EFI System
/dev/nvme0n1p2 134219776 1182795775 1048576000 500G Linux filesystem
/dev/nvme0n1p3 1182795776 3907028991 2724233216 1.3T Linux filesystem
/dev/nvme0n1p4 616448 134219775 133603328 63.7G Linux swap
On that note - perhaps u can help me out here.
So I have had a HP laptop (AMD) which burned out - the SSD is still intact.
Bought another laptop and was like - switch the SSD and you're up and running again, but it didn't work like that.
So now if I want to start up from the SSD, I need to launch from Slackware install USB and choose start from SSD from there.
I was using Grub2 as bootloader.
The new Laptop is a Zephyrus G14 2022, secure and fast boot off in BIOS.
What shall I do to be able to start up from my old slackware SSD without using the USB?
I really do not want to reinstall - my work data are up there.
This is an example for slackware64 UEFI ASSUME /dev/nvme0n1p2 is the root!
Some steps that might fix it:
Boot from your Slackware installation USB.
Once booted, open a terminal.
Code:
e2fsck -f /dev/nvme0n1p2
Code:
mount /dev/nvme0n1p2 /mnt
Code:
mount --bind /dev /mnt/dev
mount --bind /tmp /mnt/tmp
mount --bind /run /mnt/run
mount -t proc proc /mnt/proc
mount -t sysfs none /mnt/sys
mount -t devpts -o noexec,nosuid,gid=tty,mode=0620 devpts /mnt/dev/pts
Code:
mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
Chroot into the Slackware Installation
Code:
chroot /mnt /bin/bash
Different hardware may require different drivers, so run mkinitrd...and reinstall grub
This is an example for slackware64 UEFI ASSUME /dev/nvme0n1p2 is the root!
Some steps that might fix it:
Boot from your Slackware installation USB.
Once booted, open a terminal.
Code:
e2fsck -f /dev/nvme0n1p2
Code:
mount /dev/nvme0n1p2 /mnt
Code:
mount --bind /dev /mnt/dev
mount --bind /tmp /mnt/tmp
mount --bind /run /mnt/run
mount -t proc proc /mnt/proc
mount -t sysfs none /mnt/sys
mount -t devpts -o noexec,nosuid,gid=tty,mode=0620 devpts /mnt/dev/pts
Code:
mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
Chroot into the Slackware Installation
Code:
chroot /mnt /bin/bash
Different hardware may require different drivers, so run mkinitrd...and reinstall grub
Verify that your /etc/fstab file reflects the correct partition information for the new laptop.
DO IT AT YOUR OWN RISK IF BETTER SOLUTION NOT POST HERE... IF SOMETHING GO WRONG YOU MIGHT WILL LOSE EVERYTHING.
thanks, I did reinstall grub, but from the SSD itself (booted through the USB, so perhaps that was the issue).
Will try on my own risk, I always have my data on 2 PCs in case one of them excuses itself, which sadly happens from time to time.
/motherboard failure, GPU failure, controller etc.. mostly it's just me being lazy to use the huge disc with dubious software wanting me to log in online every time I access it
Once this is all chained to (using some cron jobs and wrapper scripts) I get this..
Code:
# slackpkg search mesa
Looking for mesa in package list. Please wait... DONE
The list below shows all packages with name matching "mesa".
[upgr] compat32 : mesa-compat32-23.3.0-x86_64-1compat32 --> mesa-compat32-23.3.1-x86_64-1compat32
[upgr] slackware64 : mesa-23.3.0-x86_64-1 --> mesa-23.3.1-x86_64-1
[mask] multilib : mesa-compat32-23.2.1-x86_64-1compat32
You can search specific files using "slackpkg file-search file".
Based on the conclusions of this thread I won't be seeing any problems. For anyone who hasn't already looked you should take a gander at Alien Bob's entire collection of scripts and utilities. http://www.slackware.com/~alien/
Oh also, if you installed the ENTIRE multilib repo then you already have the compat32-tools package.
Code:
# cat /var/lib/pkgtools/packages/compat32-tools-3.10-noarch-7alien
PACKAGE NAME: compat32-tools-3.10-noarch-7alien
COMPRESSED PACKAGE SIZE: 16K
UNCOMPRESSED PACKAGE SIZE: 60K
PACKAGE LOCATION: compat32-tools-3.10-noarch-7alien.tgz
PACKAGE DESCRIPTION:
compat32-tools: compat32-tools (32bit compatibility tools for 64bit Slackware)
compat32-tools:
compat32-tools: The compat32-tools are a series of scripts that allow
compat32-tools: the user to add a 32bit compatibility layer (multilib)
compat32-tools: to 64bit Slackware.
compat32-tools:
compat32-tools:
compat32-tools:
compat32-tools:
compat32-tools: Written by Fred Emmott and Eric Hameleers
compat32-tools:
FILE LIST:
./
etc/
etc/profile.d/
etc/profile.d/32dev.csh
etc/profile.d/32dev.sh
install/
install/doinst.sh
install/slack-desc
usr/
usr/bin/
usr/bin/32/
usr/bin/32/gcc
usr/bin/32/gfortran
usr/doc/
usr/doc/compat32-tools-3.10/
usr/doc/compat32-tools-3.10/README
usr/doc/compat32-tools-3.10/compat32-tools.SlackBuild
usr/sbin/
usr/sbin/check-compat32
usr/sbin/convertpkg-compat32
usr/sbin/massconvert32.sh
I'm going to do my upgrade now and if it breaks then I guess I will have to eat my words.. but it seems like the only "problem" is Eric taking a break from maintaining his repo to enjoy the holiday season.
Last edited by Pithium; 12-20-2023 at 02:03 PM.
Reason: typo..
Yeah, I'm wondering if the 32-bit problem is just that mesa, vulkan, and/or llvm need to be brought in line with slackware64-current. It shouldn't be too hard to write a script to do a wget on those packages and run them from convertpkg-compat32. My brain has been hamsterwheeling on the problem (since I need some WINE things), and I've been considering switching to AMD, depending upon Christmas/birthday funds. I'm not seeing any issues in the arch forums, where I've been lurking, because they're also on mesa 23.3.1. (Seriously, their forums and wiki are quite good for information.)
Once this is all chained to (using some cron jobs and wrapper scripts) I get this..
Code:
# slackpkg search mesa
Looking for mesa in package list. Please wait... DONE
The list below shows all packages with name matching "mesa".
[upgr] compat32 : mesa-compat32-23.3.0-x86_64-1compat32 --> mesa-compat32-23.3.1-x86_64-1compat32
[upgr] slackware64 : mesa-23.3.0-x86_64-1 --> mesa-23.3.1-x86_64-1
[mask] multilib : mesa-compat32-23.2.1-x86_64-1compat32
You can search specific files using "slackpkg file-search file".
Based on the conclusions of this thread I won't be seeing any problems. For anyone who hasn't already looked you should take a gander at Alien Bob's entire collection of scripts and utilities. http://www.slackware.com/~alien/
Oh also, if you installed the ENTIRE multilib repo then you already have the compat32-tools package.
Code:
# cat /var/lib/pkgtools/packages/compat32-tools-3.10-noarch-7alien
PACKAGE NAME: compat32-tools-3.10-noarch-7alien
COMPRESSED PACKAGE SIZE: 16K
UNCOMPRESSED PACKAGE SIZE: 60K
PACKAGE LOCATION: compat32-tools-3.10-noarch-7alien.tgz
PACKAGE DESCRIPTION:
compat32-tools: compat32-tools (32bit compatibility tools for 64bit Slackware)
compat32-tools:
compat32-tools: The compat32-tools are a series of scripts that allow
compat32-tools: the user to add a 32bit compatibility layer (multilib)
compat32-tools: to 64bit Slackware.
compat32-tools:
compat32-tools:
compat32-tools:
compat32-tools:
compat32-tools: Written by Fred Emmott and Eric Hameleers
compat32-tools:
FILE LIST:
./
etc/
etc/profile.d/
etc/profile.d/32dev.csh
etc/profile.d/32dev.sh
install/
install/doinst.sh
install/slack-desc
usr/
usr/bin/
usr/bin/32/
usr/bin/32/gcc
usr/bin/32/gfortran
usr/doc/
usr/doc/compat32-tools-3.10/
usr/doc/compat32-tools-3.10/README
usr/doc/compat32-tools-3.10/compat32-tools.SlackBuild
usr/sbin/
usr/sbin/check-compat32
usr/sbin/convertpkg-compat32
usr/sbin/massconvert32.sh
I'm going to do my upgrade now and if it breaks then I guess I will have to eat my words.. but it seems like the only "problem" is Eric taking a break from maintaining his repo to enjoy the holiday season.
I had no idea
So you say
- mirror the repo
- massconvert
- install? (I'm blond and having mesa-compat32-23.2.1-x86_64-1compat32)
ad/Oh also, if you installed the ENTIRE multilib repo then you already have the compat32-tools package.
Specifically the part about Adding 32-bit programs. You can also download packages directly if you don't have slackpkg+ or don't remember how you installed multilib in the first place. The compat32-tools package is necessary if you want to be able to fix multilib problems so please make sure you have it.
If you run into problems, it would be helpful if you described the steps you took to initially install your multilib packages. They are not officially part of Slackware and things can break in very interesting ways.
As for my specific setup... If you are new, I suggest just focusing on understanding what is wrong with your compat32 packages and fixing that. alienbob provides tools and you can pull everything you need from his repo via the browser or wget or whatever.
The reason I get fancy by chaining several different tools together is to avoid this exact problem. I'm not paying alienbob anything so I try to minimize my reliance on his pre-built package repos by using the same scripts he uses to do it myself. And I don't need to go begging him to update his repo like some internet hobo.
Case in point.. I just ran a kernel upgrade and a bunch of kde packages in addition to my own repackaged compat32 libs and Steam launches Elden Ring as expected. The only packages I rely on from his repo are the glibc/gcc toolchain and the rest are masked out of existence.
Code:
bash-5.2# slackpkg search mesa
Looking for mesa in package list. Please wait... DONE
The list below shows all packages with name matching "mesa".
[inst] compat32 : mesa-compat32-23.3.1-x86_64-1compat32
[inst] slackware64 : mesa-23.3.1-x86_64-1
[mask] multilib : mesa-compat32-23.2.1-x86_64-1compat32
You can search specific files using "slackpkg file-search file".
bash-5.2# uname -a
Linux cesium.linuxgalaxy.org 6.6.7 #1 SMP PREEMPT_DYNAMIC Wed Dec 13 15:33:50 CST 2023 x86_64 AMD Ryzen 7 7800X3D 8-Core Processor AuthenticAMD GNU/Linux
bash-5.2#
Specifically the part about Adding 32-bit programs. You can also download packages directly if you don't have slackpkg+ or don't remember how you installed multilib in the first place. The compat32-tools package is necessary if you want to be able to fix multilib problems so please make sure you have it.
If you run into problems, it would be helpful if you described the steps you took to initially install your multilib packages. They are not officially part of Slackware and things can break in very interesting ways.
As for my specific setup... If you are new, I suggest just focusing on understanding what is wrong with your compat32 packages and fixing that. alienbob provides tools and you can pull everything you need from his repo via the browser or wget or whatever.
The reason I get fancy by chaining several different tools together is to avoid this exact problem. I'm not paying alienbob anything so I try to minimize my reliance on his pre-built package repos by using the same scripts he uses to do it myself. And I don't need to go begging him to update his repo like some internet hobo.
Case in point.. I just ran a kernel upgrade and a bunch of kde packages in addition to my own repackaged compat32 libs and Steam launches Elden Ring as expected. The only packages I rely on from his repo are the glibc/gcc toolchain and the rest are masked out of existence.
Code:
bash-5.2# slackpkg search mesa
Looking for mesa in package list. Please wait... DONE
The list below shows all packages with name matching "mesa".
[inst] compat32 : mesa-compat32-23.3.1-x86_64-1compat32
[inst] slackware64 : mesa-23.3.1-x86_64-1
[mask] multilib : mesa-compat32-23.2.1-x86_64-1compat32
You can search specific files using "slackpkg file-search file".
bash-5.2# uname -a
Linux cesium.linuxgalaxy.org 6.6.7 #1 SMP PREEMPT_DYNAMIC Wed Dec 13 15:33:50 CST 2023 x86_64 AMD Ryzen 7 7800X3D 8-Core Processor AuthenticAMD GNU/Linux
bash-5.2#
i use the same mesa-compat32-23.3.1-x86_64-1compat32, problem are not all steam games just 32 bit ones, yes Elden ring work for you and me but if i launch a 32 bit game it doesn' t work. Question what gpu do you have ? if you launch /usr/bin/32/vkcube does it work?
Yeah, I'm wondering if the 32-bit problem is just that mesa, vulkan, and/or llvm need to be brought in line with slackware64-current. It shouldn't be too hard to write a script to do a wget on those packages and run them from convertpkg-compat32. My brain has been hamsterwheeling on the problem (since I need some WINE things), and I've been considering switching to AMD, depending upon Christmas/birthday funds. I'm not seeing any issues in the arch forums, where I've been lurking, because they're also on mesa 23.3.1. (Seriously, their forums and wiki are quite good for information.)
Specifically the part about Adding 32-bit programs. You can also download packages directly if you don't have slackpkg+ or don't remember how you installed multilib in the first place. The compat32-tools package is necessary if you want to be able to fix multilib problems so please make sure you have it.
If you run into problems, it would be helpful if you described the steps you took to initially install your multilib packages. They are not officially part of Slackware and things can break in very interesting ways.
As for my specific setup... If you are new, I suggest just focusing on understanding what is wrong with your compat32 packages and fixing that. alienbob provides tools and you can pull everything you need from his repo via the browser or wget or whatever.
The reason I get fancy by chaining several different tools together is to avoid this exact problem. I'm not paying alienbob anything so I try to minimize my reliance on his pre-built package repos by using the same scripts he uses to do it myself. And I don't need to go begging him to update his repo like some internet hobo.
Case in point.. I just ran a kernel upgrade and a bunch of kde packages in addition to my own repackaged compat32 libs and Steam launches Elden Ring as expected. The only packages I rely on from his repo are the glibc/gcc toolchain and the rest are masked out of existence.
Code:
bash-5.2# slackpkg search mesa
Looking for mesa in package list. Please wait... DONE
The list below shows all packages with name matching "mesa".
[inst] compat32 : mesa-compat32-23.3.1-x86_64-1compat32
[inst] slackware64 : mesa-23.3.1-x86_64-1
[mask] multilib : mesa-compat32-23.2.1-x86_64-1compat32
You can search specific files using "slackpkg file-search file".
bash-5.2# uname -a
Linux cesium.linuxgalaxy.org 6.6.7 #1 SMP PREEMPT_DYNAMIC Wed Dec 13 15:33:50 CST 2023 x86_64 AMD Ryzen 7 7800X3D 8-Core Processor AuthenticAMD GNU/Linux
bash-5.2#
my prof always told us "if you don't get it, read it once more, and again... , till you get it".
Gonna try this approach. Coming from mathematics, should be able to get a hang of this.
Actually came to slackware very early (some 2000), but it would not work for my hardware at that time.
Now using it as a "internet hobo" for some 6 years in the --current edition and never encountered these problems.
Your approach is logical and refreshing, just need to find out how to adapt and replicate considering my setup.
i use the same mesa-compat32-23.3.1-x86_64-1compat32, problem are not all steam games just 32 bit ones, yes Elden ring work for you and me but if i launch a 32 bit game it doesn' t work. Question what gpu do you have ? if you launch /usr/bin/32/vkcube does it work?
vkcube works fine for me. I see a spinning cube on my AMD 7900 XT.
mesa is not an isolated package. There are several other packages that have to updated almost in lock-step with it. I don't remember all of them, but off the top of my head you have
mesa
llvm
libdrm
libX11
vulkan
....and what else?
If a 32bit program is failing while the equivalent 64bit version works, you have a problem with your compat32 packages. If it really was a bug or something specific to x86_32 then everyone would be dealing with it. This is not something you want to bug upstream about since most of us aren't seeing any issues.
I provided links to resources for dealing with this issue in previous posts here. Before bringing this issue to upstream developers make sure that the versions of ALL your compat32 packages match x86_64 version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'm not seeing any issues in the arch forums, where I've been lurking, because they're also on mesa 23.3.1. (Seriously, their forums and wiki are quite good for information.)
