Migration path from 10.10.4 to El Capitan

[x130844]

Hi guys, what is (high level) the best way to get to El capitan without having to reinstall from scratch?
I have installed capitan no prob on another machine from scratch, no prob, but this "daily" has been running 10.10.4 very stable, It has an i7 gigabyte, UEFI, with 970GTX and Chameleon boot loader
I understand Clover now is a necessity.
Do I HAVE to go to 10.10.5 before anything else?
Do i have to convert my 10.10.4 to Clover from Chameleon and THEN do the App Store update to el capitan?

Any recommendations?
Thank you!

 

[Bob_the_Tomato]

You don't HAVE to update to 10.10.5 before upgrading to ElCap, I didn't. BUT I very much recommend getting clover working on Yosemite before using the App Store to upgrade.

Also, you must plan the video update correctly. The nVidia drivers are picky about what system you have before they install. I had to download my GTX970 El Cap drivers before the upgrade but boot without nVidia drivers before I could install them... go figure.

 

[x130844]

You don't HAVE to update to 10.10.5 before upgrading to ElCap, I didn't. BUT I very much recommend getting clover working on Yosemite before using the App Store to upgrade.

Also, you must plan the video update correctly. The nVidia drivers are picky about what system you have before they install. I had to download my GTX970 El Cap drivers before the upgrade but boot without nVidia drivers before I could install them... go figure.

Thank you very much for the help, I'm now on el capitan, clover etc, with nvidia working no prob.
the only issue is that overtime I first boot/log, it gives me an error, with trying to load some 10.4 kernel from yosemite, but lets me in, and work fine, uname -a shows Im using the correct kernel.
Trying to understand what's going on,

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 nv_disable=1 container-dmg=file:///Applications/Install%20OS%20X%20Yosemite%20Beta.app/Contents/SharedSupport/InstallESD.dmg root-dmg=file:///BaseSystem.dmg

Seen this before? not a real problemm, because I can just hit, Ok, continue, and all is well, but it is weird and annoying

 

[Bob_the_Tomato]

If you are going to continue to ask for help you must begin by following the rules and add your system build to your signature. We need info on your hardware to accurately help.]

First: How in the world did that "container-dmg=file:///Applications..." boot flag end up in your boot process? Remove it and see if it boots from the HDD and not the USB.

 

[x130844]

Thank you, and yes, I updated my profile to show my build.
I think what happened is during the update to el capitan, it rebooted and i may have selected Recover partition, which then crashed, so it rebooted, and i selected the right partition which then completed fine. but now i'm stuck with this weird boot crash when logging in el capitan.
I tried to fix the issue by removing a folder on / which i believe was called something like .IABOOTsomething
the behavior is still the same after the removal of that folder.

My question is, where is this picking this up from? my nvram? but if i clear my nvram file (or nvram -c) it comes back with the same boot option
Is it possible that my chameleon is conflicting with clover? if so, do i need to remove my chameleon?

Any help appreciated thank you!

 

[x130844]

If you are going to continue to ask for help you must begin by following the rules and add your system build to your signature. We need info on your hardware to accurately help.]

First: How in the world did that "container-dmg=file:///Applications..." boot flag end up in your boot process? Remove it and see if it boots from the HDD and not the USB.

oh i meant to say also that my clover boot flag is not showing this container-dmg, which is what allows me to boot to el capitan and have a working system.
It just that it returns a KP every time I reboot the machine and log in. I click continuum and all is well.

If my boot flag is not showing container-dmg, and if i cleaned my caches/* and use no cache, and rebuilt relinked kernel, and my current kernel is indeed 15 and not 14. and if I have removed the /.IABootxxxx Where is this getting this from still? this is weird and the fact that the system works, i'm thinking it is just a flag, or a file, or hidden partition or something?
very confused