Just start coding. Why do you think you need multilib and slackpkg+ anyway? If you know you need them, then install them. I don't use them.

Because you blacklisted kernel, slackpkg did not upgrade the kernel. My guess is that your original problem with X was that you upgraded the kernel but did not update it for elilo. (Then your system ran the old kernel without its modules.) The preferred way is to install a new kernel in addition to the old one to make sure you have a working one. But I don't use elilo so I can't help you in that.

In that video he runs the script to enable multilib, but then goes into the file and adds multilib to the REPOPLUS setting. I don't do this and I honestly don't remember why not but maybe just run the script and then leave the config alone.

Okay, will do. Can I install slackpkg+ with out breaking xorg?

Sure, I do it all the time.
Just beware that slackware gives you all admin power, even to break it.

Learn how to upgrade your kernel with elilo (can't help you cause I use grub) at first.

Then be carefull when you use slackpkg+. It works very well with all the thinkpad I have (from t410 to t450).

I guess so. If my hypothesis is correct that the X problem was caused by an unsuccessful kernel upgrade.

I have never used slackpkg+, but if it obeys the same blacklist as the stock slackpkg, you won't upgrade the kernel.

If the X problem was caused by something else, something you installed using slackpkg+, then you will hit it again when you install that something.

There is a lot going on here.

You need a starting point.

It is this a full installation?
What have you installed that is not part of slackware; i.e., slackpkg+, multilib, what else?

As Perti pointed out by blacklisting the kernel, slackpkg with or without slackpkg+ will not be able to update them.

I use slackpkg and slackpkg with slackpkg+ and I fail to see how these will affect startx at all.

Maybe start back to the basics. Slackware (full installation), no other packages and start there.

multilib and slackpkg+ almost certainly had nothing to do with it. You just didn't have a working video driver so it was trying to fall back to 'vesa' but that driver just doesn't work from an EFI environment because it's a completely different type of BIOS. I _think_ 'efifb' is sort of the EFI equivalent of the vesa driver, but you don't really want either and intl 520 has been supported for yonks.

The kernel boot log (dmesg) might have some information about what failed but it's usually pretty terse and might not help a lot. I suspect some module was missing or the kernel was otherwise somehow broken. I've had the same problem before and it's always been due to a misconfigured kernel or incorrect kernel arguments, I always build my own cut-down kernel from kernel.org and occasionally mess it up.

You don't need multilib for development anyway unless you're trying to run and/or cross compile 32-bit binaries. And even then there are alternatives like installing a 32-bit os in a separate VM instance (using qemu or virtualbox), or using something like conty[1]. For what it's worth I found using slackpkg+ and keeping multilib working a huge PITA and ditched both a couple of years ago, but i'm also no longer developing any 32-bit code either.

[1] https://github.com/Kron4ek/Conty

Okay. So I can install multilib and slackpkg+ and not experience what equates to the destruction of my OS?

For sure. Many of us do/did it.
You're advise to test at each step to find the reason you have your setup unusable (if no mistake,which is common even for experienced users).

As previous people has points out, unless you have specific need to run 32-bit program or develop 32-bit program, there is no advantage to have multi lib installed at all. I have been using pure 64-bit Slackware since Slackware64-13.0 (without needing the multilib for all my development work).

Take a look of https://www.linuxquestions.org/quest...es-4175707921/, if you really need multilib, follow the instruction by alienbob himself.

Okay and this won't break my system. So addressing the kernel versions prior fixed the issue so I can label this question SOLVED correct?

What is the point of the 32 bit slackware then? Does any one use it? What kind of a man is a 32-bit Slackware man? What kind of things does he like to do? Does he like to work on his car; when he gets to working on his car does he forget what time it is or to eat? He never forgets to smoke though... Does he always smoke when he gets to working on his car and does smoking and working go together? What does he smoke -- say it is Marlboro! What about Marlboro does he like? Well when he pulls on a cigarette he wants to taste something, with Marlboro he can. Plus Marlboro has the flip top box, this flip top box is interesting and practical further more would he suggest Slackware 32-bit to a friend or did he already suggest such?

It's for those old machines that don't support x86_64. If they still work.

Multilib is to run 32bit programs on a 64 bit installation of Slackware, such as Steam.