wasureppoi Posted April 30, 2014 Author Share Posted April 30, 2014 Instead of VoodooTSCsync.kext you can use 'TSC_sync_timer=0' (case sensitive/without the quotes) in com.apple.Boot.plist I edited the com.apple.Boot.plist as follows but not sure if I have placed your parameter in the right place. I found that when I deleted the tscsync kext and used this plist I was still unable to boot standalone. ?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>Kernel Flags</key> <string></string> TSC_sync_timer=0 </dict> </plist> Link to comment Share on other sites More sharing options...
joe75 Posted April 30, 2014 Share Posted April 30, 2014 wasureppoi, i would suggest you ignore Pike R. Alphas posts and start by telling us what cpu you have and what exactly is happening with boot now. Link to comment Share on other sites More sharing options...
wasureppoi Posted April 30, 2014 Author Share Posted April 30, 2014 CPU is an Intel Core2 Duo Quad 6600 2.4 but I had this same problem with an earlier Core2 Duo. I have used CPU=1 too to no avail. Presently I am still at square one. I have 2 differently installed Mavericks dedicated drives but both will only run and load normally if selected from the menu of another drive that will boot in its own right... I will call this piggeybacking. If I try to run either drive as the default boot drive in bios then they invariably crash. This I call standalone. If I try to boot them without -f or -v then they will crash immediately. Flushiing cache or running verbose or in safe mode they will load pages and pages of kexts and amongst the numerous messages I note there is a failure to load "org.voodoo.driver.ps2contoller" but I cannot find this to delete it... Trying to use Console to inspect the various logs but whilst it is transparent in Lion seems more elusive in Mavericks. .. Link to comment Share on other sites More sharing options...
joe75 Posted April 30, 2014 Share Posted April 30, 2014 ok, at least now we can rule out any tsc problems because your cpu should not be a problem. first thing you need to understand is that your "standalone" issues are related to your boot manager and not the os. if this install boots and runs fine with just needing to be booted from another drive or chameleon install that should be enough to tell you where the problem comes from. I have very similar hardware and have had none of the problems you mention. the main difference in our setups is i use clover, although i have booted with chameleon a few times for some tests and did see the same message about SYMTAB but it passed and booted normal each time. this was explained by meklort and shouldn't be a problem that stops boot. it sounds to me like you just have some cache problems and some unknown kexts. if you used MyHack at all you can check myhack kext plugins folder and there you might have some unneeded kexts. how did you install mavericks? you can try clover on a small usb and experiment with how that will boot for you. clover does involve some setup and learning about its functions. 1 Link to comment Share on other sites More sharing options...
wasureppoi Posted April 30, 2014 Author Share Posted April 30, 2014 Thanks for bringing the boot manager into focus. On my installations which I did through a usb stick I created I found at the outset that the installation would not boot at all ie black screen.. At least running chameleon I was able to activate the partition on the Mavericks drives so that they actually came up with a menu. I guess having achieved that I then mistakenly thought my problem lay with the (to me NEW) OS. I have not used Clover or MyHack but will let you know how I go. Link to comment Share on other sites More sharing options...
wasureppoi Posted May 1, 2014 Author Share Posted May 1, 2014 ..............clover does involve some setup and learning about its functions. As you indicated a bit of a learning curve with Clover. Installed it on a Mavericks drive and rebooted as "standalone" but all that I got on the screen was as follows: "boot1: /boot 6" That message then disappeared leaving a completely black screen. I am wondering if I need to create a drive with a special fat32 partition on it to house an ESP partition. I will do as you suggested and actually create another bootable USB and use Clover with that. Mmmm.... Just installing Clover on the pertinent drives not the shortcut to take. Nevertheless my beasts are still piggeybacking. Will persevere with the boot manager though. Link to comment Share on other sites More sharing options...
wasureppoi Posted May 3, 2014 Author Share Posted May 3, 2014 I accidentally discovered that my Clover boot manager attempt did actually work. Having already created a USB using Clover I was initially disappointed to encounter that same message. In my grief and thinking what else could I do after a rather long pregnant pause the Clover menu came up. Neat. Something amiss though in the USB for although it boots up with a screen of options and running disk utility to select the target disk it procedes and takes 10 mins to complete the target disk has virtually nothing on it. The reason for this is simple as the boot USB has b....r all on it and when I try to copy essentials onto it I get the message that I cannot replace whatever ... because it is invisible. That learning curve you mentioned! Link to comment Share on other sites More sharing options...
wasureppoi Posted May 12, 2014 Author Share Posted May 12, 2014 I have tried both chameleon and clover boot managers but mavericks drive will not boot if it is selected as boot drive in bios. At least if I select my mavericks drive as the boot drive default in org.chameleon.boot.plist on Lion or Mountain Line drives in same PC it will boot every time. Guess this is where I give up. Link to comment Share on other sites More sharing options...
wasureppoi Posted May 12, 2014 Author Share Posted May 12, 2014 So many errors and references to "org.voodoo.driver.ps2controller ..etc" but the kext is not in extensions or to be found anywhere. Is the kext in the kernel? Is it possible to remove it? Anybody know? Link to comment Share on other sites More sharing options...
RehabMan Posted May 12, 2014 Share Posted May 12, 2014 So many errors and references to "org.voodoo.driver.ps2controller ..etc" but the kext is not in extensions or to be found anywhere. Is the kext in the kernel? Is it possible to remove it? Anybody know? It is not in the kernel. It is also not part of OS X. It is something you added. 1 Link to comment Share on other sites More sharing options...
wasureppoi Posted May 14, 2014 Author Share Posted May 14, 2014 I know there were days with Snow Leopard, Line and Mountain Line when the only way I seemed to be able to get use of my keyboard and mouse was selecting voodoo in the setup. Neither of the 2 USB Maverick installations I created however are CUSTOMISABLE - there is no way to select or deselect anything. How could I have added it? More importantly where is it hiding out? Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted May 14, 2014 Share Posted May 14, 2014 If you haven't installed it yourself, then it was installed by a 3rd party post installation helper tool that you used. Check for Myhack.kext or the like 1 Link to comment Share on other sites More sharing options...
wasureppoi Posted May 14, 2014 Author Share Posted May 14, 2014 Actually that thought had occurred to me after I posted. Experimenting with boot loaders may have been my undoing although my "standalone" problem was active from the outset. I will start looking for myhack.kext or the like.. Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted January 26, 2015 Share Posted January 26, 2015 Whilst I could find myself in the Chameleon svn source tree following your link I am totally at sea. It wont let me comment out anything and even if I could what would I recompile with ? Of course it won't, you cannot change the Chameleon source code before downloading it. Download it first. Install xcode and the xcode command line tools. Download the Chameleon source code (see 'how to get the code' on the site) make the edits to the source files you need to edit, run terminal, cd into the Chameleon directory and type make to compile. Binaries are in YourChameleonfolder/sym/i386. Link to comment Share on other sites More sharing options...
Recommended Posts