Jump to content

NappyHead

Members
  • Content count

    5
  • Joined

  • Last visited

About NappyHead

  • Rank
    InsanelyMac Protégé
  1. NappyHead

    Toshiba Satellite C850 Custom

    I am also interested in the steps you took to install ML on the Toshiba laptop. I have a Satellite U505-2008 (w/ latest BIOS) and cannot even get to the main installation screen... the system hangs during boot, whether I use Chameleon or Clover (latest version of each) and no boot arguments seem to help. I've tried -v, -f, -x, npci=0x2000, npci=0x3000, GraphicsEnabler=No (also Yes), PCIRootUID=0 (also 1), Busratio=16 (this IS the correct ratio for this laptop), EthernetBuiltIn=Yes, arch=i386... and seemingly every combination of these. Any help with this would be greatly appreciated! BTW, OS X 10.6.0 loads just fine but the system hangs in the same spot upon reboot after the 10.6.8 update. Kind regards, Jack Processor and Graphics Info: Intel Core i3-330M 2.13 GHz Mobile Intel HM55 Express Chipset Intel Graphics Media Accelerator HD Memory Info: Configured with 4GB DDR3 1066MHz Wireless Info: Realtek RTL8191SE Wireless LAN adapter
  2. NappyHead

    Chameleon Boot Variables Issue...

    The boot arguements have got to be cached in a file somewhere else... Suggestions (reasonable, please) anyone?
  3. NappyHead

    Chameleon Boot Variables Issue...

    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
  4. NappyHead

    Chameleon Boot Variables Issue...

    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. 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
×