Hi,

I have a notebook with 2 disks,
the second one is Slackware, the first whatever I need for my current project

Now I need windows10 on the first disk for some time.

until now, Slackware was booted via GRUB of the Linux installation on the first disk

but now I need to install windows10 on the first disk, so before I do this

any hints tips and/or tricks for me that my Slackware stays bootable
its an EFI system with a EFI partition on disk 2, the Slackware disk

thanks!

Hi,

Before you start this endeavor I suggest that you reference; https://docs.slackware.com/start Loads of information and links to help your Slackware installation go a little easier.
Hope this helps.
Have fun & enjoy!

onebuck, thanks, but, ... did you read my post? obliviously not because than you would understand that my Slackware is already installed and I asked something different

Hi,

Yes, I read the OP and if you need to install W/10 then reading the doc will help to show the need for configuration. Remove or disconnect the current Slackware HD then install/restore W10 on it's HD and follow the instructions for adding Slackware to the Windows boot loader.

Microsoft has never liked the idea of installing second fiddle. Your install will require you to include information for the Slackware HD within the Win/10 boot loader structure. You want to have the boot loader on the win/10 HD then add the EFI for Slackware as indicated within the referenced doc.
Hope this helps.
Have fun & enjoy!

thanks,
I can not find the thing about how to add hd2 to the windows boot loader in the referenced docs
this is slightly different https://docs.slackware.com/slackbook:booting

the other think is, I can not disconnect disk2, its m2 and I can not access it (without disassembling the whole notebook what I am not allowed to do). hope this will not be a problem

just running the installation, could not wait. lets see whats happen, I mean, what can go wrong ?
hope I will still have the Slackware installation later this evening

I'm a firm believer in rEFInd.
https://slackbuilds.org/repository/1...?search=refind

Why don't you just set the boot priority to boot the second disk and use lilo or grub to chainload the Windows bootloader? I also know you can use the Windows bootloader to boot Slackware. This post on Alien Bob's blog might shed some light on the latter.

thanks, will give it a try


because I am super unskilled with installing and running Windows.
last time I had to use it I had a dedicated Notebook and the only thing I did was booting it from time to time to see that some code I have written compiles with MSVC (which is also about the only use case I have now)
but I will think about this solution and maybe give it a try, this seems to be simple

1 members found this post helpful.

a4z sometimes Windows 10 loves to install its bootloader over whatever you are using. Its important to always have a Windows 10 media install disc to have access to a command prompt to fix the Windows boot when it messes up with something like this: https://superuser.com/questions/7008...s-8-efi-system

Bios should allow you to switch to rEFInd after Windows pulls a stunt and installs over it (rarely happens).

rEFInd requires installation after installing the Slackbuild. There is a script refind-install at /usr/share/refind*. I use eliloconfig and it copies the required files from boot to the Slackware folder in the efi partition. efibootmgr order has to be changed to rEFInd after each kernel update.

This is all I know. I hope its of some help

So, what happened?

I am presuming Windows would have installed an EFI partition on the first disk with its bootloader there, and it would probably also have put its bootloader first in the priority boot list.

With UEFI it is quite simple to run several bootloaders. Since GRUB for Slackware was effectively running on the system, it will already be registered in the UEFI firmware settings (the new BIOS). So, all you have to do is change the order in the BIOS itself. The worst case will be where Windows would have completely removed your bootloader from the list, then you just have to boot a live CD/USB, install GRUB back on the proper EFI partition and register it.

You can also check rEFInd and this small HowTo: https://docs.slackware.com/howtos:sl...d_on_slackware. This article also explains a couple of things about chrooting and installing GRUB on UEFI systems.

1 members found this post helpful.

You can avoid this by answering "No" when eliloconfig asks to install a Boot Menu entry.

1 members found this post helpful.

Windows is installed, Slackware is still there but I can not boot it
there is a Slackware in the boot menu list but when I boot it it says there is no sdbX , what is the location for the initrd
maybe I need to get the UUID of the disks and write this somewhere ...

so currently I do not know how to come to elilo of the Slackware boot loader.

@a4z,
if you using UEFI, copy vmlinuz (and if it is -generic- kernel, initrd.gz) from /boot to ESP on first disk, copy elilo.efi and elilo.conf to ESP on first disk.
Use efibootmgr or machine firmware to add Slackware boot option to boot elilo.efi.

Is this kernel panic or somthing else?

no kernel panic, it just says that there is no sdbX and gives me a shell with the hint that I can fix the stuff.

the problem with some of the tips here is, they assume I already in Linux, but I am not :-) :-(
need to see how this thing looks from MS, if I can copy there something to a partition windows does not even show me

how good that I have no stress with this, but, it is astonishing how complicated our experts that define standards made it to be able to boot multipe OSes from one computer, whoever designed, published and/or signed UEFI should be punished, seriously!