well hard to tell either..i asked Viper Dev if he had some stuff pre-baked on boot or the likes never got an answer..i showed him my old install script incase it deletes some stuff..i examined the boot.img its all bone stock..
edit:
do you still have issues on cpufreq not sticking??
i had an extended weekend off from work and havent been by a computer much to really answer anything (besides a few minutes here and there)
the current versions of viper rom use the stock zimage from the 4.xx verizon ota, and the ramdisk is virtually stock minus a few changes for init.d and some other minor stuff...nothing that should interfere with flashing another kernel
as for our init.d scripts...they cannot/shouldnt be deleted by a kernel as some of our tweaks interfaces are set from there as well...
specifically 98checksettings which executes venom superuser and venomsoundehancer as well as venom_functions
im sorry if users of the rom are complaining about issues, but i didnt do anything different on this version of the rom that i havent done since back on sense4+ in terms of setup, and custom kernels were always fine before (aside from me not directly supporting them and their interfaces)
as for my trying the kernel and it not booting, i didnt grab a kmsg as i downloaded the kernel and flashed it while sitting around in the waiting room at a doctors office, so i wasnt near a terminal to do so...and really didnt have the time to reflash it later on to grab a log
