Yes, but still have to figure what drive slackware is on to get the correct uuids. With only one drive installed during installation the slackware drive is sda. With the other drives installed the slackware drive could be sdb, sdc, or sdd.

edit: nevermind I see what your doing, disconnecting the other drives, to make it easier to get the uuid of the slackware drive/partition

@quickbreakfast It is better to use 64bit distros on a uefi system.

@colorpurple21859

Using UUIDS is also part of the plan, but my biggest concern was the confusion around what the OP was actually booting and the focus on fixing Slackware first.

OK, I think we can post the original problem (Slackware restarting) as solved, because somehow you had configured a 32 bit system to load a 64bit one; That will lead to confusion at some point, probably when Devuian loads the 64bit slackware kernel and starts reading it as 32bit. Get Devuan out of circulation for the moment. You're going to have problems there, afaict. Best tuck Devuan inside a VM if you want a 32 bit system, or reinstall a 64bit one. Devuan seems to be the joker in the pack.

As for the Disks, why not mount them all, & read the o/p of From memory, or /etc/mtab, you can tell where each is mounted. the /dev/disk/by-uuid also tells you the sda-sdc bit. You should be able to sort yourself out.

Stick to 64bit or 32bit systems all round. I don't know why anyone still wants x86 32bit, except to run M$windoze code under wine, or mebbe Adobe trash which won't compile for them on 64bit. Multilib and Alien's wine package on Slackware is an elegant way out of that. I'm surprised anyone offers and supports a 32bit distro in X86; maybe it's just habit. There are some systems that never made 64bit (e.g. 68k, and some fpga cores given away by competing chip manufacturers)

1 members found this post helpful.

I took the iso linked in post #34.

Once it finished downloading I checked.The md5sum was correct.

Then I disconnected all the other drives, so that the machine either booted from the usb/iso or the Slackware drive.

The machine still looped through the boot sequence. And I became a little down hearted

Not that I can now remember.

Considering that I've added two partitions using UUIID's to the Devuan partition, modifying config files should present no problems....... providing I know which files to modify.

But I'll worry about that after Salckware boots.

Late last night I added nomodeset to lilo, so the line in lilo now looks like Now the machine goes throught the boot sequence to where it used to reboot, pauses for a second then boots Devuan, not Slackware.

Which has me thinking that lilo should not beas it currently is, but should be

or something close?

sda1 is a uefi partition that the machine requires.

Remove your other drives and see if slackware boots with the nomodeset option. Do not change your lilo config leave it /boot/vmlinuz with the nomodset option
Once booted into slackware run blkid to get the uuid of the slackware drive partitions. Edit the slack fstab and lilo.conf to use uuids as per the examples in the last link of post #45. Rerun lilo. Reboot and make sure slackware boots. If it boots then reinstall your other drives and see if slackware still boots

Do you mean PARTUUID for lilo.conf?
As I remember, you need initrd to use UUIDs here, but PARTUUIDs is ok in every case (without and with initrd).

your right it needs to be partuuid.

quickbreakfast, did you ever get it figured out?

Sorry for the slow reply.

For a couple of weeks higher priorities got in my way.

No, I have not got it worked out.

Went back to attempting to trying to install Slackware over he recent weekend, but no joy.

Thought if I could get it to boot through Puppy I could update lilo and away we'd go.

Alas Puppy (using UUID's) told me that the root Slackware partition did not exit, while fdisk -l told me that the Slackware HDD didn't start at a physical boundary.

The end result is that for reasons I can not understand my computer is allergic to Slackware. As such I've elected to walk away.

Thanks to everyone who attempted to solve my install problem and I apologise for being such a pain.

Sorry to hear that you gave up and hope you'll still reconsider Slackware in the future. It wasn't a pain, but a rather interesting experience and I wish we could have communicated a little bit better, understand your setup and help you get Slackware booted along with your other distros.

Understand totally about other commitments. The disk not actually existing is your probable cause for slackware not operating, because after it boots the kernel, your system mounts the root drive and runs /sbin/init to complete the process. If you think slackware installed, you probably still have issues on the hd unless you tidied them up installing Puppy. Not starting at a physical boundary is a nicety only hdd formatting programs notice.

Slackware does rely a bit on user experience. I didn't start on it, but promoted myself to it after getting thoroughly sick of the issues with others.

During Easter I got a new copy of the Slackware iso and it has installed.

With the reboot usb the machine kept rebooting when I suggested it look for the root partition with

But when I used

there was not the problem. The machine is nicely running Slackware.

Thanks to everyone who took the trouble to read and/or respond to my request for help.