I’m looking to finally use Linux properly and I’m planning to dual boot my laptop. There’s enough storage to go around, and while I’m comfortable messing around I’d rather not have to run and buy a new device before school while fixing my current one.
https://m.youtube.com/watch?v=VaIgbTOvAd0
This was the general guide I was planning to follow, just with KDE Plasma (or another KDE). I was going to keep windows the default, and boot into Linux as needed when I had time to learn and practice.
I assume it should be the near similar process for KDE Plasma?
I’m ok with things going wrong with the Linux install, but I’d like to keep the Windows install as safe as possible.
You must log in or # to comment.
Always install Windows first then Linux in dualboot, otherwise microsoft messes with your boot area. Have a separate boot partition for Linux and some distros have foreign OS probe and will auto setup your grub menu to chainload to windows. This stops Windiws messing with your Linux boot partition since it has no clue it exists
If your laptop has room for a second drive, it’s easiest to put Linux on its own drive.
Unfortunately there’s just the one slot. I’m going to keep that in mind for future purchases
So then if the drive is big enough, use the shitty windows partition manager and shrink the windows partition, leaving as much space as you want for Linux.
Also you can try Linux on a Live ISO or even install it on a USB stick, but with UEFI thats a pain.
Ventoy on a fast usb stick or better a nvme case (cheap one + 256Gb is easily sub $100 and who can’t use screaming fast external storage) via a usb3+ port is pretty godlike and really convenient.
But ventoy is not persistent right?
The specific ISO/distros can be (relatively) easily made persistent if they’re built with that in mind, there’s a list of choices in that link. I have a custom Arch ISO on mine that was a doddle to enable persitence on…
Thanks! Interesting!
This is good advice, I recently first tried a Linux install on a partition of a large HDD just to tinker, then pretty much immediately bought a secondary SSD and re-did all the setup there.
I’m already a convert btw! My windows partition hasn’t been fired up in weeks now.
Windows and Linux keeps track of time differently. One stores the time in your current time zone. The other stores the GMT time and adds an offset. I forget which one does what but it results in your time being wrong each time you switch from Linux to Windows or vice versa. You can search for how to fix it, its not very hard, or you can just ignore it and reset your clock each time you switch OS.
I don’t think that’s the case anymore.
I just checked, the time in the UEFI BIOS is in UTC, yet both Linux and Windows 10 display the local time correctly as an offset to UTC. I didn’t have to do anything special for that.
Edit:
So I looked a bit deeper into it, and this is apparently controlled by a registry key called
RealTimeIsUniversalin[]. You can paste the text below in a .reg file and then import it to set the parameter:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001I confirmed that this setting exists on my system, but I have no memory of ever manually setting this parameter. It’s documented in the Arch wiki though, so it’s possible that I did set it and forgot about it.
In any case, if you do a fresh Windows install and your time differs between Linux and Windows , this is what you should check.
It is with Windows 10 and Mint. I booted into Mint a few days ago, and when I switched back to Windows, the time was wrong.
Apparently it’s easy to fix, but I keep forgetting while I’m in Mint >.<
See my edit.
That’s really helpful, thanks :)
@Tippon @SpaceCadet you can set your system clock to UTC to fix the problem. Here’s a registry fix to tell Windows to use UTC.
https://uilton.com/kb/how-to-make-windows-store-time-in-utc/
Brilliant, thank you :)
You can also fix it by running the following command on your Linux machine:
timedatectl set-local-rtc 1 --adjust-system-clock
You could but this as an autostart script:
cat > ~/.config/autostart/adjust-time <Thank you :)
This is easily fix, especially at install, when I install Linux, I click on “keep hardware clock in local time” or something.
Just incase you’re unaware, if you’re looking to learn Linux but keep the windows until you’re familiar enough with Linux, there is a way to install Linux in windows as a container, it’s called WSL 2.0
Might be easier for you to learn with, and if you brick it then you can just wipe the container and start again, takes minutes to do
I don’t recommend wsl because it bodges the worst part of windows (windows terminal) onto linux. Also, it’s much nicer to learn in a vm where you are learning actual linux, instead of MS’ interpretation of linux.
It’s like playing with clay in a bag, versus playing with clay with your bare hands.
First the powershell is a very good terminal and some even consider it better than bash. And if you’re talking about the actual terminal emulator it also became really good with the new windows terminal(which is also open source) it bas many good features and customization options. Also wsl2 IS a VM running on hyper-v. It simply uses a custom kernel optimised for it and the cherry on top of the sunday : you can run gui apps natively (windows 11) with WSLg which uses wayland/xwayland
Power shell is ass because of its policy enforcement & its pseudo lisp / completely foreign grammar.
What good is a script that doesn’t run it’s alien commands?
Wsl is truly awful.
Why msft couldn’t have adopted bash and python, we will never know.
they’re too micro soft to acknowledge that bash is better than cmd
This is probably better than dual booting. You’re learning the command line, which is the happiness foundation needed to enjoy linux.*
And then you are ready to install Ubuntu and use Snaps… I dont know. Yes its useful but for me the use of the command line comes with time.
WSL 2.0
I appreciate this, I’ve had WSL for a little while now. It did take some getting used to and I think I’m ready to give it a try for real now
I would now say never on the same disk. A shame because many laptops only have one slot. But Windows 11 may do anything and you never know what happens after a “Windows update”
I’ve seen people talk about Windows messing up the Linux install. Have there been cases where the windows install itself was messed up after an update (or is it straight up “you never know” and anything can happen)
I only have one slot, and I’d prefer to not have to carry around a USB or external drive if I can avoid it. I’m ok with having to redo the Linux install/setup, and it might be nice practice anyway. But I definitely need to have windows running and stable for schoolwork.
When I was using windows 10 + linux mint for over the 2 years I never got a boot problem from windows update. You just need a separate EFI partition for linux boot loader.
My Partitions: Windows boot C: D: Windows recovery or some other crap Linux EFI for grub / (Root directory) Swap
I don’t bother with separate /home because I never know how much I will fill up my disk
I’ve never had an issue, outside of bios updates (see last paragraph). I’ve even booted into windows after hibernating in linux (but not the other way around, since I don’t let windows hibernate; not saying you can’t, just that I don’t), and everything was fine when i got back. I use a swap partition for hibernating, in case you’re curious.
I do try to make sure I’m watching when it reboots after a windows update (because linux is my default, so i have to select windows from the boot loader) just in case, but i’ve also fucked that up a time or two with no ill effects.
My one piece of advice is: once you get it working, take a picture of your bios settings. You may have to fix some settinga after bios updates, as they can get set back to the default values. I did not do this, and while it led to a very confusing afternoon due to my inexperience, it would have been a non-issue if I’d have taken some pictures and known to look at them.
Twice after a windows update I lost my bootloader menu and my laptop would boot straight into Windows. After the second time I just removed Windows. Some investigation revealed that “Windows does not support dual booting” which I believe translates to “we will ocationally cause issues that a beginner would struggle to fix in the hopes of them staying on Windows.” Just a theory. Separate drives for sure if you can. No idea if they still do this as it’s been years since I dual booted
They still do it (at least they did a couple months ago) and Windows even likes to erase or replace linux bootloaders when on separate drive in my experience.
Annoyed me enough to remove Windows too. I’ll never install that anywhere again
Boot with a live USB image first. Check and see if everything is working. Don’t be married to the first Linux distro you try.
That’s fair, I’ll take some time to explore them :)
On the other hand, try not to get into distro hopping hell
This is really the best advice. Dual boot via USB. Once something clicks, then look at dual booting.
USB boot is the second most fun way to learn Linux. Esp with high speed 40Gbs flash, there isn’t a ton of reason not to.
However backing up then trashing your windows environment will really teach one — it is a commitment!! But the learning will defn happen, there is no turning back after the windows partition gets scratched and GRUB enters the scene.
“Monitor scan line cfg don’t fail me now!”
“Interesting, mobo WiFi is MIA. Where did that 20’ Ethernet cable go?”
“Audio device not found. Okkkkkl”
I did this, and now I would say ‘is it really worth it?’
After a while of dual booting I realised I was never using Windows, I was only using it originally for playing Oblivion.
It’s probably good experience though, and you will learn a bit about GRUB.
I would argue instead, identify which applications you need Windows for, and then determine what is required to run those on Linux or find alternatives. And then just make the switch.
Linux is kinda simple. Everything is a file.
I went about it the other way around. I switched to linux because I was tired of windows and found alternatives to the software I was used to along the way.
The simplest and the most windows like in looks distro would be Linux mint, it’s probably better than trying Ubuntu or other distros for your first experience with Linux.
If you want a challenge then go for it but just letting you know it’s better start off with a few wins under your belt then getting freaked out by complex systems like fedora made for advanced users.
tbh I like mint, but for people that want to learn linux I think ubuntu is better.
There’s more people using it, so you get better support, and there’s other flavpurs available so things like kde and xfce are supported well right out the box
In that case you’d be better off installing and learning Debian. It’s what Linux Mint and Ubuntu are based on, as well as many other distros such as Knoppix, Raspberry Pi OS, Kali, and many more. What you learn about Debian will be transferable to many other systems.
I don’t think debian is good for first time users because:
- the downloads page 🗿
- sudo isn’t setup out of the box
- most guides refer to ubuntu 20.04/22.04
Have a think about how you want to arrange your data. While you can access windows partitions and files under Linux (and vise versa), it’s better not to be constantly be mounting your windows C drive from another OS. Plus, if you’re mid-update, or had to restart suddenly, windows will happily mark your drive as read-only.
I use 4 partitions for a dual boot. Sizes are based on a 1TB drive.
- Windows C (100GB or so, OS drive). Only mounted by Linux if I have a big problem.
- Windows D (NTFS formatted, my main storage partition. Mounted all the time by Linux. 700GB or so)
- Linux root (50GB or so, EX4 formatted)
- Linux storage (remaining space, EX4 formatted used for big programs, games, home folder)
This way, Windows OS is separate, main storage is accessible to both without tripping over permissions, linux root drive is separate from storage so reinstalling isn’t so painful if something goes very wrong.
This is probably some of the best advice here. Keep the drives (if possible, if not partitions) each OS is on separate from the other. Have a 3rd drive (or partition) as the bulk of your storage that both can see and use.
I’d also suggest reversing your plan of mainly using windows and hopping to linix when you want to and make it Linux default and windows when you have to. You’ll learn more immersing yourself in Linux that way, and you’ll find whatever issues or software that force you back to windows (if any). The other way around you’ll feel that Linux doesn’t do anything you need it to and likely spend very little time in it at all. Habits are hard to change.
Windows likes to fuck with your Linux boot loader after every feature update!
I haven’t had this happen in years, maybe it’s my config? I’m using GPT on a UEFI system (in UEFI mode), with systemd-boot.
I do remember having tons of issues back when I was using grub on an MBR system using legacy bios emulation.
None of my computers had Windows in years so I can’t really tell you but that sounds plausible to me
Only thing keeping on my disk is fusion360, so annoying to have to deal with booting into windows just to use a single piece of software.
F
The video missed one small, but very important thing: You need to disable fast boot in windows before mounting your windows partition in linux, otherwise it will get corrupted.
The reason for that is that windows doesn’t actually shut down if you tell it to by default and it leaves the drive in a dirty state. Windows itself can pick that back up and boot off of it, but linux won’t detect it. If you leave fast boot on, windows will run chkdsk on the next boot after using linux.
I found that out the hard way and got to not use my computer while it ran chkdsk on my 4TB HDD. It took 15 hours.
Turn off secure boot and just check if anyone has ever run your device with linux before. And kde plasma is a de not a distro.
You can leave on secure boot nowadays if you install and configure the sbctl package. It can use the Windows secure boot method, and you’ll have a successful dual boot deployment.
Do I need to turn it off initially and re-enable it after?
I’m a little unsure of when secure boot becomes a problem
For a distribution like Fedora, it’s usually not required to turn off secure boot. You’ll know if it’s needed when booting the install USB, as it’ll give a “security policy” (or similar) warning.
Other things of note when dual booting are Windows “Fast Boot” and “Hibernation” features, which can put hardware in a state where it is unusable from Linux. Turning those off in Windows can fix things like your network interface not working. Windows also stores the time in a different way than Linux, if you are in a non-utc timezone, setting up NTP (automatically syncing date and time) on both Windows and Linux can help.
This is solid advice.
Only thing I would add is if you use a different OS that doesn’t support secure boot during install, go ahead and disable it. After you install linux, then go through the sbctl setup, and it’ll tell you when you should re-enable secure boot.
Thank you!
For me this didnt do anything. You need to reboot, and when the screen is black, force kill by pressing the power button. Lol Windows.
There also is a specific shutdown command with some parameters to force that. You can create a .bat file on your Desktop and use that to really shutdown your PC.
Thank you!
Thats what I thought. Secure boot normally needs a distro signed by damn Microsoft. This only applies for official Ubuntu spins and Fedora. Maybe some others. But the distro can create its own secureboot entry once running, and then you can enable it again.
Good to know
kde plasma is a de not a distro
Whoops, I think what I meant was Kubuntu. I’ve been watching videos on what each thing is like and after many “GNOME vs. KDE Plasma”, that’s all I remember
edit: either that or Manjaro. Was going to try one while keeping the other in mind for when I eventually decide to start all over again
No manjaro never do it
Please avoid Manjaro. I’ve had my Manjaro install break more than any other distro. If you want something arch based, you’re better off installing Arch from scratch, using the arch install script, or using EndeavorOS. All three of these options use the normal arch repositories which are far more stable than the Manjaro ones, and also offer much better compatibility with the AUR
Oh intersting, ok good to know!
Jumping in to parrot the arch install script advice. It’s easy, has a fair amount of flexibility, and gives you a rock solid base to build on.
One other thing to mention once you’ve grown comfortable is looking into systemd-boot. I got fed up with dual boot issues and moving away from grub solved for them.
Best of luck.
Yeah, definitely would avoid. I’ve had to reinstall twice on desktop, twice on mobile due to update breakage. Mint is a great starting point. Kubuntu if you don’t mind snaps and like KDE.
Here is an alternative Piped link(s): https://piped.video/watch?v=VaIgbTOvAd0
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
Whatever you do, don’t cross the streams!
First, if you have only one HD, you’ll have to shrink your windows partition. You’ll have maybe 4 partitions already on your disk, a 100MB fat one for EFI, a 16MB one unformatted, a few GB recovery one, and a big one with windows on it, you may have more. Booting on a linux USB stick or with the gparted ISO, you’ll need to shrink your windows partition and let whatever the size you want, say 100GB, for your future linux, free.
You need to disable secure boot in your bios.
When installing linux, it will ask you for custom partitioning (it’s your first install, play with it, if you don’t like your partitions, want or not a swap, etc, you’ll redo it later!). Create a 20GB partition for / the root, create the remaining (e.g. 80GB) for your /home, these are the mount point that the installer ask in the custom partitioning screen. You will need to select the 100MB EFI partition as EFI/ESP mount point and keep it like this, no formatting for this one, just select it. Continue install, it will ask if you want to install GRUB, say yes, on ESP/EFI.
You may need to go in your BIOS and have to change the boot option to properly boot in EFI/GRUB. On my PC the BIOS boot option can bypass EFI and directly boot windows partition so I never had GRUB appearing.
