If only. Usually my Manjaro partition is chill, but the moment I step foot in Windows 11, it throws a pissy fit and breaks something it shouldn’t even have access to.
If Linux just calls you a cheater, Microsoft sets you and everything you love on fire to make a point.
Windows: “Looks like your bootloader was corrupted. I went ahead and reinstall it. No need to thank me, I was just doing my job. What’s that? Grub? Nope, never heard of that guy.”
at this point I’m just going to have my hard drives externally and just have windows on one and Linux on the other and depending on which one I want to boot I connect it and disconnect the other
Recently migrated to Endeavor and have Windows for Rainbow Six Siege (anticheat isn’t setup to work with Proton). Was curious why the clock was always wrong.
Ok, at least that explains that. Thanks ^^ didn’t have to switch that often so never bothered looking for a solution. So you spared me some searching, many thanks!
The clock thing is normal. Windows doesn’t like UTC clocks with local adjustment for timezone like every sane system does it.
About the resolution issue. Did you deactivate fast boot in Windows. That’s a bullshit feature decreasing boot time by not actually shutting off. It’s some kind of hybrid standby. And it can lead to all kinds of problems, like for example not properly shutting down and releasing control over hardware. Which then leads to stuff like graphics or network cards not working properly in linux.
In my case, I got a little too confident and messed around with drivers to get stable situation to work. Oops.
But in the times windows kills something… aside from messing with my boot loader (always install windows first, then Linux), it also managed to break my wifi drivers to the point that it would blue screen my windows AND prevent Manjaro from booting (and once fixed, not connect to Internet via Wi-Fi).
If only. Usually my Manjaro partition is chill, but the moment I step foot in Windows 11, it throws a pissy fit and breaks something it shouldn’t even have access to.
If Linux just calls you a cheater, Microsoft sets you and everything you love on fire to make a point.
Windows: “Looks like your bootloader was corrupted. I went ahead and reinstall it. No need to thank me, I was just doing my job. What’s that? Grub? Nope, never heard of that guy.”
Windows: “While updating I found out that some weird thing was set as first boot priority. I fixed that by setting it to myself. You are welcome!”
Yes, precisely! Haha
at this point I’m just going to have my hard drives externally and just have windows on one and Linux on the other and depending on which one I want to boot I connect it and disconnect the other
Garuda / win11 dualboot here.
When I go back to Garuda I find my display settings out of whack. Usually 800x640 resolution and desktop image back to default.
When I go back to win11 i find the timezone changed.
So dual boot is annoying for both in my experience
https://feldspaten.org/2019/11/03/windows-10-clock-in-utc/
Amazing, thank you for the link.
Recently migrated to Endeavor and have Windows for Rainbow Six Siege (anticheat isn’t setup to work with Proton). Was curious why the clock was always wrong.
Ok, at least that explains that. Thanks ^^ didn’t have to switch that often so never bothered looking for a solution. So you spared me some searching, many thanks!
The clock thing is normal. Windows doesn’t like UTC clocks with local adjustment for timezone like every sane system does it.
About the resolution issue. Did you deactivate fast boot in Windows. That’s a bullshit feature decreasing boot time by not actually shutting off. It’s some kind of hybrid standby. And it can lead to all kinds of problems, like for example not properly shutting down and releasing control over hardware. Which then leads to stuff like graphics or network cards not working properly in linux.
Thought I had but I double checked and it turns out to be enabled. Turned it off, we’ll see if that helps, thanks.
Haha, I forgot it also broke the clock. But as others explained, it’s fixable.
Lol, I killed manjaro twice 😂 it’s just too easy for Noobs to enable AUR
In my case, I got a little too confident and messed around with drivers to get stable situation to work. Oops.
But in the times windows kills something… aside from messing with my boot loader (always install windows first, then Linux), it also managed to break my wifi drivers to the point that it would blue screen my windows AND prevent Manjaro from booting (and once fixed, not connect to Internet via Wi-Fi).
Using AUR with Manjaro is dangerous cause of their stupid and useless 2 weeks rule. I would use EndevourOS or just not using the AUR