I have a Toshiba Satellite C55 laptop into which I installed slackware 15.
It will not boot.

I followed
https://docs.slackware.com/howtos:sl..._first_install

and immediately hit a wall.

[code]
bash-5.1# chroot /mnt
chroot: failed to run command ‘/bin/bash’: No such file or directory
bash-5.1#

Here is my boot directory


Any pointers please

Did you install and configure elilo?

Did you install grub?

Have you copied a kernel to /boot/efi/EFI/Slackware ?

If you copied the generic kernel, did you copy the initrd.gz file to the above mentioned directory?

All I did was as detailed in my 1st message

I assumed it would all be done like back in the day when lilo was king.

I will address the points you raised

Making this statement is not helpful. This help file has options, ypou need to telll us exactly what track you took. There are 2 paths, one for mbr drives with BIOS and a different one for GTP and UEFI. Which apth did you take?

This indicates you have not mounted any directorys on /mnt. This only applies to chroot command on a mbr system. If this is a UEFI and GPT setup, I don't see any mnt commands to do.

The link you posted is during slackware installation configuration, before rebooting the first time. There is one of two ways to fix from the slackware installer.
1. Manually mount the partitions, mount —bind /dev /proc /sys /run to the same directories on the mounted root partition. Chroot then run grub-install or eliloconfig

Or

2. Start setup select partitions in target but do not format, skip software installation and go straight to configuration. Skip the items you don’t want to reconfigure. Before exiting out configuration open a second terminal, chroot /mnt and run grub-install. A formatted fat32 efi partition mounted on/boot/efi is needed for efi mode

Is that not what this is?

No. This is a listing of fstab. After the kernel gets control, these partitions will be mounted. Without a bootloader installed and configured, this fstab is not used.

chroot is used to mount to fix non-bootable systems. You have to boot from a different medium, in this case the install medium. Have a look at post #5.

The default boot loader is elilo for a UEFI system. The help file you pointed out is to install GRUB2 during install. Grub2 comes with slackware and one way is to follow the instructions in that help file. That will install grub2.

How did you get that listing? Was it from a command prompt while the installer was in control?

After I installed Slackware 15 I rebooted but no boot device was available. I then rebooted from the install DVD and gained access that way using one of the kernel options

Armed with the above I've now migrated to this:

https://docs.slackware.com/howtos:sl...uefi_and_elilo

It ain't easy!!

If these files are essential for an install why on earth are they not installed during the Slackware install process?
It seems impossibly complicated to me for something that lilo did in a minute or less.

Hmmm. Let me give you a listing of what a working /boot/efi/EFI/Slackware/ directory has to contain. Here is one from my laptop.

This is from a current install. You are using 15.0. That is recommended for any new user to Slackware. You can see I copied both generic and huge kernls to this directory. I generated an initrd using the command generator at /usr/share/mkinitrd/mkinitrd_command_generator.sh. This .sh file creates a list of a command to create a working initrd.gz file. This is stored in /boot. I copied it along with the kernels I want to use.

You also edit the elilo.conf file. Here is mine.

This file is read by the boot loader, elilo.efi. This file is also in the /boot directory. If you look in /boot, the file is called elilo-x86_64.efi. On the cp command, you rename it to elilo.efi.

This may seem cumbersome, there are some scripts the install instructions tell you to run. They do simplify it, I choose not to use them, and prefer the names of the kernel to be there as they are in the boot directroy. Either can work.

You should read through the install instructions if you prefer to use the scripts.

The installer has no idea if you are installing a 32 bit or 64 bit system. Different things are done for the bitness to be correct. In boot you will see this file elilo-ia32.efi for 32 bit systems. It is not used on 64 bit systems. Lots of possibilities, one installer.

The directory boot/efi stops there
Do I add the other sub directories .../EFI/Slackware

Use mkdir and add them. I think one of the scripts creates them.

No, don't add the sub-directories.
Are you selecting one of the first two entries or are you selecting the "detect/boot any installed operating system"?

I would detect any operating system but it never selected one so I just selected the huge kernel manually