Jump to content
2 posts in this topic

Recommended Posts

My HP Probook 450 G5 has developed a quirk in NVRam that has turned into a hair pulling experience! Like I have enough hair to do that...

 

Among other changes, it has permanently installed boot-args "-v keepsyms=1 debug=0x100 alcid=1.   " which attaches itself to the end of the boot-vars from config.plist.

 

I have removed all instances of nvram.plist from the boot drive's EFI partition and my Thumb Drive's EFI partition.

 

I have tried entering from Terminal:

 

sudo nvram boot-args=""


 

as well as:

sudo nvram -c

I have reset the BIOS to Factory Default and re-configured it for Hackintosh.

 

I have disassembled the computer to remove the CMOS battery and shorted its terminals. The computer did report that the onboard time was wrong.

 

Without the Hard Drive & NvMe, booting from a thumb drive (boots properly on two other HP Notebooks, Probook 640 G3 & Elitebook 850 G4) I STILL get the extra commands in the boot-args!

 

It boots Windows 10 fine, but rarely boots successfully into OS X Mojave.

 

I was thinking that I could put some symbol at the end of the arguments in config.plist to mark everything following them as comments?

 

Any ideas would be greatly appreciated!

 

Thanks!

LasVegas

 

Edit... I finally resolved the issue. While clearing the NVRam was an utter failure, entering the command:

sudo nvram boot-args=""

…seems to have solved it. I could have sworn I'd tried that previously, multiple times! That was though, before I cleared the cache as well.

 

Las Vegas

Edited by LasVegas
Resolved
  • Like 1
Link to comment
https://www.insanelymac.com/forum/topic/343405-solved-nvram-corruption/
Share on other sites

×
×
  • Create New...