Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just got a HP EliteBook 840 laptop, installed a 1Tbyte Seagate drive in it and loaded Slakeware64 14.2 on it. Loading the OS was entirely standard with no special cases or devices. During the install, I specified that it should use the LILO loader and put the boot info in the MBR.
However BIOS is not finding an OS on the disk and I am forced to use a boot USB to bring the system up. Can someone tell me what I am doing wrong? Thanks.
try booting from usb and run pkgtool then pick choose slackware installation scripts to run again.
when you initially setup lilo you picked a root partition example sda2 etc where the system is?
I tried pkgtool and basically it seems to imply I need to run lilo, which I did.
lilo -A /dev/sda ... told me no partitions were active
lilo -A /dev/sda 1 ... activated /dev/sda1
lilo -M /dev/sda mbr ...said it wrote a new record
But none of this made the BIOS see the OS, i.e., same problem. I am wondering if the problem is with a BIOS setting, maybe I am looking for the wrong thing?
Did you change the BIOS settings to Legacy? If not, it would have come with UEFI since Win10 came on the original drive.
Either set it to legacy, or set UEFI and disable secure boot. Your choice. Not sure what you may have to do if Slack was installed in UEFI mode, and now you switch to legacy boot.
How did you prepare and format the drive? Did you make it bootable?
No, I haven't figured out how to make it bootable. I used cfdisk to create a Linux filesystem partition and a swap partition. I seem to remember fdisk used to have a boot option but I looked for it and didn't find it.
Did you change the BIOS settings to Legacy? If not, it would have come with UEFI since Win10 came on the original drive.
Either set it to legacy, or set UEFI and disable secure boot. Your choice. Not sure what you may have to do if Slack was installed in UEFI mode, and now you switch to legacy boot.
Yes, Legacy. Still no help though, still have to use the USB boot stick.
Could you post some information? As root, run fdisk -l and post the output inside code tags. Please post your lilo.conf file, again in code tags. Possibly we can either confirm what is wrong, or we will know what you have is good.
in the bios is an option to have one or the other or both at the same time.
gpt cannot install anything on a MBR because gpt does not have a MBR.
I have found lately that I had to flag my partition as a boot partition to get a ssd to boot. whereas is was not always the case, why it changed I do not know, I just added the boot flag to the first partition I had/have a OS on and it worked. I do not use lilo, but grub though the same basics still apply.
as I installed Slackware with other OS's, so I skipped that part all together because I use the other OS grub to boot slack. nevertheless, I bet it is the lining up of the partition table you have on your hdd to the boot type in your BIOS and then the type of install of the OS all have to be the same to get it to work without having to use you stick to boot it.
so you might have to start over by creating your partition table as GPT for uefi or MSDOS(MBR) for Legacy booting, then go into your BIOS and make sure it is selected to do the same, uefi, or Legacy booting, then if it is UEFI you have to create a separate little 100 to 150MB boot partition for the files to go into it, and mark it as same for uefi using cfdisk and like software. Slack will see it, then install into it, though you still may have to go into that boot partition and change the name of a file still to get it to work properly, I do not use UEFI, I have only tired it just to see what that is all about, I have no real need to use UEFI due to > 2TB limitations on HDDs, I do not have any hdds with 2TB or greater installed on my laptop, So i use Legacy booting.
Just make sure everything lines up and you will have no problems installing and running Slackware on your HP EliteBook 840 gx. I am using a HP EliteBook 840 g2 and have no issues running Slack on it. I am in Slackware right now typing this to you.
ACTUALLY,
if I remember correctly, I had to put a uefi boot partition in , then add the /boot/efi directory after marking it for uefi, then still it installed into a separate EFI/ dir then I had to change that one grub file name to get it to work, then it worked without a hitch for uefi boot.
Could you post some information? As root, run fdisk -l and post the output inside code tags. Please post your lilo.conf file, again in code tags. Possibly we can either confirm what is wrong, or we will know what you have is good.
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda1
#compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends
in the bios is an option to have one or the other or both at the same time.
gpt cannot install anything on a MBR because gpt does not have a MBR.
I have found lately that I had to flag my partition as a boot partition to get a ssd to boot. whereas is was not always the case, why it changed I do not know, I just added the boot flag to the first partition I had/have a OS on and it worked. I do not use lilo, but grub though the same basics still apply.
as I installed Slackware with other OS's, so I skipped that part all together because I use the other OS grub to boot slack. nevertheless, I bet it is the lining up of the partition table you have on your hdd to the boot type in your BIOS and then the type of install of the OS all have to be the same to get it to work without having to use you stick to boot it.
so you might have to start over by creating your partition table as GPT for uefi or MSDOS(MBR) for Legacy booting, then go into your BIOS and make sure it is selected to do the same, uefi, or Legacy booting, then if it is UEFI you have to create a separate little 100 to 150MB boot partition for the files to go into it, and mark it as same for uefi using cfdisk and like software. Slack will see it, then install into it, though you still may have to go into that boot partition and change the name of a file still to get it to work properly, I do not use UEFI, I have only tired it just to see what that is all about, I have no real need to use UEFI due to > 2TB limitations on HDDs, I do not have any hdds with 2TB or greater installed on my laptop, So i use Legacy booting.
Just make sure everything lines up and you will have no problems installing and running Slackware on your HP EliteBook 840 gx. I am using a HP EliteBook 840 g2 and have no issues running Slack on it. I am in Slackware right now typing this to you.
ACTUALLY,
if I remember correctly, I had to put a uefi boot partition in , then add the /boot/efi directory after marking it for uefi, then still it installed into a separate EFI/ dir then I had to change that one grub file name to get it to work, then it worked without a hitch for uefi boot.
I chose GPT simply b/c it was first. Last time I did an istall it was 14.2 on a Dell desktop and it used GRUB but that option did not present itself during the setup. I do installs so rarely that I forget how between. If I am going to have to start over and reinstall, I want to know it now, before I add any more apps. I have BIOS set for UEFI but that doesn't work any better than Legacy.
One bright spot here: when I shut the system down, it remembers where I was so rebooting isn't the issue it would be on a desktop. I can boot up to the initial login prompt, close the lid and when I come back, still have that screen waiting for me.
Last edited by rdx; 02-04-2019 at 09:20 AM.
Reason: typos
As far as I know, boot= should point at the HD, not the partition.
Try changing boot = sda1 to boot = sda , save the change, run lilo, and try to boot again.
It didn't see to make any difference. HOWEVER: Something is different, I still need to have the USB stick plugged in, but the BIOS is booting from the HD and not running the boot stick.
When you run lilo, the mbr gets written to the device you booted from. Was the boot stick plugged in when you tried my suggestion? If yes, then the mbr went to the boot stick, not the HD.
You may have to boot from install media, and chroot into the HD install and run lilo with no boot stick plugged in.
No, I haven't figured out how to make it bootable. I used cfdisk to create a Linux filesystem partition and a swap partition. I seem to remember fdisk used to have a boot option but I looked for it and didn't find it.
cfdisk allows you to set the "bootable" flag.
Quote:
Originally Posted by rdx
I tried pkgtool and basically it seems to imply I need to run lilo, which I did.
lilo -A /dev/sda ... told me no partitions were active
lilo -A /dev/sda 1 ... activated /dev/sda1
lilo -M /dev/sda mbr ...said it wrote a new record
But none of this made the BIOS see the OS, i.e., same problem. I am wondering if the problem is with a BIOS setting, maybe I am looking for the wrong thing?
FWIW - lilo -A /dev/sda shows I have no acive partitions as well but my computer runs just fine.
I have found out the hard way that Legacy Boot + gpt didn't work for me. I had to go to the start and prepare my drive and re-install. I had nothing to loose since it was a fresh install
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
pkgtool not too helpful
