Jump to content

I cannot remove a boot arg from one drive!?


jttraverse
 Share

3 posts in this topic

Recommended Posts

I have a weird thing happening this evening...somehow one drive seems to have a boot argument (nvda_drv=1) stuck in when it boots, but I can't find anywhere it's been enabled.

 

It just started this evening, I hadn't been using nvda_drv=1 at all before this. But I thought I'd install the latest Nvidia drivers to see if they'd work, so after installing them I checked that flag in Clover Configurator. That's the first and only time it was ever enabled. Unfortunately, the system would die and reboot, so I removed that argument in Clover Configurator. But, when I boot into the Clover menu, nvda_drv=1 is still there!

 

Fine, I removed it from the line in the Clover menu and made sure it wasn't selected anywhere else in the Clover options. But when I hit 'return' and get back to the Clover boot screen---it's back in the args line!!

 

I went so far as to unplug this drive so I only booted from the USB stick, and the Clover boot menu in the USB stick is clean--no nvda args, etc. But if I boot from this one HDD, which has Clover loaded in EFI, then I have the above problem. I even deleted the EFI data and reinstalled Clover completely...and it still comes back!

 

With the USB and HDD connected in the pc, if I boot to the USB that should be clean (as checked above) the nvda_drv=1 argument persists. It's as if it's somehow attached to the HDD now, and no matter what I boot with, nvda_drv=1 sticks into every boot option, so I can't avoid it.

 

The only way to get past it is to also add nv_disable=1...so I get to the HDD OS. But that leaves just plane jane low-res graphics, not full screen, etc. Somehow that argument is definitely sticking into the boot args--but where is it coming from and how can I get rid of it? (I reset CMOS and it's still there...so unless it's burned into the BIOS for this one particular drive...I'm stumped.)

Thanks..

 

Link to comment
Share on other sites

hello

 

if u are booting in uefi mode .. maybe is in nvram

 

to clear nvram in term

 

sudo nvram -c

 

to see what it have 

 

nvram -p

 

good hack

 

 

Thanks for the idea...in this case though I'm not using UEFI, just legacy bios.

  Whatever was happening was some how attached to the drive, and would cause that arg to be included no matter what I booted from (USB, etc.) I'd never seen anything like it. I ended up just formatting the drive and after that the arg was gone, so I reinstalled El Cap and finally have everything working.

Link to comment
Share on other sites

 Share

×
×
  • Create New...