Tuxedo
2018-09-07 08:31:18 UTC
Hello,
Within Slackware's setup and right after the slackware install procedure
from USB to HD was completed, the option to MAKE USB FLASH BOOT step was
returned and done.
Now the system is installed on the HD, and booting from LILO via MBR and
/boot sector works, but when testing the Flash USB, the system does not boot
from for some reason. The Flash boot begins and stops or simply hangs midway
with some non-descriptive messages, maybe because the USB was created before
the subsequent mkinitrd procedure of the Slackware HD installation?
Booting from USB will be needed next to reinstall LILO after having
installed Windows on another partition, as of course the Windows installer
will then overwrite the MBR.
Having completed the Slackware installation, can the same Flash USB creation
utility that is available via the setup program on a Slackware installation
USB be launched from within the now ready installed Slackware on the HD? If
so, what is the command?
Or is it necessary to start the setup program via the Slackware install USB
and re-run CONFIGURE, discarding various other steps until reaching the USB
Flash creation step again?
Currently, elilo.conf on the Flash USB appears as follows:
chooser=simple
message=message.txt
delay=300
timeout=300
#
image=/vmlinuz
label=huge.s
read-only
append="root=/dev/cryptvg/root vga=normal ro"
While the current and working /etc/lilo.conf on the installed Slackware
appears as follows:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/nvme0n1
#compact # faster, but won't work on all systems.
# Append any additional kernel parameters:
append=" "
prompt
timeout = 50
vga = normal
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.14.67
initrd = /boot/initrd.gz
root = /dev/cryptvg/root
label = Linux
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
Many thanks for any ideas!
Tuxedo
Within Slackware's setup and right after the slackware install procedure
from USB to HD was completed, the option to MAKE USB FLASH BOOT step was
returned and done.
Now the system is installed on the HD, and booting from LILO via MBR and
/boot sector works, but when testing the Flash USB, the system does not boot
from for some reason. The Flash boot begins and stops or simply hangs midway
with some non-descriptive messages, maybe because the USB was created before
the subsequent mkinitrd procedure of the Slackware HD installation?
Booting from USB will be needed next to reinstall LILO after having
installed Windows on another partition, as of course the Windows installer
will then overwrite the MBR.
Having completed the Slackware installation, can the same Flash USB creation
utility that is available via the setup program on a Slackware installation
USB be launched from within the now ready installed Slackware on the HD? If
so, what is the command?
Or is it necessary to start the setup program via the Slackware install USB
and re-run CONFIGURE, discarding various other steps until reaching the USB
Flash creation step again?
Currently, elilo.conf on the Flash USB appears as follows:
chooser=simple
message=message.txt
delay=300
timeout=300
#
image=/vmlinuz
label=huge.s
read-only
append="root=/dev/cryptvg/root vga=normal ro"
While the current and working /etc/lilo.conf on the installed Slackware
appears as follows:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/nvme0n1
#compact # faster, but won't work on all systems.
# Append any additional kernel parameters:
append=" "
prompt
timeout = 50
vga = normal
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.14.67
initrd = /boot/initrd.gz
root = /dev/cryptvg/root
label = Linux
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
Many thanks for any ideas!
Tuxedo