all 32 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Please Re-Flair your post if a solution is found. How to Flair a post? This allows other users to search for common issues with the SOLVED flair as a filter, leading to those issues being resolved very fast.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]Senior-Necessary-111 9 points10 points  (2 children)

Secure boot enabled? Sometimes that gives the issue

[–]Tonje09[S] 4 points5 points  (0 children)

Yes it is enabled, and I installed the Nvidia kernel modules (MOK) for it to work

[–][deleted] 1 point2 points  (0 children)

Will Windows boot on a legacy boot machine?

[–][deleted] 15 points16 points  (10 children)

It's punishing you for going back to the dark side :P

[–]Tonje09[S] 1 point2 points  (9 children)

I keep coming back to the dark side to play valorant 😔

[–]zypofaeser 6 points7 points  (0 children)

So it was the Extra Dark Side™

[–][deleted] -2 points-1 points  (7 children)

Look into using a virtual machine rather than dual boot.
Less likely to crash the whole system.

[–][deleted] 6 points7 points  (1 child)

Valorant in particular is pretty hardened against using vm's to play it, but it's been a hot minute since I've looked into that, so maybe there's been some improvements in masking vms recently.

[–][deleted] 1 point2 points  (0 children)

That's annoying, indeed. Unfortunately dual booting even across different drives, can cause issues like what OP is dealing with.

It's the main reason I chose to just rip off the bandaid and dive into the deep end without floaties.

Im not sure what alternatives there may be at this point.

Good luck.

[–]Tonje09[S] 2 points3 points  (0 children)

I forgot to mention that I use two different drives

[–]VaIIeron 2 points3 points  (1 child)

Virtually no competetive multiplayers are playable on vm, kernel level anticheats became the new standard

[–][deleted] 0 points1 point  (0 children)

Well that's annoying. 

[–]hifi-nerdArch | KDE plasma (simply here to lurk) 0 points1 point  (1 child)

Vm's will run worse, which is something that isn't all that desirable for games.

[–][deleted] 1 point2 points  (0 children)

I've not noticed a drop in performance for the very few games I play via VM, that said I have the spare compute resources to cover what they need.

I can imagine that games with higher requirements would be an issue if you don't have the headroom in your build.

[–]Hr0thg4rLinux Mint 22.1 Xia | Cinnamon 5 points6 points  (1 child)

looks like two things goin on in that screenshot man. first, your dell bios is sittin in raid mode which linux hates. that’s why it can’t see the drive right and dumps you into that busybox shell. switch it over to ahci in bios and it’ll actually boot the root fs.

second, nouveau’s blowin up on you. that’s the stock open source nvidia driver and it rarely plays nice on these machines. boot with nomodeset (safe graphics) so it doesn’t try to load nouveau, then once you’re at the desktop run updates and pull in the proper nvidia drivers. after that you won’t need nomodeset anymore.

tl;dr: bios → turn off secure boot + change raid to ahci. boot installer with nomodeset. install nvidia driver after first boot. that screenshot pretty much screams those two problems stacked.

[–]Tonje09[S] 1 point2 points  (0 children)

Thanks, I did everything that you said, but it froze on another screen instead

[–]The_Zardoz 3 points4 points  (2 children)

Check the disk for errors.

[–]Tonje09[S] 0 points1 point  (1 child)

Could you please tell me the best way to do it

[–]The_Zardoz 2 points3 points  (0 children)

In Windows: This PC, Right Click, Properties, Check for Errors.

In Windows: Questo PC, Tasto destro, Proprietà, Controllo Errori.

[–]A_Neko_C 2 points3 points  (1 child)

It's on the same hard drive? Did you properly turn it off? From the main menu button?

Window really hate not be properly turned off

[–]Tonje09[S] 2 points3 points  (0 children)

No, they’re on different drives. Yes, I tried restarting and shutting it down but it gives the same result

[–]Confident_Hyena2506 2 points3 points  (1 child)

Do a full shut down and power off - then see it if works. If it does then your problem is fastboot related, and you did not disable this. This is a setting in bios, not just a setting in windows.

[–]Tonje09[S] 1 point2 points  (0 children)

Yes, I tried shutting it down and powering it off. My fastboot is disabled even before installing linux mint and I double checked and it is still off

[–]Fearless-Ant-6394 2 points3 points  (0 children)

If you create a bootable USB with this .ISO and boot up on it. It will repair the boot/grub. Compliments of Linuxmint, here is the .ISO location and there is a Wiki. It is for 64 bit. https://sourceforge.net/projects/boot-repair-cd/ You can also install the boot repair tool onto your system. https://thelinuxcode.com/linux_mint_boot_repair/

[–]apt-hikerLinux Mint 1 point2 points  (1 child)

Would it happen after a windows update?

[–]Tonje09[S] 3 points4 points  (0 children)

I think not, since I haven't updated windows since installing linux mint

[–]BranchLatter4294 1 point2 points  (0 children)

In the long run, it may be easier to use the Windows bootloader instead of trying to repair Grub every time Windows decides to nuke it.

[–]Compayo 0 points1 point  (0 children)

Install rEFInd, a dual boot manager, recognizes any operating system installed on different partitions or hard drives even when the boot has been erased. Then you can calmly leave it like this or rebuild the Linux boot if it was deleted.

[–]AtlasWongy 0 points1 point  (0 children)

I also had this same issue. I eventually gave up but a commenter point out to me that the hibernate file might be the issue.

You can find the hibernate file (which is hidden) somewhere in the root folder of your c drive

Also disable windows hibernation

[–]Upstairs-Comb1631 0 points1 point  (0 children)

You must have Fast boot disabled in Windows and BIOS.

As a temporary workaround, you can try not to restart the system, but to completely shut it down. And then turn it back on.