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 ordered an inspiron 5680 i7 geforce 1060 and reading about win 10 security problems is freaking me out. So i think i will be spending more time in slackware, i have been away for a while entranced by windows games
I was thinking of taking the drive from my current computer, with lilo installed on the MBR and intalling it in the new inspiron, switching the inspiron to legacy boot and specifying the lilo drive as the boot drive.
Will this work?
Any thoughts on how the original drive in the inspiron would be specified in lilo.conf? /dev/sda2? There is an ssd in the new computer and idk how those are specified?
It should boot, but the details will probably be wrong. You will have drivers for the old PC, not the new. Reinstall and/or rebuild the kernel and you should be a lot further along the road.
There are basically endless size limits with the MBR format but it's one way of eliminating EFI. I share your thoughts about UEFI, MBR, Lilo although I realise I may be dragged kicking and screaming into the 21st century at some future point. I share your thoughts about windows 10. I have it confined to a VM. It doesn't even have my name. It boots (very occasionally) and says " Hello Tight Ass!":-).
If you don't want to use Windows, it would be much more efficient to just wipe it out and install Slackware anew, after having disabled Secure boot in the firmware's menu if need be.
You will most probably get better performances using the SSD of the new machine than your old drive.
If you want to use Windows 10 on occasion, see how to make an ISO of it that you could use to install it in a virtual machine. Or if you have plenty of room on this SSD, just resize main Windows partition to the minimum allowed (do it from Windows) and install Slackware in the emptied space. This works too.
Any thoughts on how the original drive in the inspiron would be specified in lilo.conf? /dev/sda2? There is an ssd in the new computer and idk how those are specified?
Looks like the Inspiron 5680 SSD is NVMe so it should show up as /dev/mnve0. The original drive should show up as /dev/sda. I'm guessing that Windows will be installed on the SSD. The Slackware 14.2 installer will not install to NVMe drives, however I do believe that the latest release of Slint does. You should be able to do a fresh install of Slackware in UEFI mode on the orginal drive and dual boot with window. Finally most UEFI firmware has what is called Compatibility Mode (CMS) which will allow you to be able to boot Windows in UEFI mode and Slackware in legacy mode. In any case you will need to disable secure boot.
Looks like the Inspiron 5680 SSD is NVMe so it should show up as /dev/mnve0. The original drive should show up as /dev/sda. I'm guessing that Windows will be installed on the SSD. The Slackware 14.2 installer will not install to NVMe drives, however I do believe that the latest release of Slint does. You should be able to do a fresh install of Slackware in UEFI mode on the orginal drive and dual boot with window. Finally most UEFI firmware has what is called Compatibility Mode (CMS) which will allow you to be able to boot Windows in UEFI mode and Slackware in legacy mode. In any case you will need to disable secure boot.
There's an option in the latest Slackware (14.2 at the time of this post) to use elilo, which is an [U]EFI-enabled Lilo. I use it on my desktop, and it works just as one would expect.
There's an option in the latest Slackware (14.2 at the time of this post) to use elilo, which is an [U]EFI-enabled Lilo. I use it on my desktop, and it works just as one would expect.
What i would like ideally is to have my Slackware-current install available by just plugging the the drive to the new computer and changing the boot drive in the bios.
From what i have read, elilo sounds a good alternative to grub, which seems (and i admit i have only a glimmer of understanding of it) needlessly complex compared to lilo.
Is it possible to switch to elilo prior to installing my current slackware drive in the new computer or will elilo only work on computers with efi or uefi?
What i would like ideally is to have my Slackware-current install available by just plugging the the drive to the new computer and changing the boot drive in the bios.
Try this:
Make sure you have installed elilo in the EFI system partition of the drive in the old computer.
Choose "Build and install the multiboot menu on your computer" then accept to install it in the BOOT directory (this is necessary).
Then you can customize the label if you want.
After that you can also make a rescue USB stick if you want.
Then you should be able to boot this drive on both computers. However I don't know if their respective hardware are fully compatible, but that would be another topic.
Please tell me how that goes, as this is a use case for EFI3M that I didn't consider at first.
PS EFI3M is supposed to be a multi-boot menu, but of course works also for only one system to boot. However, if you have several systems on the new computer, run it from there to get an entry for each in the boot menu.
Last edited by Didier Spaier; 07-01-2018 at 05:39 AM.
Choose "Build and install the multiboot menu on your computer" then accept to install it in the BOOT directory (this is necessary).
Then you can customize the label if you want.
After that you can also make a rescue USB stick if you want.
Then you should be able to boot this drive on both computers. However I don't know if their respective hardware are fully compatible, but that would be another topic.
Please tell me how that goes, as this is a use case for EFI3M that I didn't consider at first.
PS EFI3M is supposed to be a multi-boot menu, but of course works also for only one system to boot. However, if you have several systems on the new computer, run it from there to get an entry for each in the boot menu.
Thanks man, i will let you know how it goes when the new on arrives next week.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.