Hey. I'm looking to try out Garuda, and I just wanted to ask if I'll be fine if I just used a separate drive for the installation, cause I still need windows 10 for some things (unfortunately).
I've seen people saying dual booting is a problem cause the windows boot manager can override GRUB, is it still a problem if I use a separate drive? It shouldn't be right? Or am I wrong?
I used two ssd and have Windows on one and Linux on the other, set up was separate boot from either drive. Also had it from one drive to boot either, separate boot is usually my go to.
Read the pros and cons of both.
Welcome to the forums!
Honestly, I've never had issues with dual booting for years. I know people report windows messing up their GRUB but overwriting the boot partitions.. but, i've never seen this behavior. If you do a dual boot, you can avoid this by installing GRUB onto the other drive so that there is a complete separation from the windows installation, as well.. One thing is to make sure you disable fast boot and secure boot to avoid issues with installation and running both.
Drive 1 - windows boot and installation
Drive 2 - grub and linux installation
You can also utilize refind to avoid maintaining grub entries.
You may consider moving Win10 to a virtual machine so you are less likely to hit issues. Also if your motherboard has some specific features, you can pass GPU to VM and enjoy native performance while gaming. Well, except the ones with very intrusive anticheats which may get you banned just because you used a VM
There's the rub.
The number of problems users experience is usually a reflection upon their experience level. Users with many years of Linux use under their belt usually know how to setup, maintain, and fix their boot issues that may arise.
Unfortunately, our average new user is fresh off the Windows boat, and they don't have a clue about repairing grub, or repairing anything in Linux for that matter. The reason why we don't recommend dual booting is that for most users unfamiliar with Linux and dual booting, it is usually a disaster just waiting to happen.
No matter how many times we state that we don't support dual booting it still doesn't stop most people who mess their boot up from posting on the forum looking for others to help fix the mess they created by dual booting.
My comment on this behaviour would be, if you think you are experienced enough to manage multi-booting, then be mature enough to also fix your resultant breakages. Do not come crying to our forum for support with Windows created issues. We have enough Linux support issues to deal with, without having to deal with issues created by users unable to sever the umbilical cord from Windows.
You've been warned, you break it, you fix it, if you insist on running Linux and Windows together.
Many of the things that go wrong with dual booting with Windows were related to old-style MBR systems. It is less certain to mess up with an UEFI setup.
That said, the EFI partition created by Windows is quite small, which can cause OTHER problems too.
By far the least troublesome is keeping the systems on separate drives, each of which is complete in itself. The booting choice can then be done by BIOS selection of boot drive, or by later research on adding entries to grub, or by using rEFInd to choose on boot up.
There is LOTS of information out there for doing this, some of it even up-to-date and accurate. Good luck!
Yes there is, so if the user is competent and ready for all the possible ramifications, why are they asking here. Generally, my answer is always the same the when it comes running multiple OS's and DE's, if you have to ask, you in all likelihood aren't competent enough to attempt this.
I was hoping it was enough of a hint as what to try - without trying to step by step it! Even if doing a thing is unsupported, can we not say 'look here' for 'this style' ?
Ah well - chewing up a system is such fun anyway
I agree trying new stuff is fun, and breaking your system is how we all learn. However, the problem is most users never do their research, break their system, then dump it on the forum to fix for them.
When a user starts asking about information about dual booting that sets off alarm bells with me, because if they were self-motivated they would not need to ask for details in the first place, (they would do their own research). To me, if you can't do your own basic research, you're certainly not capable of correcting complex boot issues that can arise from multi-booting.
That is why I tend to preach on this subject. We don't support dual booting for a reason, and that is because our average user isn't capable of resolving their boot issues on their own and it's not our responsibility. If they're not even capable of doing the research to discover all the facets of dual booting, how could they possibly manage repairing a melt down on their own.
Imagine this equivalent scenario:
You buy a new vehicle that has an internal combustion engine. You call the car dealership where you purchased your vehicle and ask them for info on how you can convert your vehicle to a hybrid on your own. After they finished laughing, they would advise you not to not alter your stock vehicle setup or you would void the warranty.
You of course know better, so you start wrenching on your engine attempting to install a secondary power system. In no time flat your vehicle will no longer start after your alterations.
You then call your car dealership's service center to make an appointment to have them repair your vehicle under warranty. After explaining why your vehicle won't start, the service center hangs up on you.
Sound familiar, case closed.