ed_co Posted September 27, 2010 Share Posted September 27, 2010 My booter is in a USB pendrive. I prefer that. I don't know if it is related with an issue that I don't know why is happenning. The problem is, when I start, and the booter comes to the menu, by default the selection is in Snow Leopard (I didn't set anything, is done by default), and if I press enter, It says doesn't boot for any problem (I don't remember now the message), and if I redo again, same behaviour occurs. But if I select another choice, and go back to that option, it works good. So, it is sound like is a question for the first time, that something is not initialize, but if I select another option and go back, it works. I am doing something bad? Cheers. Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted September 27, 2010 Share Posted September 27, 2010 Post the contents of the com.apple.Boot.plist in /Extra on your Flash Drive. Link to comment Share on other sites More sharing options...
ed_co Posted September 27, 2010 Author Share Posted September 27, 2010 Post the contents of the com.apple.Boot.plist in /Extra on your Flash Drive. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EthernetBuiltIn</key> <string>Yes</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string>arch=i386 pmVersion=20 -v</string> <key>Timeout</key> <string>1</string> </dict> </plist> Thanks. Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted September 27, 2010 Share Posted September 27, 2010 Your com.apple.Boot.plist has its entries sorted alphabetically. I realize this may sound strange but that usually means that the file is corrupt. I've make a fresh one for you with the same settings, using the plist editor that comes with Apple developer tools. The only difference is that I've replaced the timeout flag with InstantMenu=y so that you can manually select the boot device. com.apple.Boot.plist.zip Some PC BIOS sometimes annoyingly shuffle the drive order when booting from a USB drive. Therefore you cannot be sure that the default boot device will always be the same (as far as Chameleon is concerned) when you're booting from a flash drive. Besides your boot.plist being corrupt I think your problem might be some variant of that behavior. If, after a couple of reboots you can verify that your OS X harddrive is always in the same place (lucky you) then you can put your timeout value back and remove the instant menu flag. Also you might find this interesting: http://forum.voodooprojects.org/index.php/topic,351.0.html After reading you might want to update your Chameleon bootloader to a more recent version, depending on which boot flags you would like to use - such as "Hide Partition" and "Default Partition" for example. I recommend the latest version of RC5: http://www.insanelymac.com/forum/index.php?showtopic=231075 Link to comment Share on other sites More sharing options...
ed_co Posted September 28, 2010 Author Share Posted September 28, 2010 Playing around I could get the behaviour that I want, without any error. Thanks man. Now I am using C2RC5, but the problem is that I don't get the memory speed correctly. I don't know why, because is supposed to be automatic, maybe I am doing something wrong, tell me if you can help me. I've attached 4 captures, 2 with AsereBLN and another 2 with C2RC5. Thank you very much. Link to comment Share on other sites More sharing options...
3.14r2 Posted September 29, 2010 Share Posted September 29, 2010 One of the possible solutions (not the only one) is to use SMBIOS.plist with properly edited values. Read this for more info. Any Chameleon based boot loader should support that feature... Link to comment Share on other sites More sharing options...
ed_co Posted September 29, 2010 Author Share Posted September 29, 2010 I know that, thanks, but I would like to avoid it, due to the automatic processing of that. If there is an automation, should be fixed if it's not working. But thanks, I appreciate your effort. Link to comment Share on other sites More sharing options...
3.14r2 Posted September 29, 2010 Share Posted September 29, 2010 Different boot loaders detect memory differently (at least on my PC). AsereBLN reported DDR3 installed in my MB, then there are DDR2 Personally I don't trust some feature of the current boot loaders. Have you tried AnVAL4? Link to comment Share on other sites More sharing options...
ed_co Posted September 30, 2010 Author Share Posted September 30, 2010 It doesn't work properly with my new HD 5870. Cheers. Link to comment Share on other sites More sharing options...
Recommended Posts