Was wanting to upgrade and saw this.

bash-4.2$ sudo slackpkg upgrade-all

Checking local integrity... DONE
You have a broken /var/log/packages - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:

fglrx-14.10.1006.1001-x86_64-1
fglrx-14.20-x86_64-1

You can (B)lacklist, (R)emove, or (I)gnore these packages.
Select your action (B/R/I):

What I had done originally was install the 64-bit beta driver along with the x86 driver. I installed both and everything works well enough, except for some lag in games on Steam. I wanted to upgrade and saw the above, not sure how to proceed and any information is appreciated.

Those are both 64 bit drivers. You may be able to leave both installed, but I would remove one of them if I were in that situation.
Regards,
Bill

Huh, well amd.com listed them as different architectures. Will uninstall one.

Actually you installed two versions of the x86-64 driver: one stable and one beta.Actually, when you installed the second one it just overrode the files wearing the same name from the already installed package so you don't really have the two packages installed. That's not clean and that's exactly what reports slackpkg.

What you should have done is either run upgradepkg on the second package or (in case upgradepkg failed because the two software don't' *seem* to be two versions of the same package because of differences in the packages' naming schemes), just run removepkg on the first then installpkg on the new.

Type R when asked by slackpkg to remove these packages, check that they are actually removed (output of "ls /var/log/packages/fglrx*" should be empty), if one remains remove it with removepkg, then use installpkg to install the beta version.

Oh, and don't use sudo for these commands, that's not needed on Slackware: become root with "su" instead.

TIP: to know which files were installed on your system typing "installpkg <package_name>" (in other words check the content of a package), just type "less /var/log/package/<package_name>" (q to quit).

Oh, and to actually understand how the Slackware tools work, you won't loose your time reading their respective manual page. You have man pages for explodepkg, installpkg, makepkg, pkgtool, removepkg, slackpkg, slackpkg.conf and upgradepkg, e.g. type "man slackpkg".

I've always used sudo, just wondering what is different than using su?

Typing "man su" and "man sudo" will tell you.

Now when I run steam I receive this

You are missing the following 32-bit libraries, and Steam may run:
libc.so.6
I looked around and read that it might have had something to to with glibc which I reinstalled. Not too sure what is going on.

Probably as this symlink is made when installing glibc or glic-solibs. Please show full output of PS This is to confirm my guess that you didn't install (or more probably removed) the 32 bit compatibility package for glibc or at least glibc-solibs, hence my question.

bash-4.2$ ls -1 /var/log/{packages,scripts}/glibc*
/var/log/packages/glibc-2.17-x86_64-7
/var/log/packages/glibc-i18n-2.17-x86_64-7
/var/log/packages/glibc-profile-2.17-x86_64-7
/var/log/packages/glibc-solibs-2.17-x86_64-7
/var/log/packages/glibc-zoneinfo-2013d-noarch-7
/var/log/scripts/glibc-2.17-x86_64-7
/var/log/scripts/glibc-solibs-2.17-x86_64-7
/var/log/scripts/glibc-zoneinfo-2013d-noarch-7

So yes you are missing the multilib packages for glibc*.

PS As you were able to run the Steam engine before, you probably mistakenly removed them.

Ah, so would that just mean to reinstall the lib32 compatability libraries?

Of course.

It worked. Strange, The lib32 folder exists on my desktop which I deleted at one point because I thought it wasn't needed after the packages had been installed, that might have had something to do with it.

No. But maybe, if you didn't remove these packages with either removepkg or slackpkg remove, maybe you typed slackpkg clean-system? If you typed that command these packages have been proposed for removal as they are not official Slackware packages (unless you have blacklisted them in file /etc/slackpkg/blacklist).

uhh, actually it was on the xfce desktop. I just right-clicked delete, heh.