-1

was attempting to dual boot Ubuntu on an 2006 macbook pro intel core-duo. opted instead for full metal install and completely erased Mac OS. assuming it might clear the bug. i was wrong.

i was encountering the bug

Failed to set MokListRT: 
Invalid Parameter Could not 
create MokListRT: Invalid Parameter 
Importing MOK state has failed:
import mok_state() failed: 
Invalid Parameter Continuing 
boot since secure mode is disabled

i followed the solutions i found on here but my results were not the same. i tried several different scripts and solutions but got frustrated and failed to document. will do better going forward.

nothing much to document since I only have access to GNU/GRUB command line. single line bash with every script resulting in error command not found.

once installation was complete despite the bug i restarted, removed the usb drive as prompted and waited for it to load. i got the same failed parameter. same bug. so i logged into text using c key and got the GNU/GRUB command line. or text.

tried running scripts for solutions found relative to the mentioned bug above and also tried to clear BIOS this time and to no avail. cannot access BIOS

the error is not recognizing the commands and says it doesnt exist. not sure why I'm in GRUB dealing with exe files?

for example: tried to run

sudo su *and all variations. ie -su , sudo etc

and am getting

error: cant find command 'sudo' *etc

i cant find any resources on this error and apologize if im wrong about that. I don't seem to have a functional OS to work with outside of recovery mode and GRUB

if anyone has any ideas i would love to try them.

karel
  • 122,292
  • 133
  • 301
  • 332
Atom
  • 9

1 Answers1

0

I cleared the MoKListRT bug but when I reboot holding ALT I get 2 efi drives and one of them still has the bug. what is the second EFI drive? I can't help but think there is an issue here that is in need of some guidance. the EFI drive on the left looks like a mac drive and the second one is the yellow Linux drive. they both boot Ubuntu but since booting into the first drive it's been buggy. now I'm forced to use my password which is fine just not sure why it's suddenly making the request.

Atom
  • 9