Jump to content

Chameleon Boot Variables Issue...

Chameleon Boot Loader

  • Please log in to reply
7 replies to this topic

#1
NappyHead

NappyHead

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
Greetings!

Odd issue, but I can't seem to locate the answer/solution. I manually instered the -v & -f flags on the Chameleon boot screen, and now my system always lists them there unless I manually remove them prior to booting the OS. These flags return at the next boot.

These flags are NOT in the org.chameleon.Boot.plist file, and this issue has persited through several Chameleon updates. I am using the latest version: v2.2svn r2181.

I hope this accurately describes the problem.

Thanks in advance for your help!

- Nappy

#2
k3nny

k3nny

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 553 posts
  • Gender:Male
Welcome!

You can check if they are stored inside /Library/Preferences/SystemConfiguration/com.apple.Boot.plist .

#3
nyolc8

nyolc8

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 802 posts
  • Gender:Male
  • Location:Budapest, Hungary
I think you installed fileNVRAM module which saves the boot args into a plist file in the Extra folder.
To clear the saved boot args from the nvram plist, execute this command in Terminal:
sudo nvram -d boot-args


#4
NappyHead

NappyHead

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
Thanks for the quick replies!

I first checked /Library/Preferences/SystemConfiguration/com.apple.Boot.plist ... flags not present.

I do have the fileNVRAM module, so using "sudo nvram -d boot-args" did the trick!


Thank you both so much,

Nappy

#5
NappyHead

NappyHead

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
Booted this morning and the issue is back

I typed "sudo nvram -p" to discover the boot-args were indeed listed. I then deleted the "nvram.c0571e62-023c-e111-9bc2-c8600014a311.plist" file from /Extra as well as "nvram.plist" from /. I then typed "sudo nvram -d boot-args" just to be sure.

Well, the first reboot after this methos removes the boot arguments... but they return on the next reboot.

Are there any other files where these arguments are stored / cached?

Thanks!

- Nappy

#6
nyolc8

nyolc8

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 802 posts
  • Gender:Male
  • Location:Budapest, Hungary
I don't fully understand how the nvram.UUID.plist file works because if I delete the module and the plist, then I restart the pc, the plist file gets back there...

So if you have windows on your pc, then delete the plist throught windows, and then boot into osx.
I don't know why is the boot-args gets there if you remove it...

Btw if you don't use imessage service, you can get rid of the filenvram.dylib, then this issue won't return.

#7
NappyHead

NappyHead

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts
The boot arguements have got to be cached in a file somewhere else...

Suggestions (reasonable, please) anyone?

#8
k3nny

k3nny

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 553 posts
  • Gender:Male
This should solve the issue:
http://www.insanelym...d/#entry1887472






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy