vampira

joined 3 months ago
[–] vampira@lemmy.eco.br 2 points 1 month ago

Will do, thanks!

[–] vampira@lemmy.eco.br 2 points 1 month ago (2 children)

Thank you for your answer. I just remembered I made some Timeshift backups before I tried to switch drivers. If I rollback to the backup will my keys be "overwritten" and I'll be able to try to switch drivers again with no consequences?

[–] vampira@lemmy.eco.br 1 points 1 month ago

Thanks for your answer. I just remembered I made some Timeshift backups before I tried to change the drivers. If I rollback to the backups will I be able to try again without any consequences?

 

Yesterday I tried to install the latest NVIDIA drivers on my Linux Mint laptop (version 21.3, Cinnamon Edition) and my Driver Manager said that, since i have Secure Boot enabled, I had to create a Mok key for my drivers so I could use them with Secure Boot. So I created a password and restarted my PC. However, I didn't know what to do in the MokManagement screen, so i turned off my PC and then turned it on again to be able to start over. After turning my PC on and off a few times to try a few different buttons thqt I ended up not understanding, I looked up a tutorial and tried to follow it. But when i clicked "Enroll MOK" this time, instead of showing "View Keys", it asked if I wanted to delete my existing keys.

What should I do to get this to work? I turned off my PC after this and switched back to the open source drivers because, again, I had no idea what to do. Did I fuck up my drivers? Can I try to redo the process to make it work? What about the extra keys I created? I'm really confused. Thanks in advance.

[–] vampira@lemmy.eco.br 1 points 1 month ago (1 children)

Thank you for your response! So I can select Continue boot, install Mint and then reenable Secure Boot after I'm done installing?

[–] vampira@lemmy.eco.br 1 points 1 month ago (3 children)

Thanks for the explanation! I disabled Secure Boot, though, so how did this still happen?

 

Update to this post. Please read it before commenting!

So I ended up following instructions I found online and disabled secure boot in my BIOS and then tried to boot Linux Mint (version 21.2, Cinnamon Edition) with UEFI OS. However, as soon as I did that, i got a "Perform MOK management" screen that said the following:

Continue boot Enroll MOK Enroll key from disk Enroll hash from disk

Can anyone tell me what this means and what I should do? Do keep in mind I'm a total newbie when it comes to Linux. Thanks in advance!

[–] vampira@lemmy.eco.br 3 points 1 month ago

Very informative, thanks!

[–] vampira@lemmy.eco.br 1 points 1 month ago

Thanks for the answer! From the other answers I got in this thread it seems it'll be safe to turn off Secure Boot, so I guess I'll do that and try to boot again.

[–] vampira@lemmy.eco.br 2 points 1 month ago (2 children)

I did select to wipe the whole drive and install. And I wish I could install it with Secure Boot enabled but it seems thr only solution is to disable it.

34
submitted 1 month ago* (last edited 1 month ago) by vampira@lemmy.eco.br to c/linux@lemmy.ml
 

To sum it all up, I was looking to completely migrate from Windows 10 to Linux Mint (version 22, Cinnamon Edition). I followed an installation tutorial on YouTube, flashed the ISO to a bootable flash drive using balenaEtcher and booted Mint in my notebook. Something went wrong during the installation though: I tried to go a few steps back to review my options, and when I tried to proceed again I was met with this error:

ubi-partman failed with exit code 10

It seems it means there was a problem with partitions (I selected the option to wipe Windows and replace it with Mint in the installer), so I quit Mint and tried to boot it again so I could redo the installation. However, when i tried to boot it again I was met with this error:

Failed to open \EFI\BOOT\mmx64.efi - Not Found Failed to load image ??: Not Found Failed to start MokManager: Not Found Something has gone seriously wrong: import_mok_state() failed: Not Found

So essentially, since my Windows 10 system was wiped, I was left without an OS. So I looked up the error and it seems it's because version 22 of Mint doesn't have MokManager (don't know how it booted the first time then, but okay), so downloaded the ISO for a different one (version 21.2, Cinnamon Edition) that does have it and flashed my flash drive with it (on a different laptop, since mine was wiped.) When I tried to boot it to my laptop, I was met with yet another error:

Verifying shim SBAT data failed: Security Policy Violation Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation

Now, it seems this will be solved by disabling Secure Boot in the BIOS. However, I'm a bit aprehensive on disabling Secure Boot, since the laptop I used to flash the OS into my bootable drive is a very, very old and unupdated machine. What are the odds of my flash drive being infected with malware that can compromise the installation if i disable Secure Boot? What should I do in this situation? Can anyone shine me some light? Any help would be appreciated, thanks!

[–] vampira@lemmy.eco.br 0 points 1 month ago (1 children)

This was very informative, thank you! One more question: what are the differences between Mint Cinnamon and Mint Xfce?

[–] vampira@lemmy.eco.br 4 points 1 month ago

Probably gonna go with regular Mint, then. Thank you!

[–] vampira@lemmy.eco.br 2 points 1 month ago

It did, thank you very much!

[–] vampira@lemmy.eco.br 6 points 1 month ago (2 children)

I was thinking about using something Debian-based since I love how reliable it is, though it seems I'll be better off installing regular Linux Mint.

 

I've been seriously looking to migrate away from Windows's grip recently and I've laid my eyes on LMDE, as it seems like a simple and stable distro (I'm a total beginner in Linux/Unix). However, I have a laptop with an NVIDIA integrated graphics card, and given NVIDIA's record, I'm worried about compatibility issues given that LMDE is Debian-based. Can anyone shine me some light on this? Thanks!

view more: next ›