Windows 10 and Slackware Dualboot (bootloader issues)
 

I am trying to dualboot Windows 10 with Slackware 14.1

Apparently, some on the Slackware IRC channel say it can be done, but they do not exactly know how or were just lucky (or don't know how to explain it). However, when I install on a desktop, the bootloader keeps failing. Can someone please document how s/he gets a dualboot successfully working? What bootloader configurations are needed? One claimed that a small change was needed on the Windows side, but cannot remember what it is. I went into expert mode and tried '-P ignore table', '-P fix table' among other things.

I am sure I am not the only one with this issue. Come on you Slackware Jedi's, sharesies!

Double boot with the dark side you must not. :jawa:

I erased Windows 8.1 and installed a normal MBR. I now have a lightning fast Slackware 14.2 Core i3 machine....

here are full instructions on your install medium in ftp://ftp.belnet.be/mirrors/ftp.slac...EADME_UEFI.TXT but that didn't work for me.

So I did it my way: http://fruttenboel.verhoeven272.nl/linux/lenog5080.html

I paid the tax and now the computer is mine.

If windows 10 is already installed just split the partician, install slackware and let lilo automatically install the boot loader. reboot and enjoy.

Works out of the box... So please include some more details about what fails for you...

I'm not using dualboot with Windows but think that it can be done by editing your lilo.conf. Maybe this thread can be helpful.

If you're using UEFI, disable Secure Boot, then just install normally and it will set up eLILO for you.

You should have at least the following partition layout:

/(root) - any journaled file system will work.
/boot - at least ext2. 100MB is fine.
/boot/efi - atypical 100MB FAT32(EF00) partition.
swap - 1.5x to 2x your RAM size up to 8 GB.

Let your Windows NTFS partition get automounted without an fstab entry.

If you can't get secure boot disabled, try this method:

http://www.linuxquestions.org/questi...ed-4175532990/

A /boot ext2 partition is generally useless, a swap partition is not always necessary depending on amount of RAM and usage (e.g. hibernation or not)

What is needed in all cases is:

• One partition type EFI (type ef00)
• One partition for / (type Linux)

But the first question is: can you disable Secure Boot?

I ask because if you can't disable Secure Boot you will have to provide a signed EFI image that Slackware doesn't ship, so some preparation is needed, see for instance The rEFInd Boot Manager: Managing Secure Boot by Roderick W. Smith.

As a reminder the Microsoft policy with OEM is :

• If the machine was upgraded to Windows 10 then Secure Boot may[1] be disabled.
• If the machine was shipped with Windows 10 preinstalled then disabling Secure Boot should not be allowed.

Also, if you have Windows 10 with Secure Boot disabled the Slackware64-14.1 installer can probably just re-use the existing EFI partition if there is enough room there thus you don't have to add one (but I couldn't try as I don't have such a configuration).

In any case I remind that only the 64-bit edition of Slackware version 14.1 can boot with an EFI firmware.

[1]But that it really can be disabled is up to the OEM IIRC. Not sure about that though.

...or so you think...

If you have a Lenovo, HP or Acer, the computer is yours, period. If you have another brand, which likes to walk on the leash of microsoft, you're gonna have a hard time. I chose for Lenovo or HP (I got a G50) and all traces of Windows have been eradicated and I am pretty sure MS will not bother me ever again.

If, on the other hand, you have a dual boot, windows may erase part of your system. It has access to the UEFI section so erasing the Linux entries is possible. It's just a matter of time until MS will start doing this.

The OP clearly stated "Windows 10 and Slackware Dualboot", so please stay on topic: that's his or her choice.

Didier: Doesn't Microsoft say that any PC should have an option to disable Secure boot and only ARMs should enforce secure boot?

I'll inject into this:

Windows 8 had the mandate of keeping Secure Boot optional on non-ARM.

Windows 10 has a mandate Secure Boot be mandatory on all PCs.

A few OEMs have made this switch, and a few have removed the UEFI Legacy BIOS option.

In March, there was a story that Microsoft would drop that OEM requirement for Windows 10: http://arstechnica.com/information-t...out-a-reality/

---------- Post added 18th Oct 2015 at 17:17 ----------

Source please.

Well, Lenovo has started to put rootkits into their BIOS (and has previously put Superfish preinstalled on Windows machines).

I have no reason to trust them more than other companies. They're all in the same business and Lenovo machines are certainly not "mine".