SlackwareThis Forum is for the discussion of Slackware Linux.
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.
before you installed slackware you had win-10 and MX dual booting just fine with MX's grub boot loader???, what i would do is install slackware, then just ignore slackware's boot loader and add slackware to MX's grub bootloader, with kernel-huge it wont be a problem but if you want to use kernel-generic your slackware install will need an initrd built, check the README file in slackware's /boot
if you need to reinstall both MX and slackware, then install slackware before MX and then MX's installer should find both Win10 and slackware and add it to MX's boot loader,
(this just an educated guess based on my previous experiences)
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 931
Rep:
I don't know about elilo and UEFI, but lilo can boot Windows 10.
I have dual boot Slackware/Win10, but my setup probably is different than yours.
Slackware is installed in the first disk (sda) and Lilo is installed at the MBR of that disk.
Win10 is on second disk (sdb), so the Win10 MBR record stays untouched.
I think you can set any disk as first boot device in BIOS currently.
I currently have a UEFI machine running in Legacy mode that houses 5 operating systems. I boot all systems from my Main, Slackware 14.2, which has LILO installed to MBR but all the others have their bootloaders installed to Root so I have excellent redundancy, easy, guaranteed recovery. I still have Win 7 but haven't booted it in ages but for it I just change boot order since Win7 is on a different disk from Main. I only use Grub when I'm forced to. With LILO it is possible to boot other systems with the "Other=/dev/sdfoo2" type entry or by copying the boot files to my main /boot directory. Each has it's own descriptive name so there is no conflict. I can choose to boot Win 7 from LILO but I prefer to just F11 > Boot Order.
Try rEFInd if you have UEFI https://slackbuilds.org/repository/1...?search=refind
You have to go to its directory to install it on your EFI partition after running the slackbuild. It picks up everything automatically that is bootable on EFI.
It is not at all clear to me whether or not OP is using UEFI or Legacy, since he did mention LILO, not eLILO. That information should probably come first.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.